chore(deps): update dependency eslint to ^8.47.0 #48
renovate[bot]per-arch-test.yaml
on: pull_request
frontend
1m 41s
Matrix: Test Linux
Annotations
3 errors
|
visits the app root url.My First Test visits the app root url:
frontend/visits the app root url#L1
The following error originated from your application code, not from Cypress. It was caused by an unhandled promise rejection.
> Cannot use 'in' operator to search for 'tunnels' in <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="icon" href="/favicon.ico">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>AREDN Cloud Node Console</title>
<link id="theme-css" rel="stylesheet" type="text/css" href="/themes/mdc-dark-indigo/theme.css">
<script type="module" crossorigin src="/assets/index-a523e700.js"></script>
<link rel="stylesheet" href="/assets/index-e7af3758.css">
</head>
<body>
<div id="app"></div>
</body>
</html>
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
https://on.cypress.io/uncaught-exception-from-application
|
|
visits the app root url.My First Test visits the app root url:
frontend/visits the app root url#L1
The following error originated from your application code, not from Cypress. It was caused by an unhandled promise rejection.
> Cannot use 'in' operator to search for 'tunnels' in <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<link rel="icon" href="/favicon.ico">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>AREDN Cloud Node Console</title>
<link id="theme-css" rel="stylesheet" type="text/css" href="/themes/mdc-dark-indigo/theme.css">
<script type="module" crossorigin src="/assets/index-a523e700.js"></script>
<link rel="stylesheet" href="/assets/index-e7af3758.css">
</head>
<body>
<div id="app"></div>
</body>
</html>
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
https://on.cypress.io/uncaught-exception-from-application
|
|
visits the app root url.My First Test visits the app root url:
frontend/visits the app root url#L1
The following error originated from your application code, not from Cypress. It was caused by an unhandled promise rejection.
> cannot use 'in' operator to search for "tunnels" in "<!DOCTYPE html>\n..."
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
https://on.cypress.io/uncaught-exception-from-application
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
frontend
Expired
|
21.9 MB |
|