Closed mwobensmith closed 6 years ago
Looks like Travis passed, so now it's up to me to figure out why the last PR did not.
I think I found the problem. Re-opening.
Travis is know to produce intermittent failures when running our integration tests. It seems to be up to their network connectivity.
I can restart tests manually. Unfortunately I am the only one.
So what is the issue? Was it in your changes?
I'm pretty sure I just caused a conflict between the nosetest and the new regression mode. Give me time to sort it out.
Lesson: always run nosetests before checking in. :\
No longer needed.
We seem to have some Travis integration test failures. I don't think they are caused by my work, so this PR just contains one line of bogus log output on top of the current, last-known-good changeset.
Let's see if the tests still fail.