Closed
Bug 931926
Opened 12 years ago
Closed 12 years ago
Please schedule cpp unittests on Try
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dminor, Assigned: dminor)
References
Details
Attachments
(1 file, 3 obsolete files)
|
6.20 KB,
patch
|
jgriffin
:
review+
|
Details | Diff | Splinter Review |
There are a pair of cpp unittests which fail consistently on Cedar: see bug 931062 and bug 929985.
These could be resolved through the use of loaner machines, but being able to run them on try would make facillitate developer involvement and would be another step towards being able to remove cpp unittests from make check.
The visibility for these should be hidden for now.
Comment 1•12 years ago
|
||
I assume you still want this too?
cpp unittests enabled on opt but not for fedora, fedora64 https://bugzilla.mozilla.org/show_bug.cgi?id=912192
| Assignee | ||
Comment 2•12 years ago
|
||
kmoir, matching the current scheduling on Cedar should be fine.
Comment 3•12 years ago
|
||
Comment on attachment 824286 [details] [diff] [review]
WIP patch
The way the platforms are configured, this doesn't enable any desktop tests on try. Also, the mobile_config.py part of this patch is part of the work for bug 931874.
Attachment #824286 -
Flags: review?(bugspam.Callek)
Updated•12 years ago
|
Attachment #824286 -
Flags: review?(bugspam.Callek) → review+
Comment 4•12 years ago
|
||
Comment 5•12 years ago
|
||
in production
Comment 6•12 years ago
|
||
Backed out in https://hg.mozilla.org/build/buildbot-configs/rev/31ec4864ebab - this only enabled some of the Cpp tests (debug Mac and Windows, and opt Android, while missing all Linux and opt Mac and Windows), but also enabled Jit tests on Android, which was the one place that we absolutely did not yet want them since they infinitely retry there.
| Assignee | ||
Comment 7•12 years ago
|
||
This is based on kmoir's patch. I consolidated the opt and debug logic. I removed the checks for Fedora as I don't think they are relevant anymore. I also removed the part that enabled jit-tests for Android.
I'm not able to test this locally, but this should at least partially address the problems philor noted.
Assignee: nobody → dminor
Attachment #824286 -
Attachment is obsolete: true
Attachment #8334513 -
Flags: review?(jgriffin)
| Assignee | ||
Comment 8•12 years ago
|
||
Sorry, missed the android changes the first time.
Attachment #8334513 -
Attachment is obsolete: true
Attachment #8334513 -
Flags: review?(jgriffin)
Attachment #8334521 -
Flags: review?(jgriffin)
Comment 9•12 years ago
|
||
Comment on attachment 8334521 [details] [diff] [review]
Enable cpp unittests on try
Review of attachment 8334521 [details] [diff] [review]:
-----------------------------------------------------------------
AFAICT, this will end up scheduling cpp tests on both Fedora and EC2 slaves (like the JIT tests on cedar now), which I don't think is what we want; we'll want to keep the "exclude Fedora" logic.
Attachment #8334521 -
Flags: review?(jgriffin) → review-
| Assignee | ||
Comment 10•12 years ago
|
||
Added back in the check for fedora and fedora64. The reporting on tbpl had changed which lead me to believe we didn't need this anymore.
Attachment #8334521 -
Attachment is obsolete: true
Attachment #8335269 -
Flags: review?(jgriffin)
Comment 11•12 years ago
|
||
Comment on attachment 8335269 [details] [diff] [review]
Enable cpp unittests on try
Review of attachment 8335269 [details] [diff] [review]:
-----------------------------------------------------------------
Great, thanks.
Attachment #8335269 -
Flags: review?(jgriffin) → review+
| Assignee | ||
Comment 12•12 years ago
|
||
Thanks, pushed to https://hg.mozilla.org/build/buildbot-configs/rev/261194f39dac
Status: NEW → ASSIGNED
Comment 13•12 years ago
|
||
something[s] here made it to production
| Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•