3 ms·
Incorrect title, should be 2^31 milliseconds
by congresstart 8y ago
Incorrect title, should be 2^31 milliseconds
- mijoharas 8y agoAgreed, I just read the title and thought: Who cares? there is no way this could be a problem yet.
- femto113 8y agoWhich is about 25 days, or roughly a month, either of which would make a better title. I read the article hoping to discover how they ran a test that was 60 years long...
- Arnavion 8y agoWell it would've been the same as what they did for the 25 days case I imagine - using libfaketime.
- stevenwoo 8y agoJust spitballing, could use a tool like the debugger to inject a value into a system library function to set it to 59.99 years or whatever value necessary to do tests.
- johannes1234321 8y ago> I read the article hoping to discover how they ran a test that was 60 years long... If you read the link you could figure that out: ;) "I used libfaketime to speed things up by a factor of 1000 on a linux server "
- rtkwe 8y agoI don't think so, seeing 2^31 (units) immediately tells me what's probably going wrong in a way that 25 days or ~1 month doesn't unless I go and convert that into milliseconds.
- peterkelly 8y agoEven Windows 95 lasted longer than that: https://www.cnet.com/news/windows-may-crash-after-49-7-days/ https://www.cnet.com/news/windows-may-crash-after-49-7-days/