Enable some local storage tests for Fission
Categories
(Core :: Storage: localStorage & sessionStorage, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: ytausky, Assigned: ytausky)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
The following tests pass when run with Fission and need to be enabled:
- dom/tests/mochitest/localstorage/test_keySync.html
- dom/tests/mochitest/localstorage/test_localStorageOriginsDiff.html
- dom/tests/mochitest/localstorage/test_localStorageOriginsDomainDiffs.html
- dom/tests/mochitest/localstorage/test_localStorageOriginsEquals.html
- dom/tests/mochitest/localstorage/test_localStorageOriginsPortDiffs.html
- dom/tests/mochitest/localstorage/test_localStorageOriginsSchemaDiffs.html
Note that this has already been done once in bug 1576233, but was reverted in bug 1576814.
Assignee | ||
Comment 1•6 years ago
|
||
These tests now pass when run under Fission.
Comment 2•6 years ago
•
|
||
Yaron, these tests are marked as expected failures. If you run them locally, mochitest.ini is still respected for the fail-if tests (its different for the skip-if tests). So for running them locally, you'll also need to remove the respective fail-if(s) from the mochitest.ini file.
If an expected failing test starts passing in central, we'll see an orange for "unexpected success" and that will get enabled for fission pretty quickly. These tests haven't, indicating there's more work needed here.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Currently these tests pass for me both locally and on try. I'm still trying to figure out why they are not reported as unexpected passes locally and why they seem to fail on some machines.
Comment 5•6 years ago
|
||
bugherder |
Comment 6•6 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•