ARROW-13249: [Java][CI] Consistent timeout in the Java JNI build #10631
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
As you can see, after bumping the timeout a lot, it fails with another error. I would suggest sending an e-mail to the dev mailing-list about JNI CI, and if nobody answers, disable the build. |
kszucs
changed the title
kszucs
commented
Jul 2, 2021
| fail-fast: false | ||
| matrix: | ||
| jdk: [8] | ||
| maven: [3.5.2] |
Member
Author
There was a problem hiding this comment.
The default in .env is 3.5.4
Member
Author
|
After using maven 3.5.4 the build work again. I'm going to reduce the build timeout to 90 minutes so it can rebuild the image on a cache miss. |
Contributor
|
@github-actions crossbow submit test-r-linux-valgrind |
|
Revision: 232aafa Submitted crossbow builds: ursacomputing/crossbow @ actions-562
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The JNI build gets stopped due to build timeout. Seems like the docker cache isn't valid anymore so it must build the docker image as well, but doesn't have the opportunity to push at the and of the build.