Closed Bug 1127920 Opened 5 years ago Closed 5 years ago
This got disabled in bug 1126465 comment 33.
Actually, it looks like the timeout is still 10s, even though I set it to be 60s. Push with failure: https://treeherder.mozilla.org/ui/#/jobs?repo=mozilla-inbound&revision=8d3180c7e7cd Log showing it being killed 10s after starting: https://tbpl.mozilla.org/php/getParsedLog.php?id=57850026&tree=Mozilla-Inbound&full=1 Setting the test to use a long timeout: https://hg.mozilla.org/integration/mozilla-inbound/file/8d3180c7e7cd/testing/web-platform/tests/media-source/mediasource-redundant-seek.html#l5 Am I doing something dumb? What gives?
Flags: needinfo?(bobbyholley) → needinfo?(james)
You need to regenerate the manifest file so that the longer timeout gets picked up. This happens automagically on import but the process for doing it in-tree isn't as smooth as it could be yet. In fact it looks like if you only update a timeout, the manifest generation script won't realise that the file changed, which is unfortunate; I'll fix that as part of the refactor of that code that's currently in progress. In the meantime you could add a "timeout"="long" key/value to the testing/web-platform/meta/MANIFEST.json file for the relevant test or wait a little for me to do the next sync.
Ok. Can you block this bug on whatever bug tracks the next sync, and flip this test back on when you do that? Thanks!
You need to log in before you can comment on or make changes to this bug.