lhotari commented on issue #20661: URL: https://github.com/apache/pulsar/issues/20661#issuecomment-1611216464
In forks, the Pulsar CI will activate ssh access to the user that triggered the build. I'm currently trying to find the reason why the failure happens. To investigate integration test failures, there's a possibility to leave docker containers running so that problems can be investigated. This makes only sense when triggering the test manually. Here's an example: ``` # terminate any existing java processes or current running build: pkill java # setup Java 17 export JAVA_HOME=/opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.7-7/x64 export PATH=$JAVA_HOME/bin:$PATH # leave docker containers running after the test completes export PULSAR_CONTAINERS_LEAVE_RUNNING=true TESTCONTAINERS_REUSE_ENABLE=true # run a single test method mvn test -DredirectTestOutputToFile=false -DtestRetryCount=0 -Dspotbugs.skip=true -DintegrationTests -pl tests/integration -Dtest=org.apache.pulsar.tests.integration.io.sinks.PulsarSinksTest#testElasticSearch8Sink # list running containers docker ps ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
