Okay, so two different feature requests. :)
On Fri, Jul 14, 2017 at 2:51 PM, Allen Wittenauer <[email protected]> wrote: > > > > On Jul 14, 2017, at 8:01 AM, Sean Busbey <[email protected]> wrote: > > > > I think that the lack of a vote from jdk8 is a bug. > > Well... maybe. We've always only run one JDK during unit tests even in > non-QBT mode due to the time restraints. If we look at HBase's results, > there are 2.5+hours of unit test time with just one JDK. Running them both > in succession leads to 5+hours. For Hadoop, unit test time clocks in around > 8-9 hours... for one JDK. Running two in succession would ... not be good. For HBase this is would be perfect. I'd rather take up a single executor for 5 hours than burn two executor for 2.5 hours each, if only to keep more executors open for other projects to use. We only need one set of results per day and we already try to allow jenkins to schedule it via hash, so are relatively insensitive to how long the job takes. a run per JDK is a solid work around though, and I think I can tell jenkins to not parallelize them. I'll just need to find a way to avoid needing a second docker image. On Fri, Jul 14, 2017 at 2:54 PM, Allen Wittenauer <[email protected]> wrote: > > > > One other thing! > > Keep in mind that Jenkins doesn't know that Yetus is running multiple > JDKs. So any reports (e.g., Test Trend report) that you would have it > generate will still only show the last JDK result too. Yep, but I'm expressly pointing jenkins to the test results within the archiver output, so if there were results per jdk I could point it at all of them.
