[
https://jira.codehaus.org/browse/MERCURY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MERCURY-112.
----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> Investigate failure of IT
> ComprehensiveRepositoryTest.testWriteTimestampReadSnapshotSingleRepo
> ----------------------------------------------------------------------------------------------
>
> Key: MERCURY-112
> URL: https://jira.codehaus.org/browse/MERCURY-112
> Project: Mercury (retired)
> Issue Type: Task
> Affects Versions: 1.0-alpha-6
> Reporter: Benjamin Bentmann
> Assignee: Oleg Gusakov
> Priority: Minor
> Attachments: org.apache.maven.mercury.all.it.AllTestCases.txt,
> org.apache.maven.mercury.all.it.AllTestCases.txt,
> TEST-org.apache.maven.mercury.all.it.AllTestCases.xml,
> TEST-org.apache.maven.mercury.all.it.AllTestCases.xml
>
>
> See attached Surefire output. The test fails sporadically, I assume when the
> two files end up having the same timestamp due to the low resolution of the
> timestamps. If the metadata can't be consulted here to add some more
> robustness, the test likely needs a sleep(1000) on Windows.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
