The failures are weird, it seems that the ETag is not a multipart and instead a full part. Maybe some issue storing xattr? I think it is OK to release without this since filesystem is usually used for testing.
On Wed, Oct 09, 2019 at 02:58:10PM +0200, Ignasi Barrera wrote: > I only have easy access to OSX now, so I was running the release there. > > Anyway, if there have been no relevant code changes for quite some time, > and we have not had any issues regarding the filesystem provider in OSX > (which I'd say is not being widely used), I think it is reasonable to not > consider this as a blocker to the release, file the corresponding issue and > move forward. > > Thoughts? > > On Wed, 9 Oct 2019 at 14:19, Andrew Gaul <g...@apache.org> wrote: > > > Unfortunately I do not have easy access to a Mac for a few days. This > > does work on Linux and it does not appear that there are any filesystem > > or blobstore changes in git log since 2.1.2. Perhaps JVM versions > > influence this? > > > > On Wed, Oct 09, 2019 at 12:30:27PM +0200, Ignasi Barrera wrote: > > > Hi! > > > > > > I was about to cut the jclouds release, and when building everything I've > > > found the following failures in the filesystem integration tests. > > > > > > They seem to only appear in OSX: > > > > > > > > ------------------------------------------------------------------------------- > > > Test set: TestSuite > > > > > ------------------------------------------------------------------------------- > > > Tests run: 109, Failures: 3, Errors: 0, Skipped: 15, Time elapsed: > > > 13.243 sec <<< FAILURE! - in TestSuite > > > > > testMultipartUploadMultipleParts(org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest) > > > Time elapsed: 0.02 sec <<< FAILURE! > > > java.lang.AssertionError: > > > Expecting: > > > <"afda318cf3d611557e2b8414c7f6d7d8"> > > > to end with: > > > <"-2""> > > > > > > at > > org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest.checkMPUParts(FilesystemBlobIntegrationTest.java:123) > > > > > > > > testMultipartUploadSinglePart(org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest) > > > Time elapsed: 0.011 sec <<< FAILURE! > > > java.lang.AssertionError: > > > Expecting: > > > <"833344d5e1432da82ef02e1301477ce8"> > > > to end with: > > > <"-1""> > > > > > > at > > org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest.checkMPUParts(FilesystemBlobIntegrationTest.java:123) > > > > > > > > testMultipartUploadMultiplePartsKnownETag(org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest) > > > Time elapsed: 0.262 sec <<< FAILURE! > > > java.lang.AssertionError: > > > Expecting: > > > <"2372ca1fec5cf0e587f0ed51dc204b32"> > > > to be equal to: > > > <""84462a16f6a60478d50148808aa609c1-2""> > > > but was not. > > > at > > org.jclouds.filesystem.integration.FilesystemBlobIntegrationTest.testMultipartUploadMultiplePartsKnownETag(FilesystemBlobIntegrationTest.java:161) > > > > > > > > > @Andrew Gaul <g...@apache.org> have you seen these failures? Is there an > > > issue in the tests or is it a real issue of the filesystem provider in > > OSX? > > > Should this block the release or should we proceed? > > > > > > Thanks! > > > > > > I. > > > > -- > > Andrew Gaul > > http://gaul.org/ > > -- Andrew Gaul http://gaul.org/
