view CONTRIBUTING @ 51952:f4c038081561

run-tests: bump the default timeout on Windows to 4x the normal value

There are a ridiculous number of tests that timeout on Windows with the 360 sec
default (~60).  And because of the bug where timed out tests still run to
completion before the results are thrown away[1], the timeout does nothing but
waste time, so there's no reason to try to find a lower value that still works.
For reference on my system:

    # Ran 909 tests, 116 skipped, 119 failed.
    python hash seed: 2052473208

    real    151m44.322s
    user    0m0.077s
    sys     0m0.046s

[1] I thought that I wrote a bug for this, but search isn't finding it.

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).