kokoro-macos/continuous builds failing
See original GitHub issueIt seems there’s an issue on macOS where consecutive builds introduce a slowdown, which causes the test to fail.
[ERROR] testExecute_empty(com.google.cloud.tools.jib.maven.BuildImageMojoIntegrationTest) Time elapsed: 20.664 s <<< FAILURE!
java.lang.AssertionError: First build time (8728749621) is not greater than second build time (9143508245)
at com.google.cloud.tools.jib.maven.BuildImageMojoIntegrationTest.buildAndRun(BuildImageMojoIntegrationTest.java:67)
at com.google.cloud.tools.jib.maven.BuildImageMojoIntegrationTest.testExecute_empty(BuildImageMojoIntegrationTest.java:129)
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Remove the legacy OpenGL ES and EGL implementations ...
This change marks the OpenGL ES build targets for CMake as deprecated. The legacy code is unmaintained as is being replaced by "SwANGLE",...
Read more >Question - Android build failing on unity 2022.1.0a15
When building for android, I get this IL2CPP error Building Library\Bee\artifacts\Android\d8kzr\b22p_cMethods19.o failed with output:...
Read more >D12001 Update google-cloud-sdk to 360.0.0 - Solus
Harbormaster completed remote builds in B1965: Diff 29159. ... -cloud-sdk/platform/gsutil_py2/test/ci/kokoro/macos/continuous.cfg</Path>.
Read more >koji builds failing with "GenericError: Build already in progress ...
I have seen this a few times lately. When a build is started for rawhide, and in succession builds for other branches, they...
Read more >Bug #1642317 “armhf build fails” : Bugs : Oxide
This doesn't seem to affect cross builds, but only archive builds: [13145/19378] python ../../v8/tools/run.py .
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 my testing, seems like we can work around the certificate error by following the simple trick documented in the bug (just restarting the Docker daemon). It may take a long time for the Kokoro team to apply and roll out a permanent fix, so let’s just restart Docker on our side as a temporary fix. I’ll work on this.
Closing as this is basically not happening anymore.