raptor-tp6-imgur-chrome fails to load with latest Chromium update
Categories
(Testing :: Raptor, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: rwood, Unassigned)
References
Details
With the latest Chromium update in Bug 1520523, raptor-tp6-imgur-chrome fails to load. That test is temporarily disabled until the Chromium issue is fixed. Once a new Chromium is available that loads that page, re-enable the test.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Unassigning myself from this Bug because of Bug 1603557 - TypeError: environment can only contain strings, which is blocking development on WIndows.
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Now (25-Feb-2020) there is no need to change the code, because latest Chromium is already used in our tests (see Restore daily Chromium updates for Windows).
So, to prove that there is no issue, a try
push with
test-linux64-shippable/opt-raptor-tp6-3-chrome-e10s
test-windows7-32-shippable/opt-raptor-tp6-3-chrome-e10s
test-windows10-64-shippable/opt-raptor-tp6-3-chrome-e10s
test-linux64-shippable/opt-raptor-tp6-9-chrome-cold-e10s
test-windows7-32-shippable/opt-raptor-tp6-9-chrome-cold-e10s
test-windows10-64-shippable/opt-raptor-tp6-9-chrome-cold-e10s
test-macosx1014-64-shippable/opt-raptor-tp6-9-chrome-cold-e10s
was done. Results here
Notice: because at this moment the try
pushes doesn't work on Windows, I applied the fix from this Bug prior to pushing to try
.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Since this bug was filed we started running tests on Chrome in addition to Chromium, and jobs were renamed appropriately. Octavian: can you make sure we dont have any issues with this test running on Chromium and update the status appropriately?
Comment 4•5 years ago
|
||
Sure, with pleasure.
Do you mean that I should trigger a try
push with Cromium
tests, right?
Only once or from time to time?
Comment 5•5 years ago
|
||
ALl that needed to be done here is check to see if the test was sitll disabled. Looking at the test config, it's been enabled and running since bug 1559932 was resolved.
Description
•