I want to make sure I'm thinking about things correctly before filing issues.
In HBase I'm setting up nightly jobs that rely on Yetus in QBR mode. On some of our branches, we support both jdk7 and jdk8 so I want to run unit tests for both. I'm currently using 0.5.0. Here's the report from two example jobs (they link back to more jenkins details): https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-1-HBASE-18147/1/Nightly_Build_Report/ https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-1-HBASE-18147/2/Nightly_Build_Report/ Here's the pipeline they're referencing: https://github.com/apache/hbase/blob/branch-1-HBASE-18147/dev-support/Jenkinsfile In both of the above, jdk8 unit tests fail. One also has failures in jdk7. Only the jdk7 status appears to be reported in the vote tables, and only jdk7 shows up in the "more details" section for the job where it fails. AFAICT, the archiver functionality only runs after all the tests so it fails to capture the surefire logs from the jkd8 run. The job zips up the archiver directory after yetus runs (we got pinged for using up gigs-per-run from test logs), so you have to download test_logs.zip to see what the archiver did (I manually checked that the directories match what was present prior to adding zipping htings up). I think that the lack of a vote from jdk8 is a bug. I suspect the lack of archiving the files that come out of multijdk builds other than the JAVA_HOME one is just a feature gap (and would get filed as a proposed improvement). Does this all sound correct? Or have I botched configuration somehow?
