[GRADLE-831] ArchiveIntegrationTest.canCreateATarArchive assumes umask of 022 Created: 20/Feb/10  Updated: 24/Jan/17  Resolved: 24/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Russel Winder Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   

I get one integration test failure, all other unit and integration tests pass. The failure is:

ArchiveIntegrationTest	canCreateATarArchive	Failure	mismatched permissions for '/home/users/russel/Repositories/Bazaar/SharedRepositories/Gradle/Working/build/tmp/tests/ArchiveIntegrationTest/canCreateATarArchive/expanded/dir1' Expected: "drwxr-xr-x" got: "drwx------" 

junit.framework.AssertionFailedError: mismatched permissions for '/home/users/russel/Repositories/Bazaar/SharedRepositories/Gradle/Working/build/tmp/tests/ArchiveIntegrationTest/canCreateATarArchive/expanded/dir1'
Expected: "drwxr-xr-x"
got: "drwx------"

Expected: "drwxr-xr-x"
got: "drwx------"

at org.gradle.util.TestFile.assertPermissions(TestFile.java:216)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:52)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:117)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at org.gradle.integtests.ArchiveIntegrationTest.canCreateATarArchive(ArchiveIntegrationTest.groovy:203)
at org.gradle.util.TemporaryFolder$1.evaluate(TemporaryFolder.java:69)
at org.gradle.util.Resources$1.evaluate(Resources.java:56)
0.834

The test is, I think, making assumptions of the umask. I set mine to 077 instead of the default of 022, and I think this is the reason for the failure. So the integration test needs to check the users umask and amend expectations accordingly.



 Comments   
Comment by Lars Hvile [ 15/Feb/12 ]

I've made some changes to this test, related to GRADLE-796, GRADLE-673 & GRADLE-971. Those changes may have fixed the problem..

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Generated at Wed Jun 30 11:40:03 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.