action #61952
closed
[opensuse][qam] test fails in java - ./test_java.sh fails on javac test, because there are 3 javac alternatives for 4 javac version (including openjfx)
Added by ggardet_arm over 4 years ago.
Updated about 4 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-extra@aarch64-HD24G fails in
java
./test_java.sh fails on javac test, because there are 3 javac alternatives for 4 javac version (including openjfx)
Test suite description¶
Same as jeos, plus some more tests.
Reproducible¶
Fails since (at least) Build 20190724 for aarch64, same for ppc64le
Expected result¶
Last good: 20190712 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from test fails in java to [opensuse][aarch64][qam] test fails in java - ./test_java.sh fails on javac test, because there are 3 javac alternatives for 4 javac version (including openjfx)
@ggardet as you already try to find out what's problematic when you create tickets I suggest to put a bit more detail in the ticket subject line as this is helpful in ticket triaging and for people that want to help with the overview. So I just added the one line you added into the subject line as I think it's helpful to understand (and solve) the problem.
- Has duplicate action #61988: test fails in java for tw 20200108 ppc64le added
- Subject changed from [opensuse][aarch64][qam] test fails in java - ./test_java.sh fails on javac test, because there are 3 javac alternatives for 4 javac version (including openjfx) to [opensuse][qam] test fails in java - ./test_java.sh fails on javac test, because there are 3 javac alternatives for 4 javac version (including openjfx)
- Description updated (diff)
- Priority changed from Normal to High
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: jeos-extra@64bit_virtio-2G
https://openqa.opensuse.org/tests/1158733
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
- % Done changed from 0 to 20
- Status changed from New to In Progress
- % Done changed from 20 to 100
- Status changed from In Progress to Resolved
Also available in: Atom
PDF