ARROW-17840: [Java] Disable flaky JaCoCo coverage check #14231
Conversation
|
@github-actions crossbow submit java-jars |
|
Revision: 63a87f5 Submitted crossbow builds: ursacomputing/crossbow @ actions-b04d06f201
|
The check doesn't add much value, and makes things flaky because whether a branch is covered or not can come down to chance based on where exactly an exception occurs.
lidavidm
force-pushed
the
arrow-17840
branch
from
63a87f5
to
9823720
Compare
|
@github-actions crossbow submit java-jars |
|
Revision: 9823720 Submitted crossbow builds: ursacomputing/crossbow @ actions-c3889846c2
|
|
What's the connection between JaCoCo and the JDK8 and JDK9+ profiles? |
|
We used to have to pass more options to Surefire to get JaCoCo to work, so we had to duplicate some of the test config (since JDK8/9+ require different Surefire options). Now that we're not using JaCoCo, we also don't need that config, so we can simplify it |
Makes sense. |
|
Benchmark runs are scheduled for baseline = acd69f9 and contender = 9b4a181. 9b4a181 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
|
['Python', 'R'] benchmarks have high level of regressions. |
The check doesn't add much value, and makes things flaky because whether a branch is covered or not can come down to chance based on where exactly an exception occurs. Authored-by: David Li <li.davidm96@gmail.com> Signed-off-by: David Li <li.davidm96@gmail.com>
The check doesn't add much value, and makes things flaky because whether a branch is covered or not can come down to chance based on where exactly an exception occurs.