Closed Bug 1617626 Opened 5 months ago Closed 4 months ago

Enable trace level logs for browser-chrome tests in CI

Categories

(Remote Protocol :: Agent, task, P1)

Tracking

(firefox76 fixed)

RESOLVED FIXED
Firefox 76
Tracking Status
firefox76 --- fixed

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

Attachments

(1 file)

To better analyze test failures for remote jobs it would be great to have trace logging enabled for these jobs.

Andrew, what would be the best place these days to set the preference remote.log.level='Trace' for CI jobs? Those tests are part of browser-chrome tests. Maybe it's under testing/profiles/unittest-features?

Flags: needinfo?(ahal)

I'm not really sure.. that seems fine to me. Just double check profiles.json and make sure that profile applies to the suites you expect.

Flags: needinfo?(ahal)

Hm, but when I add the preference there it would apply to each and every mochitest, and not just remote. Another option would be modifying some code for desktop unit tests in mozharness. Changing mochitest runner directly would enable it even for local runs via mach.

Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Priority: P2 → P1

And that looks fine. Trace logs are getting written out.

Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d17e920c25e0
[remote] Enable trace level logs for browser-chrome tests in CI. r=ahal
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 76
You need to log in before you can comment on or make changes to this bug.