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.
Travis tests failing
See original GitHub issueTravis tests have failed or errored for the last 16 days, and for 20 of the 21 latest runs in master.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Tests are failing on travis, TypeError but works fine locally
I am running my test on Travis, but I'm currently facing this issue. I have no idea where the problem is coming from....
Read more >Travis build passes, but a test fails · Issue #1006 - GitHub
Found the cause of the bug, the tests exited with exit code 0. ... // process.exit(code || exitCode);. and make a test to...
Read more >I don't know how to tackle "The Travis CI build failed"
@nkumar The failure is in one of the Cypress tests which you can see in the Travis build log (to get to the...
Read more >Build test failing on Travis - Stack Overflow
We've set up Travis on our GitHub repo to test every pull request made, one test out of 73 is failing with a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The
yaml:decodeerror was fixed in the 1.4.5 release of the k8s provider.Confirmed that i have not seen this today in EKS CI.
Still debugging rest of the issues we’re seeing today: