Closed
Bug 1000582
Opened 11 years ago
Closed 7 years ago
Run Sync TPS tests with e10s enabled
Categories
(Testing Graveyard :: TPS, defect)
Testing Graveyard
TPS
Tracking
(e10s+)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: markh, Unassigned)
References
(Blocks 2 open bugs)
Details
Anecdotally, Sync fails when run in e10s, probably due to unrelated session store issues. However, we should arrange for TPS to be able to run with e10s enabled so any issues which affect sync can be identified.
Updated•10 years ago
|
Blocks: e10s-tests
tracking-e10s:
--- → ?
Summary: Run Sync TPS tests with e10s enabled. → Run Sync TPS tests with e10s enabled
Updated•10 years ago
|
Updated•10 years ago
|
No longer blocks: e10s-tests
Updated•10 years ago
|
Blocks: e10s-harness
Comment 1•7 years ago
|
||
I think e10s enabled is now the default...ni? myself to double-check.
Flags: needinfo?(markh)
Updated•7 years ago
|
Flags: needinfo?(markh) → needinfo?(kit)
Reporter | ||
Comment 2•7 years ago
|
||
TBH I'm not sure this bug has value any more - we've probably missed the boat for TPS to help us find issues with sync that are specific to e10s, but we should double-check that TPS doesn't set any e10s related prefs (ie, that TPS runs using the default e10s semantics for whatever it is running on)
Comment 3•7 years ago
|
||
TPS does use default e10s semantics now, so I think this can be closed. \o/
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(kit)
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•