Closed Bug 1557122 Opened 5 years ago Closed 5 years ago

Perma test_ext_storage_cleanup.html | Undefined value! - "tracker-0.3787650295256073" == "undefined" - | localStorage data was cleared - got true, expected false - when Gecko 69 merges to Beta on 2019-07-01

Categories

(WebExtensions :: General, defect)

defect
Not set
normal

Tracking

(geckoview66 unaffected, firefox-esr60 unaffected, firefox67 unaffected, firefox67.0.1 unaffected, firefox68 unaffected, firefox69- fixed)

RESOLVED DUPLICATE of bug 1556093
Tracking Status
geckoview66 --- unaffected
firefox-esr60 --- unaffected
firefox67 --- unaffected
firefox67.0.1 --- unaffected
firefox68 --- unaffected
firefox69 - fixed

People

(Reporter: aryx, Unassigned)

Details

(Keywords: regression)

Does this regression go away if https://hg.mozilla.org/mozilla-central/rev/9cd79017eae8 is backed out?

(In reply to :Ehsan Akhgari from comment #1)

Does this regression go away if https://hg.mozilla.org/mozilla-central/rev/9cd79017eae8 is backed out?

I backed out all three parts of bug 1555564 locally and this regression still doesn't go away. So I don't think this has any relationship with bug 1556093 besides both hitting tests with "storage" in their names.

It would be nice if this failure was bisected separately from bug 1556093 to get to its cause.

No longer depends on: 1555562, 1556093

I've took a look at the failure logs, but unfortunately it doesn't seem to contain any useful clue about what is happening.

The test_ext_storage_cleanup.html tests are verifying that, when an extension is uninstalled, the data stored by the extension in the various storage APIs available to an extension page are all being cleared, and the linked failures logs seem to be both be happening in the test_uninstall_with_webapi_storages task, which is testing that the webAPI storages (localStorage and IndexedDB) are being cleared.

The failure suggests that the data stored in the localStorage web API have not been cleared after the test extension has been fully uninstalled, but the failure logs (at least at a first glance) are not providing any useful info about the underlying reason.

I tried to reproduce it locally but without any luck yet.

:aryx is this still happening in beta simulations even after the fix landed for Bug 1556093?

Flags: needinfo?(lgreco) → needinfo?(aryx.bugmail)
Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(aryx.bugmail)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.