Closed Bug 1636556 Opened 6 years ago Closed 6 years ago

Intermittent tools/profiler/tests/browser/browser_test_feature_jsallocations.js | Allocations were recorded for the parent process' main thread when the JS Allocation feature was turned on. - 0 > 0 -

Categories

(Core :: Gecko Profiler, defect, P5)

Product:
Core
Component:
Gecko Profiler
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Assigned: mozbugz)

References

Details

(Keywords: intermittent-failure)

Filed by: archaeopteryx [at] coole-files.de
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=301409184&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/d0QT605zRzWMsSUGLR1h7Q/runs/0/artifacts/public/logs/live_backing.log

[task 2020-05-08T13:28:22.398Z] 13:28:22 INFO - Entering test bound test_profile_feature_jsallocations
[task 2020-05-08T13:28:22.398Z] 13:28:22 INFO - TEST-PASS | tools/profiler/tests/browser/browser_test_feature_jsallocations.js | The profiler is not currently active - true == true -
[task 2020-05-08T13:28:22.399Z] 13:28:22 INFO - Buffered messages finished
[task 2020-05-08T13:28:22.399Z] 13:28:22 INFO - TEST-UNEXPECTED-FAIL | tools/profiler/tests/browser/browser_test_feature_jsallocations.js | Allocations were recorded for the parent process' main thread when the JS Allocation feature was turned on. - 0 > 0 - JS frame :: chrome://mochitests/content/browser/tools/profiler/tests/browser/browser_test_feature_jsallocations.js :: test_profile_feature_jsallocations/< :: line 40
[task 2020-05-08T13:28:22.399Z] 13:28:22 INFO - Stack trace:
[task 2020-05-08T13:28:22.399Z] 13:28:22 INFO - chrome://mochitests/content/browser/tools/profiler/tests/browser/browser_test_feature_jsallocations.js:test_profile_feature_jsallocations/<:40
[task 2020-05-08T13:28:22.399Z] 13:28:22 INFO - TEST-PASS | tools/profiler/tests/browser/browser_test_feature_jsallocations.js | Allocations were recorded for the content process' main thread when the JS Allocation feature was turned on. - 56 > 0 -

No more failures since bug 1636398 landed.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Assignee: nobody → gsquelart
You need to log in before you can comment on or make changes to this bug.