Skip to content

CAMEL-23323 - avoid all tests hanging when building with Maven#22606

Merged
apupier merged 1 commit intoapache:mainfrom
apupier:23323-avoidTestHangingInTearDownAndSetup
Apr 14, 2026
Merged

CAMEL-23323 - avoid all tests hanging when building with Maven#22606
apupier merged 1 commit intoapache:mainfrom
apupier:23323-avoidTestHangingInTearDownAndSetup

Conversation

@apupier
Copy link
Copy Markdown
Contributor

@apupier apupier commented Apr 14, 2026

it will avoid build taking several hours and being aborted on Jenkins CI

note that it doesn't solve the root cause of why the test hangs

Description

Previously we used this same property in junit-platform.properties for jms tests. Given that similar issue occurs with other tests, I propose to try to configure it in the maven build level so it can be applied on all kind of tests. I think 10 minutes is in theory enough for all tests

more information on test timeout here https://docs.junit.org/6.0.3/writing-tests/timeouts.html#default-timeouts

Target

  • I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

  • If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

  • I checked that each commit in the pull request has a meaningful subject line and body.
  • I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

@apupier apupier marked this pull request as draft April 14, 2026 10:18
@github-actions
Copy link
Copy Markdown
Contributor

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 14, 2026

🧪 CI tested the following changed modules:

  • parent

⚙️ View full build and test results

@apupier
Copy link
Copy Markdown
Contributor Author

apupier commented Apr 14, 2026

/component-test infinispan

it will avoid build taking several hours and being aborted on Jenkins CI

note that it doesn't solve the root cause of why the test hangs

Signed-off-by: Aurélien Pupier <apupier@ibm.com>
@apupier apupier force-pushed the 23323-avoidTestHangingInTearDownAndSetup branch from a5d20e9 to a82b062 Compare April 14, 2026 11:37
@apupier apupier marked this pull request as ready for review April 14, 2026 12:09
@apupier apupier merged commit 81d5fd5 into apache:main Apr 14, 2026
6 checks passed
@apupier apupier deleted the 23323-avoidTestHangingInTearDownAndSetup branch April 14, 2026 12:09
@apupier
Copy link
Copy Markdown
Contributor Author

apupier commented Apr 14, 2026

for refrence, I modified a test with a thread.sleep in afterAll, it gives this kind of error:

[�[1;31mERROR�[m] org.apache.camel.component.infinispan.remote.cluster.InfinispanRemoteClusteredViewIT -- Time elapsed: 607.6 s <<< ERROR!
java.util.concurrent.TimeoutException: afterAll() timed out after 10 minutes
	at java.base/java.lang.Iterable.forEach(Iterable.java:75)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	Suppressed: java.lang.InterruptedException: sleep interrupted
		at java.base/java.lang.Thread.sleep(Native Method)
		at org.apache.camel.component.infinispan.remote.cluster.InfinispanRemoteClusteredViewIT.afterAll(InfinispanRemoteClusteredViewIT.java:44)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants