You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2019/02/21 19:03:29 UTC

[GitHub] apeforest edited a comment on issue #14146: Disables flaky test test_operator_gpu.test_deconvolution

apeforest edited a comment on issue #14146: Disables flaky test test_operator_gpu.test_deconvolution
URL: https://github.com/apache/incubator-mxnet/pull/14146#issuecomment-466123438
 
 
   @perdasilva Thanks for your detailed explanation. I am not disagreeing with your analysis. However, such analysis based on individual's expertise case by case IMHO is not a scalable mechanism for a software release and deployment. On the other hand, even if this PR passes and fails CI tests at random times, we cannot exclude the possibility that the flaskiness was introduced by this particular PR. The most reliable way to monitor flaky tests should be and only be through master branch over a period of time. 
   
   CI is our last guard to protect the quality of our software. I think it's better to be more conservative than optimistic. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services