mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-23 09:52:26 +01:00
Ignore 4Byte 502 errors during e2e tests (#13204)
The 4Byte API can sometimes fail during e2e tests with a 502 error. Ideally we would avoid calling it at all during e2e tests, but in the meantime we shouldn't treat this as a reason to fail the e2e test. We have multiple fallbacks for 4Byte, it isn't relied upon by any tests.
This commit is contained in:
parent
c266d4e6af
commit
8e835b1d78
@ -361,6 +361,8 @@ class Driver {
|
|||||||
'favicon.ico - Failed to load resource: the server responded with a status of 404 (Not Found)',
|
'favicon.ico - Failed to load resource: the server responded with a status of 404 (Not Found)',
|
||||||
// Sentry rate limiting
|
// Sentry rate limiting
|
||||||
'Failed to load resource: the server responded with a status of 429',
|
'Failed to load resource: the server responded with a status of 429',
|
||||||
|
// 4Byte
|
||||||
|
'Failed to load resource: the server responded with a status of 502 (Bad Gateway)',
|
||||||
];
|
];
|
||||||
const browserLogs = await this.driver.manage().logs().get('browser');
|
const browserLogs = await this.driver.manage().logs().get('browser');
|
||||||
const errorEntries = browserLogs.filter(
|
const errorEntries = browserLogs.filter(
|
||||||
|
Loading…
x
Reference in New Issue
Block a user