Closed Bug 1376934 Opened 7 years ago Closed 7 years ago

[e10s] Re-identify which tests are skipped under e10s mode

Categories

(Testing :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Felipe, Assigned: Felipe)

References

Details

Attachments

(4 files)

We should find out which tests are skipped under e10s mode (e.g. skip-if=e10s) to figure out what to do with them once we disable non-e10s tests.
I used this old script that I had to find the current tests that are disabled on non-e10s.

The file all-tests.json doesn't exist anymore, it's now all-tests.pkl which needs to be loaded by python's pickle first and rewritten as all-tests.json before running this script.
Attachment #8895546 - Attachment description: 49 mochitest-plain tests disabled → 49 mochitest-plain tests disabled on non-e10s
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Attachment #8895546 - Attachment description: 49 mochitest-plain tests disabled on non-e10s → 49 mochitest-plain tests disabled
Attachment #8895547 - Attachment description: 15 browser-chrome tests disabled on non-e10s → 15 browser-chrome tests disabled
Attachment #8895548 - Attachment description: 86 devtools tests disabled on non-e10s → 86 devtools tests disabled
Note to any curious onlookers that this is only looking at tests that are completely disabled on e10s, not ones that are only partially disabled (like |e10s && debug| and such).
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: