Travis CI build failing
See original GitHub issueLast two travis builds are failing.
ERROR: /home/travis/build/google/[secure]/BUILD.bazel:202:1: Compiling 13 JavaScript files to compiler-j2cl_dev.js failed: Worker process returned an unparseable WorkResponse!
Did you try to print something to stdout? Workers aren't allowed to do this, as it breaks the protocol between Bazel and the worker process.
---8<---8<--- Exception details ---8<---8<---
com.google.protobuf.InvalidProtocolBufferException: While parsing a protocol message, the input ended unexpectedly in the middle of a field. This could mean either that the input has been truncated or that an embedded message misreported its own length.
...
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Github - Failure: The Travis CI build failed - Stack Overflow
Your build is failing, so something is wrong (unit tests?) as @osowskit said. Please paste your logs from travis (yes, it probably will...
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 icon shows 'failing' but all builds seem succesful #8389
https://travis-ci.org/AqoviaElements/properties-from-ancestor-behavior.svg?branch=master. I see here: icon. But the project doesn't have any failing builds.
Read more >Mark a build "passed with warning" when "allow_failures" jobs ...
Basically, I think that “allow_failures” does not mean “should fail”, so I believe there should be a third state “passed with warning” to ......
Read more >An Explorative Analysis of Travis CI with GitHub - Moritz Beller
The use of multiple integration environments leads to 10% more failures being caught at build time. However, testing on TRAVIS CI does not...
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 FreeTop 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
Top GitHub Comments
From https://github.com/google/closure-compiler/issues/3667, these warnings are possibly significant:
Closing as obsolete since we decided to move to using GitHub actions.