yep!
I'll walk through how to find it, skip to "tl;dr:" if you just want the answer.
Start with the "Console output" line in the footer of the QABot post
Console output
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/console
Search the output for "Checking client artifacts". There'll be two
instances, one for the branch and one for the patch. The QABot said
there was a problem with both.
The branch stanza is:
Checking client artifacts on branch
cd /testptch/hadoop
/usr/bin/mvn --batch-mode
-Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-HADOOP-15407-patch-1
verify -fae --batch-mode -am -pl
hadoop-client-modules/hadoop-client-check-invariants -pl
hadoop-client-modules/hadoop-client-check-test-invariants -pl
hadoop-client-modules/hadoop-client-integration-tests
-Dtest=NoUnitTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
-Dfindbugs.skip=true > /testptch/patchprocess/branch-shadedclient.txt
2>&1
And the patch stanza is:
Checking client artifacts on patch
cd /testptch/hadoop
/usr/bin/mvn --batch-mode
-Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-HADOOP-15407-patch-1
verify -fae --batch-mode -am -pl
hadoop-client-modules/hadoop-client-check-invariants -pl
hadoop-client-modules/hadoop-client-check-test-invariants -pl
hadoop-client-modules/hadoop-client-integration-tests
-Dtest=NoUnitTests -Dmaven.javadoc.skip=true -Dcheckstyle.skip=true
-Dfindbugs.skip=true > /testptch/patchprocess/patch-shadedclient.txt
2>&1
So the two files we want are "branch-shadedclient.txt" and
"patch-shadedclient.txt"
Next we go from the console output of the build to browse the build artifacts.
Click on the build number in the breadcrumbs at the top of the page,
in this case "#1477"
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/
click on the "Build Artifacts" link in the center of that page
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/artifact/
Then follow "out" to get the contents of the patchprocess directory:
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/artifact/out/
tl;dr:
In this directory listing we'll find both of the logs:
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/artifact/out/branch-shadedclient.txt
https://builds.apache.org/job/PreCommit-HADOOP-Build/14777/artifact/out/patch-shadedclient.txt
In both cases it looks like the failure is before we do the shaded client test:
...
[INFO] --- maven-antrun-plugin:1.7:run (common-test-bats-driver) @
hadoop-common ---
...
[exec] ok 1 hadoop_stop_daemon_changing_pid
[exec] not ok 2 hadoop_stop_daemon_force_kill
[exec] # (in test file hadoop_stop_daemon.bats, line 43)
[exec] # `[ -f ${TMP}/pidfile ]' failed
[exec] # bindir:
/testptch/hadoop/hadoop-common-project/hadoop-common/src/test/scripts
[exec] # sh: 0: Can't open
/testptch/hadoop/hadoop-common-project/hadoop-common/src/test/scripts/process_with_sigterm_trap.sh
Unfortunately, I don't know what help I can provide on the specific
failure. I haven't really dug into the bats testing of shell scripts
yet.
If someone could file a JIRA about having the shaded client test post
a link to its log in the QABot footer and assign it to me I can take
care of making it easier to find this stuff.
On Fri, Jun 15, 2018 at 6:05 AM, Steve Loughran wrote:
>
> There's a patch for https://issues.apache.org/jira/browse/HADOOP-15407 which
> is being rejected due to unrelated tests (probably) and to s failure in the
> shading
>
> Is there a way to get the output of that specific log?
>
> -steve
--
busbey
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
