Closed Bug 1591502 Opened 11 months ago Closed 10 months ago

[wpt-sync] Sync PR 19898 - Added task to cleanup Edge regkeys and folders

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox72 fixed)

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Attachments

(1 file)

Sync web-platform-tests PR 19898 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/19898
Details from upstream follow.

Mustapha Jaber <mustjab@windows.microsoft.com> wrote:

Added task to cleanup Edge regkeys and folders

This change fixes issue tracked in #19878 The fix is to cleanup Edge registry and files that can get left behind if uninstall fails. As part of this change we also copy setup log file to help analyze failure and hopefully prevent it from happening in the future.

The change is in cleanup code, requires two runs to confirm it:

Run1 (expect failures): https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=35216
Run2 (expect it to pass): https://dev.azure.com/web-platform-tests/wpt/_build/results?buildId=35218

Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Result changes from PR not available.
Result changes from PR not available.

Automatic update from web-platform-tests
Added task to cleanup Edge regkeys and folders (#19898)

  • Added task to cleanup Edge regkeys and folders

  • Addressed PR feedback

  • Fixed wrong folder name for Canary channel

--

wpt-commits: 436bf315615d923d756067bedbf5f69176582876
wpt-pr: 19898

Result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d96ca44a861e
[wpt PR 19898] - Added task to cleanup Edge regkeys and folders, a=testonly
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.