Closed
Bug 1087647
Opened 10 years ago
Closed 10 years ago
./mach reftest has "Error: Could not find debugger None." in its first few lines of output
Categories
(Firefox Build System :: Mach Core, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla36
People
(Reporter: dholbert, Assigned: Dexter)
Details
Attachments
(1 file, 1 obsolete file)
1.26 KB,
patch
|
Dexter
:
review+
|
Details | Diff | Splinter Review |
STR: 1. Run "./mach reftest". Look at the first few lines of output. ACTUAL RESULTS: The third line of output is: > Error: Could not find debugger None. EXPECTED RESULTS: No such error message; mach shouldn't be trying to find or run a debugger called "None"! Looks like we're initializing "debugger" to None here: http://mxr.mozilla.org/mozilla-central/source/layout/tools/reftest/mach_commands.py?rev=e8559c32028f#217 ...but the error message seems to come from here: http://mxr.mozilla.org/mozilla-central/source/testing/mozbase/mozdebug/mozdebug/mozdebug.py?rev=d29a91fd9c40#105 Not sure where exactly the bug lies. (Presumably somewhere in between those two parts of the code.)
Reporter | ||
Updated•10 years ago
|
Summary: Error: Could not find debugger None. → ./mach reftest has "Error: Could not find debugger None." in its first few lines of output
Comment 1•10 years ago
|
||
Dexter: can you take a look at this? It's not fatal, just annoying.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → alessio.placitelli
Assignee | ||
Comment 2•10 years ago
|
||
This patch fixes the issue by making runreftest.py not call |get_debugger_info| if no debugger name was provided. I've used 2 spaces instead of 4 spaces to conform to local styling. Is this ok?
Attachment #8511527 -
Flags: review?(ted)
Updated•10 years ago
|
Attachment #8511527 -
Flags: review?(ted) → review+
Assignee | ||
Comment 3•10 years ago
|
||
I've updated the commit message by adding the rewiever name.
Attachment #8511527 -
Attachment is obsolete: true
Attachment #8513370 -
Flags: review+
Assignee | ||
Comment 4•10 years ago
|
||
The try push: https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=fe0f5c8a0a88. It contains some failures, which I think may be unrelated.
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 5•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2c5d603aa12f In the future, try to be more conscientious about your Try runs. Given that patch only touched the desktop reftest harness, the vast majority of that Try run was wasted cycles that contribute to backlog pain felt by all developers. The link below has some more recommendations to look at. https://wiki.mozilla.org/Sheriffing/How:To:Recommended_Try_Practices
Keywords: checkin-needed
Comment 6•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2c5d603aa12f
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #5) > In the future, try to be more conscientious about your Try runs. Given that > patch only touched the desktop reftest harness, the vast majority of that > Try run was wasted cycles that contribute to backlog pain felt by all > developers. The link below has some more recommendations to look at. > https://wiki.mozilla.org/Sheriffing/How:To:Recommended_Try_Practices I'm terribly sorry about that. I will be taking more care about this issue next time.
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•