Closed Bug 1391350 Opened 4 years ago Closed 1 day ago

[meta] tracking bug for issues related to running tests in non-e10s mode


(Testing :: General, enhancement, P3)



(Not tracked)



(Reporter: jmaher, Unassigned)



(Keywords: meta)

No description provided.
Depends on: 1391363
Depends on: 1391369
Depends on: 1391371
Blocks: 1386689
we are turning on:

Ideally we will be able to for each suite we turned on:
* inspect which tests are unique to non-e10s and follow up with owners to determine what is required to make the tests work in e10s
* assess coverage and determine if there is large areas of code that is non-e10s specific which is only covered by running in non-e10s mode (note: other tests might cover this, android might, or e10s tests might cover it as well)
* file bugs to fix things
* when all things are fixed, only run in e10s mode.
Depends on: 1391376
Depends on: 1391378
Depends on: 1391379
Depends on: 1391380
Depends on: 1391381
Depends on: 1391382
Depends on: 1391383
Depends on: 1391384
Depends on: 1391386
Depends on: 1391387
Depends on: 1391388
in addition we currently run some of our jsdebugger based code coverage on linux64 opt builds and we specifically only run the tests in non-e10s mode- this is for:

I know this isn't web-platform-tests, nor reftest; but our coverage is not as dire as it would seem.  Android does run reftest, so any web-platform-tests that are exercising code in non-e10s mode or non-windows have a chance of lacking coverage.
Priority: -- → P3
Geoff, has there been a change here? I recently found a devtools test skipped in e10s that was no longer passing, so I tried to understand why CI didn't catch this. It looks like almost no tests are running in non-e10s now? Looking at for instance.

Note that I'm not asking for non-e10s tests to be re-enabled, but I'd like to confirm that this is the expected state, so that we can prioritize enabling the ~60 devtools tests still skipped in e10s correctly.
Flags: needinfo?(gbrown)
I'm not aware of a change.

I expect to see most tests running in a non-e10s configuration on linux32/debug only (and Android) and I see that in recent mozilla-central pushes for plain mochitests, plain reftests, wpt, etc. -- but I do not see mochitest-devtools-chrome included there.

I looked back about 6 weeks and saw no relevant scheduling changes.

I am a little surprised we are not running linux32/debug mochitest-devtools-chrome (e10s or not) and I don't immediately see how that is configured. Having a look...
Recall the non-e10s testing issue initially came up in bug 1386689 and was discussed in!topic/ ... although lots has changed since then.

> I am a little surprised we are not running linux32/debug mochitest-devtools-chrome (e10s or not)

Of course it turns out I wrote the patch to do that! (bug 1328915).

So in that sense, this is the expected state: We intentionally do not run linux32/debug mochitest-devtools-chrome, and we intentionally run most non-e10s tests only on linux32/debug.

I haven't read through all the related history. I think it is possible that we did not explicitly decide to stop running non-e10s devtools -- but that's where we are.
Flags: needinfo?(gbrown)
As discussed on IRC, I think this is fine for DevTools, we are making progress on Bug 1387330
Closed: 1 day ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.