-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure of test FatJarExportTests.exportInternalLib #699
Comments
fedejeanne
added a commit
to fedejeanne/eclipse.jdt.ui
that referenced
this issue
Sep 20, 2023
Give it a max of 30s per test instead of 5s. This doesn't slow down the tests execution, it just lets the tests run a bit longer if the hardware is slow. Fixes eclipse-jdt#699
fedejeanne
added a commit
to fedejeanne/eclipse.jdt.ui
that referenced
this issue
Sep 21, 2023
Give it a max of 30s per test instead of 5s. This doesn't slow down the tests execution, it just lets the tests run a bit longer if the hardware is slow. Fixes eclipse-jdt#699
github-actions bot
pushed a commit
to fedejeanne/eclipse.jdt.ui
that referenced
this issue
Sep 21, 2023
Give it a max of 30s per test instead of 5s. This doesn't slow down the tests execution, it just lets the tests run a bit longer if the hardware is slow. Fixes eclipse-jdt#699
jjohnstn
pushed a commit
that referenced
this issue
Sep 21, 2023
) Give it a max of 30s per test instead of 5s. This doesn't slow down the tests execution, it just lets the tests run a bit longer if the hardware is slow. Fixes #699
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test just failed in this CI-Build of #675 .
It seems to be unrelated to the changes in the PR since it happened after a rebase (no changes were made to the code).
Stack-Trace:
The text was updated successfully, but these errors were encountered: