-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s390x jdk_other tests fail No route to host (Receive failed) #1992
Comments
@lumpfish Using When using
Is it because there isnt an XL version available here? https://adoptopenjdk.net/nightly.html |
There is no |
This is the job I took the command line from: https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/21/parameters/ |
@lumpfish Yes it's something that needs fixing - Andrew and I have seen that elsewhere (in fact we hit it on the "how to investigate build/test failures" call this morning. I think I mentioned it at least in passing to @smlambert somewhere, but can't remember if we created an issue on it (Clearly, if we didn't, that was an oversight and we need one). I had another one today that had a |
@lumpfish Can you see if you can reproduce it again? If not, we'll have to put this into the "random network glitch" bucket (I need a label for that...) |
I just reran the test and it passed. Did you fix anything? This issue was raised on 2nd March, but my chase up was 14th April (#1992 (comment)), so if it's a 'glitch' it's a recurring one. |
Since March 2, the playbooks have been run on all linux machines, as per #1990. This may have fixed it |
Not if the error has been seen in the last week as suggested by adoptium/aqa-tests#2360 (looks like the same failure). I've queued up 100 of @lumpfish's test case at https://ci.adoptopenjdk.net/job/Grinder/92/consoleFull (Takes about 3 minutes per iteration so will be churning for a while) - we can see if it shows as intermittent. Tagging adoptium/temurin-build#1450 as it seems likely this is an intermittent failure. [EDIT: Yes it is showing up on that run] |
@Haroon-Khel Can you compare my grinder with yours - it seems to be failing on every iteration on my run |
I used Simon's comment from 2 days ago to recreate the failing test, while you used the link in the first comment. I think the latter may be a better way to recreate the failing tests seeing as all of mine passed. The differences between the two are yours uses openj9 jdk 16 while mine uses hotspot jdk11, and yours runs the target |
I dont think the cause is due to an error in |
The reason we're getting different results is that if the test is resubmitted via the
|
The problem lies with the generated link again. It inserts
works (that is, the test fails). |
The rerun link simply captures all params of the last run. It is on the user to then adjust the parameters accordingly. It exists as a convenience to help prepopulate params. I can remove it if its causing confusion (you would use Jenkins Rebuild link in the same way). |
"The rerun link simply captures all params of the last run." By 'last run' do you mean the parameters the job was submitted with? The original test was run with |
Raised adoptium/aqa-tests#2527 for the issue with the incorrect test being run. |
The test code can be found at https://github.com/adoptium/jdk11u/blob/master/test/jdk/com/sun/jndi/dns/ConfigTests/Timeout.java As far as I can tell, the test tries to connect to a mock/non existent dns server at 10.0.0.0:9 intentionally and waits for the request to timeout. On a passing test, expected timeout is 7750ms. Testing on build-marist-rhel77-s390x-1, the test will pass randomly, and then return to failing with javax.naming.CommunicationException: DNS error [Root exception is java.net.NoRouteToHostException: No route to host]; remaining name '' |
Running with 20 iterations at https://ci.adoptopenjdk.net/job/Grinder/1461/ |
Hmmm those are giving me |
Finding this same type of failure on the new Marist systems being setup at OpenJ9, but only on the Redhat 7 systems. Ubuntu 20 installations work as expected. The older Redhat 7 systems from Marist do not have this |
I ran those grinders using #1992 (comment) which look to be the correct instructions as they failed for Simon. They all pass now |
s390x_linux extended.openjdk target jdk_other fails with
Example failing job: https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_extended.openjdk_s390x_linux/9/consoleFull
Looks like it occurs on both hotspot and openj9, all releases and all s390x machines - so I'm guessing it's a machine setup issue on the marist machines.
To rerun the test: https://ci.adoptopenjdk.net/job/Grinder/parambuild/?JDK_VERSION=16&JDK_IMPL=openj9&JDK_VENDOR=adoptopenjdk&BUILD_LIST=openjdk&PLATFORM=s390x_linux_mixed&TARGET=jdk_other_1
Full output of failing test:
The text was updated successfully, but these errors were encountered: