Closed Bug 558777 (darwin_unittests) Opened 11 years ago Closed 11 years ago
Tracking bug for running unit tests on darwin talos machines and disabling unittests on build slaves
There is too many bugs on bug 548768 and it is difficult to have the big picture of each platform. We can add the summary updates for Leopard and Snow Leopard in here. The current status update is the following: * Leopard unit tests are currently running on talos slaves for mozilla-central * Snow Leopard is not currently running (I thought it was) unit tests. See bug 558776. * We want to disable unit tests for mozilla-central on build machines. See bug 557921. ** We will do so this week * We want to enable unit tests for all other branches ** This requires more Rev 3 machines
Depends on: 558501
10.6 unit tests are not running because of bug 559182 (not uploading the package test).
Depends on: 559182
10.6 unit tests are now running only for "opt" builds (thanks to bug 559182) and only for a subset of the test suites. To fix the rest of the test suites for "opt" builds I have filed bug 559824. To disable the debug unit tests I have filed bug 559826.
Added bug 559824 to check that all 10.6 oranges have been filed.
* Reftests (opt/debug) for 10.6 are now fixed thanks to bug 550335#c7 and showing on the waterfall
Summary: Tracking bug for running unit tests on darwin talos machines → Tracking bug for running unit tests on darwin talos machines and disabling unittests on build slaves
Depends on: 568479
Depends on: 570816
philor landed bug 561354 and unhid the jsreftests. I noticed that mochitest-plain-5/5 was also green, and unhid that too. That leaves xpcshell and mochitest-plain-1/5 as still hidden. The one xpcshell problem is bug 561350. However, it looks like there are at least two problems with mochitest-plain-1/5, and I don't see any dependencies of this bug for any of them (though I could be missing something). It's probably worth getting bugs on file for these -- it might help lead to progress, in that there's something to point people to when asking if they can help. In particular, of the last 5 debug and 5 opt runs: (a) the 3 debug runs and 4 opt runs that made it to shutdown timed out during shutdown rather than shutting down cleanly: TEST-UNEXPECTED-FAIL | Shutdown | application timed out after 330 seconds with no output (b) all 10 had: 51263 ERROR TEST-UNEXPECTED-FAIL | /tests/content/media/test/test_playback_errors.html | Test timed out. There were some other problems that were more intermittent; they may match existing intermittent orange bugs.
I don't see any sign of a dependency on bug 494028 - we've had reftests unhidden for quite a while now.
No longer depends on: 494028
Filed bug 573405 for test_playback_errors.html
Unhid Md1/Mo1, since it looks like the shutdown timeout and the intermittent other failures (which weren't known oranges, at least not most of them) were fallout from the way the test was attempting to allocate 3.1TB, and being unhappy not getting it.
We've long since disabled all mac unit tests on build machines. Calling this fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.