This is an automated email from the ASF dual-hosted git repository.
jungm pushed a commit to branch ee11
in repository https://gitbox.apache.org/repos/asf/tomee-tck.git
The following commit(s) were added to refs/heads/ee11 by this push:
new b622a4e Run JavaTest-to-JUnit conversion unconditionally, not
per-partition
b622a4e is described below
commit b622a4ef39ed1adb97062ab00cebef280cf37add
Author: Markus Jung <[email protected]>
AuthorDate: Mon Jul 20 06:04:23 2026 +0200
Run JavaTest-to-JUnit conversion unconditionally, not per-partition
javatest-report-to-junit.sh already no-ops when a module produced no
JavaTest report, so gating it on a hardcoded id allowlist just misses
conversion for any future partition that starts producing JTS output.
---
runner-standalone/run-standalone-suite.sh | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/runner-standalone/run-standalone-suite.sh
b/runner-standalone/run-standalone-suite.sh
index 541eb0c..18e69db 100755
--- a/runner-standalone/run-standalone-suite.sh
+++ b/runner-standalone/run-standalone-suite.sh
@@ -137,11 +137,11 @@ set -e
# Convert the JT Harness report of the legacy JavaTest suites into JUnit XML
# under target/surefire-reports/ so the Jenkins junit step surfaces per-test
# results (with the .jtr harness log embedded for failures). Conversion
-# problems never mask the Maven result.
-case "$ID" in
- transactions|security-old|faces-old)
- sh "$SCRIPT_DIR/javatest-report-to-junit.sh" "$SCRIPT_DIR/$ID" ||
- echo "run-standalone-suite: WARN: JavaTest report conversion failed" >&2
;;
-esac
+# problems never mask the Maven result. javatest-report-to-junit.sh no-ops
+# when the module produced no JavaTest report, so it is safe to try for
+# every runner rather than hardcoding the subset that currently uses
+# JavaTest.
+sh "$SCRIPT_DIR/javatest-report-to-junit.sh" "$SCRIPT_DIR/$ID" ||
+ echo "run-standalone-suite: WARN: JavaTest report conversion failed" >&2
exit "$MVN_STATUS"
