Open
Bug 1319266
Opened 8 years ago
Updated 2 years ago
Intermittent devtools/client/responsive.html/test/browser/browser_page_state.js | Content is still modified from click in viewport - Got transparent, expected rgb(0, 128, 0)
Categories
(DevTools :: Responsive Design Mode, defect, P3)
DevTools
Responsive Design Mode
Tracking
(Not tracked)
NEW
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: intermittent-failure, leave-open, Whiteboard: [rdm-v2])
Filed by: wkocher [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=6981967&repo=autoland https://archive.mozilla.org/pub/firefox/tinderbox-builds/autoland-win64-debug/1479766560/autoland_win8_64-debug_test-mochitest-e10s-devtools-chrome-5-bm126-tests1-windows-build5.txt.gz
Pushed by kwierso@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/976c2f56d46f Skip browser_page_state.js on e10s/Win8 a=me CLOSED TREE
Like bug 1319248, these e10s Win8 tests were all re-enabled today, so these are likely old issues that just never surfaced until now.
Flags: needinfo?(jryans)
Keywords: leave-open
|
||
Comment 3•8 years ago
|
||
This is turning into a bit of a game of whack-a-mole, so I've just disabled the RDM tests at the manifest level for now. You officially have the same amount of Win8 e10s test coverage you started the day with, so I don't think it's a terrible outcome :) https://hg.mozilla.org/integration/mozilla-inbound/rev/cc2b85fdc6259e575242c934cbaa66b2571bf6b9
|
||
Comment 4•8 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/976c2f56d46f
I'll move this to our backlog. Not sure when there'll be time to look more closely, so ni? again if you believe higher priority is needed.
Flags: needinfo?(jryans)
Priority: -- → P3
Whiteboard: [rdm-v2]
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
|
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•