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

Reduce number of parallel builds in ParallelBuildChainTest #825 #1387

Merged
merged 1 commit into from
May 21, 2024

Conversation

HeikoKlare
Copy link
Contributor

The test case testIndividualProjectBuilds_WithManyProjects_ProjectRelaxedRule() in ParallelBuildChainTest fails randomly (in I-Builds) because not all jobs that are supposed to run build operations are scheduled and started in time. Since the test is not supposed to validate that a specific number of jobs can be started, the number of jobs/builds to be spawned must actually not be as high as currently defined. This change reduces the number of projects in the test case to avoid random test failures while keeping expressiveness of the test case.

Fixes #825

Copy link
Contributor

github-actions bot commented May 21, 2024

Test Results

 1 737 files  ±0   1 737 suites  ±0   1h 23m 8s ⏱️ - 6m 39s
 3 972 tests ±0   3 950 ✅ ±0   22 💤 ±0  0 ❌ ±0 
12 513 runs  ±0  12 352 ✅ ±0  161 💤 ±0  0 ❌ ±0 

Results for commit f865814. ± Comparison against base commit 40c9740.

♻️ This comment has been updated with latest results.

@HeikoKlare HeikoKlare force-pushed the issue-825 branch 2 times, most recently from 751d569 to ce1bf6b Compare May 21, 2024 15:42
…atform#825

The test case
testIndividualProjectBuilds_WithManyProjects_ProjectRelaxedRule() in
ParallelBuildChainTest fails randomly (in I-Builds) because not all jobs
that are supposed to run build operations are scheduled and started in
time. Since the test is not supposed to validate that a specific number
of jobs can be started, the number of jobs/builds to be spawned must
actually not be as high as currently defined. This change reduces the
number of projects in the test case to avoid random test failures while
keeping expressiveness of the test case.

Fixes eclipse-platform#825
@HeikoKlare HeikoKlare marked this pull request as ready for review May 21, 2024 18:16
@HeikoKlare
Copy link
Contributor Author

Build failure is only because of new deprecation issue because of gson version increment: eclipse-platform/eclipse.platform.releng.aggregator#2036

Triggered build for master reports the same new issue: https://ci.eclipse.org/platform/job/eclipse.platform/job/master/847/

Jenkins reference build has been updated but was not properly taken into account for this PR build, which is still compared against the previous master build.

Change only affects test, thus merging despite freeze period.

@HeikoKlare HeikoKlare merged commit 15c6f84 into eclipse-platform:master May 21, 2024
12 of 16 checks passed
@HeikoKlare HeikoKlare deleted the issue-825 branch May 21, 2024 18:19
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.

Random failing ParallelBuildChainTest.testIndividualProjectBuilds_WithManyProjects_ProjectRelaxedRule
1 participant