-
-
Notifications
You must be signed in to change notification settings - Fork 316
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
Solaris/x64 test failures on new Vagrant environment #5127
Comments
Latest run on the latest nightly build (so in sync with the test material) had five failures on the new system but were green on the old ones:
Hotspot targets re-run at Grinder#9054 Re-run with RAM increased to 6GB: https://ci.adoptium.net/job/Grinder/9056/ which has reduced the failures to the last two in the table above. |
Reran the failing tests on the new azure build solaris machine build-azure-solaris10-x64-1 using the rerun link from the comment above: https://ci.adoptium.net/job/Grinder/9349/testReport/ failing tests
|
All the same except for the mmap one which may be intermittent then. |
Taking a look. |
Down to 2 failing tests, after increasing memory to 8GB and CPU cap to 75%.. Test Result (2 failures / -2) |
I can get this test to pass by killing the DHCP agent , which is blocking port 4999 sun/management/jmxremote/bootstrap/SSLConfigFilePermissionTest.sh.SSLConfigFilePermissionTest I'll attempt to find a solution to get dhcpagent to use a different port. |
This test also passes intermittently |
Interesting - I'd suggest re-running that Grinder with 1000 iterations and see how many times it passes to get a feel for what the suitable course of action would be. |
I've found a root cause, its related to xvfb not being able to start and stop cleanly and write to /tmp and /tmp/.X11-pipe, mostly what looks like permission related things.. |
Is there an error in the log related to xvfb? I'm somewhat surprised that if Xvfb is unable to start we're only seeing an issue with one SSL test (I'm also a touch surprised that such a test needs Xvfb but 🤷🏻 ) |
The final issue, appears to pass intermittently on both machines.. The build machine: One pass out of 5 runs here.. https://ci.adoptium.net/job/Grinder/9448/console and the same result on the test machine.. |
Good to know - I've just kicked off 500 on each of the three machines to see how intermittent it is and whether there is a difference in the ESXi vs Vagrant/VirtualBox hosted ones. |
This can be closed. as determined to be intermittent, with around 48/500 test attempts passing. |
Ref: adoptium/infrastructure#3347 (comment)
We are seeing some failures on the new Solaris/x64 machines which have been provisioned on x64 hosts using Vagrant/Virtualbox virtualisation:
https://ci.adoptium.net/job/Grinder/9047/testReport/ is the latest run which was against the latest release, although that will be superceded by a run against the nightly build at https://ci.adoptium.net/job/Grinder/9051/testReport (Not yet complete - will update this with the specific test case failures once it's done)
The comparable run on one of the previous ESXi machines is https://ci.adoptium.net/job/Grinder/9052 but that is expected to pass.
The text was updated successfully, but these errors were encountered: