1617626 - Enable trace level logs for browser-chrome tests in CI

Status: RESOLVED FIXED

(Remote Protocol :: Agent, task, P1)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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?

Comment 2

[Andrew Halberstadt [: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.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Lets try via the mozharness extra-options in the TaskCluster config:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=557b89628b5a3bc64b8d060445b2acb7a888d0d0

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+2]]

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

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: Bug 1617626 - [remote] Enable trace level logs for browser-chrome tests in CI.

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d17e920c25e0
[remote] Enable trace level logs for browser-chrome tests in CI. r=ahal

Comment 8

[Cristina Coroiu [:ccoroiu]]

https://hg.mozilla.org/mozilla-central/rev/d17e920c25e0