-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
JTReg Failures: well known file exceptions on macos/hotspot #1274
Comments
Recent builds of 11 are intermittently passing. A result of this test failing on all machines except for |
@smlambert can you transfer this issue to infrastructure? |
This is to do with the fact that Jenkins isn't in a security group: test-macincloud-macos1014-x64-: test-macincloud-macos1014-x64-1:~ admin$ dscl . search /Groups GroupMembership jenkins
test-macincloud-macos1014-x64-1:~ $ test-macincloud-macos1010-x64-1 test-macincloud-macos1010-x64-1:~ admin$ dscl . search /Groups GroupMembership jenkins
com.apple.sharepoint.group.1 GroupMembership = (
jenkins
) |
testing with a group added to Jenkins user: |
test failed, trying with a reboot first: https://ci.adoptopenjdk.net/job/Grinder/2813/console |
hmm maybe not. |
trying with |
hmm so the test shows that it picked up the top dir: Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/tmp but then runs the test without it: 12:38:37 Command line: [/Users/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image/Contents/Home/bin/../bin/java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n -classpath /Users/jenkins/workspace/Grinder/openjdk-tests/TKG/test_output_158686425467/jdk_svc_sanity_0/work/classes/0/com/sun/jdi/ProcessAttachTest.d ProcessAttachTestTarg ] @smlambert any idea why? |
using EXTRA_OPTIONS https://ci.adoptopenjdk.net/job/Grinder/2822 ❎ trying with |
Adding this from our DM in Slack for search-ability later: Command definition for that test: Command that gets run: EXTRA_OPTIONS is appended to JVM_OPTIONS, which gets fed to jtreg via -vmoptions parameter (see https://openjdk.java.net/jtreg/vmoptions.html) |
Exclude PR adoptium/aqa-tests#1734 |
@M-Davies I've landed that PR - can this be closed in that case? |
@karianna probably not, the issue still exists, we've just skipped the test for now |
This is also occurring for @gdams Are there any differences between the 1010 and 1013 machines that could cause this? Maybe that'll lead you to the solution for this?
Exclude PR: adoptium/aqa-tests#1741 |
Same core issue for failures in a system test target HCRLateAttachWorkload_previewEnabled (deep history noting it passes on macos1010 but not on macos1012/13/14 machines). This error will occur in any test that invokes jdk.attach/sun.tools.attach.VirtualMachineImpl.checkPermissions(Native Method) stderr Exception in thread "main" java.io.IOException: well-known file /var/folders/h1/b_v48zpd1zd54jblxnx58p3r0000gr/T/.java_pid1386 is not secure: file's group should be the current group (which is -1) but the group is 0 |
Grinder re-run from the ealiier parameters is now running ok as per 1021 1022 1023 - do we need further work on this or can it now be closed (or retested if the test has actually been disabled)? I see it's been re-assiged to @smlambert ... |
Someone should remove the 4 exclusions and rerun tests:
|
@karianna Was there a reason why this was re-assigned to Shelley in March? |
Created adoptium/aqa-tests#2716 as good first issue to verify this infra issue has been addressed. |
I suspect I was thinking it was ready for a re-test but forgot to add a comment explaining that. |
Anyone can handle this so I will unassign. |
@smlambert Have we seen any problems as a result of the exclusions being reverted in the aforementioned PR? |
Describe the bug
On mac machines for 11 and 14 hotspot the following tests are failing due to pretty much the same error
To Reproduce
Steps to reproduce the behavior (or Grinder rerun link):
Expected behavior
Tests pass
Screenshots
ProcessAttachTest.java
TestJcmdStartStopDefault.java
com/sun/jdi/ProcessAttachTest.sh
Additional context
It appears to be a perm issue on the surface. The test is creating items in the
/var/
directory which is a sensitive directory to be creating files in. Its possible that this is likely caused by the the debugger that the test creates not having the same perms as the java_pid file.The text was updated successfully, but these errors were encountered: