[SERVER-36750] blacklist memory.js on ppc64le in memory variants Created: 17/Aug/18 Updated: 08/Jan/24 Resolved: 22/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.21, 3.6.12, 4.0.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Gabriel Russell (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.6, v3.4
|
||||||||||||
| Sprint: | Dev Tools 2018-12-31, Dev Tools 2019-01-14, Dev Tools 2019-01-28, Dev Tools 2019-02-25, Dev Tools 2019-03-11, Dev Tools 2019-03-25 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 13 | ||||||||||||
| Description |
|
memory.js can timeout in its $where when filling up memory on the ppc64le in memory variants. We don't need to run it there, and probably shouldn't |
| Comments |
| Comment by Githook User [ 04/Apr/19 ] |
|
Author: {'email': 'gabriel.russell@mongodb.com', 'name': 'Gabriel Russell', 'username': 'gabrielrussell'}Message: |
| Comment by Githook User [ 25/Mar/19 ] |
|
Author: {'name': 'Gabriel Russell', 'username': 'gabrielrussell', 'email': 'gabriel.russell@mongodb.com'}Message: |
| Comment by Githook User [ 25/Mar/19 ] |
|
Author: {'email': 'gabriel.russell@mongodb.com', 'name': 'Gabriel Russell', 'username': 'gabrielrussell'}Message: |
| Comment by Githook User [ 22/Mar/19 ] |
|
Author: {'email': 'gabriel.russell@mongodb.com', 'name': 'Gabriel Russell', 'username': 'gabrielrussell'}Message: |
| Comment by Gabriel Russell (Inactive) [ 14/Mar/19 ] |
|
Waiting for 4.0 code freeze to end. |
| Comment by Gabriel Russell (Inactive) [ 06/Feb/19 ] |
|
This has reoccurred on v3.4 and v4.0. If this wasn't fixed by the moz-60 upgrade then it was fixed by Jasons js interruption fixes. I'll just proceed with the original solution in this ticket, and blacklist this test, albeit just for v3.4 and v4.0 |