Make timeouts also on Windows based on last output timestamp

[pv]

I don't have a Windows machine at hand (only WINE), so this isn't fully tested, but should work.

Fixes gh-319

cc @jorisvandenbossche

[jorisvandenbossche]

Yes, this seems to work!

[mdboom]

Makes sense to me (though I don't have Windows to test on, either)

[pv]

Probably safe to merge, seems simple in principle.

[seth-p]

FYI, using the latest code from master (0.2.dev818+c07fdbf2) I get a timeout after a bit under 4 minutes when running the Pandas asv tests (64-bit Python 3.4.3 on Windows 7). pandas-dev/pandas#9023 (comment)

[pv]

Perhaps the compilation of algos.c just takes more than 120 seconds --- can probably be checked by running the command shown in the log manually?

However, 2 min timeout is probably too short for compilation, and it's not handled correctly anyway (asv quits with error rather than dealing with it).

[seth-p]

Perhaps one should be able to specify/override the timeouts (I recall seeing them in three places in the code) on the command line and/or confit file?

On Oct 18, 2015, at 6:43 AM, Pauli Virtanen [email protected] wrote:

Perhaps the compilation of algos.c just takes more than 120 seconds --- can probably be checked by running the command shown in the log manually?

However, 2 min timeout is probably too short for compilation, and it's not handled correctly anyway (asv quits with error rather than dealing with it).

—
Reply to this email directly or view it on GitHub.