Skip to content

Commit dc63159

Browse files
jerboaajmartisk
authored andcommitted
Bump the time-out to 4 minutes for NativeImageBundleIT
We see the occasional timeout being reached in our Mandrel CI which tests graal/master builds (GraalVM CE Innovation builds). What's more the CI runs on free GHA runners, with 4 CPU cores and 14GB of memory. Those builds received features which increase build time. For example: - Priority inliner (approx. 30-40% longer build times) oracle/graal#14138 Some successful builds take around up to 2 minutes 50-ish seconds to complete for the said native IT test. We only see failures of the test after this upstream PR merged. This seems in-line with the build time increase. Note that older builds of graal/master from July 2026 took about 2 minutes and 30 seconds at most. (cherry picked from commit e57529f)
1 parent 6549150 commit dc63159

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

integration-tests/maven/src/test/java/io/quarkus/maven/it/NativeImageBundleIT.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ public void testNativeImageBundleCreation() throws MavenInvocationException, IOE
3434

3535
try {
3636
final MavenProcessInvocationResult result = running.execute(mvnArgs, Collections.emptyMap());
37-
await().atMost(3, TimeUnit.MINUTES).until(() -> result.getProcess() != null && !result.getProcess().isAlive());
37+
await().atMost(4, TimeUnit.MINUTES).until(() -> result.getProcess() != null && !result.getProcess().isAlive());
3838

3939
// Check the build was successful with dry run and actual build executed
4040
final String processLog = running.log();

0 commit comments

Comments
 (0)