Closed Bug 1356001 Opened 3 years ago Closed 3 years ago

browser chrome tests that stage an update should set MOZ_TEST_SKIP_UPDATE_STAGE in the environment prior to staging.

Categories

(Toolkit :: Application Update, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: rstrong, Unassigned)

References

Details

Attachments

(1 file)

The existing mochitest chrome tests do this since tests that stage have periodically timed out due to having to copy the installation directory... especially on Linux.

https://dxr.mozilla.org/mozilla-central/search?q=MOZ_TEST_SKIP_UPDATE_STAGE&redirect=false
Comment on attachment 8857658 [details]
Bug 1356001 - Set MOZ_TEST_SKIP_UPDATE_STAGE in tests

https://reviewboard.mozilla.org/r/129610/#review132212
Attachment #8857658 - Flags: review?(robert.strong.bugs) → review+
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 1b2c403e3e8b -d 27cee08fb420: rebasing 389533:1b2c403e3e8b "Bug 1356001 - Set MOZ_TEST_SKIP_UPDATE_STAGE in tests r=rstrong" (tip)
merging browser/base/content/test/appUpdate/head.js
warning: conflicts while merging browser/base/content/test/appUpdate/head.js! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
Pushed by rstrong@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/31efcf613615
Set MOZ_TEST_SKIP_UPDATE_STAGE in tests r=rstrong
https://hg.mozilla.org/mozilla-central/rev/31efcf613615
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.