Closed Bug 1276296 Opened 8 years ago Closed 8 years ago

Unexpected assertions when running Autophone WebRTC job on debug builds on Try

Categories

(Testing Graveyard :: Autophone, defect)

Version 3
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dminor, Assigned: bc)

References

Details

When running the WebRTC job on Try with debug builds, the first test run fails with "Assertion count 12 is greater than expected range 0-0 assertions." It doesn't seem to matter which test is run first, if I introduce a "no-op" test job, it will fail with 12 assertions [1]. This failure does not show up when the tests are run on mozilla-central [2]. A work around is to add expected assertions to the no-op test [3]. [1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=8fbc69a9e12af71427b37a9c56a59afe9e269f62&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=21580722 [2] https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&filter-tier=3&selectedJob=3960672&selectedJob=21580398 [3] https://treeherder.mozilla.org/#/jobs?repo=try&revision=78bcaab5d7a46b8d446a7af1958372c845249922&filter-tier=1&filter-tier=2&filter-tier=3
Depends on: 1295138
dminor: Can you test this again? This should be fixed by bug 1295138.
nevermind, I need to run the other tests to make sure everyone is green. https://treeherder.mozilla.org/#/jobs?repo=try&revision=7cb770f17813
The try run didn't initiate any autophone tests for some reason. I'll look into it more later.
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.