question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

uncaught:exception breaks the Gitlab pipeline

See original GitHub issue

Current behavior

When running locally, I can see the exception being thrown and am informed by Cypress about it, however, the tests continue running.

When running it on the pipeline, the output shown gets cut off, and no information is displayed as to why the pipeline failed. image

Here it is stated that only the tests will fail (nothing else is mentioned). https://docs.cypress.io/guides/references/error-messages#Uncaught-exceptions-from-your-application

After I’ve added cy.on('uncaught:exception', () => false); to my test, the pipeline run fine, but this should have nothing to do with the pipeline passing or not in my oppinion.

Desired behavior

The pipeline should continue running, and the reported failed and passed tests should be displayed correctly so that the debugging information can be useful.

Test code to reproduce

Don’t have it as of this time.

Cypress Version

10.7.0

Node version

16.14.0

Operating System

Ubuntu 20.04.5

Debug Logs

No response

Other

No response

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
nemonemicommented, Sep 12, 2022

Yes, I will try to do so in the following days.

0reactions
ZachJW34commented, Sep 20, 2022

Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Pipeline gets broken for no reason - GitLab CI/CD
I think I've got an idea. “build_tagged” job throws an error, because it needs “build_latest”, but “build_latest” doesn't use the same trigger ( ......
Read more >
Ensure after_script is called for cancelled and timed out ...
If pipeline gets aborted while the second line is running, first line will ensure it gets stopped - at some point. Note: all...
Read more >
How to troubleshoot a GitLab pipeline failure
While a failed pipeline is annoying, it's important to remember that “tests can fail for different reasons: some are really bad or some...
Read more >
Troubleshooting CI/CD - GitLab Docs
GitLab provides several tools to help make troubleshooting your pipelines easier. This guide also lists common issues and possible solutions.
Read more >
Handling broken master pipelines - GitLab Docs
This mirror is configured to send pipeline failure notifications to #g_distribution channel on Slack. A broken master pipeline gets priority over other ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found