[
https://issues.apache.org/jira/browse/KUDU-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901616#comment-17901616
]
Alexey Serbin commented on KUDU-3616:
-------------------------------------
At least, there are some issues with concurrently using the same workspace at
Jenkins executor nodes by different tasks. The attached file shows that a TSAN
build was running in {{/home/jenkins-slave/workspace/build_and_test@3}}, but at
the time of submitting Java tests via dist-test it was suddenly looking up JARs
in the {{/home/jenkins-slave/workspace/build_and_test@3/build/release/bin}}
directory:
{noformat}
org.apache.kudu.client.TestSplitKeyRange lstat
/home/jenkins-slave/workspace/build_and_test@3/build/release/bin/hms-plugin.jar:
no such file or directory
{noformat}
Probably, that's because the {{latest}} link in the {{build}} sub-directory was
changed by some other task that ran RELEASE build, and the dist-test.py script
finds all the required dependencies using that {{latest}} symbolic link.
[^build-and-test-4410.log.xz]
> Java CI failure
> ---------------
>
> Key: KUDU-3616
> URL: https://issues.apache.org/jira/browse/KUDU-3616
> Project: Kudu
> Issue Type: Task
> Components: infra
> Reporter: Marton Greber
> Priority: Minor
> Attachments: build-and-test-4410.log.xz, log.txt
>
>
> CI pipeline failures: Could not submit Java distributed test job Distributed
> Java tests failed.
> Seen in multiple places, for example: https://gerrit.cloudera.org/#/c/21759/
> Attached example log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
