Closed
Bug 1123945
Opened 10 years ago
Closed 10 years ago
mach mochitest-chrome --no-autorun won't allow running
Categories
(Testing :: Mochitest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla38
People
(Reporter: jryans, Assigned: jryans)
Details
Attachments
(1 file)
1005 bytes,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
If I use the command
mach mochitest-chrome browser/devtools/webide --no-autorun
then clicking the button to actually run fails with:
JavaScript error: chrome://mochikit/content/tests/SimpleTest/setup.js, line 253: TypeError: RunSet is undefined
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8552058 -
Flags: review?(jmaher)
Comment 2•10 years ago
|
||
Comment on attachment 8552058 [details] [diff] [review]
0002-Bug-1123945-Fix-no-autorun-harness-option.-r-jmaher.patch
Review of attachment 8552058 [details] [diff] [review]:
-----------------------------------------------------------------
I like most of this, but I do want to learn more before r+.
::: testing/mochitest/tests/SimpleTest/setup.js
@@ +58,5 @@
> }
>
> if (config.testRoot == "chrome" || config.testRoot == "a11y") {
> + for (let p in params) {
> + if (params[p] == [1]) {
I don't understand the [1] and [0], is there a specific javascript feature for this?
Attachment #8552058 -
Flags: review?(jmaher) → review-
Assignee | ||
Comment 3•10 years ago
|
||
Comment on attachment 8552058 [details] [diff] [review]
0002-Bug-1123945-Fix-no-autorun-harness-option.-r-jmaher.patch
Review of attachment 8552058 [details] [diff] [review]:
-----------------------------------------------------------------
::: testing/mochitest/tests/SimpleTest/setup.js
@@ +58,5 @@
> }
>
> if (config.testRoot == "chrome" || config.testRoot == "a11y") {
> + for (let p in params) {
> + if (params[p] == [1]) {
No, nothing that magical.
|parseQueryString| is called with useArrays: true, so it puts each query param's value in an array, I think to allow for multiple values with the same param name?
I'll confess I don't understand what's expected to happen here at all, so I was mostly just flailing to get this to work. :)
I looked through version history, but did not see any recent changes to explain why this broke... so I tried to make what seemed like the smallest change possible.
Assignee | ||
Comment 4•10 years ago
|
||
See comment 3. Maybe a different approach is needed? Not sure.
Flags: needinfo?(jmaher)
Comment 5•10 years ago
|
||
I see where you get it. have you tested this patch with mochitest-plain? on try server to see what android and b2g do?
Assuming this works for everything, I would like a small comment explaining why we are comparing to an array. This wouldn't make sense just reading it a year from now, without some context in this bug.
Flags: needinfo?(jmaher)
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Comment 7•10 years ago
|
||
Seems some contexts don't load the file with "let" support. For such a small change, I've just gone back to "var".
Let's see what happens.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=09555dbc59aa
Comment 8•10 years ago
|
||
Comment on attachment 8552058 [details] [diff] [review]
0002-Bug-1123945-Fix-no-autorun-harness-option.-r-jmaher.patch
Review of attachment 8552058 [details] [diff] [review]:
-----------------------------------------------------------------
please add a comment to the code to indicate why you have the []
Attachment #8552058 -
Flags: review- → review+
Assignee | ||
Comment 9•10 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #8)
> Comment on attachment 8552058 [details] [diff] [review]
> 0002-Bug-1123945-Fix-no-autorun-harness-option.-r-jmaher.patch
>
> Review of attachment 8552058 [details] [diff] [review]:
> -----------------------------------------------------------------
>
> please add a comment to the code to indicate why you have the []
Thanks! I've got a comment in the one[1] on Try now. Was going to re-request review once I was sure it looked good, but this works too! :)
Looking okay, except for some kind of Mac build failure, waiting on a rebased Try run to confirm.
[1]: https://hg.mozilla.org/try/rev/9bda75f63db7
Assignee | ||
Comment 10•10 years ago
|
||
With the additional run[1], it looks like the Mac issues were fixed after rebase.
[1]: https://treeherder.mozilla.org/#/jobs?repo=try&revision=d796ff6e72ff
Assignee | ||
Comment 11•10 years ago
|
||
Whiteboard: [fixed-in-fx-team]
Comment 12•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla38
Updated•7 years ago
|
Component: Mochitest Chrome → Mochitest
You need to log in
before you can comment on or make changes to this bug.
Description
•