ci: disable saucelabs tests on Firefox ESR while investigating failures (#37647)
Firefox ESR tests fail running the acceptance tests on saucelabs. These tests are being disabled while investigating the failure as it is not entirely clear whether this is saucelabs failure or a something like a memory pressure error in the test itself. PR Close #37647
This commit is contained in:
parent
34259e90cb
commit
c8c0063499
|
@ -14,7 +14,8 @@
|
|||
var CIconfiguration = {
|
||||
'Chrome': {unitTest: {target: 'SL', required: true}, e2e: {target: null, required: true}},
|
||||
'Firefox': {unitTest: {target: 'SL', required: true}, e2e: {target: null, required: true}},
|
||||
'FirefoxESR': {unitTest: {target: 'SL', required: true}, e2e: {target: null, required: true}},
|
||||
// Set ESR as a not required browser as it fails for Ivy acceptance tests.
|
||||
'FirefoxESR': {unitTest: {target: 'SL', required: false}, e2e: {target: null, required: true}},
|
||||
// Disabled because using the "beta" channel of Chrome can cause non-deterministic CI results.
|
||||
// e.g. a new chrome beta version has been released, but the Saucelabs selenium server does
|
||||
// not provide a chromedriver version that is compatible with the new beta.
|
||||
|
|
Loading…
Reference in New Issue