[ 
https://issues.apache.org/jira/browse/COMPRESS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072561#comment-16072561
 ] 

Simon Spero commented on COMPRESS-416:
--------------------------------------

>From the mercurial logs I think this it is definitely related - possibly
fixing a performance regression there was an issue with locales being
initialized too eagerly.

It is indeed very sensitive to jdk(since it seems to be randomized each
release). The extended header  is parsed correctly (and the zip entry
itself has the right FileTime). It's the dosxtime that seems  messed up.
Now to see where that's set (of course, extended header test should be OK
just testing itself).

If this wasn't the only known jdk9 fail issue it wouldn't be bugging me :)




> Tests failing under jdk 9 : one reflection issue, one change to ZipEntry 
> related issue
> --------------------------------------------------------------------------------------
>
>                 Key: COMPRESS-416
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-416
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.14, 1.15
>         Environment: JDK 9 ( jdk9 tree tip - I believe this is what will be 
> the RC, or if not, what would have been RC). 
>     java.runtime.version = 9-internal+0-adhoc.ses.jdk9
>     java.specification.version = 9
>     java.version = 9-internal
>     java.vm.specification.version = 9
>     os.arch = amd64
>     os.name = Linux
>     os.version = 4.4.0-81-generic
>            Reporter: Simon Spero
>             Fix For: 1.15
>
>         Attachments: surefire-reports.zip
>
>
> X5455_ExtendedTimestampTest is failing under JDK 9 , due to what appears to 
> be a bogus value returned from getTime().  It seems like the test failure 
> might be due to the changes introduced for this: 
> https://bugs.openjdk.java.net/browse/JDK-8073497
> Tests were run using intelliJ TestRunner, using the openjdk9 build from the 
> tip of the jdk9 tree (not dev).  I believe that this is at most one commit 
> away from what will be the RC (which was delayed at the last minute due to 
> two issues, one of which was javadoc related, and the other hotspot. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to