Skip to content
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

Improve error message and fail behavior of ParallelBuildChainTest #657 #658

Merged
merged 2 commits into from
Sep 11, 2023

Conversation

HeikoKlare
Copy link
Contributor

The ParallelBuildChainTest has some flaws in error message design and failure handling, which are addressed by this change:

  1. The timeout for builds to start/finish is higher than the execution time of a long running build. Thus in case builds are unexpectedly not run in parallel, the assertion for timely build start/finish is not evaluated as expected.
  2. In case an error occurs before starting a build operation, the number of expected builds in the TimerBuilder may be higher than the number of builds that will every be executed. Since the TimerBuilder abortion tries to wait for all expected builds indefinitely, the operation (and thus test tear down) may never terminate.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 4, 2023

Test Results

       42 files  ±0         42 suites  ±0   54m 22s ⏱️ - 4m 15s
  3 770 tests ±0    3 766 ✔️ +1    3 💤 ±0  1 ±0 
11 313 runs  ±0  11 283 ✔️ +1  27 💤 ±0  3 ±0 

For more details on these failures, see this check.

Results for commit 1bbae07. ± Comparison against base commit 90105ec.

♻️ This comment has been updated with latest results.

@HeikoKlare HeikoKlare marked this pull request as ready for review September 5, 2023 05:59
@HeikoKlare HeikoKlare force-pushed the issue-657 branch 5 times, most recently from 8aa9977 to 6140002 Compare September 11, 2023 09:40
…ipse-platform#657

The ParallelBuildChainTest has some flaws in error message design and
failure handling, which are addressed by this change:
1. The timeout for builds to start/finish is higher than the execution
time of a long running build. Thus in case builds are unexpectedly not
run in parallel, the assertion for timely build start/finish is not
evaluated as expected.
2. In case an error occurs before starting a build operation, the number
of expected builds in the TimerBuilder may be higher than the number of
builds that will every be executed. Since the TimerBuilder abortion
tries to wait for all expected builds indefinitely, the operation (and
thus test tear down) may never terminate.
@HeikoKlare
Copy link
Contributor Author

Failing test documented in #668.

@HeikoKlare HeikoKlare merged commit 3baaffe into eclipse-platform:master Sep 11, 2023
@HeikoKlare HeikoKlare deleted the issue-657 branch September 11, 2023 10:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant