Closed
Bug 1391172
Opened 7 years ago
Closed 7 years ago
Debug-only tests get skipped in Windows 7 debug try runs
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1388012
People
(Reporter: johannh, Unassigned)
References
(Blocks 1 open bug)
Details
See https://treeherder.mozilla.org/logviewer.html#?job_id=123549421&repo=try&lineNumber=1771 (from bug 1382588, please read that bug for the entire context). The browser-chrome test browser_startup_images.js is marked as debug-only in the test manifest (https://searchfox.org/mozilla-central/rev/5ce320a16f6998dc2b36e30458131d029d107077/browser/base/content/test/performance/browser.ini#9). It gets skipped on Windows 7 automation for debug builds. This has led to backouts already because people can't see the test failing on try and assume they're covered and ready to land. I've written the test and I'm getting pinged by people who assume my test is flaky and are annoyed by having been backed out. It's not fun. Thanks for investigating!
Reporter | ||
Comment 1•7 years ago
|
||
jmaher needinfo'd Ted in bug 1382588, so I'm carrying that ni over. :)
Flags: needinfo?(ted)
Comment 2•7 years ago
|
||
Might be related to --artifact?
Comment 3•7 years ago
|
||
The debug build used for this test job comes from the following task: https://tools.taskcluster.net/groups/HsMm3HwRQR2V_jLKXXyNyg/tasks/ZeZNETzRQJCFpBVnEaB1uQ/details And the problem here is that the mozinfo.json contains "debug: false": https://queue.taskcluster.net/v1/task/ZeZNETzRQJCFpBVnEaB1uQ/runs/0/artifacts/public/build/target.mozinfo.json This makes it a dupe of bug 1388012.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(ted)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•