Reenable WebLogic integration tests
:broken_heart: Build Failed
the below badges are clickable and redirect to their specific view in the CI or DOCS
![]()
![]()
![]()
![]()
![]()
Expand to view the summary
Build stats
-
Start Time: 2023-07-03T11:39:26.880+0000
-
Duration: 20 min 20 sec
Steps errors 
Expand to view the steps failures
mvn install
- Took 5 min 26 sec . View more details here
- Description:
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
mvn install
- Took 2 min 23 sec . View more details here
- Description:
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
mvn install
- Took 2 min 23 sec . View more details here
- Description:
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
mvn install
- Took 2 min 22 sec . View more details here
- Description:
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
mvn install
- Took 2 min 22 sec . View more details here
- Description:
./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true
:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments
To re-run your PR in the CI, just comment with:
-
/test: Re-trigger the build. -
run benchmark tests: Run the benchmark tests. -
run jdk compatibility tests: Run the JDK Compatibility tests. -
run integration tests: Run the Agent Integration tests. -
run end-to-end tests: Run the APM-ITs. -
run windows tests: Build & tests on windows. -
runelasticsearch-ci/docs: Re-trigger the docs validation. (use unformatted text in the comment!)
/test
Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as stalled to make it hit our filters and make sure we get back to it in as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!
Hi! This issue has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this issue if you think it should stay open. Thank you for your contribution!