@jhamrick It’s not you. It’s Travis and/or a legitimate issue in our code base. I’ve been working on resolving for @parente on kernel gateway. Travis was down for maintenance about an hour ago. I’ll rekick it on nbgrader and see what happens.
Not sure. It may be a low level websocket issue. More likely, it is Travis throttling under load and then something in the websocket times out which gets propagated up. I’ve been babysitting the nbgrader pr and rerunning the individual fails.
Ok, well no need to babysit it unless it’s helpful for figuring out what’s going wrong… it doesn’t seem like restarting always fixes it. I tried to restart the builds a whole bunch earlier today and they kept failing so I gave up
Umm, I don’t know exactly; I usually only run the tests that are relevant to the part I’m working on
Let me run the full test suite now and I’ll let you know when it’s done :-)
Actually, the individual tests that fail are all different. I’m babysitting to see if there is anything different than what I was seeing on kernel gateway where I had the test verbosity set high. Thanks for running the full suite.
File an issue on the test speed. I think I know someone at PyCon that can help with that at the end of May. I did limit the number of concurrent Travis jobs to 1 while I troubleshoot. I will disable back to the original Travis setting after I’m done.