[JIRA] (JENKINS-61792) DoubleLaunchChecker false positive

[email protected] (JIRA) Fri, 03 Apr 2020 11:12:25 -0700

Title: Message Title

Wade Cline commented on

We've hit this issue twice recently on the same machine, here is the snippet from earlier:

 
                                                                2020-03-14 02:02:45.357+0000 [id=56]    SEVERE  hudson.util.DoubleLaunchChecker#execute: Collision detected. timestamp=1584146805000, expected=1584146805350

The underlying filesystem is 'ext4' with standard options 'rw,relatime,errors=remount-ro', and the unit test shows that the filesystem does support sub-second timestamps... and yet the messages appear to suggest the opposite.

There might be an uncommon case which causes the sub-second timestamp to be downgraded to a second timestamp when writing to disk (yet that didn't happen in the unit test I wrote), or there might be something more nefarious going on here.

Add Comment

This message was sent by Atlassian Jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205632.1585870918000.6277.1585937520130%40Atlassian.JIRA.

[JIRA] (JENKINS-61792) DoubleLaunchChecker false positive

Reply via email to