Project

General

Profile

Bug #46624

mgr/dashboard: E2E: Failed to connect to Chrome

Added by Tiago Melo over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Testing & QA
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Some times e2e fails because it can't connect to chrome.

Failed to connect to Chrome, retrying in 1 second (attempt 60/62)
Failed to connect to Chrome, retrying in 1 second (attempt 61/62)
Failed to connect to Chrome, retrying in 1 second (attempt 62/62)
Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

The CDP port requested was 46831.

Error details:

Error: connect ECONNREFUSED 127.0.0.1:46831
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1128:14)

https://jenkins.ceph.com/view/mgr-dashboard/job/ceph-api-nightly-master-e2e/235/consoleFull#-85362248744e9240e-b50a-4693-bac0-8a991bac86ac

History

#2 Updated by Tiago Melo over 3 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 36212

#3 Updated by Tiago Melo over 3 years ago

  • Status changed from Fix Under Review to Resolved

#4 Updated by Ernesto Puerta almost 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 151 to Testing & QA

Also available in: Atom PDF