Closed
Bug 961707
Opened 11 years ago
Closed 11 years ago
Add cppunittests as option in TryChooser
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dminor, Assigned: dminor)
References
Details
(Keywords: trychooser)
Attachments
(2 files)
2.05 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
1.92 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
Currently the only way to run cpp unit tests on try is by running all tests. It would be good to have an option to run only the cpp unit tests.
Assignee | ||
Comment 1•11 years ago
|
||
Might as well do this for the jit-tests at the same time.
Summary: Add CPP Unit Tests as an option to TryChooser → Add cppunittests and jittests as options in TryChooser
Assignee | ||
Comment 2•11 years ago
|
||
Should 'cppunittest' and 'jittest' just work without changes to the try syntax parser?
They don't seem to: https://tbpl.mozilla.org/?tree=Try&rev=ab1dda33eae6
Flags: needinfo?(bhearsum)
Comment 3•11 years ago
|
||
cppunit and jittest - not sure where your jit went, unless the parser throws away everything after an unrecognized option, which it might.
Flags: needinfo?(bhearsum)
Assignee | ||
Comment 4•11 years ago
|
||
Thanks, 'cppunit' works fine. 'jittest' doesn't seem to work which might be due to the way it is handled in the build configs (it is added where we want it to run, rather than being removed from where we don't want it to run.)
I'll just do cppunittests for now.
Summary: Add cppunittests and jittests as options in TryChooser → Add cppunittests as option in TryChooser
Assignee | ||
Comment 5•11 years ago
|
||
Updated•11 years ago
|
Attachment #8367292 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 6•11 years ago
|
||
Thanks, pushed to https://hg.mozilla.org/build/tools/rev/0c1f065025cb
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 7•11 years ago
|
||
Oh, no wonder jittest didn't work for you when it did for me (on a -p all push), bug 969988.
Assignee | ||
Comment 8•11 years ago
|
||
Appears to be broken for Android 4.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 9•11 years ago
|
||
As Philor pointed out, we call these cppunittest instead of cppunit on Android so we need a separate line item in the Android section of the page.
Attachment #8386206 -
Flags: review?(bhearsum)
Updated•11 years ago
|
Attachment #8386206 -
Flags: review?(bhearsum) → review+
Assignee | ||
Comment 10•11 years ago
|
||
Thanks, pushed to: https://hg.mozilla.org/build/tools/rev/48ff10b10b22
Comment 11•11 years ago
|
||
Wait, why are we making sure that nearly nobody will actually run them on Android, rather than fixing the name?
Comment 12•11 years ago
|
||
There is actually an alternative to fixing the (broken, incorrect) name, though: just like the way http://mxr.mozilla.org/build/source/buildbotcustom/try_parser.py#14 works around "-u reftest" needing to match reftest, plain-reftest-8 and reftest-10, it could work around that stray unnecessary "test" without any need for a second checkbox nobody will ever remember to check until their second push.
Assignee | ||
Comment 13•11 years ago
|
||
(In reply to Phil Ringnalda (:philor) from comment #11)
> Wait, why are we making sure that nearly nobody will actually run them on
> Android, rather than fixing the name?
Filed bug 980279 to get this fixed.
Assignee | ||
Comment 14•11 years ago
|
||
Looks like the new option is working: https://tbpl.mozilla.org/?tree=Try&rev=ccd3a1fd98d7
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•