sklochkov2 commented on PR #19754:
URL: https://github.com/apache/druid/pull/19754#issuecomment-5132502047

   Here are the CI errors.
   
   1. Could not acquire shared lock for artifacts: (redacted) in 900 SECONDS; 
consider using 'aether.syncContext.named.time' property to increase lock 
timeout to a value that fits your environment
   2. Error: Process completed with exit code 1. (No details provided).
   3. The action `Execute: .github/scripts/run_unit-tests -Dtest=QTest 
-Dquidem.split=1/4 -Dmaven.test.failure.ignore=true` has timed out after 60 
minutes; it doesn't appear to correspond to any of the code affected by the 
changes.
   4. 
embedded-tests/target/test-classes/org/apache/druid/testing/embedded/indexing/KafkaIndexFaultToleranceTest.class
 | Timed out waiting for event after [240,000]ms.
   5. 
   ```
   [ERROR] Failed to execute goal 
org.codehaus.mojo:exec-maven-plugin:3.5.1:exec (check-licenses) on project 
distribution: Command execution failed. Process exited with an error: 1 (Exit 
value: 1) -> [Help 1]
   [ERROR] 
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR] 
   [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
   [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
   [ERROR] 
   [ERROR] After correcting the problems, you can resume the build with the 
command
   [ERROR]   mvn <args> -rf :distribution
   ```
   None of those appear to point at an exact issue, and I've noticed random 
timeouts when working on the changeset in my own repo as well. @FrankChen021 
can we try re-running failing jobs once to check if it's a fluke or I should 
double check the cause? Thanks in advance!


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to