Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
593,039 | 17,936,666,245 | IssuesEvent | 2021-09-10 16:10:37 | assurance-maladie-digital/design-system | https://api.github.com/repos/assurance-maladie-digital/design-system | closed | Documentation de la règle de validation exactLength | low-priority | ## Description
En tant que développeur utilisant le Design System, je veux savoir comment utiliser la règle de validation [`exactLength`](https://github.com/assurance-maladie-digital/design-system/blob/dev/packages/vue-dot/src/rules/exactLength/index.ts).
| 1.0 | Documentation de la règle de validation exactLength - ## Description
En tant que développeur utilisant le Design System, je veux savoir comment utiliser la règle de validation [`exactLength`](https://github.com/assurance-maladie-digital/design-system/blob/dev/packages/vue-dot/src/rules/exactLength/index.ts).
| priority | documentation de la règle de validation exactlength description en tant que développeur utilisant le design system je veux savoir comment utiliser la règle de validation | 1 |
820,143 | 30,761,206,490 | IssuesEvent | 2023-07-29 18:22:32 | prakhartiwari0/Arito | https://api.github.com/repos/prakhartiwari0/Arito | closed | [FEATURE] Add a challenge mode | enhancement priority: Low gssoc23 | **Is your feature request related to a problem? Please describe.**
Yes, the feature request is related to improving the user experience on the mathematical quiz website. Currently, the website lacks a time-based challenge mode and an option to skip questions, which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions.
**Describe the solution you'd like**
I would like the addition of a challenge mode on the mathematical quiz website. This mode would require players to complete tasks within a specific time limit, adding an element of excitement and urgency to the gameplay. Users would be motivated to solve questions quickly and accurately, enhancing their mathematical skills under pressure.
Furthermore, I suggest implementing an option to skip questions. This feature would allow users to bypass questions they find challenging or don't know the answer to, providing a smoother and less frustrating experience. It would enable players to continue progressing through the quiz without getting stuck on a particular question.
**Additional context**
These features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities.
| 1.0 | [FEATURE] Add a challenge mode - **Is your feature request related to a problem? Please describe.**
Yes, the feature request is related to improving the user experience on the mathematical quiz website. Currently, the website lacks a time-based challenge mode and an option to skip questions, which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions.
**Describe the solution you'd like**
I would like the addition of a challenge mode on the mathematical quiz website. This mode would require players to complete tasks within a specific time limit, adding an element of excitement and urgency to the gameplay. Users would be motivated to solve questions quickly and accurately, enhancing their mathematical skills under pressure.
Furthermore, I suggest implementing an option to skip questions. This feature would allow users to bypass questions they find challenging or don't know the answer to, providing a smoother and less frustrating experience. It would enable players to continue progressing through the quiz without getting stuck on a particular question.
**Additional context**
These features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities.
| priority | add a challenge mode is your feature request related to a problem please describe yes the feature request is related to improving the user experience on the mathematical quiz website currently the website lacks a time based challenge mode and an option to skip questions which can limit user engagement and frustrate players who encounter difficult or unfamiliar questions describe the solution you d like i would like the addition of a challenge mode on the mathematical quiz website this mode would require players to complete tasks within a specific time limit adding an element of excitement and urgency to the gameplay users would be motivated to solve questions quickly and accurately enhancing their mathematical skills under pressure furthermore i suggest implementing an option to skip questions this feature would allow users to bypass questions they find challenging or don t know the answer to providing a smoother and less frustrating experience it would enable players to continue progressing through the quiz without getting stuck on a particular question additional context these features can attract a wider audience and encourage users to continue using the website to improve their mathematical abilities | 1 |
676,349 | 23,123,448,944 | IssuesEvent | 2022-07-28 01:25:22 | FEeasy404/GameUs | https://api.github.com/repos/FEeasy404/GameUs | closed | 하단탭 화면 좁아질 경우 height가 높아짐 | 🐛bug 🌿Priority: Low ⚔Fix | ## 버그 발생 설명
- 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다!
- 게시물수정' 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다!
## 할 일
- [ ] 하단탭 height 수정
## ETC
| 1.0 | 하단탭 화면 좁아질 경우 height가 높아짐 - ## 버그 발생 설명
- 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다!
- 게시물수정' 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다!
## 할 일
- [ ] 하단탭 height 수정
## ETC
| priority | 하단탭 화면 좁아질 경우 height가 높아짐 버그 발생 설명 화면이 좁아질 경우 하단탭의 height가 높아져 페이지 하단 내용을 가립니다 게시물수정 텍스트가 화면이 좁아져도 한줄로 유지되도록 하면 좋을것 같습니다 할 일 하단탭 height 수정 etc | 1 |
561,480 | 16,617,888,173 | IssuesEvent | 2021-06-02 19:16:56 | department-of-veterans-affairs/caseflow | https://api.github.com/repos/department-of-veterans-affairs/caseflow | closed | [Dogfooding Bug] Offset is displayed instead of Timezone for some cases | Priority: Low Product: caseflow-hearings Stakeholder: BVA Team: Tango 💃 Type: Bug | ## Description
An offset is displayed instead of a timezone for some timezones (e.g. "Vladivostok", which shows "+10").
## Acceptance criteria
- [ ] Ensure something friendlier than the timezone offset displays
## Background/context/resources
## Technical notes
Possibly because there is no timezone abbreviation associated with "Vladivostok"; this is an issue in both the front end (moment.js) and back end (Rails timezones). | 1.0 | [Dogfooding Bug] Offset is displayed instead of Timezone for some cases - ## Description
An offset is displayed instead of a timezone for some timezones (e.g. "Vladivostok", which shows "+10").
## Acceptance criteria
- [ ] Ensure something friendlier than the timezone offset displays
## Background/context/resources
## Technical notes
Possibly because there is no timezone abbreviation associated with "Vladivostok"; this is an issue in both the front end (moment.js) and back end (Rails timezones). | priority | offset is displayed instead of timezone for some cases description an offset is displayed instead of a timezone for some timezones e g vladivostok which shows acceptance criteria ensure something friendlier than the timezone offset displays background context resources technical notes possibly because there is no timezone abbreviation associated with vladivostok this is an issue in both the front end moment js and back end rails timezones | 1 |
539,518 | 15,790,275,629 | IssuesEvent | 2021-04-02 01:00:11 | getting-things-gnome/gtg | https://api.github.com/repos/getting-things-gnome/gtg | opened | Automatic dark mode | enhancement low-hanging-fruit priority:low | Since GTG 0.5 has a dark mode setting in the preferences, I guess I should point out that it ought to have an accompanying "Automatic" dark/night mode feature available, where the dark mode gets turned on automatically at sunset and off at sunrise. Because manually managing this is "not the user's job" (unless they _want_ to have the same theme no matter what the hour), in my opinion.
The basic/primitive way to do this would be to use the app's internal clock (since it already knows the time, using that to update the dates at midnight etc.), but the "optimal" way would be, when available on the system, to use GNOME's night mode (connecting over DBus or something?) so that it happens with the rest of the desktop and benefits from its heuristics (as it takes into account timezone/DST/seasons/etc., I think). | 1.0 | Automatic dark mode - Since GTG 0.5 has a dark mode setting in the preferences, I guess I should point out that it ought to have an accompanying "Automatic" dark/night mode feature available, where the dark mode gets turned on automatically at sunset and off at sunrise. Because manually managing this is "not the user's job" (unless they _want_ to have the same theme no matter what the hour), in my opinion.
The basic/primitive way to do this would be to use the app's internal clock (since it already knows the time, using that to update the dates at midnight etc.), but the "optimal" way would be, when available on the system, to use GNOME's night mode (connecting over DBus or something?) so that it happens with the rest of the desktop and benefits from its heuristics (as it takes into account timezone/DST/seasons/etc., I think). | priority | automatic dark mode since gtg has a dark mode setting in the preferences i guess i should point out that it ought to have an accompanying automatic dark night mode feature available where the dark mode gets turned on automatically at sunset and off at sunrise because manually managing this is not the user s job unless they want to have the same theme no matter what the hour in my opinion the basic primitive way to do this would be to use the app s internal clock since it already knows the time using that to update the dates at midnight etc but the optimal way would be when available on the system to use gnome s night mode connecting over dbus or something so that it happens with the rest of the desktop and benefits from its heuristics as it takes into account timezone dst seasons etc i think | 1 |
650,954 | 21,444,840,726 | IssuesEvent | 2022-04-25 04:26:25 | darrylsyms/fretwise-app | https://api.github.com/repos/darrylsyms/fretwise-app | closed | Excessive Height in ProfileCourses Screen Header | bug low-priority | I am unable to use `navigation.state.routeName` prop inside the `indexScreenApiHooks.setHeaderHeight` hook. This prop crashes the app immediately when the ProfileCourses Screen is opened:
```
externalCodeSetup.indexScreenApiHooks.setHeaderHeight((defaultHeaderHeight, filterType, navigation) => {
if (filterType === "courses" && navigation.state.routeName === "ProfileCourses" ) {
return 140
}
return 150;
});
```
I have tested `console.log(navigation.state.routeName)`, and the result is most certainly `ProfileCourses`:
<img width="309" alt="Capture 2022-03-06 at 19 15 07@2x" src="https://user-images.githubusercontent.com/82924984/156916935-0eda1e01-b2e5-447f-930a-139b1048de65.png">
**I can confirm that the `filterType` prop works. It is `navigation.state.routeName` that causes this problem.**
## What I'm trying to fix:
There is a large gap in the header of the ProfileCourses Screen after using the `indexScreenApiHooks.setHeaderHeight` hook. This can be easily rectified by using the `navigation.state.routeName` prop from react-navigation, but unfortunately this prop crashes the app when the ProfileCourses Screen is opened.
 | 1.0 | Excessive Height in ProfileCourses Screen Header - I am unable to use `navigation.state.routeName` prop inside the `indexScreenApiHooks.setHeaderHeight` hook. This prop crashes the app immediately when the ProfileCourses Screen is opened:
```
externalCodeSetup.indexScreenApiHooks.setHeaderHeight((defaultHeaderHeight, filterType, navigation) => {
if (filterType === "courses" && navigation.state.routeName === "ProfileCourses" ) {
return 140
}
return 150;
});
```
I have tested `console.log(navigation.state.routeName)`, and the result is most certainly `ProfileCourses`:
<img width="309" alt="Capture 2022-03-06 at 19 15 07@2x" src="https://user-images.githubusercontent.com/82924984/156916935-0eda1e01-b2e5-447f-930a-139b1048de65.png">
**I can confirm that the `filterType` prop works. It is `navigation.state.routeName` that causes this problem.**
## What I'm trying to fix:
There is a large gap in the header of the ProfileCourses Screen after using the `indexScreenApiHooks.setHeaderHeight` hook. This can be easily rectified by using the `navigation.state.routeName` prop from react-navigation, but unfortunately this prop crashes the app when the ProfileCourses Screen is opened.
 | priority | excessive height in profilecourses screen header i am unable to use navigation state routename prop inside the indexscreenapihooks setheaderheight hook this prop crashes the app immediately when the profilecourses screen is opened externalcodesetup indexscreenapihooks setheaderheight defaultheaderheight filtertype navigation if filtertype courses navigation state routename profilecourses return return i have tested console log navigation state routename and the result is most certainly profilecourses img width alt capture at src i can confirm that the filtertype prop works it is navigation state routename that causes this problem what i m trying to fix there is a large gap in the header of the profilecourses screen after using the indexscreenapihooks setheaderheight hook this can be easily rectified by using the navigation state routename prop from react navigation but unfortunately this prop crashes the app when the profilecourses screen is opened | 1 |
63,554 | 3,196,988,396 | IssuesEvent | 2015-10-01 00:15:09 | GonzaloAlvarez/gonal | https://api.github.com/repos/GonzaloAlvarez/gonal | closed | 'videoAutoplay' is defined but never used. | enhancement priority-LOW | ### [Codacy](https://www.codacy.com/app/gonzaloab/gonal/commit?cid=15481408) detected an issue:
#### Message: `'videoAutoplay' is defined but never used.`
#### Occurred on:
+ **Commit**: 5c74fa669f9f4005ea83731517f05892079a5c4a
+ **File**: [js/blog/video.js](https://github.com/GonzaloAlvarez/gonal/blob/5c74fa669f9f4005ea83731517f05892079a5c4a/js/blog/video.js)
+ **LineNum**: [9](https://github.com/GonzaloAlvarez/gonal/blob/5c74fa669f9f4005ea83731517f05892079a5c4a/js/blog/video.js#L9)
+ **Code**: `var videoAutoplay = function($) {`
#### Currently on:
+ **Commit**: 4f54b7badcafd07eec0990f41d2d927c71c01e27
+ **File**: [js/blog/video.js](https://github.com/GonzaloAlvarez/gonal/blob/4f54b7badcafd07eec0990f41d2d927c71c01e27/js/blog/video.js)
+ **LineNum**: [9](https://github.com/GonzaloAlvarez/gonal/blob/4f54b7badcafd07eec0990f41d2d927c71c01e27/js/blog/video.js#L9)
| 1.0 | 'videoAutoplay' is defined but never used. - ### [Codacy](https://www.codacy.com/app/gonzaloab/gonal/commit?cid=15481408) detected an issue:
#### Message: `'videoAutoplay' is defined but never used.`
#### Occurred on:
+ **Commit**: 5c74fa669f9f4005ea83731517f05892079a5c4a
+ **File**: [js/blog/video.js](https://github.com/GonzaloAlvarez/gonal/blob/5c74fa669f9f4005ea83731517f05892079a5c4a/js/blog/video.js)
+ **LineNum**: [9](https://github.com/GonzaloAlvarez/gonal/blob/5c74fa669f9f4005ea83731517f05892079a5c4a/js/blog/video.js#L9)
+ **Code**: `var videoAutoplay = function($) {`
#### Currently on:
+ **Commit**: 4f54b7badcafd07eec0990f41d2d927c71c01e27
+ **File**: [js/blog/video.js](https://github.com/GonzaloAlvarez/gonal/blob/4f54b7badcafd07eec0990f41d2d927c71c01e27/js/blog/video.js)
+ **LineNum**: [9](https://github.com/GonzaloAlvarez/gonal/blob/4f54b7badcafd07eec0990f41d2d927c71c01e27/js/blog/video.js#L9)
| priority | videoautoplay is defined but never used detected an issue message videoautoplay is defined but never used occurred on commit file linenum code var videoautoplay function currently on commit file linenum | 1 |
248,393 | 7,930,058,440 | IssuesEvent | 2018-07-06 17:17:01 | department-of-veterans-affairs/caseflow | https://api.github.com/repos/department-of-veterans-affairs/caseflow | closed | SyncIntakeJob is failing | In-Validation bug-medium-priority caseflow-intake sierra | The SyncIntakeJob has been failing for more than a month.
We haven't noticed it because the error has been appearing in appeals-app-alerts
- [x] Get the `SyncIntakeJob` to redirect sentry errors to `#caseflow-intake` slack channel
- [x] Determine the cause of the error and fix it. | 1.0 | SyncIntakeJob is failing - The SyncIntakeJob has been failing for more than a month.
We haven't noticed it because the error has been appearing in appeals-app-alerts
- [x] Get the `SyncIntakeJob` to redirect sentry errors to `#caseflow-intake` slack channel
- [x] Determine the cause of the error and fix it. | priority | syncintakejob is failing the syncintakejob has been failing for more than a month we haven t noticed it because the error has been appearing in appeals app alerts get the syncintakejob to redirect sentry errors to caseflow intake slack channel determine the cause of the error and fix it | 1 |
300,689 | 9,211,704,208 | IssuesEvent | 2019-03-09 17:35:46 | TTUSDC/ttuacm-website | https://api.github.com/repos/TTUSDC/ttuacm-website | closed | Use Sinon to mock the XHR in request.js | Priority: Low help wanted | Right now, we are using the environment variable to resolve with configuration instead of mocking the API call. We should be mocking the API call altogether and get rid of the `process.env.NODE_ENV` if statement | 1.0 | Use Sinon to mock the XHR in request.js - Right now, we are using the environment variable to resolve with configuration instead of mocking the API call. We should be mocking the API call altogether and get rid of the `process.env.NODE_ENV` if statement | priority | use sinon to mock the xhr in request js right now we are using the environment variable to resolve with configuration instead of mocking the api call we should be mocking the api call altogether and get rid of the process env node env if statement | 1 |
242,073 | 7,837,773,737 | IssuesEvent | 2018-06-18 07:51:04 | telerik/kendo-ui-core | https://api.github.com/repos/telerik/kendo-ui-core | opened | Chart error when using two category and two mixed-type value axes | Bug C: Chart Priority 1 SEV: Low | ### Bug report
When using a Chart with two or more category axes and two or more value axes, where the second of the axes is with `type: "log"` setting applied, results in an error:
`Uncaught TypeError: Cannot read property 'x1' of null.`
### Reproduction of the problem
The problem can be reproduced in the following Dojo:
[https://dojo.telerik.com/IBaVubOk](https://dojo.telerik.com/IBaVubOk)
A workaround for this is to provide non-zero axisCrossingValue in the first value axis:
```
"valueAxis": [
{
title: { text: "First" },
"name": "primaryValue",
"min": 95,
"max": 160,
axisCrossingValue: [1,1]
},
{
title: { text: "Second" },
"name": "secondaryValue",
"majorUnit": 10,
"type": "log",
"min": 100000,
"max": 1000000
}
]
```
### Environment
* **Kendo UI version:** 2018.2.516
Reported in: 1171308
| 1.0 | Chart error when using two category and two mixed-type value axes - ### Bug report
When using a Chart with two or more category axes and two or more value axes, where the second of the axes is with `type: "log"` setting applied, results in an error:
`Uncaught TypeError: Cannot read property 'x1' of null.`
### Reproduction of the problem
The problem can be reproduced in the following Dojo:
[https://dojo.telerik.com/IBaVubOk](https://dojo.telerik.com/IBaVubOk)
A workaround for this is to provide non-zero axisCrossingValue in the first value axis:
```
"valueAxis": [
{
title: { text: "First" },
"name": "primaryValue",
"min": 95,
"max": 160,
axisCrossingValue: [1,1]
},
{
title: { text: "Second" },
"name": "secondaryValue",
"majorUnit": 10,
"type": "log",
"min": 100000,
"max": 1000000
}
]
```
### Environment
* **Kendo UI version:** 2018.2.516
Reported in: 1171308
| priority | chart error when using two category and two mixed type value axes bug report when using a chart with two or more category axes and two or more value axes where the second of the axes is with type log setting applied results in an error uncaught typeerror cannot read property of null reproduction of the problem the problem can be reproduced in the following dojo a workaround for this is to provide non zero axiscrossingvalue in the first value axis valueaxis title text first name primaryvalue min max axiscrossingvalue title text second name secondaryvalue majorunit type log min max environment kendo ui version reported in | 1 |
293,488 | 8,996,535,953 | IssuesEvent | 2019-02-02 02:10:07 | tgsachse/lion | https://api.github.com/repos/tgsachse/lion | closed | Commands are case sensitive | Low Priority Bug | Commands are currently not being recognized as commands unless they are typed in all lowercase. | 1.0 | Commands are case sensitive - Commands are currently not being recognized as commands unless they are typed in all lowercase. | priority | commands are case sensitive commands are currently not being recognized as commands unless they are typed in all lowercase | 1 |
241,795 | 7,834,532,723 | IssuesEvent | 2018-06-16 15:13:51 | SAUSy-Lab/itinerum-trip-breaker | https://api.github.com/repos/SAUSy-Lab/itinerum-trip-breaker | closed | Timestamps are inconsistent across input and output files | low-priority | Not a major issue, but it does cause minor headaches and multiple different timestamp parsing functions. | 1.0 | Timestamps are inconsistent across input and output files - Not a major issue, but it does cause minor headaches and multiple different timestamp parsing functions. | priority | timestamps are inconsistent across input and output files not a major issue but it does cause minor headaches and multiple different timestamp parsing functions | 1 |
636,319 | 20,597,306,852 | IssuesEvent | 2022-03-05 18:06:39 | checkmarx-ltd/cx-flow | https://api.github.com/repos/checkmarx-ltd/cx-flow | closed | PDF Report | enhancement priority:low | ### Describe the problem
The CLI Plugin has an option to generate a PDF report, it would be nice to be able to generate such a report from CxFlow too.
### Proposed solution
A "bug tracker" which generates a PDF Report.
### Additional details
Can be seen at this link: [https://checkmarx.atlassian.net/wiki/spaces/SD/pages/914096139/CxSAST+CxOSA+Scan+v8.9.0](https://checkmarx.atlassian.net/wiki/spaces/SD/pages/914096139/CxSAST+CxOSA+Scan+v8.9.0)
| 1.0 | PDF Report - ### Describe the problem
The CLI Plugin has an option to generate a PDF report, it would be nice to be able to generate such a report from CxFlow too.
### Proposed solution
A "bug tracker" which generates a PDF Report.
### Additional details
Can be seen at this link: [https://checkmarx.atlassian.net/wiki/spaces/SD/pages/914096139/CxSAST+CxOSA+Scan+v8.9.0](https://checkmarx.atlassian.net/wiki/spaces/SD/pages/914096139/CxSAST+CxOSA+Scan+v8.9.0)
| priority | pdf report describe the problem the cli plugin has an option to generate a pdf report it would be nice to be able to generate such a report from cxflow too proposed solution a bug tracker which generates a pdf report additional details can be seen at this link | 1 |
295,853 | 9,101,521,107 | IssuesEvent | 2019-02-20 11:19:23 | jqwidgets/jQWidgets | https://api.github.com/repos/jqwidgets/jQWidgets | opened | jqxScheduler - the "addAppointment" method does not add appropriate appointments depending on the "Room" | low priority | Add more than one appointment from different "Rooms".
**Example:**
http://jsfiddle.net/n9ag4zmo/ | 1.0 | jqxScheduler - the "addAppointment" method does not add appropriate appointments depending on the "Room" - Add more than one appointment from different "Rooms".
**Example:**
http://jsfiddle.net/n9ag4zmo/ | priority | jqxscheduler the addappointment method does not add appropriate appointments depending on the room add more than one appointment from different rooms example | 1 |
634,260 | 20,356,922,736 | IssuesEvent | 2022-02-20 04:21:13 | 3jins/blog-renewal | https://api.github.com/repos/3jins/blog-renewal | opened | [BUG] `pino.debug` is not shown | type: bug field: backend priority: low | It's found in GitHub Action console.
To represent:
- Fix `path.logging` of `backend/config/test.yml` to `stdout`.
- Add `leaveLog('test', LogLevel.DEBUG);` anywhere. I recommend you to add `leaveLog('control group', LogLevel.INFO);` with it.
- Make a PR and see. | 1.0 | [BUG] `pino.debug` is not shown - It's found in GitHub Action console.
To represent:
- Fix `path.logging` of `backend/config/test.yml` to `stdout`.
- Add `leaveLog('test', LogLevel.DEBUG);` anywhere. I recommend you to add `leaveLog('control group', LogLevel.INFO);` with it.
- Make a PR and see. | priority | pino debug is not shown it s found in github action console to represent fix path logging of backend config test yml to stdout add leavelog test loglevel debug anywhere i recommend you to add leavelog control group loglevel info with it make a pr and see | 1 |
738,451 | 25,560,290,335 | IssuesEvent | 2022-11-30 10:15:03 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | closed | Leader line property - a line that connect the mark, icon, model or label to ground in 3D view | Priority: Low StyleEditor New Feature 3D C040-COMUNE_GE-2022-CUSTOM-SUPPORT | ## Description
<!-- A few sentences describing new feature -->
<!-- screenshot, video, or link to mockup/prototype are welcome -->
It would be interesting to add a leading line options to mark, icon, model or label style symbolizer that show the relation between the point and a position on the terrain.
Here a possible implementation found on stackexchange that use a billboard graphic to draw a line
https://gis.stackexchange.com/questions/163733/cesium-js-draw-line-binding-a-label-to-a-position
## Acceptance criteria
<!-- Describe here the list of acceptance criteria -->
- [x] evaluate the feasibility of this new property
- [x] provide implementation proposal
## Other useful information
| 1.0 | Leader line property - a line that connect the mark, icon, model or label to ground in 3D view - ## Description
<!-- A few sentences describing new feature -->
<!-- screenshot, video, or link to mockup/prototype are welcome -->
It would be interesting to add a leading line options to mark, icon, model or label style symbolizer that show the relation between the point and a position on the terrain.
Here a possible implementation found on stackexchange that use a billboard graphic to draw a line
https://gis.stackexchange.com/questions/163733/cesium-js-draw-line-binding-a-label-to-a-position
## Acceptance criteria
<!-- Describe here the list of acceptance criteria -->
- [x] evaluate the feasibility of this new property
- [x] provide implementation proposal
## Other useful information
| priority | leader line property a line that connect the mark icon model or label to ground in view description it would be interesting to add a leading line options to mark icon model or label style symbolizer that show the relation between the point and a position on the terrain here a possible implementation found on stackexchange that use a billboard graphic to draw a line acceptance criteria evaluate the feasibility of this new property provide implementation proposal other useful information | 1 |
492,569 | 14,216,011,502 | IssuesEvent | 2020-11-17 08:21:51 | rathena/rathena | https://api.github.com/repos/rathena/rathena | closed | @autotraders not displaying headgears when server resets | component:core mode:prerenewal mode:renewal priority:low type:enhancement | <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: Latest
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 20151104
<!-- Please specify the client date you used. -->
* **Server Mode**: Both
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
* Result: <!-- Describe the issue that you experienced in detail. -->
* Expected Result: Im not really sure if this is a bug. But this is about @autotrade command. When you are on autotrade command and you restart your server, the vendors will not display headgears. Thats upper lower and middle. And also it doesnt display costume. That includes the garment.
* How to Reproduce: to reproduce. Simply put 1 character to @autotrade. The character should have headgears. Then close your login, char and map server. Re open it again and wait for the autotraders to load back in. Once the trunk loaded the vendors it will not display the headgears.
* Official Information: well i thought theres something wrong with my trunk. Turns out that the latest pull from git does have the same problem.
* **Modifications that may affect results**: Nope. Im using latest git.
<!-- * Please provide any information that could influence the expected result. -->
<!-- * This can be either configurations you changed, database values you changed, or even external source modifications. -->
| 1.0 | @autotraders not displaying headgears when server resets - <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: Latest
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 20151104
<!-- Please specify the client date you used. -->
* **Server Mode**: Both
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
* Result: <!-- Describe the issue that you experienced in detail. -->
* Expected Result: Im not really sure if this is a bug. But this is about @autotrade command. When you are on autotrade command and you restart your server, the vendors will not display headgears. Thats upper lower and middle. And also it doesnt display costume. That includes the garment.
* How to Reproduce: to reproduce. Simply put 1 character to @autotrade. The character should have headgears. Then close your login, char and map server. Re open it again and wait for the autotraders to load back in. Once the trunk loaded the vendors it will not display the headgears.
* Official Information: well i thought theres something wrong with my trunk. Turns out that the latest pull from git does have the same problem.
* **Modifications that may affect results**: Nope. Im using latest git.
<!-- * Please provide any information that could influence the expected result. -->
<!-- * This can be either configurations you changed, database values you changed, or even external source modifications. -->
| priority | autotraders not displaying headgears when server resets rathena hash latest please specify the rathena on which you encountered this issue how to get your github hash cd your rathena directory git rev parse short head copy the resulting hash client date server mode both description of issue result expected result im not really sure if this is a bug but this is about autotrade command when you are on autotrade command and you restart your server the vendors will not display headgears thats upper lower and middle and also it doesnt display costume that includes the garment how to reproduce to reproduce simply put character to autotrade the character should have headgears then close your login char and map server re open it again and wait for the autotraders to load back in once the trunk loaded the vendors it will not display the headgears official information well i thought theres something wrong with my trunk turns out that the latest pull from git does have the same problem modifications that may affect results nope im using latest git | 1 |
508,008 | 14,688,236,269 | IssuesEvent | 2021-01-02 01:16:42 | blchelle/collabogreat | https://api.github.com/repos/blchelle/collabogreat | opened | Implement drag and drop functionality for the Board Stages | Priority: Low Status: Available Type: Enhancement | ## Description
Users may want to swap the positions of two stages in their workflow. Implement a drag and drop interface where the users can easily swap the position of two workflow stages. This is to be done in the ProjectBoard component
This issue does not involve any redux logic or any api logc | 1.0 | Implement drag and drop functionality for the Board Stages - ## Description
Users may want to swap the positions of two stages in their workflow. Implement a drag and drop interface where the users can easily swap the position of two workflow stages. This is to be done in the ProjectBoard component
This issue does not involve any redux logic or any api logc | priority | implement drag and drop functionality for the board stages description users may want to swap the positions of two stages in their workflow implement a drag and drop interface where the users can easily swap the position of two workflow stages this is to be done in the projectboard component this issue does not involve any redux logic or any api logc | 1 |
470,638 | 13,541,963,910 | IssuesEvent | 2020-09-16 16:36:36 | shahednasser/sbuttons | https://api.github.com/repos/shahednasser/sbuttons | opened | Add a link to submit new button ideas | Priority: Low enhancement first-timers-only good first issue help wanted up-for-grabs website | In the "How to Use" section on the website, add text at the end of it that should say something like "Do you have amazing ideas for new buttons? Submit them here." where "here" is a link that would take the person to issue #96 | 1.0 | Add a link to submit new button ideas - In the "How to Use" section on the website, add text at the end of it that should say something like "Do you have amazing ideas for new buttons? Submit them here." where "here" is a link that would take the person to issue #96 | priority | add a link to submit new button ideas in the how to use section on the website add text at the end of it that should say something like do you have amazing ideas for new buttons submit them here where here is a link that would take the person to issue | 1 |
488,983 | 14,100,014,484 | IssuesEvent | 2020-11-06 02:58:23 | hydroshare/hydroshare | https://api.github.com/repos/hydroshare/hydroshare | closed | Discovery temporal search overlapping range fails | Discover bug low priority | The temporal search functionality will find resources that have a date range completely with the specified range, but fails to find resources with date ranges that partially overlap the specified range. | 1.0 | Discovery temporal search overlapping range fails - The temporal search functionality will find resources that have a date range completely with the specified range, but fails to find resources with date ranges that partially overlap the specified range. | priority | discovery temporal search overlapping range fails the temporal search functionality will find resources that have a date range completely with the specified range but fails to find resources with date ranges that partially overlap the specified range | 1 |
4,998 | 2,570,188,102 | IssuesEvent | 2015-02-10 06:53:59 | honestbleeps/Reddit-Enhancement-Suite | https://api.github.com/repos/honestbleeps/Reddit-Enhancement-Suite | opened | Dashboard looks broken with "show custom subreddit style" reddit preference turned off | Concern-Bug-Confirmed Concern-UX Difficulty-2_Medium Priority-1_Low | solution: always load dashboard stylesheet | 1.0 | Dashboard looks broken with "show custom subreddit style" reddit preference turned off - solution: always load dashboard stylesheet | priority | dashboard looks broken with show custom subreddit style reddit preference turned off solution always load dashboard stylesheet | 1 |
488,763 | 14,086,128,151 | IssuesEvent | 2020-11-05 02:51:16 | capstone-team-c-2020-summer/development-angular | https://api.github.com/repos/capstone-team-c-2020-summer/development-angular | reopened | As an advisor, I want to create a student profile so that I can schedule an appointment with students not in the system | Low Priority | **User Story Details**
- [ ] Create entry form for new student information
- [ ] Save student info in the system for later reference
**Acceptance Criteria**
- Student info can be easily added to a profile creation form
- New profile should be added to the database so that it can be referenced in the future
**Definition of Done**
- All acceptance criteria met
**Work Hours**
- 25 | 1.0 | As an advisor, I want to create a student profile so that I can schedule an appointment with students not in the system - **User Story Details**
- [ ] Create entry form for new student information
- [ ] Save student info in the system for later reference
**Acceptance Criteria**
- Student info can be easily added to a profile creation form
- New profile should be added to the database so that it can be referenced in the future
**Definition of Done**
- All acceptance criteria met
**Work Hours**
- 25 | priority | as an advisor i want to create a student profile so that i can schedule an appointment with students not in the system user story details create entry form for new student information save student info in the system for later reference acceptance criteria student info can be easily added to a profile creation form new profile should be added to the database so that it can be referenced in the future definition of done all acceptance criteria met work hours | 1 |
313,141 | 9,557,583,584 | IssuesEvent | 2019-05-03 12:01:12 | InfiniteFlightAirportEditing/Airports | https://api.github.com/repos/InfiniteFlightAirportEditing/Airports | closed | VVDL-Lien Khuong Airport-LAM DONG-VIETNAM | Being Redone Low Priority | # Airport Name
< Lien Khuong International Airport >
# Country?
< Vietnam >
# Improvements that need to be made?
< The airport hasn’t been added >
# Are you working on this airport?
< No >
# Airport Priority? (IF Event, 10000ft+ Runway, World/US Capital, Low)
< None >
| 1.0 | VVDL-Lien Khuong Airport-LAM DONG-VIETNAM - # Airport Name
< Lien Khuong International Airport >
# Country?
< Vietnam >
# Improvements that need to be made?
< The airport hasn’t been added >
# Are you working on this airport?
< No >
# Airport Priority? (IF Event, 10000ft+ Runway, World/US Capital, Low)
< None >
| priority | vvdl lien khuong airport lam dong vietnam airport name country improvements that need to be made are you working on this airport airport priority if event runway world us capital low | 1 |
48,143 | 2,993,748,714 | IssuesEvent | 2015-07-22 07:07:38 | fpco/ide-backend | https://api.github.com/repos/fpco/ide-backend | closed | Apply patch to #8266 | Low Priority | Working with an in-place compiler on OSX gives some problems due to a bug in either ghc [(#8266)](https://ghc.haskell.org/trac/ghc/ticket/8266) or cabal. | 1.0 | Apply patch to #8266 - Working with an in-place compiler on OSX gives some problems due to a bug in either ghc [(#8266)](https://ghc.haskell.org/trac/ghc/ticket/8266) or cabal. | priority | apply patch to working with an in place compiler on osx gives some problems due to a bug in either ghc or cabal | 1 |
527,871 | 15,355,011,509 | IssuesEvent | 2021-03-01 10:32:04 | mlr-org/mlr3 | https://api.github.com/repos/mlr-org/mlr3 | closed | Error handling for non-parallelizable learners | Priority: Low Type: Enhancement | I am unsure how easy this is to do, and it may be that it requires manual checks for every learner, but it would be useful to have some sort of error handling or checks to prevent conflicting parallelisation methods. This is related to #501 and possible #542.
For example, I ran a large benchmark experiment that kept crashing without me realising, the first time because a learner was being used when OpenMP was automatically enabled by its package, the second time because the learner was interfaced via `reticulate`, which `future` specifically says cannot be parallelised.
Some ideas for how we could deal with this, in increasingly complexity:
1. Add a line in the `@details` section of docs - but people don't read this and then may not realise why the experiment never ends
2. Write manual checks for each learner to detect which `future::plan` is used - e.g. in `train`
3. Same as 2. but if conflict detected then call `future::plan("sequential")`
| 1.0 | Error handling for non-parallelizable learners - I am unsure how easy this is to do, and it may be that it requires manual checks for every learner, but it would be useful to have some sort of error handling or checks to prevent conflicting parallelisation methods. This is related to #501 and possible #542.
For example, I ran a large benchmark experiment that kept crashing without me realising, the first time because a learner was being used when OpenMP was automatically enabled by its package, the second time because the learner was interfaced via `reticulate`, which `future` specifically says cannot be parallelised.
Some ideas for how we could deal with this, in increasingly complexity:
1. Add a line in the `@details` section of docs - but people don't read this and then may not realise why the experiment never ends
2. Write manual checks for each learner to detect which `future::plan` is used - e.g. in `train`
3. Same as 2. but if conflict detected then call `future::plan("sequential")`
| priority | error handling for non parallelizable learners i am unsure how easy this is to do and it may be that it requires manual checks for every learner but it would be useful to have some sort of error handling or checks to prevent conflicting parallelisation methods this is related to and possible for example i ran a large benchmark experiment that kept crashing without me realising the first time because a learner was being used when openmp was automatically enabled by its package the second time because the learner was interfaced via reticulate which future specifically says cannot be parallelised some ideas for how we could deal with this in increasingly complexity add a line in the details section of docs but people don t read this and then may not realise why the experiment never ends write manual checks for each learner to detect which future plan is used e g in train same as but if conflict detected then call future plan sequential | 1 |
579,165 | 17,174,068,572 | IssuesEvent | 2021-07-15 09:12:43 | woocommerce/woocommerce-android | https://api.github.com/repos/woocommerce/woocommerce-android | closed | Shipping label refunds will not work if the order contains a total product decimal quantity of less than one | feature: shipping labels priority: low type: bug | Steps to reproduce:
1. Plugin requirements: [WooCommerce Shipping & Tax](https://wordpress.org/plugins/woocommerce-services/) and [WPC Product Quantity for WooCommerce](https://wordpress.org/plugins/wpc-product-quantity/).
1. Go to WP Admin > WPClever > Product Quantity, change Decimal Quantities to Yes, add a Minimum and a Step of 0.5.
1. Submit an order that contains a decimal quantity of less than one, such as 0.5.
1. In the app, purchase a shipping label for the order from the previous step.
1. Try to get a refund for the shipping label.
**Result:** refunding a shipping label if the total product quantity for an order is less than one will fail with a notice that says to try again. Trying again will not help though because the WooCommerce Shipping & Tax plugin only supports refunding by whole item quantities (internal reference: p5T066-2uV-p2#comment-9152).
> Something went wrong with the refund. Please try again
Decimal quantity >1|Should this be eligible for refund?|Refund request fails, <br>trying again will never work
---|---|---
<img src="https://user-images.githubusercontent.com/1119271/125717079-33f3334e-fd2d-4d4e-86fb-6fe3d605a0ba.png" width="270" alt="Screenshot_20210714-193825">|<img src="https://user-images.githubusercontent.com/1119271/125716759-7d16ba89-6c13-4d10-ab5e-cf88915b4744.png" width="270" alt="Screenshot_20210714-193653">|<img src="https://user-images.githubusercontent.com/1119271/125716756-e5c9971d-396e-4be9-8f61-486c34d295d3.png" width="270" alt="Screenshot_20210714-193714">
**Note:** I understand this may be quite an edge case, and I am comfortable either closing this issue as wontfix or keeping it open just long enough to see if any user reports reach us mentioning it as a point of confusion. | 1.0 | Shipping label refunds will not work if the order contains a total product decimal quantity of less than one - Steps to reproduce:
1. Plugin requirements: [WooCommerce Shipping & Tax](https://wordpress.org/plugins/woocommerce-services/) and [WPC Product Quantity for WooCommerce](https://wordpress.org/plugins/wpc-product-quantity/).
1. Go to WP Admin > WPClever > Product Quantity, change Decimal Quantities to Yes, add a Minimum and a Step of 0.5.
1. Submit an order that contains a decimal quantity of less than one, such as 0.5.
1. In the app, purchase a shipping label for the order from the previous step.
1. Try to get a refund for the shipping label.
**Result:** refunding a shipping label if the total product quantity for an order is less than one will fail with a notice that says to try again. Trying again will not help though because the WooCommerce Shipping & Tax plugin only supports refunding by whole item quantities (internal reference: p5T066-2uV-p2#comment-9152).
> Something went wrong with the refund. Please try again
Decimal quantity >1|Should this be eligible for refund?|Refund request fails, <br>trying again will never work
---|---|---
<img src="https://user-images.githubusercontent.com/1119271/125717079-33f3334e-fd2d-4d4e-86fb-6fe3d605a0ba.png" width="270" alt="Screenshot_20210714-193825">|<img src="https://user-images.githubusercontent.com/1119271/125716759-7d16ba89-6c13-4d10-ab5e-cf88915b4744.png" width="270" alt="Screenshot_20210714-193653">|<img src="https://user-images.githubusercontent.com/1119271/125716756-e5c9971d-396e-4be9-8f61-486c34d295d3.png" width="270" alt="Screenshot_20210714-193714">
**Note:** I understand this may be quite an edge case, and I am comfortable either closing this issue as wontfix or keeping it open just long enough to see if any user reports reach us mentioning it as a point of confusion. | priority | shipping label refunds will not work if the order contains a total product decimal quantity of less than one steps to reproduce plugin requirements and go to wp admin wpclever product quantity change decimal quantities to yes add a minimum and a step of submit an order that contains a decimal quantity of less than one such as in the app purchase a shipping label for the order from the previous step try to get a refund for the shipping label result refunding a shipping label if the total product quantity for an order is less than one will fail with a notice that says to try again trying again will not help though because the woocommerce shipping tax plugin only supports refunding by whole item quantities internal reference comment something went wrong with the refund please try again decimal quantity should this be eligible for refund refund request fails trying again will never work note i understand this may be quite an edge case and i am comfortable either closing this issue as wontfix or keeping it open just long enough to see if any user reports reach us mentioning it as a point of confusion | 1 |
163,298 | 6,195,909,744 | IssuesEvent | 2017-07-05 13:42:35 | DDMAL/Neon.js | https://api.github.com/repos/DDMAL/Neon.js | closed | Change the alert for merge systems | Bug Low Priority | Make it for clear that there needs to be a clef on the system if they're both empty. | 1.0 | Change the alert for merge systems - Make it for clear that there needs to be a clef on the system if they're both empty. | priority | change the alert for merge systems make it for clear that there needs to be a clef on the system if they re both empty | 1 |
393,215 | 11,611,928,172 | IssuesEvent | 2020-02-26 07:52:26 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | Introspection data providers must be OOTB enabled | Affected/5.8.0-Alpha2 Complexity/Low Component/Migration Component/UMA Priority/High Severity/Major | To inject UMA permissions to introspect response, the following PR introduced "Introspection DataProvider" concept.
https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/1009
In order to use this, the following configuration should be present in identity.xml
```
<Introspection>
<EnableDataProviders>true</EnableDataProviders>
</Introspection>
```
This configuration should be OOTB available in the identity.xml rather having someone to manually modify the identity.xml...
**Without this, UMA flow breaks when the resource server introspects the RPT.**
Ex:
Introspection response without above configuration:
```
{
"nbf": 1553411123,
"active": true,
"token_type": "Bearer",
"exp": 1553414723,
"iat": 1553411123,
"client_id": "JfTSiJ24gh8sYHTQVuOl5RoftkAa",
"username": "oliver.uma.demo"
}
```
Introspection response with above configuration:
```
{
"nbf": 1553414959,
"permissions": [
{
"resource_scopes": [
"view"
],
"resource_id": "08e69621-e418-4914-b85f-164e127c20de"
}
],
"active": true,
"token_type": "Bearer",
"exp": 1553418559,
"iat": 1553414959,
"client_id": "JfTSiJ24gh8sYHTQVuOl5RoftkAa",
"username": "oliver.uma.demo"
}
```
Further, (migration?) docs should mention the impact on both having the configuration and not having the configuration, and the vendor recommendation. | 1.0 | Introspection data providers must be OOTB enabled - To inject UMA permissions to introspect response, the following PR introduced "Introspection DataProvider" concept.
https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/1009
In order to use this, the following configuration should be present in identity.xml
```
<Introspection>
<EnableDataProviders>true</EnableDataProviders>
</Introspection>
```
This configuration should be OOTB available in the identity.xml rather having someone to manually modify the identity.xml...
**Without this, UMA flow breaks when the resource server introspects the RPT.**
Ex:
Introspection response without above configuration:
```
{
"nbf": 1553411123,
"active": true,
"token_type": "Bearer",
"exp": 1553414723,
"iat": 1553411123,
"client_id": "JfTSiJ24gh8sYHTQVuOl5RoftkAa",
"username": "oliver.uma.demo"
}
```
Introspection response with above configuration:
```
{
"nbf": 1553414959,
"permissions": [
{
"resource_scopes": [
"view"
],
"resource_id": "08e69621-e418-4914-b85f-164e127c20de"
}
],
"active": true,
"token_type": "Bearer",
"exp": 1553418559,
"iat": 1553414959,
"client_id": "JfTSiJ24gh8sYHTQVuOl5RoftkAa",
"username": "oliver.uma.demo"
}
```
Further, (migration?) docs should mention the impact on both having the configuration and not having the configuration, and the vendor recommendation. | priority | introspection data providers must be ootb enabled to inject uma permissions to introspect response the following pr introduced introspection dataprovider concept in order to use this the following configuration should be present in identity xml true this configuration should be ootb available in the identity xml rather having someone to manually modify the identity xml without this uma flow breaks when the resource server introspects the rpt ex introspection response without above configuration nbf active true token type bearer exp iat client id username oliver uma demo introspection response with above configuration nbf permissions resource scopes view resource id active true token type bearer exp iat client id username oliver uma demo further migration docs should mention the impact on both having the configuration and not having the configuration and the vendor recommendation | 1 |
793,111 | 27,983,087,021 | IssuesEvent | 2023-03-26 11:46:16 | AY2223S2-CS2103T-W12-1/tp | https://api.github.com/repos/AY2223S2-CS2103T-W12-1/tp | closed | Missing check for the same person in both elderly and volunteer list | type.Bug priority.High severity.Low | When adding or editing elderly, we did not check if the same person exists inside both the elderly list and volunteer list.
This causes problems in some cases such as edit person, since edit person assumes that a person is an elderly or volunteer but not both.
Let's fix the add and edit commands to check if that each person appears in at most 1 list. | 1.0 | Missing check for the same person in both elderly and volunteer list - When adding or editing elderly, we did not check if the same person exists inside both the elderly list and volunteer list.
This causes problems in some cases such as edit person, since edit person assumes that a person is an elderly or volunteer but not both.
Let's fix the add and edit commands to check if that each person appears in at most 1 list. | priority | missing check for the same person in both elderly and volunteer list when adding or editing elderly we did not check if the same person exists inside both the elderly list and volunteer list this causes problems in some cases such as edit person since edit person assumes that a person is an elderly or volunteer but not both let s fix the add and edit commands to check if that each person appears in at most list | 1 |
69,566 | 3,305,629,672 | IssuesEvent | 2015-11-04 06:42:08 | wpengine/hgv | https://api.github.com/repos/wpengine/hgv | opened | Add an ID to the private networking config to allow for easier overriding | enhancement needs-patch priority-low systems Vagrant | Came across [this gem](https://github.com/Varying-Vagrant-Vagrants/VVV/pull/781) on the VVV side of things and though HGV should just straight up copy it. *grin* | 1.0 | Add an ID to the private networking config to allow for easier overriding - Came across [this gem](https://github.com/Varying-Vagrant-Vagrants/VVV/pull/781) on the VVV side of things and though HGV should just straight up copy it. *grin* | priority | add an id to the private networking config to allow for easier overriding came across on the vvv side of things and though hgv should just straight up copy it grin | 1 |
212,181 | 7,229,132,987 | IssuesEvent | 2018-02-11 16:59:04 | taniman/profit-trailer | https://api.github.com/repos/taniman/profit-trailer | closed | "Daily Stats" in "Sales Log" | frontend low priority | It would be awesome to see daily grouped stats in "Sales Log".
I mean that each day should be separated from the previouse one with a row, which contains something like this:
December 1 ---- Trades: 34; BTC amount traded: 0.4012940; Average profit: 1.45% Median profit: 1.2%; 0.05% more profit than all log | 1.0 | "Daily Stats" in "Sales Log" - It would be awesome to see daily grouped stats in "Sales Log".
I mean that each day should be separated from the previouse one with a row, which contains something like this:
December 1 ---- Trades: 34; BTC amount traded: 0.4012940; Average profit: 1.45% Median profit: 1.2%; 0.05% more profit than all log | priority | daily stats in sales log it would be awesome to see daily grouped stats in sales log i mean that each day should be separated from the previouse one with a row which contains something like this december trades btc amount traded average profit median profit more profit than all log | 1 |
480,989 | 13,878,960,906 | IssuesEvent | 2020-10-17 12:16:12 | sButtons/sbuttons | https://api.github.com/repos/sButtons/sbuttons | closed | Gradient | Priority: Low button-idea buttons enhancement | **Hover effect using gradient.**
**In this the gradient of button will change when hovered over it**
**I would like to work on it**
| 1.0 | Gradient - **Hover effect using gradient.**
**In this the gradient of button will change when hovered over it**
**I would like to work on it**
| priority | gradient hover effect using gradient in this the gradient of button will change when hovered over it i would like to work on it | 1 |
707,363 | 24,303,384,768 | IssuesEvent | 2022-09-29 15:24:22 | FC-final-project-team7/FinalProject-BE | https://api.github.com/repos/FC-final-project-team7/FinalProject-BE | closed | 프로젝트 텍스트 자동 저장 | Type: enhacement Priority: Low status: In progress | ## 설명
- 텍스트를 통해서 프로젝트를 만들 때 텍스트를 자동 저장하는 기능
## 해야할 일
- [x] Project 텍스트 업데이트
## 참고
| 1.0 | 프로젝트 텍스트 자동 저장 - ## 설명
- 텍스트를 통해서 프로젝트를 만들 때 텍스트를 자동 저장하는 기능
## 해야할 일
- [x] Project 텍스트 업데이트
## 참고
| priority | 프로젝트 텍스트 자동 저장 설명 텍스트를 통해서 프로젝트를 만들 때 텍스트를 자동 저장하는 기능 해야할 일 project 텍스트 업데이트 참고 | 1 |
817,923 | 30,663,290,189 | IssuesEvent | 2023-07-25 16:22:20 | recro/ats-issues | https://api.github.com/repos/recro/ats-issues | closed | Reformat some filter selections in the grids | area/candidate priority/medium complexity/low area/application area/job | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
The formatting of the list selections on the grids should be adjusted
### Describe the solution you'd like
Candidate grid:
- When using the filters for state, clearance, highest degree and status the selections should left aligned and the the entire box should be made to fit the text.
Application grid:
- when using the filters for owner, status, contract and clin the selections should be left aligned and the entire box should be made to fit the text
Job grid:
- when using the filters for contract, clin, status, priority and published, the selections should be left aligned and the entire box should be made to fit the text
### Additional context
_No response_ | 1.0 | Reformat some filter selections in the grids - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
The formatting of the list selections on the grids should be adjusted
### Describe the solution you'd like
Candidate grid:
- When using the filters for state, clearance, highest degree and status the selections should left aligned and the the entire box should be made to fit the text.
Application grid:
- when using the filters for owner, status, contract and clin the selections should be left aligned and the entire box should be made to fit the text
Job grid:
- when using the filters for contract, clin, status, priority and published, the selections should be left aligned and the entire box should be made to fit the text
### Additional context
_No response_ | priority | reformat some filter selections in the grids is there an existing issue for this i have searched the existing issues is your feature request related to a problem please describe the problem the formatting of the list selections on the grids should be adjusted describe the solution you d like candidate grid when using the filters for state clearance highest degree and status the selections should left aligned and the the entire box should be made to fit the text application grid when using the filters for owner status contract and clin the selections should be left aligned and the entire box should be made to fit the text job grid when using the filters for contract clin status priority and published the selections should be left aligned and the entire box should be made to fit the text additional context no response | 1 |
15,020 | 2,611,054,904 | IssuesEvent | 2015-02-27 00:25:18 | alistairreilly/andors-trail | https://api.github.com/repos/alistairreilly/andors-trail | closed | Dedicated D-pad | auto-migrated Milestone-0.6.10 Priority-Low Type-Enhancement | ```
A dedicated D-pad would make movement especially on larger devices much easier.
```
Original issue reported on code.google.com by `sdeva...@gmail.com` on 21 Dec 2010 at 9:24 | 1.0 | Dedicated D-pad - ```
A dedicated D-pad would make movement especially on larger devices much easier.
```
Original issue reported on code.google.com by `sdeva...@gmail.com` on 21 Dec 2010 at 9:24 | priority | dedicated d pad a dedicated d pad would make movement especially on larger devices much easier original issue reported on code google com by sdeva gmail com on dec at | 1 |
282,779 | 8,710,388,976 | IssuesEvent | 2018-12-06 16:18:23 | Webiny/webiny-js | https://api.github.com/repos/Webiny/webiny-js | closed | Entity attribute - save linked entity only if dirty | pkg: webiny-entity priority: low tag: enhancement tag: new feature | Currently when saving main entity, linked entity will be saved if it was instantiated. Add additional checking - only save if actually something has changed in the loaded linked entity.
Implementing this would improve performance. | 1.0 | Entity attribute - save linked entity only if dirty - Currently when saving main entity, linked entity will be saved if it was instantiated. Add additional checking - only save if actually something has changed in the loaded linked entity.
Implementing this would improve performance. | priority | entity attribute save linked entity only if dirty currently when saving main entity linked entity will be saved if it was instantiated add additional checking only save if actually something has changed in the loaded linked entity implementing this would improve performance | 1 |
298,550 | 9,200,507,932 | IssuesEvent | 2019-03-07 17:13:09 | qissue-bot/QGIS | https://api.github.com/repos/qissue-bot/QGIS | closed | Run actions directly from the map canvas | Category: Map Canvas Component: Easy fix? Component: Pull Request or Patch supplied Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Feature request | ---
Author Name: **Gavin Macaulay -** (Gavin Macaulay -)
Original Redmine Issue: 119, https://issues.qgis.org/issues/119
Original Assignee: Giuseppe Sucameli
---
It would be nice to be able to run actions by clicking on the map canvas aka identify but instead getting a list of the various actions that could be run on the identified features.
| 1.0 | Run actions directly from the map canvas - ---
Author Name: **Gavin Macaulay -** (Gavin Macaulay -)
Original Redmine Issue: 119, https://issues.qgis.org/issues/119
Original Assignee: Giuseppe Sucameli
---
It would be nice to be able to run actions by clicking on the map canvas aka identify but instead getting a list of the various actions that could be run on the identified features.
| priority | run actions directly from the map canvas author name gavin macaulay gavin macaulay original redmine issue original assignee giuseppe sucameli it would be nice to be able to run actions by clicking on the map canvas aka identify but instead getting a list of the various actions that could be run on the identified features | 1 |
777,702 | 27,291,473,770 | IssuesEvent | 2023-02-23 16:54:27 | department-of-veterans-affairs/abd-vro | https://api.github.com/repos/department-of-veterans-affairs/abd-vro | closed | Remove rrd_mas_disability_tracking and rrd_mas_notification feature toggles | Engineer Low-priority | **Notes about work**
- Follow-up to #576 | 1.0 | Remove rrd_mas_disability_tracking and rrd_mas_notification feature toggles - **Notes about work**
- Follow-up to #576 | priority | remove rrd mas disability tracking and rrd mas notification feature toggles notes about work follow up to | 1 |
436,765 | 12,553,399,413 | IssuesEvent | 2020-06-06 21:50:04 | space-wizards/RobustToolbox | https://api.github.com/repos/space-wizards/RobustToolbox | closed | CurTime jumps around if you modify server tick rate on a live server. | Priority: 3-low Type: Bug | This is because it's calculated purely as `ticks passed / tickrate`. Changing tickrate changes total time.
This is problematic because `CurTime` is used as an absolute time measure server side. If it were to change many things like cooldowns could get stuck or act incorrectly.
To reproduce:
1. Spawn a bike horn
2. `cvar net.tickrate 10` in the server.
3. Honk the horn
4. `cvar net.tickrate 60` in the server.
5. Your bike horn cooldown is now stuck on a huge value. | 1.0 | CurTime jumps around if you modify server tick rate on a live server. - This is because it's calculated purely as `ticks passed / tickrate`. Changing tickrate changes total time.
This is problematic because `CurTime` is used as an absolute time measure server side. If it were to change many things like cooldowns could get stuck or act incorrectly.
To reproduce:
1. Spawn a bike horn
2. `cvar net.tickrate 10` in the server.
3. Honk the horn
4. `cvar net.tickrate 60` in the server.
5. Your bike horn cooldown is now stuck on a huge value. | priority | curtime jumps around if you modify server tick rate on a live server this is because it s calculated purely as ticks passed tickrate changing tickrate changes total time this is problematic because curtime is used as an absolute time measure server side if it were to change many things like cooldowns could get stuck or act incorrectly to reproduce spawn a bike horn cvar net tickrate in the server honk the horn cvar net tickrate in the server your bike horn cooldown is now stuck on a huge value | 1 |
674,232 | 23,043,672,978 | IssuesEvent | 2022-07-23 14:56:28 | amplication/amplication | https://api.github.com/repos/amplication/amplication | closed | Client: Search bar position | type: bug type: style priority: low | **Describe the bug**
The search bar should be next to the page title and not aligned to the right.
**To Reproduce**
Please change the order of the HTML elements to:
And delete the 'search-field' alignment left.
**Screenshots**
See below how it should be:
| 1.0 | Client: Search bar position - **Describe the bug**
The search bar should be next to the page title and not aligned to the right.
**To Reproduce**
Please change the order of the HTML elements to:
And delete the 'search-field' alignment left.
**Screenshots**
See below how it should be:
| priority | client search bar position describe the bug the search bar should be next to the page title and not aligned to the right to reproduce please change the order of the html elements to and delete the search field alignment left screenshots see below how it should be | 1 |
420,171 | 12,234,150,383 | IssuesEvent | 2020-05-04 12:57:52 | CDH-Studio/UpSkill | https://api.github.com/repos/CDH-Studio/UpSkill | opened | Add descriptions to "Extra Info" icons on Edit profile components | Low Priority UI | - Extra Info icons at:
- Employee Data -> Temporary Role
- Language Proficiency -> I have been graded...
- Talent -> Competencies, Skills, I am Available to Mentor, Mentorship Skills
- Personal Growth Interests -> Developmental Goals, Willing to Relocate to
Each icon should have a french/english (language dependant on toggle in nav bar) description about the component or feature it is next to.
| 1.0 | Add descriptions to "Extra Info" icons on Edit profile components - - Extra Info icons at:
- Employee Data -> Temporary Role
- Language Proficiency -> I have been graded...
- Talent -> Competencies, Skills, I am Available to Mentor, Mentorship Skills
- Personal Growth Interests -> Developmental Goals, Willing to Relocate to
Each icon should have a french/english (language dependant on toggle in nav bar) description about the component or feature it is next to.
| priority | add descriptions to extra info icons on edit profile components extra info icons at employee data temporary role language proficiency i have been graded talent competencies skills i am available to mentor mentorship skills personal growth interests developmental goals willing to relocate to each icon should have a french english language dependant on toggle in nav bar description about the component or feature it is next to | 1 |
308,978 | 9,459,726,630 | IssuesEvent | 2019-04-17 09:12:53 | WoWManiaUK/Blackwing-Lair | https://api.github.com/repos/WoWManiaUK/Blackwing-Lair | closed | [NPC] Innkeeper Nufa <Innkeeper>-46642- Orgrimmar | Fixed Confirmed Fixed in Dev Low Priority Major City | **Links:**
https://www.wowhead.com/npc=46642/innkeeper-nufa
**What is happening:**
- innkeep has 2 "make this inn your home"
**What should happen:**
- Only should be 1
| 1.0 | [NPC] Innkeeper Nufa <Innkeeper>-46642- Orgrimmar - **Links:**
https://www.wowhead.com/npc=46642/innkeeper-nufa
**What is happening:**
- innkeep has 2 "make this inn your home"
**What should happen:**
- Only should be 1
| priority | innkeeper nufa orgrimmar links what is happening innkeep has make this inn your home what should happen only should be | 1 |
543,392 | 15,881,057,101 | IssuesEvent | 2021-04-09 14:23:43 | AY2021S2-CS2103T-T12-4/tp | https://api.github.com/repos/AY2021S2-CS2103T-T12-4/tp | closed | [PE-D] Incomplete screenshots | priority.High severity.VeryLow type.Bug | Screenshots do not show the endpoints portion of the listing. Could be helpful to show the added endpoint + its result in the command result display for `add`/`edit` functions
<!--session: 1617429875593-dcdd67d2-97a2-4f0f-9da4-b5ab7ad08181-->
-------------
Labels: `severity.VeryLow` `type.DocumentationBug`
original: candyhy/ped#21 | 1.0 | [PE-D] Incomplete screenshots - Screenshots do not show the endpoints portion of the listing. Could be helpful to show the added endpoint + its result in the command result display for `add`/`edit` functions
<!--session: 1617429875593-dcdd67d2-97a2-4f0f-9da4-b5ab7ad08181-->
-------------
Labels: `severity.VeryLow` `type.DocumentationBug`
original: candyhy/ped#21 | priority | incomplete screenshots screenshots do not show the endpoints portion of the listing could be helpful to show the added endpoint its result in the command result display for add edit functions labels severity verylow type documentationbug original candyhy ped | 1 |
785,018 | 27,594,790,013 | IssuesEvent | 2023-03-09 05:01:10 | AY2223S2-CS2113-T12-4/tp | https://api.github.com/repos/AY2223S2-CS2113-T12-4/tp | opened | [User Story Feature] Update atomic habit | type.Story priority.Low | **User Story**
As a Computing student with a bad lifestyle, I wish to update the number of times an atomic habit has been carried out.
**Is your feature request related to a problem? Please describe.**
I do not see the progress of my new habit, over time I feel that I have not developed a new habit. Therefore, I wish to be able to track the number of times my atomic habit has been carried out to see my progress and help me to maintain the consistency of my habit.
**Describe the solution you'd like**
Users can use WellNUS++ to update the number of times a habit has been performed.
```update```
WellNUS++ will return this output
```
Here is the current accumulation of your atomic habits!
Keep up the good work and you will develop a helpful habit in no time
1. Make bed every morning - 5
2. Read for at least 30 minutes every day - 3
Select which habit to update!
```
The user will be prompted to insert the index of habit that they wish to increment
```2```
WellNUS++ will return this output
```
The following habit has been incremented! Keep up the good work!
2. Read for at least 30 minutes every day - 4
```
**Additional context**
Update command will automatically add +1 count to the number of times a habit has been performed
| 1.0 | [User Story Feature] Update atomic habit - **User Story**
As a Computing student with a bad lifestyle, I wish to update the number of times an atomic habit has been carried out.
**Is your feature request related to a problem? Please describe.**
I do not see the progress of my new habit, over time I feel that I have not developed a new habit. Therefore, I wish to be able to track the number of times my atomic habit has been carried out to see my progress and help me to maintain the consistency of my habit.
**Describe the solution you'd like**
Users can use WellNUS++ to update the number of times a habit has been performed.
```update```
WellNUS++ will return this output
```
Here is the current accumulation of your atomic habits!
Keep up the good work and you will develop a helpful habit in no time
1. Make bed every morning - 5
2. Read for at least 30 minutes every day - 3
Select which habit to update!
```
The user will be prompted to insert the index of habit that they wish to increment
```2```
WellNUS++ will return this output
```
The following habit has been incremented! Keep up the good work!
2. Read for at least 30 minutes every day - 4
```
**Additional context**
Update command will automatically add +1 count to the number of times a habit has been performed
| priority | update atomic habit user story as a computing student with a bad lifestyle i wish to update the number of times an atomic habit has been carried out is your feature request related to a problem please describe i do not see the progress of my new habit over time i feel that i have not developed a new habit therefore i wish to be able to track the number of times my atomic habit has been carried out to see my progress and help me to maintain the consistency of my habit describe the solution you d like users can use wellnus to update the number of times a habit has been performed update wellnus will return this output here is the current accumulation of your atomic habits keep up the good work and you will develop a helpful habit in no time make bed every morning read for at least minutes every day select which habit to update the user will be prompted to insert the index of habit that they wish to increment wellnus will return this output the following habit has been incremented keep up the good work read for at least minutes every day additional context update command will automatically add count to the number of times a habit has been performed | 1 |
425,432 | 12,340,151,155 | IssuesEvent | 2020-05-14 19:24:21 | wri/gfw-mapbuilder | https://api.github.com/repos/wri/gfw-mapbuilder | closed | Left Panel performance | 4.x Upgrade low priority | We need to inspect/profile left panel performance in terms of re-rendering all components inside it. Especially layer tab. We want to prevent unnecessary re-renders when we switch between tabs or toggle panel. | 1.0 | Left Panel performance - We need to inspect/profile left panel performance in terms of re-rendering all components inside it. Especially layer tab. We want to prevent unnecessary re-renders when we switch between tabs or toggle panel. | priority | left panel performance we need to inspect profile left panel performance in terms of re rendering all components inside it especially layer tab we want to prevent unnecessary re renders when we switch between tabs or toggle panel | 1 |
252,015 | 8,030,685,209 | IssuesEvent | 2018-07-27 20:38:30 | CypherpunkArmory/UserLAnd | https://api.github.com/repos/CypherpunkArmory/UserLAnd | closed | Can simplify to not use VNC? Text console is good enough. | enhancement low priority | I've used GNUroot before for similar things. I don't need a GUI to occasionally adjust the temp on a thermostat. www.TurboControl.com/userland.htm is the new page (links to old page) | 1.0 | Can simplify to not use VNC? Text console is good enough. - I've used GNUroot before for similar things. I don't need a GUI to occasionally adjust the temp on a thermostat. www.TurboControl.com/userland.htm is the new page (links to old page) | priority | can simplify to not use vnc text console is good enough i ve used gnuroot before for similar things i don t need a gui to occasionally adjust the temp on a thermostat is the new page links to old page | 1 |
467,115 | 13,441,424,852 | IssuesEvent | 2020-09-08 04:05:40 | privacy-tech-lab/optmeowt-browser-extension | https://api.github.com/repos/privacy-tech-lab/optmeowt-browser-extension | closed | Fix display of long domain names in popup | low priority | Currently the popup only displays part of long domain names (per below the domain for OptMeow, for example). Ideally, we would like to break long domain names into multiple lines. If that is not possible, maybe truncated domain names.
<img width="346" alt="Screen Shot 2020-08-15 at 11 01 41 AM" src="https://user-images.githubusercontent.com/11034003/90315104-bba1aa00-dee6-11ea-9a14-89f683a519c2.png">
| 1.0 | Fix display of long domain names in popup - Currently the popup only displays part of long domain names (per below the domain for OptMeow, for example). Ideally, we would like to break long domain names into multiple lines. If that is not possible, maybe truncated domain names.
<img width="346" alt="Screen Shot 2020-08-15 at 11 01 41 AM" src="https://user-images.githubusercontent.com/11034003/90315104-bba1aa00-dee6-11ea-9a14-89f683a519c2.png">
| priority | fix display of long domain names in popup currently the popup only displays part of long domain names per below the domain for optmeow for example ideally we would like to break long domain names into multiple lines if that is not possible maybe truncated domain names img width alt screen shot at am src | 1 |
712,303 | 24,489,926,630 | IssuesEvent | 2022-10-09 23:09:37 | raceintospace/raceintospace | https://api.github.com/repos/raceintospace/raceintospace | closed | Viewing Stand shows wrong newscast | bug Low Priority | I just started a game, and on the third turn I went back to see again what the newscast on my second turn was, but instead it showed the first newscast as being the newscast for my second turn.
| 1.0 | Viewing Stand shows wrong newscast - I just started a game, and on the third turn I went back to see again what the newscast on my second turn was, but instead it showed the first newscast as being the newscast for my second turn.
| priority | viewing stand shows wrong newscast i just started a game and on the third turn i went back to see again what the newscast on my second turn was but instead it showed the first newscast as being the newscast for my second turn | 1 |
609,197 | 18,857,137,373 | IssuesEvent | 2021-11-12 08:13:03 | ever-co/ever-gauzy | https://api.github.com/repos/ever-co/ever-gauzy | closed | Bug: Proposal Page | type: bug :bug: type: enhancement ✨ priority: low | @dokata99 We have check and fix below things for Sales -> Proposal page.
- [ ] Edit button missing on proposal listing page.
- [ ] Add/Edit proposal page should be very similar (Mannge form UI).
- [ ] Non editable things should be in box same as details proposal page.
| 1.0 | Bug: Proposal Page - @dokata99 We have check and fix below things for Sales -> Proposal page.
- [ ] Edit button missing on proposal listing page.
- [ ] Add/Edit proposal page should be very similar (Mannge form UI).
- [ ] Non editable things should be in box same as details proposal page.
| priority | bug proposal page we have check and fix below things for sales proposal page edit button missing on proposal listing page add edit proposal page should be very similar mannge form ui non editable things should be in box same as details proposal page | 1 |
718,070 | 24,703,207,457 | IssuesEvent | 2022-10-19 16:49:48 | openvk/mobile-android-legacy | https://api.github.com/repos/openvk/mobile-android-legacy | opened | Сборка №123: при запуске приложения, аккаунт не выходит в онлайн | priority:low | При каждом запуске приложения нужно выбивать аккаунт в онлайн, сейчас же такое не происходит.
И вообще, желательно добавить это в настройки клиента, чтобы пользователь сам выбирал: быть видимым на сайте или скрыть своё присутствие на сайте | 1.0 | Сборка №123: при запуске приложения, аккаунт не выходит в онлайн - При каждом запуске приложения нужно выбивать аккаунт в онлайн, сейчас же такое не происходит.
И вообще, желательно добавить это в настройки клиента, чтобы пользователь сам выбирал: быть видимым на сайте или скрыть своё присутствие на сайте | priority | сборка № при запуске приложения аккаунт не выходит в онлайн при каждом запуске приложения нужно выбивать аккаунт в онлайн сейчас же такое не происходит и вообще желательно добавить это в настройки клиента чтобы пользователь сам выбирал быть видимым на сайте или скрыть своё присутствие на сайте | 1 |
475,018 | 13,685,949,050 | IssuesEvent | 2020-09-30 07:58:36 | incognitochain/incognito-chain | https://api.github.com/repos/incognitochain/incognito-chain | closed | [transaction] defragment for pToken | Priority: Low Type: Feature | The current defragment rpc is only support PRV
```
{
"jsonrpc": "1.0",
"method": "defragmentaccount",
"params": [
{{privateKey}},
{{lessthanValue}},
{{unitFee}},
{{hasPrivacy}}
],
"id": 1
}
```
We need the same rpc that support defragment privacy Token | 1.0 | [transaction] defragment for pToken - The current defragment rpc is only support PRV
```
{
"jsonrpc": "1.0",
"method": "defragmentaccount",
"params": [
{{privateKey}},
{{lessthanValue}},
{{unitFee}},
{{hasPrivacy}}
],
"id": 1
}
```
We need the same rpc that support defragment privacy Token | priority | defragment for ptoken the current defragment rpc is only support prv jsonrpc method defragmentaccount params privatekey lessthanvalue unitfee hasprivacy id we need the same rpc that support defragment privacy token | 1 |
268,931 | 8,415,856,058 | IssuesEvent | 2018-10-13 18:54:01 | qhacks/qhacks-website | https://api.github.com/repos/qhacks/qhacks-website | opened | Give EventSchedule table a fixed height | priority: nice-to-have (low) | ## Summary
The EventSchedule component's table should not shrink when switching days
### Motivation
The way the table shrinks now prevents switching between days from looking smooth
| 1.0 | Give EventSchedule table a fixed height - ## Summary
The EventSchedule component's table should not shrink when switching days
### Motivation
The way the table shrinks now prevents switching between days from looking smooth
| priority | give eventschedule table a fixed height summary the eventschedule component s table should not shrink when switching days motivation the way the table shrinks now prevents switching between days from looking smooth | 1 |
20,337 | 2,622,843,286 | IssuesEvent | 2015-03-04 08:01:16 | max99x/pagemon-chrome-ext | https://api.github.com/repos/max99x/pagemon-chrome-ext | opened | Page Organization: Tags, Labels, Folders | auto-migrated Priority-Low Type-Enhancement | ```
Add ability to tag monitored pages/URLs and filter on tags in the options
page.
```
Original issue reported on code.google.com by `max99x` on 24 Feb 2010 at 7:10 | 1.0 | Page Organization: Tags, Labels, Folders - ```
Add ability to tag monitored pages/URLs and filter on tags in the options
page.
```
Original issue reported on code.google.com by `max99x` on 24 Feb 2010 at 7:10 | priority | page organization tags labels folders add ability to tag monitored pages urls and filter on tags in the options page original issue reported on code google com by on feb at | 1 |
71,342 | 3,355,888,061 | IssuesEvent | 2015-11-18 18:11:55 | jarz/slimtune | https://api.github.com/repos/jarz/slimtune | closed | Instrumentation Support | auto-migrated Priority-Low Type-Task | ```
SlimTune needs instrumentation support. Although this is supported by the
CLR backend, the UI currently ignores all of the data. Apart from standard
min/max/avg data, the storage engine needs to record a statistical
distribution, powered by the binning system. Need to work on a good
heuristic for bin merging as well.
```
Original issue reported on code.google.com by `promit....@gmail.com` on 10 Nov 2009 at 10:51 | 1.0 | Instrumentation Support - ```
SlimTune needs instrumentation support. Although this is supported by the
CLR backend, the UI currently ignores all of the data. Apart from standard
min/max/avg data, the storage engine needs to record a statistical
distribution, powered by the binning system. Need to work on a good
heuristic for bin merging as well.
```
Original issue reported on code.google.com by `promit....@gmail.com` on 10 Nov 2009 at 10:51 | priority | instrumentation support slimtune needs instrumentation support although this is supported by the clr backend the ui currently ignores all of the data apart from standard min max avg data the storage engine needs to record a statistical distribution powered by the binning system need to work on a good heuristic for bin merging as well original issue reported on code google com by promit gmail com on nov at | 1 |
774,445 | 27,197,069,775 | IssuesEvent | 2023-02-20 06:32:39 | KDT3-miniproject-team1/backend | https://api.github.com/repos/KDT3-miniproject-team1/backend | closed | [Feat] 검색 기능 페이징 처리 및 예외처리 | For : API Priority : Low Status : In progress Type : Feature | ## 🔨개발 할 기능
상품 정보를 10개씩 페이징 처리
## 🧩 세부 기능
해당 기능에 대한 세부 계획 작성 (ex. -[ ] 로그인 시 아이디 비번 입력 받기)
- [x] 상품 검색 예외처리
- [ ] 상품 검색 페이징 처리
## 📖 참고 사항
레퍼런스나 추가로 발생할 것으로 예상되는 이슈 작성
- 페이지네이션 Annotation 찾아보기 | 1.0 | [Feat] 검색 기능 페이징 처리 및 예외처리 - ## 🔨개발 할 기능
상품 정보를 10개씩 페이징 처리
## 🧩 세부 기능
해당 기능에 대한 세부 계획 작성 (ex. -[ ] 로그인 시 아이디 비번 입력 받기)
- [x] 상품 검색 예외처리
- [ ] 상품 검색 페이징 처리
## 📖 참고 사항
레퍼런스나 추가로 발생할 것으로 예상되는 이슈 작성
- 페이지네이션 Annotation 찾아보기 | priority | 검색 기능 페이징 처리 및 예외처리 🔨개발 할 기능 상품 정보를 페이징 처리 🧩 세부 기능 해당 기능에 대한 세부 계획 작성 ex 로그인 시 아이디 비번 입력 받기 상품 검색 예외처리 상품 검색 페이징 처리 📖 참고 사항 레퍼런스나 추가로 발생할 것으로 예상되는 이슈 작성 페이지네이션 annotation 찾아보기 | 1 |
298,726 | 9,200,713,052 | IssuesEvent | 2019-03-07 17:43:36 | qissue-bot/QGIS | https://api.github.com/repos/qissue-bot/QGIS | closed | Polygon & multipolygon shape file crashes qgis | Category: Vectors Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report | ---
Author Name: **creeping -** (creeping -)
Original Redmine Issue: 283, https://issues.qgis.org/issues/283
Original Assignee: Gary Sherman
---
win32 preview 2 crashes when shape vector file is loaded. See attached file.
| 1.0 | Polygon & multipolygon shape file crashes qgis - ---
Author Name: **creeping -** (creeping -)
Original Redmine Issue: 283, https://issues.qgis.org/issues/283
Original Assignee: Gary Sherman
---
win32 preview 2 crashes when shape vector file is loaded. See attached file.
| priority | polygon multipolygon shape file crashes qgis author name creeping creeping original redmine issue original assignee gary sherman preview crashes when shape vector file is loaded see attached file | 1 |
619,865 | 19,538,122,629 | IssuesEvent | 2021-12-31 12:38:38 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | opened | Genderfluid Sayaad | suggestion :question: priority low :grey_exclamation: | <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
As a demon of lust, sayaadi could have a decision to change their sex to best suit the desires of their master/prey. In lore they seems to be genderfluid.
| 1.0 | Genderfluid Sayaad - <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
As a demon of lust, sayaadi could have a decision to change their sex to best suit the desires of their master/prey. In lore they seems to be genderfluid.
| priority | genderfluid sayaad do not remove pre existing lines describe your suggestion in full detail below as a demon of lust sayaadi could have a decision to change their sex to best suit the desires of their master prey in lore they seems to be genderfluid | 1 |
299,162 | 9,205,177,073 | IssuesEvent | 2019-03-08 09:50:32 | qissue-bot/QGIS | https://api.github.com/repos/qissue-bot/QGIS | closed | Crash when opening .tif when projection is on | Category: Projection Support Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report | ---
Author Name: **Magnus Homann** (Magnus Homann)
Original Redmine Issue: 574, https://issues.qgis.org/issues/574
---
1) Start qgis
2) Turn on projection with default WGS84
3) Load topo.tif (see #561)
4) Out of memory abort
| 1.0 | Crash when opening .tif when projection is on - ---
Author Name: **Magnus Homann** (Magnus Homann)
Original Redmine Issue: 574, https://issues.qgis.org/issues/574
---
1) Start qgis
2) Turn on projection with default WGS84
3) Load topo.tif (see #561)
4) Out of memory abort
| priority | crash when opening tif when projection is on author name magnus homann magnus homann original redmine issue start qgis turn on projection with default load topo tif see out of memory abort | 1 |
707,855 | 24,321,727,489 | IssuesEvent | 2022-09-30 11:23:36 | dbis-uibk/relax | https://api.github.com/repos/dbis-uibk/relax | closed | [Test] Consistent capitalization on pages | low-priority task | Please make sure that capitalization is consistent across all pages. E.g., on the loading/generating/selecting dataset popup, the word "dataset" is capitalized, which should not be the case. | 1.0 | [Test] Consistent capitalization on pages - Please make sure that capitalization is consistent across all pages. E.g., on the loading/generating/selecting dataset popup, the word "dataset" is capitalized, which should not be the case. | priority | consistent capitalization on pages please make sure that capitalization is consistent across all pages e g on the loading generating selecting dataset popup the word dataset is capitalized which should not be the case | 1 |
152,302 | 5,844,031,296 | IssuesEvent | 2017-05-10 10:43:32 | jasp-stats/jasp-desktop | https://api.github.com/repos/jasp-stats/jasp-desktop | opened | Error in Descriptive correlation plot with really big and really small numbers. | Layer: R Priority 3: Low Type: Bug | ## Environment (for bugs)
<!--- Include as many relevant details about the environment you experienced the bug in -->
* JASP version: 0.8.1.1
* OS name and version: Mac Sierra
* Analysis: Descriptive
Load the debug dataset, select first contNarrow, then contWide. Click on Display correlation plot: 'This analysis terminated unexpectedly'
What strange is, if you select fist contWide, and then contNarrow, you don't get any error... | 1.0 | Error in Descriptive correlation plot with really big and really small numbers. - ## Environment (for bugs)
<!--- Include as many relevant details about the environment you experienced the bug in -->
* JASP version: 0.8.1.1
* OS name and version: Mac Sierra
* Analysis: Descriptive
Load the debug dataset, select first contNarrow, then contWide. Click on Display correlation plot: 'This analysis terminated unexpectedly'
What strange is, if you select fist contWide, and then contNarrow, you don't get any error... | priority | error in descriptive correlation plot with really big and really small numbers environment for bugs jasp version os name and version mac sierra analysis descriptive load the debug dataset select first contnarrow then contwide click on display correlation plot this analysis terminated unexpectedly what strange is if you select fist contwide and then contnarrow you don t get any error | 1 |
274,256 | 8,559,006,241 | IssuesEvent | 2018-11-08 19:56:20 | CS2113-AY1819S1-W13-2/main | https://api.github.com/repos/CS2113-AY1819S1-W13-2/main | closed | Edit commands allows for timezones that do not exist. | priority.low severity.High | **Describe the bug**
Time zones can be +500000, which is not a valid time zone
**To Reproduce**
Steps to reproduce the behavior:
edit 1 tz/500000
**Expected behavior**
Should check for valid timezone and give an error.
<hr>
**Reported by:** @andrewome
**Severity:** `Low`
<sub>[original: nusCS2113-AY1819S1/pe-1#466]</sub> | 1.0 | Edit commands allows for timezones that do not exist. - **Describe the bug**
Time zones can be +500000, which is not a valid time zone
**To Reproduce**
Steps to reproduce the behavior:
edit 1 tz/500000
**Expected behavior**
Should check for valid timezone and give an error.
<hr>
**Reported by:** @andrewome
**Severity:** `Low`
<sub>[original: nusCS2113-AY1819S1/pe-1#466]</sub> | priority | edit commands allows for timezones that do not exist describe the bug time zones can be which is not a valid time zone to reproduce steps to reproduce the behavior edit tz expected behavior should check for valid timezone and give an error reported by andrewome severity low | 1 |
366,728 | 10,825,414,234 | IssuesEvent | 2019-11-09 15:42:21 | kiwicom/schemathesis | https://api.github.com/repos/kiwicom/schemathesis | closed | Make method names case insensitive in schema mapping interface | Priority: Low Type: Enhancement good first issue | It should be equivalent:
‘’’schema[“/foo”][“get”]’’’ and ‘’’schema[“/foo”][“GET”]’’’ | 1.0 | Make method names case insensitive in schema mapping interface - It should be equivalent:
‘’’schema[“/foo”][“get”]’’’ and ‘’’schema[“/foo”][“GET”]’’’ | priority | make method names case insensitive in schema mapping interface it should be equivalent ‘’’schema ’’’ and ‘’’schema ’’’ | 1 |
309,310 | 9,473,228,470 | IssuesEvent | 2019-04-19 00:44:15 | hayata-yamamoto/neural_search | https://api.github.com/repos/hayata-yamamoto/neural_search | opened | rewrite api by django | low priority | fastapi has not their original models. Firstly, this api is designed not to use database. | 1.0 | rewrite api by django - fastapi has not their original models. Firstly, this api is designed not to use database. | priority | rewrite api by django fastapi has not their original models firstly this api is designed not to use database | 1 |
715,166 | 24,588,849,336 | IssuesEvent | 2022-10-13 22:50:32 | VoltanFr/memcheck | https://api.github.com/repos/VoltanFr/memcheck | closed | Adpatative sleep time in retries | priority-medium complexity-low | Retries in the Learn page are always done after a 1 second sleep.
This sleep time should increase with retries (similarly to the computing of the timeOut). This happens in `handlePendingMoveOperations`, `downloadCardsIfNeeded`, `handlePendingNotificationRegistrations` and `handlePendingRatingOperations`.
This will save power and bandwidth.
But beware: the user is waiting, and when the train gets out of this long tunnel, he doesn't want to wait for a long time; so don't increase the sleep time too much. I'd say 10ms is a good first sleep time, and we don't want to increase it to more than 5 seconds (or maybe even less?) | 1.0 | Adpatative sleep time in retries - Retries in the Learn page are always done after a 1 second sleep.
This sleep time should increase with retries (similarly to the computing of the timeOut). This happens in `handlePendingMoveOperations`, `downloadCardsIfNeeded`, `handlePendingNotificationRegistrations` and `handlePendingRatingOperations`.
This will save power and bandwidth.
But beware: the user is waiting, and when the train gets out of this long tunnel, he doesn't want to wait for a long time; so don't increase the sleep time too much. I'd say 10ms is a good first sleep time, and we don't want to increase it to more than 5 seconds (or maybe even less?) | priority | adpatative sleep time in retries retries in the learn page are always done after a second sleep this sleep time should increase with retries similarly to the computing of the timeout this happens in handlependingmoveoperations downloadcardsifneeded handlependingnotificationregistrations and handlependingratingoperations this will save power and bandwidth but beware the user is waiting and when the train gets out of this long tunnel he doesn t want to wait for a long time so don t increase the sleep time too much i d say is a good first sleep time and we don t want to increase it to more than seconds or maybe even less | 1 |
449,546 | 12,970,491,918 | IssuesEvent | 2020-07-21 09:25:01 | elixir-cloud-aai/cwl-WES | https://api.github.com/repos/elixir-cloud-aai/cwl-WES | opened | Document logging to files | priority: low type: docs workload: hours | **Is your feature request related to a problem? Please describe.**
Currently, app and worker logs are streamed to STDERR. While this guarantees easy access to logs by devops/administrators, logs are not persisting when the service is re-deployed. It may also be harder to find and analyze logs.
**Describe the solution you'd like**
Different logging handlers can be configured via `cwl_wes/config/log_config.yaml`. Document how logging to files, as well as a [basic log rotation scheme](https://docs.python.org/3/library/logging.handlers.html#baserotatinghandler) can be configured.
**Describe alternatives you've considered**
N/A
**Additional context**
For log rotations, consider how overflowing volumes can be avoided given a configured volume size for the service. This may require code changes.
| 1.0 | Document logging to files - **Is your feature request related to a problem? Please describe.**
Currently, app and worker logs are streamed to STDERR. While this guarantees easy access to logs by devops/administrators, logs are not persisting when the service is re-deployed. It may also be harder to find and analyze logs.
**Describe the solution you'd like**
Different logging handlers can be configured via `cwl_wes/config/log_config.yaml`. Document how logging to files, as well as a [basic log rotation scheme](https://docs.python.org/3/library/logging.handlers.html#baserotatinghandler) can be configured.
**Describe alternatives you've considered**
N/A
**Additional context**
For log rotations, consider how overflowing volumes can be avoided given a configured volume size for the service. This may require code changes.
| priority | document logging to files is your feature request related to a problem please describe currently app and worker logs are streamed to stderr while this guarantees easy access to logs by devops administrators logs are not persisting when the service is re deployed it may also be harder to find and analyze logs describe the solution you d like different logging handlers can be configured via cwl wes config log config yaml document how logging to files as well as a can be configured describe alternatives you ve considered n a additional context for log rotations consider how overflowing volumes can be avoided given a configured volume size for the service this may require code changes | 1 |
299,548 | 9,205,602,770 | IssuesEvent | 2019-03-08 11:03:37 | qissue-bot/QGIS | https://api.github.com/repos/qissue-bot/QGIS | closed | identify tool: features highlited wrong when a polygon inside a polygon is presnt | Category: Vectors Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report | ---
Author Name: **Maciej Sieczka -** (Maciej Sieczka -)
Original Redmine Issue: 926, https://issues.qgis.org/issues/926
Original Assignee: Tim Sutton
---
Look at the attached screendumps.
Black arrow points at the polygon being queried.
identify_bad.png shows how it is now. This is wrong - although the smaller polygon inside is not being queried, it looks like if it was too.
identify_ok.png shows how it should look like - it is clear which polygon is queried actually.
---
- [identify_bad.png](https://issues.qgis.org/attachments/download/1989/identify_bad.png) (Maciej Sieczka -)
- [identify_ok.png](https://issues.qgis.org/attachments/download/1990/identify_ok.png) (Maciej Sieczka -)
- [Screenshot.png](https://issues.qgis.org/attachments/download/1993/Screenshot.png) (Giovanni Manghi)
- [Screenshot-1.png](https://issues.qgis.org/attachments/download/1991/Screenshot-1.png) (Giovanni Manghi)
- [Screenshot-2.png](https://issues.qgis.org/attachments/download/1992/Screenshot-2.png) (Giovanni Manghi) | 1.0 | identify tool: features highlited wrong when a polygon inside a polygon is presnt - ---
Author Name: **Maciej Sieczka -** (Maciej Sieczka -)
Original Redmine Issue: 926, https://issues.qgis.org/issues/926
Original Assignee: Tim Sutton
---
Look at the attached screendumps.
Black arrow points at the polygon being queried.
identify_bad.png shows how it is now. This is wrong - although the smaller polygon inside is not being queried, it looks like if it was too.
identify_ok.png shows how it should look like - it is clear which polygon is queried actually.
---
- [identify_bad.png](https://issues.qgis.org/attachments/download/1989/identify_bad.png) (Maciej Sieczka -)
- [identify_ok.png](https://issues.qgis.org/attachments/download/1990/identify_ok.png) (Maciej Sieczka -)
- [Screenshot.png](https://issues.qgis.org/attachments/download/1993/Screenshot.png) (Giovanni Manghi)
- [Screenshot-1.png](https://issues.qgis.org/attachments/download/1991/Screenshot-1.png) (Giovanni Manghi)
- [Screenshot-2.png](https://issues.qgis.org/attachments/download/1992/Screenshot-2.png) (Giovanni Manghi) | priority | identify tool features highlited wrong when a polygon inside a polygon is presnt author name maciej sieczka maciej sieczka original redmine issue original assignee tim sutton look at the attached screendumps black arrow points at the polygon being queried identify bad png shows how it is now this is wrong although the smaller polygon inside is not being queried it looks like if it was too identify ok png shows how it should look like it is clear which polygon is queried actually maciej sieczka maciej sieczka giovanni manghi giovanni manghi giovanni manghi | 1 |
257,278 | 8,135,276,277 | IssuesEvent | 2018-08-20 01:43:23 | BigOokie/skywire-wing-commander | https://api.github.com/repos/BigOokie/skywire-wing-commander | opened | Prevent starting multiple instances | enhancement low priority | **Is your feature request related to a problem? Please describe.**
Its currently possible for any number of instances of the Bot application (`wcbot`) to be run on the same machine - however there is no point and this has caused confusion with some users.
**Describe the solution you'd like**
The Bot (`wcbot`) should detect if another instance is already present and running on the same machine and inform the user with a helpful message. The second instance should not start.
| 1.0 | Prevent starting multiple instances - **Is your feature request related to a problem? Please describe.**
Its currently possible for any number of instances of the Bot application (`wcbot`) to be run on the same machine - however there is no point and this has caused confusion with some users.
**Describe the solution you'd like**
The Bot (`wcbot`) should detect if another instance is already present and running on the same machine and inform the user with a helpful message. The second instance should not start.
| priority | prevent starting multiple instances is your feature request related to a problem please describe its currently possible for any number of instances of the bot application wcbot to be run on the same machine however there is no point and this has caused confusion with some users describe the solution you d like the bot wcbot should detect if another instance is already present and running on the same machine and inform the user with a helpful message the second instance should not start | 1 |
383,209 | 11,352,472,305 | IssuesEvent | 2020-01-24 13:43:21 | ntop/ntopng | https://api.github.com/repos/ntop/ntopng | closed | Alert... How can I find all the hosts with a modified thresholds? | alerts enhancement low-priority bug | In the last days I modified the Alert thresholds for 15/16 internal IPs.
Now I should set the SYN flood threshold for all these IPs to another value but:
-) I don't remember which IPs I modified and in which interfaces
-) I don't remember which threshold values I set for each IP
So... What do you think to add a global page with the list of all modified IPs ad all the set thresholds? This would be useful to easily manage this kind of settings.
Thanks!
Bye bye...
PS: I'm using ntopng version "3.8.190118 - Professional Edition" | 1.0 | Alert... How can I find all the hosts with a modified thresholds? - In the last days I modified the Alert thresholds for 15/16 internal IPs.
Now I should set the SYN flood threshold for all these IPs to another value but:
-) I don't remember which IPs I modified and in which interfaces
-) I don't remember which threshold values I set for each IP
So... What do you think to add a global page with the list of all modified IPs ad all the set thresholds? This would be useful to easily manage this kind of settings.
Thanks!
Bye bye...
PS: I'm using ntopng version "3.8.190118 - Professional Edition" | priority | alert how can i find all the hosts with a modified thresholds in the last days i modified the alert thresholds for internal ips now i should set the syn flood threshold for all these ips to another value but i don t remember which ips i modified and in which interfaces i don t remember which threshold values i set for each ip so what do you think to add a global page with the list of all modified ips ad all the set thresholds this would be useful to easily manage this kind of settings thanks bye bye ps i m using ntopng version professional edition | 1 |
200,578 | 7,009,265,705 | IssuesEvent | 2017-12-19 18:29:40 | larshp/abapGit | https://api.github.com/repos/larshp/abapGit | closed | Improve usability of repository popup | low priority new feature | When we try to clone a repository and an error occurs, e.g. invalid url or non existing package, the popup is closed and then the error is displayed.
Then the user has to redo his actions and refill values. I think it would a good idea to keep the popup open respectively the popup is displayed again with populated values. | 1.0 | Improve usability of repository popup - When we try to clone a repository and an error occurs, e.g. invalid url or non existing package, the popup is closed and then the error is displayed.
Then the user has to redo his actions and refill values. I think it would a good idea to keep the popup open respectively the popup is displayed again with populated values. | priority | improve usability of repository popup when we try to clone a repository and an error occurs e g invalid url or non existing package the popup is closed and then the error is displayed then the user has to redo his actions and refill values i think it would a good idea to keep the popup open respectively the popup is displayed again with populated values | 1 |
132,468 | 5,186,702,140 | IssuesEvent | 2017-01-20 14:52:08 | bioinformatics-ua/dicoogle | https://api.github.com/repos/bioinformatics-ua/dicoogle | closed | Search service does not warn about invalid query provider names | dicoogle-core easy low priority | If I attempt to GET "/search?provider=idontexist&query=CT", I obtain an empty result list. Although it's a somewhat coherent behaviour, I would actually prefer the service to tell me that "idontexist" is not a valid query provider.
The proposal here: if _any_ of the query providers listed does not exist, an error message must be returned from the server (HTTP 400, `{"error": ..., ...}` | 1.0 | Search service does not warn about invalid query provider names - If I attempt to GET "/search?provider=idontexist&query=CT", I obtain an empty result list. Although it's a somewhat coherent behaviour, I would actually prefer the service to tell me that "idontexist" is not a valid query provider.
The proposal here: if _any_ of the query providers listed does not exist, an error message must be returned from the server (HTTP 400, `{"error": ..., ...}` | priority | search service does not warn about invalid query provider names if i attempt to get search provider idontexist query ct i obtain an empty result list although it s a somewhat coherent behaviour i would actually prefer the service to tell me that idontexist is not a valid query provider the proposal here if any of the query providers listed does not exist an error message must be returned from the server http error | 1 |
232,978 | 7,688,355,652 | IssuesEvent | 2018-05-17 09:12:17 | bounswe/bounswe2018group1 | https://api.github.com/repos/bounswe/bounswe2018group1 | closed | Team Logo | Position: Abandoned Priority: Low Type: Suggestion Who: Group-Work | I think we can create a cooler and more beautiful logo. I don't like the current one. | 1.0 | Team Logo - I think we can create a cooler and more beautiful logo. I don't like the current one. | priority | team logo i think we can create a cooler and more beautiful logo i don t like the current one | 1 |
176,915 | 6,569,232,077 | IssuesEvent | 2017-09-09 04:29:45 | ODIQueensland/data-curator | https://api.github.com/repos/ODIQueensland/data-curator | opened | On Quit, don't offer to save unsaved work when all work is saved | priority:Low problem:Bug | > Please provide a general summary of the issue in the Issue Title above
> fill out the headings below as applicable to the issue you are reporting,
> deleting as appropriate but offering us as much detail as you can to help us resolve the issue
### Expected Behaviour
https://relishapp.com/odi-australia/data-curator/docs/data-curator/quit#quit-the-application,-all-work-saved
### Current Behaviour
Work is saved but prompted to save work on Quit
### Steps to Reproduce
1. Create data
2. Save data
3. Quit
4. Prompt presented to save unsaved work, when application should quit
### Your Environment
- Data Curator 0.2.3
- Operating System macOS Seirra 10.12.6 | 1.0 | On Quit, don't offer to save unsaved work when all work is saved - > Please provide a general summary of the issue in the Issue Title above
> fill out the headings below as applicable to the issue you are reporting,
> deleting as appropriate but offering us as much detail as you can to help us resolve the issue
### Expected Behaviour
https://relishapp.com/odi-australia/data-curator/docs/data-curator/quit#quit-the-application,-all-work-saved
### Current Behaviour
Work is saved but prompted to save work on Quit
### Steps to Reproduce
1. Create data
2. Save data
3. Quit
4. Prompt presented to save unsaved work, when application should quit
### Your Environment
- Data Curator 0.2.3
- Operating System macOS Seirra 10.12.6 | priority | on quit don t offer to save unsaved work when all work is saved please provide a general summary of the issue in the issue title above fill out the headings below as applicable to the issue you are reporting deleting as appropriate but offering us as much detail as you can to help us resolve the issue expected behaviour current behaviour work is saved but prompted to save work on quit steps to reproduce create data save data quit prompt presented to save unsaved work when application should quit your environment data curator operating system macos seirra | 1 |
398,619 | 11,742,031,081 | IssuesEvent | 2020-03-11 23:22:47 | thaliawww/concrexit | https://api.github.com/repos/thaliawww/concrexit | closed | Functie in bestuur in profielpagina | easy and fun priority: low | In GitLab by @joren485 on Mar 25, 2017, 12:43
Op dit moment staat er bij (oud-)bestuursleden alleen in welk jaar ze bestuur zijn (geweest). Ik zie hier graag ook hun functie in dat bestuur bij. | 1.0 | Functie in bestuur in profielpagina - In GitLab by @joren485 on Mar 25, 2017, 12:43
Op dit moment staat er bij (oud-)bestuursleden alleen in welk jaar ze bestuur zijn (geweest). Ik zie hier graag ook hun functie in dat bestuur bij. | priority | functie in bestuur in profielpagina in gitlab by on mar op dit moment staat er bij oud bestuursleden alleen in welk jaar ze bestuur zijn geweest ik zie hier graag ook hun functie in dat bestuur bij | 1 |
466,372 | 13,400,901,821 | IssuesEvent | 2020-09-03 16:28:35 | easydigitaldownloads/easy-digital-downloads | https://api.github.com/repos/easydigitaldownloads/easy-digital-downloads | closed | Make Chosen.js matches wordpress style | component-administration priority-low type-feature | EDD and other plugins uses this js resources (built-in edd core)
I know this is a really low priority but with a few lines of code we can made this matches same style like wordpress inputs
```css
.chosen-container .chosen-single,
.chosen-container .chosen-drop {
border: 1px solid #ddd;
-webkit-box-shadow: inset 0 1px 2px rgba(0,0,0,.07);
box-shadow: inset 0 1px 2px rgba(0,0,0,.07);
background: #fff;
border-radius: 0;
}
.chosen-container .chosen-single {
padding: 3px 5px;
}
.chosen-container .chosen-drop {
border-top: none;
}
.chosen-container-active.chosen-with-drop .chosen-single {
background: #fff;
}
.chosen-container .chosen-results li.highlighted {
background: #0073aa;
}
``` | 1.0 | Make Chosen.js matches wordpress style - EDD and other plugins uses this js resources (built-in edd core)
I know this is a really low priority but with a few lines of code we can made this matches same style like wordpress inputs
```css
.chosen-container .chosen-single,
.chosen-container .chosen-drop {
border: 1px solid #ddd;
-webkit-box-shadow: inset 0 1px 2px rgba(0,0,0,.07);
box-shadow: inset 0 1px 2px rgba(0,0,0,.07);
background: #fff;
border-radius: 0;
}
.chosen-container .chosen-single {
padding: 3px 5px;
}
.chosen-container .chosen-drop {
border-top: none;
}
.chosen-container-active.chosen-with-drop .chosen-single {
background: #fff;
}
.chosen-container .chosen-results li.highlighted {
background: #0073aa;
}
``` | priority | make chosen js matches wordpress style edd and other plugins uses this js resources built in edd core i know this is a really low priority but with a few lines of code we can made this matches same style like wordpress inputs css chosen container chosen single chosen container chosen drop border solid ddd webkit box shadow inset rgba box shadow inset rgba background fff border radius chosen container chosen single padding chosen container chosen drop border top none chosen container active chosen with drop chosen single background fff chosen container chosen results li highlighted background | 1 |
248,279 | 7,928,801,688 | IssuesEvent | 2018-07-06 13:03:29 | gwu-libraries/lai-libsite | https://api.github.com/repos/gwu-libraries/lai-libsite | opened | Institute captcha on forms to deter spam | low priority (after Primo/AC/Study Spaces) | Definitely need captcha on contact us form :https://library.gwu.edu/contact and maybe all forms. | 1.0 | Institute captcha on forms to deter spam - Definitely need captcha on contact us form :https://library.gwu.edu/contact and maybe all forms. | priority | institute captcha on forms to deter spam definitely need captcha on contact us form and maybe all forms | 1 |
269,471 | 8,435,929,370 | IssuesEvent | 2018-10-17 14:17:53 | chanzuckerberg/cellxgene | https://api.github.com/repos/chanzuckerberg/cellxgene | closed | clean up f/e lint | Priority Low cleanup frontend | reduce overall lint warnings & errors pre release. Progress:
* [x] src/actions
* [ ] src/components/
* [x] src/middleware
* [x] src/reducers
* [X] src/util
* [X] top-level | 1.0 | clean up f/e lint - reduce overall lint warnings & errors pre release. Progress:
* [x] src/actions
* [ ] src/components/
* [x] src/middleware
* [x] src/reducers
* [X] src/util
* [X] top-level | priority | clean up f e lint reduce overall lint warnings errors pre release progress src actions src components src middleware src reducers src util top level | 1 |
219,778 | 7,345,830,079 | IssuesEvent | 2018-03-07 18:40:56 | HeathWallace/ethereum-pos | https://api.github.com/repos/HeathWallace/ethereum-pos | closed | Progress indicator by each transaction | Priority: Low Type: Backend Type: Component Type: UI Type: User story | As a user I want to see a progress indicator by each transaction so I predict how long they need to wait for confirmation.
## `<TransactionProgress />`
A visualisation of the transaction's progress.
- This component should be created in Storybook
- Designs already exist for this (wave pattern fills up as progress completes)
- This component needs to be hooked up via the back-end
### Input props
- `progress`: the percentage completed
| 1.0 | Progress indicator by each transaction - As a user I want to see a progress indicator by each transaction so I predict how long they need to wait for confirmation.
## `<TransactionProgress />`
A visualisation of the transaction's progress.
- This component should be created in Storybook
- Designs already exist for this (wave pattern fills up as progress completes)
- This component needs to be hooked up via the back-end
### Input props
- `progress`: the percentage completed
| priority | progress indicator by each transaction as a user i want to see a progress indicator by each transaction so i predict how long they need to wait for confirmation a visualisation of the transaction s progress this component should be created in storybook designs already exist for this wave pattern fills up as progress completes this component needs to be hooked up via the back end input props progress the percentage completed | 1 |
806,156 | 29,803,313,395 | IssuesEvent | 2023-06-16 09:44:03 | briandfoy/PerlPowerTools | https://api.github.com/repos/briandfoy/PerlPowerTools | closed | Make a test directory/test files for every program | Type: enhancement Priority: low | Let's make a test directory for every program, such as *t/ed/*, and instead that directory is all the tests for that program.
- [x] there's a program to make the test directory and fill it in
- [x] all programs have a test directory
- [x] there's a project-wide test to check that each program has a test directory
At a minimum, we can test:
* the program compiles
* some simple runs
* use Test::Warnings
* pod test
The GitHub actions will run through all the perls to check for warnings (see conversation in #164), and as we build out the tests the Test::Warnings will handle that.
With prove, we can then just give the program directory to run all it's tests without caring about other programs.
prove t/ed
Right now we have *compile.t* which checks every file in bin, but that takes awhile. It's annoying if you want to check a single program as you work on just that program. | 1.0 | Make a test directory/test files for every program - Let's make a test directory for every program, such as *t/ed/*, and instead that directory is all the tests for that program.
- [x] there's a program to make the test directory and fill it in
- [x] all programs have a test directory
- [x] there's a project-wide test to check that each program has a test directory
At a minimum, we can test:
* the program compiles
* some simple runs
* use Test::Warnings
* pod test
The GitHub actions will run through all the perls to check for warnings (see conversation in #164), and as we build out the tests the Test::Warnings will handle that.
With prove, we can then just give the program directory to run all it's tests without caring about other programs.
prove t/ed
Right now we have *compile.t* which checks every file in bin, but that takes awhile. It's annoying if you want to check a single program as you work on just that program. | priority | make a test directory test files for every program let s make a test directory for every program such as t ed and instead that directory is all the tests for that program there s a program to make the test directory and fill it in all programs have a test directory there s a project wide test to check that each program has a test directory at a minimum we can test the program compiles some simple runs use test warnings pod test the github actions will run through all the perls to check for warnings see conversation in and as we build out the tests the test warnings will handle that with prove we can then just give the program directory to run all it s tests without caring about other programs prove t ed right now we have compile t which checks every file in bin but that takes awhile it s annoying if you want to check a single program as you work on just that program | 1 |
709,677 | 24,386,640,974 | IssuesEvent | 2022-10-04 12:19:35 | MattTheLegoman/RealmsInExile | https://api.github.com/repos/MattTheLegoman/RealmsInExile | closed | Bug: Hold localisation errors | bug oddity priority: low | But-report from discord
Have double checked, checks out
The Barony Hold in the Barony Laddun, in the county of Entwash Vale is placed in the barony of Turfaham, in Westemnet county.
The barony hold of Aldorstowe Barony, in the county of Westfold Vale are on the borders and partially inside the barony Brimlad, in Grimslade county
Should probably be some relocations for these | 1.0 | Bug: Hold localisation errors - But-report from discord
Have double checked, checks out
The Barony Hold in the Barony Laddun, in the county of Entwash Vale is placed in the barony of Turfaham, in Westemnet county.
The barony hold of Aldorstowe Barony, in the county of Westfold Vale are on the borders and partially inside the barony Brimlad, in Grimslade county
Should probably be some relocations for these | priority | bug hold localisation errors but report from discord have double checked checks out the barony hold in the barony laddun in the county of entwash vale is placed in the barony of turfaham in westemnet county the barony hold of aldorstowe barony in the county of westfold vale are on the borders and partially inside the barony brimlad in grimslade county should probably be some relocations for these | 1 |
364,370 | 10,763,149,102 | IssuesEvent | 2019-11-01 02:42:35 | InfiniteFlightAirportEditing/Airports | https://api.github.com/repos/InfiniteFlightAirportEditing/Airports | opened | LIDG-Lugo Di Romagna Airport-EMILIA-ROMAGNA-ITALY | Being Redone Low Priority | # Airport Name
Lugo Di Romagna Airport
# Country?
Italy
# Improvements that need to be made?
Redo
# Are you working on this airport?
Yes
# Airport Priority? (IF Event, 10000ft+ Runway, World/US Capital, Low)
N/A | 1.0 | LIDG-Lugo Di Romagna Airport-EMILIA-ROMAGNA-ITALY - # Airport Name
Lugo Di Romagna Airport
# Country?
Italy
# Improvements that need to be made?
Redo
# Are you working on this airport?
Yes
# Airport Priority? (IF Event, 10000ft+ Runway, World/US Capital, Low)
N/A | priority | lidg lugo di romagna airport emilia romagna italy airport name lugo di romagna airport country italy improvements that need to be made redo are you working on this airport yes airport priority if event runway world us capital low n a | 1 |
194,388 | 6,894,429,979 | IssuesEvent | 2017-11-23 09:58:21 | pmem/issues | https://api.github.com/repos/pmem/issues | closed | tests: vmmalloc_fork/TEST1,2,3,4 fails with drd | Exposure: Low OS: Linux Priority: 4 low State: To be verified Type: Bug | Found on 7f6dcc563f09d1aeae49dabc33ebdbcc1bb2f961
> vmmalloc_fork/TEST1: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 crashed (signal 6). err1.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
>
> Last 30 lines of drd1.log below (whole file has 28510 lines).
> vmmalloc_fork/TEST1 drd1.log sched status:
> vmmalloc_fork/TEST1 drd1.log running_tid=1
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST1 drd1.log ==18167== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E7AC51: je_vmem_je_malloc_rwlock_wrlock (mutex.h:158)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E4BBDB: je_vmem_je_arenas_cleanup (jemalloc.c:351)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E55E80: jemalloc_destructor (jemalloc.c:2915)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x5719FF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x571A044: exit (exit.c:104)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x5700836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST1 drd1.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST1 drd1.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST1 drd1.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST1 drd1.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST1 drd1.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST1 drd1.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log ==18149==
> vmmalloc_fork/TEST1 drd1.log ==18149== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST1 drd1.log ==18149== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 22 from 10)
>
> trace1.log below.
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 trace1.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
>
> Last 30 lines of vmmalloc1.log below (whole file has 44 lines).
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x6800000
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x6800000
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:500 libvmmalloc_prefork] remap the pool file as private
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST1 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST1: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 crashed (signal 6). err1.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
>
> Last 30 lines of drd1.log below (whole file has 24555 lines).
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log sched status:
> vmmalloc_fork/TEST1 drd1.log running_tid=1
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST1 drd1.log ==18239== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4E47ED3: je_vmem_je_arenas_cleanup (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56FEFF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56FF044: exit (exit.c:104)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56E5836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST1 drd1.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST1 drd1.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST1 drd1.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST1 drd1.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST1 drd1.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST1 drd1.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log ==18222==
> vmmalloc_fork/TEST1 drd1.log ==18222== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST1 drd1.log ==18222== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 18 from 8)
>
> trace1.log below.
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 trace1.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST1 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST1' failed
> make[3]: *** [TEST1] Error 1
> vmmalloc_fork/TEST2: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 crashed (signal 6). err2.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
>
> Last 30 lines of drd2.log below (whole file has 27403 lines).
> vmmalloc_fork/TEST2 drd2.log sched status:
> vmmalloc_fork/TEST2 drd2.log running_tid=1
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST2 drd2.log ==18383== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E7AC51: je_vmem_je_malloc_rwlock_wrlock (mutex.h:158)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E4BBDB: je_vmem_je_arenas_cleanup (jemalloc.c:351)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E55E80: jemalloc_destructor (jemalloc.c:2915)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x5719FF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x571A044: exit (exit.c:104)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x5700836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST2 drd2.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST2 drd2.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST2 drd2.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST2 drd2.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST2 drd2.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST2 drd2.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log ==18365==
> vmmalloc_fork/TEST2 drd2.log ==18365== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST2 drd2.log ==18365== ERROR SUMMARY: 9 errors from 1 contexts (suppressed: 18 from 8)
>
> trace2.log below.
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 trace2.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
>
> Last 30 lines of vmmalloc2.log below (whole file has 72 lines).
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:487 libvmmalloc_prefork] clone the entire pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:411 libvmmalloc_clone]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.bDhnGc"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:430 libvmmalloc_clone] copy the entire pool file: dst 0xb802000 src 0x6800000 size 67108864
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:260 util_range_rw] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:545 libvmmalloc_postfork_parent] close the cloned pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:487 libvmmalloc_prefork] clone the entire pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:411 libvmmalloc_clone]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.vSzKsL"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:430 libvmmalloc_clone] copy the entire pool file: dst 0xb802000 src 0x6800000 size 67108864
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:260 util_range_rw] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:545 libvmmalloc_postfork_parent] close the cloned pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST2 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST2: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 crashed (signal 6). err2.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
>
> Last 30 lines of drd2.log below (whole file has 26705 lines).
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log sched status:
> vmmalloc_fork/TEST2 drd2.log running_tid=1
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST2 drd2.log ==18456== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4E47ED3: je_vmem_je_arenas_cleanup (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56FEFF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56FF044: exit (exit.c:104)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56E5836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST2 drd2.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST2 drd2.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST2 drd2.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST2 drd2.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST2 drd2.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST2 drd2.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log ==18438==
> vmmalloc_fork/TEST2 drd2.log ==18438== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST2 drd2.log ==18438== ERROR SUMMARY: 11 errors from 1 contexts (suppressed: 18 from 8)
>
> trace2.log below.
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 trace2.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST2 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST2' failed
> make[3]: *** [TEST2] Error 1
> vmmalloc_fork/TEST3: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 crashed (signal 6). err3.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
>
> Last 30 lines of drd3.log below (whole file has 29255 lines).
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4664D: libvmmalloc_init (libvmmalloc.c:620)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST3 drd3.log ==18599==
> vmmalloc_fork/TEST3 drd3.log ==18599== Mutex reinitialization: mutex 0x50a2800, recursion count 1, owner 1.
> vmmalloc_fork/TEST3 drd3.log ==18599== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7ADA6: je_vmem_je_malloc_mutex_postfork_child (mutex.c:142)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E6D43A: je_vmem_je_ctl_postfork_child (ctl.c:1010)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E5643B: je_vmem_je_jemalloc_postfork_child (jemalloc.c:3038)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x57AC4F5: fork (fork.c:211)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST3 drd3.log ==18599== mutex 0x50a2800 was first observed at:
> vmmalloc_fork/TEST3 drd3.log ==18599== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E6D3F2: je_vmem_je_ctl_boot (ctl.c:986)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FAE3: malloc_init_hard (jemalloc.c:855)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4DC93: malloc_init (jemalloc.c:379)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4DCE1: malloc_init_base_pool (jemalloc.c:399)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FE54: imalloc_body (jemalloc.c:982)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FF23: je_vmem_malloc (jemalloc.c:1004)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E45110: malloc (libvmmalloc.c:110)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x574DCDC: __fopen_internal (iofopen.c:69)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4A6A3: os_fopen (os_linux.c:102)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4954B: out_init (out.c:241)
> vmmalloc_fork/TEST3 drd3.log ==18599==
> vmmalloc_fork/TEST3 drd3.log ==18581==
> vmmalloc_fork/TEST3 drd3.log ==18581== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST3 drd3.log ==18581== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace3.log below.
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 trace3.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
>
> vmmalloc3.log below.
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:265 out_init] pid 18599: program: /bin/echo
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:267 out_init] libvmmalloc version 1.1
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:91 util_mmap_init]
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [out.c:358 out_set_vsnprintf_func] vsnprintf 0x7f2d7351ed3b
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:624 libvmmalloc_init]
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:350 libvmmalloc_create] dir "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" size 67108864
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.2tZQzw"
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:140 util_map] fd 12 len 67108864 flags 1 rdonly 0 req_align 4194304
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x7f2d6e000000
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x7f2d6e000000 len 4096
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x7f2d6e000000
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
> vmmalloc_fork/TEST3 vmmalloc3.log ����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������<libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST3 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST3: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 crashed (signal 6). err3.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
>
> Last 30 lines of drd3.log below (whole file has 24366 lines).
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFE: ???
> vmmalloc_fork/TEST3 drd3.log ==18671==
> vmmalloc_fork/TEST3 drd3.log ==18671== Mutex reinitialization: mutex 0x50877c0, recursion count 1, owner 1.
> vmmalloc_fork/TEST3 drd3.log ==18671== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69278: je_vmem_je_malloc_mutex_postfork_child (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x57914F5: fork (fork.c:211)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST3 drd3.log ==18671== mutex 0x50877c0 was first observed at:
> vmmalloc_fork/TEST3 drd3.log ==18671== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E48E31: malloc_init_hard (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E4D6E4: je_vmem_pool_create (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E44E70: libvmmalloc_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40107CA: call_init (dl-init.c:30)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40107CA: _dl_init (dl-init.c:120)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4000C69: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x3: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCEA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST3 drd3.log ==18671==
> vmmalloc_fork/TEST3 drd3.log ==18654==
> vmmalloc_fork/TEST3 drd3.log ==18654== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST3 drd3.log ==18654== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 16 from 10)
>
> trace3.log below.
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 trace3.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST3 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST3' failed
> make[3]: *** [TEST3] Error 1
> vmmalloc_fork/TEST4: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 crashed (signal 6). err4.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
>
> Last 30 lines of drd4.log below (whole file has 27247 lines).
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4664D: libvmmalloc_init (libvmmalloc.c:620)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST4 drd4.log ==18815==
> vmmalloc_fork/TEST4 drd4.log ==18815== Mutex reinitialization: mutex 0x50a2800, recursion count 1, owner 1.
> vmmalloc_fork/TEST4 drd4.log ==18815== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7ADA6: je_vmem_je_malloc_mutex_postfork_child (mutex.c:142)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E6D43A: je_vmem_je_ctl_postfork_child (ctl.c:1010)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E5643B: je_vmem_je_jemalloc_postfork_child (jemalloc.c:3038)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x57AC4F5: fork (fork.c:211)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST4 drd4.log ==18815== mutex 0x50a2800 was first observed at:
> vmmalloc_fork/TEST4 drd4.log ==18815== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E6D3F2: je_vmem_je_ctl_boot (ctl.c:986)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FAE3: malloc_init_hard (jemalloc.c:855)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4DC93: malloc_init (jemalloc.c:379)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4DCE1: malloc_init_base_pool (jemalloc.c:399)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FE54: imalloc_body (jemalloc.c:982)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FF23: je_vmem_malloc (jemalloc.c:1004)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E45110: malloc (libvmmalloc.c:110)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x574DCDC: __fopen_internal (iofopen.c:69)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4A6A3: os_fopen (os_linux.c:102)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4954B: out_init (out.c:241)
> vmmalloc_fork/TEST4 drd4.log ==18815==
> vmmalloc_fork/TEST4 drd4.log ==18797==
> vmmalloc_fork/TEST4 drd4.log ==18797== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST4 drd4.log ==18797== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace4.log below.
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 trace4.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
>
> vmmalloc4.log below.
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:265 out_init] pid 18815: program: /bin/echo
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:267 out_init] libvmmalloc version 1.1
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:91 util_mmap_init]
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [out.c:358 out_set_vsnprintf_func] vsnprintf 0x7fc935bb9d3b
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:624 libvmmalloc_init]
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:350 libvmmalloc_create] dir "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" size 67108864
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.Zo2CGu"
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:140 util_map] fd 12 len 67108864 flags 1 rdonly 0 req_align 4194304
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x7fc930800000
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x7fc930800000 len 4096
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x7fc930800000
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
> vmmalloc_fork/TEST4 vmmalloc4.log ��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������<libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST4 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST4: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 crashed (signal 6). err4.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
>
> Last 30 lines of drd4.log below (whole file has 24540 lines).
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFE: ???
> vmmalloc_fork/TEST4 drd4.log ==18889==
> vmmalloc_fork/TEST4 drd4.log ==18889== Mutex reinitialization: mutex 0x50877c0, recursion count 1, owner 1.
> vmmalloc_fork/TEST4 drd4.log ==18889== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69278: je_vmem_je_malloc_mutex_postfork_child (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x57914F5: fork (fork.c:211)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST4 drd4.log ==18889== mutex 0x50877c0 was first observed at:
> vmmalloc_fork/TEST4 drd4.log ==18889== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E48E31: malloc_init_hard (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E4D6E4: je_vmem_pool_create (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E44E70: libvmmalloc_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40107CA: call_init (dl-init.c:30)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40107CA: _dl_init (dl-init.c:120)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4000C69: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x3: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCEA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST4 drd4.log ==18889==
> vmmalloc_fork/TEST4 drd4.log ==18871==
> vmmalloc_fork/TEST4 drd4.log ==18871== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST4 drd4.log ==18871== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace4.log below.
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 trace4.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST4 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST4' failed
> make[3]: *** [TEST4] Error 1
> make[3]: Target 'pcheck' not remade because of errors.
> make[3]: Leaving directory '/home/jenkins/workspace/nvml_tests_drd/src/test/vmmalloc_fork'
> Makefile:385: recipe for target 'vmmalloc_fork' failed
> make[2]: *** [vmmalloc_fork] Error 2 | 1.0 | tests: vmmalloc_fork/TEST1,2,3,4 fails with drd - Found on 7f6dcc563f09d1aeae49dabc33ebdbcc1bb2f961
> vmmalloc_fork/TEST1: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 crashed (signal 6). err1.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
>
> Last 30 lines of drd1.log below (whole file has 28510 lines).
> vmmalloc_fork/TEST1 drd1.log sched status:
> vmmalloc_fork/TEST1 drd1.log running_tid=1
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST1 drd1.log ==18167== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E7AC51: je_vmem_je_malloc_rwlock_wrlock (mutex.h:158)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E4BBDB: je_vmem_je_arenas_cleanup (jemalloc.c:351)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4E55E80: jemalloc_destructor (jemalloc.c:2915)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x5719FF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x571A044: exit (exit.c:104)
> vmmalloc_fork/TEST1 drd1.log ==18167== by 0x5700836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST1 drd1.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST1 drd1.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST1 drd1.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST1 drd1.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST1 drd1.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST1 drd1.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log ==18149==
> vmmalloc_fork/TEST1 drd1.log ==18149== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST1 drd1.log ==18149== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 22 from 10)
>
> trace1.log below.
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 trace1.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
>
> Last 30 lines of vmmalloc1.log below (whole file has 44 lines).
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x6800000
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x6800000
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:500 libvmmalloc_prefork] remap the pool file as private
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:477 libvmmalloc_prefork] already mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:543 libvmmalloc_postfork_parent] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:564 libvmmalloc_postfork_child] pool mapped as private - do nothing
> vmmalloc_fork/TEST1 vmmalloc1.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST1 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST1: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 crashed (signal 6). err1.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
>
> Last 30 lines of drd1.log below (whole file has 24555 lines).
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log sched status:
> vmmalloc_fork/TEST1 drd1.log running_tid=1
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST1 drd1.log ==18239== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4E47ED3: je_vmem_je_arenas_cleanup (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56FEFF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56FF044: exit (exit.c:104)
> vmmalloc_fork/TEST1 drd1.log ==18239== by 0x56E5836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST1 drd1.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST1 drd1.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST1 drd1.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST1 drd1.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST1 drd1.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST1 drd1.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST1 drd1.log
> vmmalloc_fork/TEST1 drd1.log ==18222==
> vmmalloc_fork/TEST1 drd1.log ==18222== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST1 drd1.log ==18222== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 18 from 8)
>
> trace1.log below.
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST1: START: vmmalloc_fork
> vmmalloc_fork/TEST1 trace1.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST1 trace1.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST1: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST1: Signal 6, backtrace:
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST1: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST1 trace1.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST1:
> vmmalloc_fork/TEST1 trace1.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST1 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST1' failed
> make[3]: *** [TEST1] Error 1
> vmmalloc_fork/TEST2: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 crashed (signal 6). err2.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
>
> Last 30 lines of drd2.log below (whole file has 27403 lines).
> vmmalloc_fork/TEST2 drd2.log sched status:
> vmmalloc_fork/TEST2 drd2.log running_tid=1
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST2 drd2.log ==18383== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E7AC51: je_vmem_je_malloc_rwlock_wrlock (mutex.h:158)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E4BBDB: je_vmem_je_arenas_cleanup (jemalloc.c:351)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4E55E80: jemalloc_destructor (jemalloc.c:2915)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x5719FF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x571A044: exit (exit.c:104)
> vmmalloc_fork/TEST2 drd2.log ==18383== by 0x5700836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST2 drd2.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST2 drd2.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST2 drd2.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST2 drd2.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST2 drd2.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST2 drd2.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log ==18365==
> vmmalloc_fork/TEST2 drd2.log ==18365== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST2 drd2.log ==18365== ERROR SUMMARY: 9 errors from 1 contexts (suppressed: 18 from 8)
>
> trace2.log below.
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 trace2.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
>
> Last 30 lines of vmmalloc2.log below (whole file has 72 lines).
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:487 libvmmalloc_prefork] clone the entire pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:411 libvmmalloc_clone]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.bDhnGc"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:430 libvmmalloc_clone] copy the entire pool file: dst 0xb802000 src 0x6800000 size 67108864
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:260 util_range_rw] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:545 libvmmalloc_postfork_parent] close the cloned pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:463 libvmmalloc_prefork]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:487 libvmmalloc_prefork] clone the entire pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:411 libvmmalloc_clone]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork2😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.vSzKsL"
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:430 libvmmalloc_clone] copy the entire pool file: dst 0xb802000 src 0x6800000 size 67108864
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:260 util_range_rw] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x6800000 len 4096
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:535 libvmmalloc_postfork_parent]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:545 libvmmalloc_postfork_parent] close the cloned pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:556 libvmmalloc_postfork_child]
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:566 libvmmalloc_postfork_child] close the original pool file
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:573 libvmmalloc_postfork_child] mapping cloned pool file at 0x6800000
> vmmalloc_fork/TEST2 vmmalloc2.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST2 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST2: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 crashed (signal 6). err2.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
>
> Last 30 lines of drd2.log below (whole file has 26705 lines).
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log sched status:
> vmmalloc_fork/TEST2 drd2.log running_tid=1
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Thread 1: status = VgTs_Runnable
> vmmalloc_fork/TEST2 drd2.log ==18456== at 0x4C37E74: pthread_rwlock_trywrlock_intercept (drd_pthread_intercepts.c:1242)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4C37E74: pthread_rwlock_trywrlock$* (drd_pthread_intercepts.c:1247)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4E47ED3: je_vmem_je_arenas_cleanup (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x4010DE6: _dl_fini (dl-fini.c:235)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56FEFF7: __run_exit_handlers (exit.c:82)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56FF044: exit (exit.c:104)
> vmmalloc_fork/TEST2 drd2.log ==18456== by 0x56E5836: (below main) (libc-start.c:325)
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log Note: see also the FAQ in the source distribution.
> vmmalloc_fork/TEST2 drd2.log It contains workarounds to several common problems.
> vmmalloc_fork/TEST2 drd2.log In particular, if Valgrind aborted or crashed after
> vmmalloc_fork/TEST2 drd2.log identifying problems in your program, there's a good chance
> vmmalloc_fork/TEST2 drd2.log that fixing those problems will prevent Valgrind aborting or
> vmmalloc_fork/TEST2 drd2.log crashing, especially if it happened in m_mallocfree.c.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log If that doesn't help, please report this bug to: www.valgrind.org
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log In the bug report, send all the above text, the valgrind
> vmmalloc_fork/TEST2 drd2.log version, and what OS and version you are using. Thanks.
> vmmalloc_fork/TEST2 drd2.log
> vmmalloc_fork/TEST2 drd2.log ==18438==
> vmmalloc_fork/TEST2 drd2.log ==18438== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST2 drd2.log ==18438== ERROR SUMMARY: 11 errors from 1 contexts (suppressed: 18 from 8)
>
> trace2.log below.
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST2: START: vmmalloc_fork
> vmmalloc_fork/TEST2 trace2.log ./vmmalloc_fork c 4 2
> vmmalloc_fork/TEST2 trace2.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST2: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST2: Signal 6, backtrace:
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST2: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST2 trace2.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST2:
> vmmalloc_fork/TEST2 trace2.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST2 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST2' failed
> make[3]: *** [TEST2] Error 1
> vmmalloc_fork/TEST3: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 crashed (signal 6). err3.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
>
> Last 30 lines of drd3.log below (whole file has 29255 lines).
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4664D: libvmmalloc_init (libvmmalloc.c:620)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST3 drd3.log ==18599==
> vmmalloc_fork/TEST3 drd3.log ==18599== Mutex reinitialization: mutex 0x50a2800, recursion count 1, owner 1.
> vmmalloc_fork/TEST3 drd3.log ==18599== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7ADA6: je_vmem_je_malloc_mutex_postfork_child (mutex.c:142)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E6D43A: je_vmem_je_ctl_postfork_child (ctl.c:1010)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E5643B: je_vmem_je_jemalloc_postfork_child (jemalloc.c:3038)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x57AC4F5: fork (fork.c:211)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST3 drd3.log ==18599== mutex 0x50a2800 was first observed at:
> vmmalloc_fork/TEST3 drd3.log ==18599== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E6D3F2: je_vmem_je_ctl_boot (ctl.c:986)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FAE3: malloc_init_hard (jemalloc.c:855)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4DC93: malloc_init (jemalloc.c:379)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4DCE1: malloc_init_base_pool (jemalloc.c:399)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FE54: imalloc_body (jemalloc.c:982)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4FF23: je_vmem_malloc (jemalloc.c:1004)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E45110: malloc (libvmmalloc.c:110)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x574DCDC: __fopen_internal (iofopen.c:69)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4A6A3: os_fopen (os_linux.c:102)
> vmmalloc_fork/TEST3 drd3.log ==18599== by 0x4E4954B: out_init (out.c:241)
> vmmalloc_fork/TEST3 drd3.log ==18599==
> vmmalloc_fork/TEST3 drd3.log ==18581==
> vmmalloc_fork/TEST3 drd3.log ==18581== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST3 drd3.log ==18581== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace3.log below.
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 trace3.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
>
> vmmalloc3.log below.
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:265 out_init] pid 18599: program: /bin/echo
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:267 out_init] libvmmalloc version 1.1
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:91 util_mmap_init]
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [out.c:358 out_set_vsnprintf_func] vsnprintf 0x7f2d7351ed3b
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:624 libvmmalloc_init]
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:350 libvmmalloc_create] dir "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" size 67108864
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork3😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.2tZQzw"
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:140 util_map] fd 12 len 67108864 flags 1 rdonly 0 req_align 4194304
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x7f2d6e000000
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x7f2d6e000000 len 4096
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x7f2d6e000000
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST3 vmmalloc3.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
> vmmalloc_fork/TEST3 vmmalloc3.log ����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������<libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST3 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST3: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 crashed (signal 6). err3.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
>
> Last 30 lines of drd3.log below (whole file has 24366 lines).
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFE: ???
> vmmalloc_fork/TEST3 drd3.log ==18671==
> vmmalloc_fork/TEST3 drd3.log ==18671== Mutex reinitialization: mutex 0x50877c0, recursion count 1, owner 1.
> vmmalloc_fork/TEST3 drd3.log ==18671== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69278: je_vmem_je_malloc_mutex_postfork_child (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x57914F5: fork (fork.c:211)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST3 drd3.log ==18671== mutex 0x50877c0 was first observed at:
> vmmalloc_fork/TEST3 drd3.log ==18671== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E48E31: malloc_init_hard (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E4D6E4: je_vmem_pool_create (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4E44E70: libvmmalloc_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40107CA: call_init (dl-init.c:30)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x40107CA: _dl_init (dl-init.c:120)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x4000C69: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so)
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0x3: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCEA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST3 drd3.log ==18671== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST3 drd3.log ==18671==
> vmmalloc_fork/TEST3 drd3.log ==18654==
> vmmalloc_fork/TEST3 drd3.log ==18654== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST3 drd3.log ==18654== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 16 from 10)
>
> trace3.log below.
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST3: START: vmmalloc_fork
> vmmalloc_fork/TEST3 trace3.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST3 trace3.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST3: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST3: Signal 6, backtrace:
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST3: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST3 trace3.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST3:
> vmmalloc_fork/TEST3 trace3.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST3 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST3' failed
> make[3]: *** [TEST3] Error 1
> vmmalloc_fork/TEST4: SETUP (all/pmem/debug/drd)
> vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 crashed (signal 6). err4.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
>
> Last 30 lines of drd4.log below (whole file has 27247 lines).
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4664D: libvmmalloc_init (libvmmalloc.c:620)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST4 drd4.log ==18815==
> vmmalloc_fork/TEST4 drd4.log ==18815== Mutex reinitialization: mutex 0x50a2800, recursion count 1, owner 1.
> vmmalloc_fork/TEST4 drd4.log ==18815== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7ADA6: je_vmem_je_malloc_mutex_postfork_child (mutex.c:142)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E6D43A: je_vmem_je_ctl_postfork_child (ctl.c:1010)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E5643B: je_vmem_je_jemalloc_postfork_child (jemalloc.c:3038)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x57AC4F5: fork (fork.c:211)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST4 drd4.log ==18815== mutex 0x50a2800 was first observed at:
> vmmalloc_fork/TEST4 drd4.log ==18815== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E7AD0F: je_vmem_je_malloc_mutex_init (mutex.c:96)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E6D3F2: je_vmem_je_ctl_boot (ctl.c:986)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FAE3: malloc_init_hard (jemalloc.c:855)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4DC93: malloc_init (jemalloc.c:379)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4DCE1: malloc_init_base_pool (jemalloc.c:399)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FE54: imalloc_body (jemalloc.c:982)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4FF23: je_vmem_malloc (jemalloc.c:1004)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E45110: malloc (libvmmalloc.c:110)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x574DCDC: __fopen_internal (iofopen.c:69)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4A6A3: os_fopen (os_linux.c:102)
> vmmalloc_fork/TEST4 drd4.log ==18815== by 0x4E4954B: out_init (out.c:241)
> vmmalloc_fork/TEST4 drd4.log ==18815==
> vmmalloc_fork/TEST4 drd4.log ==18797==
> vmmalloc_fork/TEST4 drd4.log ==18797== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST4 drd4.log ==18797== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace4.log below.
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 trace4.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x57154ef] [0x354ef]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x5715428] [0x35428]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x571702a] [0x3702a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x5700830] [0x20830]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
>
> vmmalloc4.log below.
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:265 out_init] pid 18815: program: /bin/echo
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:267 out_init] libvmmalloc version 1.1
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:91 util_mmap_init]
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [out.c:358 out_set_vsnprintf_func] vsnprintf 0x7fc935bb9d3b
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:624 libvmmalloc_init]
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:350 libvmmalloc_create] dir "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" size 67108864
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [file_linux.c:57 util_tmpfile] dir "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋" template "/vmem.XXXXXX"
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [file_linux.c:87 util_tmpfile] unlinked file is "/mnt/pmem//////test_vmmalloc_fork4😘⠝⠧⠍⠇ɗNVMLӜ⥺🙋/vmem.Zo2CGu"
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:140 util_map] fd 12 len 67108864 flags 1 rdonly 0 req_align 4194304
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap_linux.c:146 util_map_hint] len 67108864 req_align 4194304
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:158 util_map] mapped at 0x7fc930800000
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [mmap.c:289 util_range_none] addr 0x7fc930800000 len 4096
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:401 libvmmalloc_create] vmp 0x7fc930800000
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <2> [libvmmalloc.c:685 libvmmalloc_init] initialization completed
> vmmalloc_fork/TEST4 vmmalloc4.log <libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
> vmmalloc_fork/TEST4 vmmalloc4.log ��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������<libvmmalloc>: <3> [libvmmalloc.c:698 libvmmalloc_fini]
>
> RUNTESTS: stopping: vmmalloc_fork/TEST4 failed, TEST=all FS=any BUILD=debug
> vmmalloc_fork/TEST4: SETUP (all/pmem/nondebug/drd)
> vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 crashed (signal 6). err4.log below.
> {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
>
> {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
>
> Last 30 lines of drd4.log below (whole file has 24540 lines).
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFE: ???
> vmmalloc_fork/TEST4 drd4.log ==18889==
> vmmalloc_fork/TEST4 drd4.log ==18889== Mutex reinitialization: mutex 0x50877c0, recursion count 1, owner 1.
> vmmalloc_fork/TEST4 drd4.log ==18889== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69278: je_vmem_je_malloc_mutex_postfork_child (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x57914F5: fork (fork.c:211)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40343B: main (vmmalloc_fork.c:145)
> vmmalloc_fork/TEST4 drd4.log ==18889== mutex 0x50877c0 was first observed at:
> vmmalloc_fork/TEST4 drd4.log ==18889== at 0x4C34A99: pthread_mutex_init_intercept (drd_pthread_intercepts.c:603)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4C34A99: pthread_mutex_init$* (drd_pthread_intercepts.c:612)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E69214: je_vmem_je_malloc_mutex_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E48E31: malloc_init_hard (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E4D6E4: je_vmem_pool_create (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4E44E70: libvmmalloc_init (in /home/jenkins/workspace/nvml_tests_drd/src/nondebug/libvmmalloc.so.1.0.0)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40106B9: call_init.part.0 (dl-init.c:72)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40107CA: call_init (dl-init.c:30)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x40107CA: _dl_init (dl-init.c:120)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x4000C69: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so)
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0x3: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCEA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFA: ???
> vmmalloc_fork/TEST4 drd4.log ==18889== by 0xFFEFFFCFC: ???
> vmmalloc_fork/TEST4 drd4.log ==18889==
> vmmalloc_fork/TEST4 drd4.log ==18871==
> vmmalloc_fork/TEST4 drd4.log ==18871== For counts of detected and suppressed errors, rerun with: -v
> vmmalloc_fork/TEST4 drd4.log ==18871== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 18 from 8)
>
> trace4.log below.
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:95 main} vmmalloc_fork/TEST4: START: vmmalloc_fork
> vmmalloc_fork/TEST4 trace4.log ./vmmalloc_fork e 4 2
> vmmalloc_fork/TEST4 trace4.log {vmmalloc_fork.c:189 main} vmmalloc_fork/TEST4: Error: assertion failure: ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0xff00) >> 8) (0x1) == 0 (0x0)
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:198 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:199 ut_sighandler} vmmalloc_fork/TEST4: Signal 6, backtrace:
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 0: ./vmmalloc_fork (ut_sighandler+0x52) [0x406967] [0x6967]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 1: /lib/x86_64-linux-gnu/libc.so.6 (killpg+0x40) [0x56fa4ef] [0x354ef]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x38) [0x56fa428] [0x35428]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16a) [0x56fc02a] [0x3702a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 4: ./vmmalloc_fork (ut_out+0x0) [0x404d8a] [0x4d8a]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 5: ./vmmalloc_fork (main+0xb0d) [0x40390e] [0x390e]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x56e5830] [0x20830]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 7: ./vmmalloc_fork (_start+0x29) [0x402b09] [0x2b09]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:115 ut_dump_backtrace} vmmalloc_fork/TEST4: 8: ? (?+0x29) [0x29] [0x0]
> vmmalloc_fork/TEST4 trace4.log {ut_backtrace.c:201 ut_sighandler} vmmalloc_fork/TEST4:
> vmmalloc_fork/TEST4 trace4.log
>
> RUNTESTS: stopping: vmmalloc_fork/TEST4 failed, TEST=all FS=any BUILD=nondebug
> ../Makefile.inc:350: recipe for target 'TEST4' failed
> make[3]: *** [TEST4] Error 1
> make[3]: Target 'pcheck' not remade because of errors.
> make[3]: Leaving directory '/home/jenkins/workspace/nvml_tests_drd/src/test/vmmalloc_fork'
> Makefile:385: recipe for target 'vmmalloc_fork' failed
> make[2]: *** [vmmalloc_fork] Error 2 | priority | tests vmmalloc fork fails with drd found on vmmalloc fork setup all pmem debug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log sched status vmmalloc fork log running tid vmmalloc fork log vmmalloc fork log thread status vgts runnable vmmalloc fork log at pthread rwlock trywrlock intercept drd pthread intercepts c vmmalloc fork log by pthread rwlock trywrlock drd pthread intercepts c vmmalloc fork log by je vmem je malloc rwlock wrlock mutex h vmmalloc fork log by je vmem je arenas cleanup jemalloc c vmmalloc fork log by jemalloc destructor jemalloc c vmmalloc fork log by dl fini dl fini c vmmalloc fork log by run exit handlers exit c vmmalloc fork log by exit exit c vmmalloc fork log by below main libc start c vmmalloc fork log vmmalloc fork log vmmalloc fork log note see also the faq in the source distribution vmmalloc fork log it contains workarounds to several common problems vmmalloc fork log in particular if valgrind aborted or crashed after vmmalloc fork log identifying problems in your program there s a good chance vmmalloc fork log that fixing those problems will prevent valgrind aborting or vmmalloc fork log crashing especially if it happened in m mallocfree c vmmalloc fork log vmmalloc fork log if that doesn t help please report this bug to vmmalloc fork log vmmalloc fork log in the bug report send all the above text the valgrind vmmalloc fork log version and what os and version you are using thanks vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork c vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log last lines of log below whole file has lines vmmalloc fork log len req align vmmalloc fork log mapped at vmmalloc fork log addr len vmmalloc fork log vmp vmmalloc fork log initialization completed vmmalloc fork log vmmalloc fork log remap the pool file as private vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log already mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log already mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log already mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log vmmalloc fork log pool mapped as private do nothing vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build debug vmmalloc fork setup all pmem nondebug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by run a thread noreturn syswrap linux c vmmalloc fork log vmmalloc fork log sched status vmmalloc fork log running tid vmmalloc fork log vmmalloc fork log thread status vgts runnable vmmalloc fork log at pthread rwlock trywrlock intercept drd pthread intercepts c vmmalloc fork log by pthread rwlock trywrlock drd pthread intercepts c vmmalloc fork log by je vmem je arenas cleanup in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by dl fini dl fini c vmmalloc fork log by run exit handlers exit c vmmalloc fork log by exit exit c vmmalloc fork log by below main libc start c vmmalloc fork log vmmalloc fork log vmmalloc fork log note see also the faq in the source distribution vmmalloc fork log it contains workarounds to several common problems vmmalloc fork log in particular if valgrind aborted or crashed after vmmalloc fork log identifying problems in your program there s a good chance vmmalloc fork log that fixing those problems will prevent valgrind aborting or vmmalloc fork log crashing especially if it happened in m mallocfree c vmmalloc fork log vmmalloc fork log if that doesn t help please report this bug to vmmalloc fork log vmmalloc fork log in the bug report send all the above text the valgrind vmmalloc fork log version and what os and version you are using thanks vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork c vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build nondebug makefile inc recipe for target failed make error vmmalloc fork setup all pmem debug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log sched status vmmalloc fork log running tid vmmalloc fork log vmmalloc fork log thread status vgts runnable vmmalloc fork log at pthread rwlock trywrlock intercept drd pthread intercepts c vmmalloc fork log by pthread rwlock trywrlock drd pthread intercepts c vmmalloc fork log by je vmem je malloc rwlock wrlock mutex h vmmalloc fork log by je vmem je arenas cleanup jemalloc c vmmalloc fork log by jemalloc destructor jemalloc c vmmalloc fork log by dl fini dl fini c vmmalloc fork log by run exit handlers exit c vmmalloc fork log by exit exit c vmmalloc fork log by below main libc start c vmmalloc fork log vmmalloc fork log vmmalloc fork log note see also the faq in the source distribution vmmalloc fork log it contains workarounds to several common problems vmmalloc fork log in particular if valgrind aborted or crashed after vmmalloc fork log identifying problems in your program there s a good chance vmmalloc fork log that fixing those problems will prevent valgrind aborting or vmmalloc fork log crashing especially if it happened in m mallocfree c vmmalloc fork log vmmalloc fork log if that doesn t help please report this bug to vmmalloc fork log vmmalloc fork log in the bug report send all the above text the valgrind vmmalloc fork log version and what os and version you are using thanks vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork c vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log last lines of log below whole file has lines vmmalloc fork log vmmalloc fork log close the original pool file vmmalloc fork log mapping cloned pool file at vmmalloc fork log vmmalloc fork log clone the entire pool file vmmalloc fork log vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 template vmem xxxxxx vmmalloc fork log unlinked file is mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 vmem bdhngc vmmalloc fork log copy the entire pool file dst src size vmmalloc fork log addr len vmmalloc fork log addr len vmmalloc fork log vmmalloc fork log close the cloned pool file vmmalloc fork log vmmalloc fork log close the original pool file vmmalloc fork log mapping cloned pool file at vmmalloc fork log vmmalloc fork log clone the entire pool file vmmalloc fork log vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 template vmem xxxxxx vmmalloc fork log unlinked file is mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 vmem vszksl vmmalloc fork log copy the entire pool file dst src size vmmalloc fork log addr len vmmalloc fork log addr len vmmalloc fork log vmmalloc fork log close the cloned pool file vmmalloc fork log vmmalloc fork log close the original pool file vmmalloc fork log mapping cloned pool file at vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build debug vmmalloc fork setup all pmem nondebug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by run a thread noreturn syswrap linux c vmmalloc fork log vmmalloc fork log sched status vmmalloc fork log running tid vmmalloc fork log vmmalloc fork log thread status vgts runnable vmmalloc fork log at pthread rwlock trywrlock intercept drd pthread intercepts c vmmalloc fork log by pthread rwlock trywrlock drd pthread intercepts c vmmalloc fork log by je vmem je arenas cleanup in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by dl fini dl fini c vmmalloc fork log by run exit handlers exit c vmmalloc fork log by exit exit c vmmalloc fork log by below main libc start c vmmalloc fork log vmmalloc fork log vmmalloc fork log note see also the faq in the source distribution vmmalloc fork log it contains workarounds to several common problems vmmalloc fork log in particular if valgrind aborted or crashed after vmmalloc fork log identifying problems in your program there s a good chance vmmalloc fork log that fixing those problems will prevent valgrind aborting or vmmalloc fork log crashing especially if it happened in m mallocfree c vmmalloc fork log vmmalloc fork log if that doesn t help please report this bug to vmmalloc fork log vmmalloc fork log in the bug report send all the above text the valgrind vmmalloc fork log version and what os and version you are using thanks vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork c vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build nondebug makefile inc recipe for target failed make error vmmalloc fork setup all pmem debug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by libvmmalloc init libvmmalloc c vmmalloc fork log by call init part dl init c vmmalloc fork log vmmalloc fork log mutex reinitialization mutex recursion count owner vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init mutex c vmmalloc fork log by je vmem je malloc mutex postfork child mutex c vmmalloc fork log by je vmem je ctl postfork child ctl c vmmalloc fork log by je vmem je jemalloc postfork child jemalloc c vmmalloc fork log by fork fork c vmmalloc fork log by main vmmalloc fork c vmmalloc fork log mutex was first observed at vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init mutex c vmmalloc fork log by je vmem je ctl boot ctl c vmmalloc fork log by malloc init hard jemalloc c vmmalloc fork log by malloc init jemalloc c vmmalloc fork log by malloc init base pool jemalloc c vmmalloc fork log by imalloc body jemalloc c vmmalloc fork log by je vmem malloc jemalloc c vmmalloc fork log by malloc libvmmalloc c vmmalloc fork log by fopen internal iofopen c vmmalloc fork log by os fopen os linux c vmmalloc fork log by out init out c vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork e vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log log below vmmalloc fork log pid program bin echo vmmalloc fork log libvmmalloc version vmmalloc fork log src version srcversion vmmalloc fork log compiled with support for valgrind pmemcheck vmmalloc fork log compiled with support for valgrind helgrind vmmalloc fork log compiled with support for valgrind memcheck vmmalloc fork log compiled with support for valgrind drd vmmalloc fork log vmmalloc fork log vsnprintf vmmalloc fork log vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 size vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 template vmem xxxxxx vmmalloc fork log unlinked file is mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 vmem vmmalloc fork log fd len flags rdonly req align vmmalloc fork log len req align vmmalloc fork log mapped at vmmalloc fork log addr len vmmalloc fork log vmp vmmalloc fork log initialization completed vmmalloc fork log vmmalloc fork log ���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� runtests stopping vmmalloc fork failed test all fs any build debug vmmalloc fork setup all pmem nondebug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log vmmalloc fork log mutex reinitialization mutex recursion count owner vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by je vmem je malloc mutex postfork child in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by fork fork c vmmalloc fork log by main vmmalloc fork c vmmalloc fork log mutex was first observed at vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by malloc init hard in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by je vmem pool create in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by libvmmalloc init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by call init part dl init c vmmalloc fork log by call init dl init c vmmalloc fork log by dl init dl init c vmmalloc fork log by in lib linux gnu ld so vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork e vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build nondebug makefile inc recipe for target failed make error vmmalloc fork setup all pmem debug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by libvmmalloc init libvmmalloc c vmmalloc fork log by call init part dl init c vmmalloc fork log vmmalloc fork log mutex reinitialization mutex recursion count owner vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init mutex c vmmalloc fork log by je vmem je malloc mutex postfork child mutex c vmmalloc fork log by je vmem je ctl postfork child ctl c vmmalloc fork log by je vmem je jemalloc postfork child jemalloc c vmmalloc fork log by fork fork c vmmalloc fork log by main vmmalloc fork c vmmalloc fork log mutex was first observed at vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init mutex c vmmalloc fork log by je vmem je ctl boot ctl c vmmalloc fork log by malloc init hard jemalloc c vmmalloc fork log by malloc init jemalloc c vmmalloc fork log by malloc init base pool jemalloc c vmmalloc fork log by imalloc body jemalloc c vmmalloc fork log by je vmem malloc jemalloc c vmmalloc fork log by malloc libvmmalloc c vmmalloc fork log by fopen internal iofopen c vmmalloc fork log by os fopen os linux c vmmalloc fork log by out init out c vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork e vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log log below vmmalloc fork log pid program bin echo vmmalloc fork log libvmmalloc version vmmalloc fork log src version srcversion vmmalloc fork log compiled with support for valgrind pmemcheck vmmalloc fork log compiled with support for valgrind helgrind vmmalloc fork log compiled with support for valgrind memcheck vmmalloc fork log compiled with support for valgrind drd vmmalloc fork log vmmalloc fork log vsnprintf vmmalloc fork log vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 size vmmalloc fork log dir mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 template vmem xxxxxx vmmalloc fork log unlinked file is mnt pmem test vmmalloc 😘⠝⠧⠍⠇ɗnvmlӝ⥺🙋 vmem vmmalloc fork log fd len flags rdonly req align vmmalloc fork log len req align vmmalloc fork log mapped at vmmalloc fork log addr len vmmalloc fork log vmp vmmalloc fork log initialization completed vmmalloc fork log vmmalloc fork log �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� runtests stopping vmmalloc fork failed test all fs any build debug vmmalloc fork setup all pmem nondebug drd vmmalloc fork start vmmalloc fork vmmalloc fork crashed signal log below vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i ut backtrace c ut sighandler vmmalloc fork ut backtrace c ut sighandler vmmalloc fork signal backtrace ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start ut backtrace c ut dump backtrace vmmalloc fork ut backtrace c ut sighandler vmmalloc fork last lines of log below whole file has lines vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log vmmalloc fork log mutex reinitialization mutex recursion count owner vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by je vmem je malloc mutex postfork child in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by fork fork c vmmalloc fork log by main vmmalloc fork c vmmalloc fork log mutex was first observed at vmmalloc fork log at pthread mutex init intercept drd pthread intercepts c vmmalloc fork log by pthread mutex init drd pthread intercepts c vmmalloc fork log by je vmem je malloc mutex init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by malloc init hard in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by je vmem pool create in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by libvmmalloc init in home jenkins workspace nvml tests drd src nondebug libvmmalloc so vmmalloc fork log by call init part dl init c vmmalloc fork log by call init dl init c vmmalloc fork log by dl init dl init c vmmalloc fork log by in lib linux gnu ld so vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log by vmmalloc fork log vmmalloc fork log vmmalloc fork log for counts of detected and suppressed errors rerun with v vmmalloc fork log error summary errors from contexts suppressed from log below vmmalloc fork log vmmalloc fork c main vmmalloc fork start vmmalloc fork vmmalloc fork log vmmalloc fork e vmmalloc fork log vmmalloc fork c main vmmalloc fork error assertion failure extension union typeof status in int i in status i vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork signal backtrace vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut sighandler vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so killpg vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so gsignal vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so abort vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork ut out vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork lib linux gnu libc so libc start main vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork start vmmalloc fork log ut backtrace c ut dump backtrace vmmalloc fork vmmalloc fork log ut backtrace c ut sighandler vmmalloc fork vmmalloc fork log runtests stopping vmmalloc fork failed test all fs any build nondebug makefile inc recipe for target failed make error make target pcheck not remade because of errors make leaving directory home jenkins workspace nvml tests drd src test vmmalloc fork makefile recipe for target vmmalloc fork failed make error | 1 |
281,073 | 8,690,428,433 | IssuesEvent | 2018-12-03 21:32:59 | conan-io/conan | https://api.github.com/repos/conan-io/conan | closed | scm get ignore files crashing | complex: low priority: high stage: review type: bug | By an unknown cause, the `excluded_files` function (Conan 1.8.4) during the call to `git check-ignore` is raising a `FileNotFoundError`. Investigate when it can happen. Maybe the `self.folder`? Apparently calling manually it works. But anyway it would be better to just print a warning and ignore the failure, because this is only an optimization. | 1.0 | scm get ignore files crashing - By an unknown cause, the `excluded_files` function (Conan 1.8.4) during the call to `git check-ignore` is raising a `FileNotFoundError`. Investigate when it can happen. Maybe the `self.folder`? Apparently calling manually it works. But anyway it would be better to just print a warning and ignore the failure, because this is only an optimization. | priority | scm get ignore files crashing by an unknown cause the excluded files function conan during the call to git check ignore is raising a filenotfounderror investigate when it can happen maybe the self folder apparently calling manually it works but anyway it would be better to just print a warning and ignore the failure because this is only an optimization | 1 |
609,225 | 18,857,772,690 | IssuesEvent | 2021-11-12 09:00:48 | RE-SS3D/SS3D | https://api.github.com/repos/RE-SS3D/SS3D | closed | Chat is 'hackable': Round Two! | Type: Bug (Unconfirmed) HONK! Coding: C# Priority: 1 - Average Difficulty: 1 - Low System: Communications | ## Summary
Despite efforts to prevent users from customizing their text in the chat, it is still possible. Users should not be able to apply custom formatting to their chat text.
## Current Behavior
Issue #762 described the ability to hack the chat text. PR #779 made it less convenient for users to do so by applying the 'noparse' tags to the chat. However, it is possible to circumvent that measure by closing that tag within the message, then applying the formatting.
The open source nature of SS3D makes us vulnerable to people exploiting our code. We need to ensure that players cannot circumvent our defences *despite* them knowing what measures have been implemented.
## Steps to Reproduce
- While in-game, open the chat window by clicking the chat (speech bubble) icon in the bottom right area of the screen.
- Begin your text with < /noparse > (**without** the spaces), then apply other tags to your chat as described in #762
- Observe that the formatting can be customized.
## Expected Behavior
All user chat should be in the predefined font, colour and size. However, the ability for custom formatting must be maintained for server announcements, events etc.
## Possible Solution
Possibly use a regular expression (regex) to identify and sanitize tags within user input.
## Context
Issue is present in version 0.3.95g | 1.0 | Chat is 'hackable': Round Two! - ## Summary
Despite efforts to prevent users from customizing their text in the chat, it is still possible. Users should not be able to apply custom formatting to their chat text.
## Current Behavior
Issue #762 described the ability to hack the chat text. PR #779 made it less convenient for users to do so by applying the 'noparse' tags to the chat. However, it is possible to circumvent that measure by closing that tag within the message, then applying the formatting.
The open source nature of SS3D makes us vulnerable to people exploiting our code. We need to ensure that players cannot circumvent our defences *despite* them knowing what measures have been implemented.
## Steps to Reproduce
- While in-game, open the chat window by clicking the chat (speech bubble) icon in the bottom right area of the screen.
- Begin your text with < /noparse > (**without** the spaces), then apply other tags to your chat as described in #762
- Observe that the formatting can be customized.
## Expected Behavior
All user chat should be in the predefined font, colour and size. However, the ability for custom formatting must be maintained for server announcements, events etc.
## Possible Solution
Possibly use a regular expression (regex) to identify and sanitize tags within user input.
## Context
Issue is present in version 0.3.95g | priority | chat is hackable round two summary despite efforts to prevent users from customizing their text in the chat it is still possible users should not be able to apply custom formatting to their chat text current behavior issue described the ability to hack the chat text pr made it less convenient for users to do so by applying the noparse tags to the chat however it is possible to circumvent that measure by closing that tag within the message then applying the formatting the open source nature of makes us vulnerable to people exploiting our code we need to ensure that players cannot circumvent our defences despite them knowing what measures have been implemented steps to reproduce while in game open the chat window by clicking the chat speech bubble icon in the bottom right area of the screen begin your text with without the spaces then apply other tags to your chat as described in observe that the formatting can be customized expected behavior all user chat should be in the predefined font colour and size however the ability for custom formatting must be maintained for server announcements events etc possible solution possibly use a regular expression regex to identify and sanitize tags within user input context issue is present in version | 1 |
323,574 | 9,856,769,251 | IssuesEvent | 2019-06-19 23:28:53 | RobotLocomotion/drake | https://api.github.com/repos/RobotLocomotion/drake | closed | Use double precision in tinyobjloader | priority: low team: kitware type: installation and distribution | In https://github.com/RobotLocomotion/drake/tree/master/tools/workspace/tinyobjloader we don't set any definitions, which means that we get `float` precision by default. We should just use `double` so as not to discard digits from the file.
\CC @SeanCurtis-TRI | 1.0 | Use double precision in tinyobjloader - In https://github.com/RobotLocomotion/drake/tree/master/tools/workspace/tinyobjloader we don't set any definitions, which means that we get `float` precision by default. We should just use `double` so as not to discard digits from the file.
\CC @SeanCurtis-TRI | priority | use double precision in tinyobjloader in we don t set any definitions which means that we get float precision by default we should just use double so as not to discard digits from the file cc seancurtis tri | 1 |
54,214 | 3,060,803,693 | IssuesEvent | 2015-08-14 23:28:22 | LemADEC/WarpDrive | https://api.github.com/repos/LemADEC/WarpDrive | opened | Determine whether to revert #b510f84 | Improvement Low Priority | Someone should take a look and see whether it would actually be an improvement | 1.0 | Determine whether to revert #b510f84 - Someone should take a look and see whether it would actually be an improvement | priority | determine whether to revert someone should take a look and see whether it would actually be an improvement | 1 |
734,306 | 25,342,928,767 | IssuesEvent | 2022-11-19 00:09:30 | VocaDB/vocadb | https://api.github.com/repos/VocaDB/vocadb | closed | Signup/login with Facebook | Priority: Low usability security users | Probably similar to current Twitter authentication. Twitter authentication is implemented with DotNetOpenAuth, the code is almost directly from samples (I added some error handling). DotNetOpenAuth should probably be updated, making sure Twitter login still works.
| 1.0 | Signup/login with Facebook - Probably similar to current Twitter authentication. Twitter authentication is implemented with DotNetOpenAuth, the code is almost directly from samples (I added some error handling). DotNetOpenAuth should probably be updated, making sure Twitter login still works.
| priority | signup login with facebook probably similar to current twitter authentication twitter authentication is implemented with dotnetopenauth the code is almost directly from samples i added some error handling dotnetopenauth should probably be updated making sure twitter login still works | 1 |
296,844 | 9,126,559,094 | IssuesEvent | 2019-02-24 22:28:34 | itayo96/luminous-bringers | https://api.github.com/repos/itayo96/luminous-bringers | closed | Play the game and make it harder | finishes low_priority | Play a bit, make the game a little harder maybe, some hard jumps or more enemies. | 1.0 | Play the game and make it harder - Play a bit, make the game a little harder maybe, some hard jumps or more enemies. | priority | play the game and make it harder play a bit make the game a little harder maybe some hard jumps or more enemies | 1 |
670,753 | 22,702,797,661 | IssuesEvent | 2022-07-05 12:16:38 | teogor/teogor.github.io | https://api.github.com/repos/teogor/teogor.github.io | opened | Add `TikTok` account | @UI @priority-low | Add the tiktok account in the 'connect with me section'.
Account -> @teogor.dev | 1.0 | Add `TikTok` account - Add the tiktok account in the 'connect with me section'.
Account -> @teogor.dev | priority | add tiktok account add the tiktok account in the connect with me section account teogor dev | 1 |
593,499 | 18,009,489,508 | IssuesEvent | 2021-09-16 06:47:43 | YangCatalog/sdo_analysis | https://api.github.com/repos/YangCatalog/sdo_analysis | opened | Results should include the validation date | enhancement Priority: Low | IF POSSIBLE, then the pages like https://yangcatalog.org/results/ietf-l2-topology@2020-06-29_ietf.html should also display the date when the validation was executed.
Perhaps based on the file creation date ? | 1.0 | Results should include the validation date - IF POSSIBLE, then the pages like https://yangcatalog.org/results/ietf-l2-topology@2020-06-29_ietf.html should also display the date when the validation was executed.
Perhaps based on the file creation date ? | priority | results should include the validation date if possible then the pages like should also display the date when the validation was executed perhaps based on the file creation date | 1 |
654,365 | 21,648,975,771 | IssuesEvent | 2022-05-06 07:15:33 | Blackoutburst/Wally | https://api.github.com/repos/Blackoutburst/Wally | opened | help command | feature easy low priority | Create a help command with a main help menu displaying the sub menu in embed messages like
- help Hypixel
- help practice
- help misc
- help staff
- help admin
Help staff and admin only display if the user does have the required permission | 1.0 | help command - Create a help command with a main help menu displaying the sub menu in embed messages like
- help Hypixel
- help practice
- help misc
- help staff
- help admin
Help staff and admin only display if the user does have the required permission | priority | help command create a help command with a main help menu displaying the sub menu in embed messages like help hypixel help practice help misc help staff help admin help staff and admin only display if the user does have the required permission | 1 |
720,023 | 24,776,299,601 | IssuesEvent | 2022-10-23 19:24:40 | sjdv1982/seamless | https://api.github.com/repos/sjdv1982/seamless | closed | Mounts in library argument contexts lead to spurious error messages | bug low priority | Tested with a context mapped with map_list
Of the kind:
```
Undestroyed Seamless context: <toplevel> (0x7f0194f3bee0), mount points may remain
```
a long list, when the program exits.
Ignore mounts in context arguments? | 1.0 | Mounts in library argument contexts lead to spurious error messages - Tested with a context mapped with map_list
Of the kind:
```
Undestroyed Seamless context: <toplevel> (0x7f0194f3bee0), mount points may remain
```
a long list, when the program exits.
Ignore mounts in context arguments? | priority | mounts in library argument contexts lead to spurious error messages tested with a context mapped with map list of the kind undestroyed seamless context mount points may remain a long list when the program exits ignore mounts in context arguments | 1 |
91,975 | 3,863,915,516 | IssuesEvent | 2016-04-08 11:40:29 | CoderDojo/community-platform | https://api.github.com/repos/CoderDojo/community-platform | opened | Map Issue when you search fir "EGYPT" | bug dojo listings low priority up-for-grabs | I search for Egypt and it gives me a Dojo in Cyprus. This seems to only happen with this country at the moment.
<img width="1162" alt="screen shot 2016-04-08 at 11 49 25" src="https://cloud.githubusercontent.com/assets/10957621/14382450/c653042c-fd85-11e5-82f8-9c27cda462b2.png">
| 1.0 | Map Issue when you search fir "EGYPT" - I search for Egypt and it gives me a Dojo in Cyprus. This seems to only happen with this country at the moment.
<img width="1162" alt="screen shot 2016-04-08 at 11 49 25" src="https://cloud.githubusercontent.com/assets/10957621/14382450/c653042c-fd85-11e5-82f8-9c27cda462b2.png">
| priority | map issue when you search fir egypt i search for egypt and it gives me a dojo in cyprus this seems to only happen with this country at the moment img width alt screen shot at src | 1 |
16,498 | 2,615,117,394 | IssuesEvent | 2015-03-01 05:42:43 | chrsmith/google-api-java-client | https://api.github.com/repos/chrsmith/google-api-java-client | opened | Google Calendar Data API Android Insert/Edit/Delete Repeating Event | auto-migrated Priority-Low Type-Sample | ```
Which API and version (e.g. Google Calendar Data API version 2)?
Google Calendar Data API 2
What format (e.g. JSON, Atom)?
Atom
What Authentation (e.g. OAuth, OAuth 2, Android, ClientLogin)?
Android
Java environment (e.g. Java 6, Android 2.2, App Engine 1.3.7)?
Android 2.2
External references, such as API reference guide?
Please provide any additional information below.
```
Original issue reported on code.google.com by `andyh...@gmail.com` on 10 Nov 2010 at 12:31 | 1.0 | Google Calendar Data API Android Insert/Edit/Delete Repeating Event - ```
Which API and version (e.g. Google Calendar Data API version 2)?
Google Calendar Data API 2
What format (e.g. JSON, Atom)?
Atom
What Authentation (e.g. OAuth, OAuth 2, Android, ClientLogin)?
Android
Java environment (e.g. Java 6, Android 2.2, App Engine 1.3.7)?
Android 2.2
External references, such as API reference guide?
Please provide any additional information below.
```
Original issue reported on code.google.com by `andyh...@gmail.com` on 10 Nov 2010 at 12:31 | priority | google calendar data api android insert edit delete repeating event which api and version e g google calendar data api version google calendar data api what format e g json atom atom what authentation e g oauth oauth android clientlogin android java environment e g java android app engine android external references such as api reference guide please provide any additional information below original issue reported on code google com by andyh gmail com on nov at | 1 |
723,551 | 24,901,369,211 | IssuesEvent | 2022-10-28 21:19:22 | QuiltMC/quiltflower | https://api.github.com/repos/QuiltMC/quiltflower | closed | Support decompiling jars embedded into executables | enhancement Subsystem: IO Priority: Low | ## Why?
Sometimes it's convenient that when you know an executable contains a valid JAR or ZIP to just run the decompiler pointing to the executable directly. An older Minecraft launcher or server JAR-as-EXE maybe a good candidate to test the implementation. It maybe possible to extend this to jlink images if they share a similar format, perhaps ignoring the bundled stdlib where applicable unless a flag is passed.
## Expected behaviour
`java -jar quiltflower-1.7.0.jar Minecraft.exe ./output`
The above command to be able to find the JAR in the executable and to be able to decompile it.
Of course, when there's no valid JAR to be found, it can exit with an error.
## Actual behaviour
Right now, it just prints the current JVM version and immediately exits without any error or warning. | 1.0 | Support decompiling jars embedded into executables - ## Why?
Sometimes it's convenient that when you know an executable contains a valid JAR or ZIP to just run the decompiler pointing to the executable directly. An older Minecraft launcher or server JAR-as-EXE maybe a good candidate to test the implementation. It maybe possible to extend this to jlink images if they share a similar format, perhaps ignoring the bundled stdlib where applicable unless a flag is passed.
## Expected behaviour
`java -jar quiltflower-1.7.0.jar Minecraft.exe ./output`
The above command to be able to find the JAR in the executable and to be able to decompile it.
Of course, when there's no valid JAR to be found, it can exit with an error.
## Actual behaviour
Right now, it just prints the current JVM version and immediately exits without any error or warning. | priority | support decompiling jars embedded into executables why sometimes it s convenient that when you know an executable contains a valid jar or zip to just run the decompiler pointing to the executable directly an older minecraft launcher or server jar as exe maybe a good candidate to test the implementation it maybe possible to extend this to jlink images if they share a similar format perhaps ignoring the bundled stdlib where applicable unless a flag is passed expected behaviour java jar quiltflower jar minecraft exe output the above command to be able to find the jar in the executable and to be able to decompile it of course when there s no valid jar to be found it can exit with an error actual behaviour right now it just prints the current jvm version and immediately exits without any error or warning | 1 |
5,541 | 2,577,389,911 | IssuesEvent | 2015-02-12 16:45:41 | SiCKRAGETV/sickrage-issues | https://api.github.com/repos/SiCKRAGETV/sickrage-issues | closed | FreeNAS: Symlink Post-Processing Fails Across Datasets | 1: Bug / issue 2: Low Priority 3: Confirmed 3: Fix 5: Duplicate branch: master | **Branch:** master
**Commit hash:** 401cb666016e45b42fe675bafdf7908ad6c2b9bb
**Operating system and python version:** FreeNAS-9.3-STABLE with Python 2.7.6
**What did you do?**
Set my Post-Processing method to Symlink.
**What happened?**
The `moveAndSymlinkFile` function in helpers.py would fail (and revert to copying) on the call to `ek.ek(os.rename, srcFile, destFile)` because my library is in a different dataset than my download folder, and `os.rename` doesn't work across datasets. I temporarily fixed this in my install by passing `shutil.move` as the first parameter in place of `os.rename`. | 1.0 | FreeNAS: Symlink Post-Processing Fails Across Datasets - **Branch:** master
**Commit hash:** 401cb666016e45b42fe675bafdf7908ad6c2b9bb
**Operating system and python version:** FreeNAS-9.3-STABLE with Python 2.7.6
**What did you do?**
Set my Post-Processing method to Symlink.
**What happened?**
The `moveAndSymlinkFile` function in helpers.py would fail (and revert to copying) on the call to `ek.ek(os.rename, srcFile, destFile)` because my library is in a different dataset than my download folder, and `os.rename` doesn't work across datasets. I temporarily fixed this in my install by passing `shutil.move` as the first parameter in place of `os.rename`. | priority | freenas symlink post processing fails across datasets branch master commit hash operating system and python version freenas stable with python what did you do set my post processing method to symlink what happened the moveandsymlinkfile function in helpers py would fail and revert to copying on the call to ek ek os rename srcfile destfile because my library is in a different dataset than my download folder and os rename doesn t work across datasets i temporarily fixed this in my install by passing shutil move as the first parameter in place of os rename | 1 |
71,849 | 3,368,434,444 | IssuesEvent | 2015-11-22 23:20:06 | Apollo-Community/ApolloStation | https://api.github.com/repos/Apollo-Community/ApolloStation | closed | metal sheets in mining don't stack | bug priority: low | the metak compactor doesn't compact the new sheets into stacks they go straight through. it still stacks gold etc. | 1.0 | metal sheets in mining don't stack - the metak compactor doesn't compact the new sheets into stacks they go straight through. it still stacks gold etc. | priority | metal sheets in mining don t stack the metak compactor doesn t compact the new sheets into stacks they go straight through it still stacks gold etc | 1 |
512,301 | 14,893,441,880 | IssuesEvent | 2021-01-21 05:25:51 | kartevonmorgen/kartevonmorgen | https://api.github.com/repos/kartevonmorgen/kartevonmorgen | reopened | Routing: when using left=hide it is turned into left=show | 12 low-priority good first issue | # Problem
~~The URL does always indicate left=show, even if the left sidebare is hidden.~~
The URL should indicate the actual status of the sidebar.
# Solution
- [ ] Default: if no URL Command left=... is given, sidebar should be open
- [ ] The URL-Command &left=hide should only appear, if a user hides the sidebar manually, (or you got a shared link)
- [ ] When you open the sidebar again, the left=... command can be deleted in the URL
# low Relevance
This URL-Command is only important for iframes, and there it is perfectly working!
So no hurry | 1.0 | Routing: when using left=hide it is turned into left=show - # Problem
~~The URL does always indicate left=show, even if the left sidebare is hidden.~~
The URL should indicate the actual status of the sidebar.
# Solution
- [ ] Default: if no URL Command left=... is given, sidebar should be open
- [ ] The URL-Command &left=hide should only appear, if a user hides the sidebar manually, (or you got a shared link)
- [ ] When you open the sidebar again, the left=... command can be deleted in the URL
# low Relevance
This URL-Command is only important for iframes, and there it is perfectly working!
So no hurry | priority | routing when using left hide it is turned into left show problem the url does always indicate left show even if the left sidebare is hidden the url should indicate the actual status of the sidebar solution default if no url command left is given sidebar should be open the url command left hide should only appear if a user hides the sidebar manually or you got a shared link when you open the sidebar again the left command can be deleted in the url low relevance this url command is only important for iframes and there it is perfectly working so no hurry | 1 |
166,294 | 6,302,218,525 | IssuesEvent | 2017-07-21 10:14:03 | BinPar/PRM | https://api.github.com/repos/BinPar/PRM | closed | PRM VD: ¿CÓMO SE HACE RETORNO DE CARRO EN LOS COMENTARIOS? | Priority: Low Venta Directa | 
Si se utiliza la tecla RETURN, se graba el comentario, no se cambia de línea.
@CristianBinpar @minigoBinpar | 1.0 | PRM VD: ¿CÓMO SE HACE RETORNO DE CARRO EN LOS COMENTARIOS? - 
Si se utiliza la tecla RETURN, se graba el comentario, no se cambia de línea.
@CristianBinpar @minigoBinpar | priority | prm vd ¿cómo se hace retorno de carro en los comentarios si se utiliza la tecla return se graba el comentario no se cambia de línea cristianbinpar minigobinpar | 1 |
116,785 | 4,706,562,710 | IssuesEvent | 2016-10-13 17:32:24 | google/grr | https://api.github.com/repos/google/grr | opened | MySQL datastore Warning: Duplicate entry | bug Priority-Low | When running the tests on mysql 5.7 (installed from xenial ubuntu), I get tons of warnings. Since this code hasn't changed in a while I suspect this is just MySQL being more noisy in the newer version.
Sean could you take a look when you get a chance? Might be we need to give some people guidance on how to disable these warnings.
```
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\i\xC1\x18B\xB3\xC7\xB4\x09\xB5\xE2L\xB2_\xCDU' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xB7\x91h\xAE5\xDD}B)J6q~\x19\x9F\xA1' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xB3M\xD7r\xDD_\xEA\x8A\xAA\xBAyl\xEF-\x08\x8E' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry 'QN-\xE0_\x02\xAA\xE3\xDE\xAA\x15z\x12\xDC$\xCA' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\x96\xA8guq\x96\xAB\xC8t`\xF6@\xB0x\xBC\xFA' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\x82y\x1B\x9E\xF0\x15\x11A\x94\x0E\x85\xCE\xA1\xCC`\xA0' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xE5\xD4\x1F\x1F!\xC9t_w\xB3\xAC\x1A\xBD\xE3\xA8\x82' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
Test name: MysqlAdvancedDataStoreTest
...........................................................
----------------------------------------------------------------------
Ran 59 tests in 36.773s
OK
``` | 1.0 | MySQL datastore Warning: Duplicate entry - When running the tests on mysql 5.7 (installed from xenial ubuntu), I get tons of warnings. Since this code hasn't changed in a while I suspect this is just MySQL being more noisy in the newer version.
Sean could you take a look when you get a chance? Might be we need to give some people guidance on how to disable these warnings.
```
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\i\xC1\x18B\xB3\xC7\xB4\x09\xB5\xE2L\xB2_\xCDU' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xB7\x91h\xAE5\xDD}B)J6q~\x19\x9F\xA1' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xB3M\xD7r\xDD_\xEA\x8A\xAA\xBAyl\xEF-\x08\x8E' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry 'QN-\xE0_\x02\xAA\xE3\xDE\xAA\x15z\x12\xDC$\xCA' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\x96\xA8guq\x96\xAB\xC8t`\xF6@\xB0x\xBC\xFA' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\x82y\x1B\x9E\xF0\x15\x11A\x94\x0E\x85\xCE\xA1\xCC`\xA0' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
/grr/grr/grr/lib/data_stores/mysql_advanced_data_store.py:596: Warning: Duplicate entry '\xE5\xD4\x1F\x1F!\xC9t_w\xB3\xAC\x1A\xBD\xE3\xA8\x82' for key 'PRIMARY'
connection.cursor.execute(query["query"], query["args"])
Test name: MysqlAdvancedDataStoreTest
...........................................................
----------------------------------------------------------------------
Ran 59 tests in 36.773s
OK
``` | priority | mysql datastore warning duplicate entry when running the tests on mysql installed from xenial ubuntu i get tons of warnings since this code hasn t changed in a while i suspect this is just mysql being more noisy in the newer version sean could you take a look when you get a chance might be we need to give some people guidance on how to disable these warnings grr grr grr lib data stores mysql advanced data store py warning duplicate entry i xcdu for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry xdd b for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry xdd xea xaa xbayl xef for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry qn xaa xde xaa xdc xca for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry xab xbc xfa for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry xce xcc for key primary connection cursor execute query query grr grr grr lib data stores mysql advanced data store py warning duplicate entry w xac xbd for key primary connection cursor execute query query test name mysqladvanceddatastoretest ran tests in ok | 1 |
258,732 | 8,179,346,429 | IssuesEvent | 2018-08-28 16:06:19 | melsicon/melsicon.de | https://api.github.com/repos/melsicon/melsicon.de | opened | Space around contact section | Priority: Low Type: Enhancement | ### **Type of Issue**
- [ ] Bug
- [X] Enhancement
- [ ] Documentation
- [ ] Maintenance
- [ ] Question
#### Priority
- [X] Low
- [ ] Medium
- [ ] High
- [ ] Critical
## **Description**
The space around the contact section is too cramped
## **Steps to reproduce**
Scroll to contact section
## **Possible Solution**
Add some padding or margin to .section-contact
| 1.0 | Space around contact section - ### **Type of Issue**
- [ ] Bug
- [X] Enhancement
- [ ] Documentation
- [ ] Maintenance
- [ ] Question
#### Priority
- [X] Low
- [ ] Medium
- [ ] High
- [ ] Critical
## **Description**
The space around the contact section is too cramped
## **Steps to reproduce**
Scroll to contact section
## **Possible Solution**
Add some padding or margin to .section-contact
| priority | space around contact section type of issue bug enhancement documentation maintenance question priority low medium high critical description the space around the contact section is too cramped steps to reproduce scroll to contact section possible solution add some padding or margin to section contact | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.