This works: git checkout b067250080e6cc434563a2b507abe6f99fc3e73d && tox -r
The next change hangs on py34: git checkout 40fc003f0fbff5c0216ca2eaea7c79a77db5cbf5 && tox -r
I can't explain how subsequent check and gate jobs were able to succeed after that went through, including that change by itself, but starting at 2015-02-21 21:15 the hang started showing up and has caused the last five reviews to run jobs to end up failing py34 after hanging for 40 minutes.
This works: git checkout b067250080e6cc4 34563a2b507abe6 f99fc3e73d && tox -r 0216ca2eaea7c79 a77db5cbf5 && tox -r
The next change hangs on py34: git checkout 40fc003f0fbff5c
I can't explain how subsequent check and gate jobs were able to succeed after that went through, including that change by itself, but starting at 2015-02-21 21:15 the hang started showing up and has caused the last five reviews to run jobs to end up failing py34 after hanging for 40 minutes.