Upon upgrading the Sauce OnDemand plugin from 1.83 to 1.85, every job using Sauce Connect started failing with the following error:

Starting Sauce OnDemand SSH tunnel on slave node
Launching Sauce Connect on <hostname>
FATAL: Negative time
java.lang.IllegalArgumentException: Negative time
at java.io.File.setLastModified(File.java:1349)
at org.codehaus.plexus.archiver.zip.AbstractZipUnArchiver.extractFile(AbstractZipUnArchiver.java:234)
at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:93)
at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:120)
at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.untarGzFile(SauceConnectFourManager.java:153)
at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.extractZipFile(SauceConnectFourManager.java:143)
at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.createProcessBuilder(SauceConnectFourManager.java:111)
at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:172)
at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:542)
at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectStarter.call(SauceOnDemandBuildWrapper.java:517)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)

So basically, it blows up when trying to extract Sauce Connect 4 from the .tar.gz resource. This seems to be related to the following bugs:

https://jira.codehaus.org/browse/MJAR-142
http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6791812

I'm not sure why it's being triggered in this case; I didn't see any suspicious timestamps when inspecting the plugin resources, but I may well have missed something.