marcoabreu commented on issue #16995: CI timeout on unix-cpu Python2 test URL: https://github.com/apache/incubator-mxnet/issues/16995#issuecomment-564761718 Reading this thread really hurts. Can we please have less guessing and more rootcausing? How should a unit test be related to ccache, considering it's not a compile task? Why should network or disk io be a problem in a suite of tests? Even if there was limited io, I've never heard of a case where your request gets terminated or put into a deadlock in case of hitting the limit. AWS always uses throttling. MXNet is a highly parallel piece of software. If something in tests was about to get stuck intermittently, my first thought would be to actually look into my software under test and not just plain out blame the infrastructure. You wouldn't blame a processor in case your program prints a wrong value, right? So please, for the sake of the entire project, can we stop the guessing game and stop turning of production systems as a measure to apparently resolve or root cause an issue?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
