Hi, looking at [1], the Travis build failed in some cases, but it looks to me as if it's just one of the strange Travis failures we have (specifically the line "Server error occurred. status: 504 Gateway Time-out" seems to me a testing server problem rather than a failing test). Would someone with a better understanding of the test suite mind confirming my understanding?
On Thu, May 15, 2014 at 9:59 PM, Isaac Bennetch bennetch@gmail.com wrote:
Hi, looking at [1], the Travis build failed in some cases, but it looks to me as if it's just one of the strange Travis failures we have (specifically the line "Server error occurred. status: 504 Gateway Time-out" seems to me a testing server problem rather than a failing test). Would someone with a better understanding of the test suite mind confirming my understanding?
Hi, I also saw Travis is failing today, even on my own copy of repo. I have Travis activated and it is failing for every commit I do on any branch today. As what I can understand from logs is that its not about failing test case, maybe it is some problem about uploading coverage report of the build to coveralls.
Hi
Dne Thu, 15 May 2014 12:29:38 -0400 Isaac Bennetch bennetch@gmail.com napsal(a):
Hi, looking at [1], the Travis build failed in some cases, but it looks to me as if it's just one of the strange Travis failures we have (specifically the line "Server error occurred. status: 504 Gateway Time-out" seems to me a testing server problem rather than a failing test). Would someone with a better understanding of the test suite mind confirming my understanding?
Indeed this is problem in uploading test coverage to Coveralls, not in the code. I've just restarted these tests now.
-
Chirayu Chiripal -
Isaac Bennetch -
Michal Čihař