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/12/07 11:17:24 UTC

[GitHub] [incubator-mxnet] wkcn commented on issue #16866: skip quantized conv flaky case

wkcn commented on issue #16866: skip quantized conv flaky case
URL: https://github.com/apache/incubator-mxnet/pull/16866#issuecomment-562841591
 
 
   Hi @access2rohit and @larroy, I have several suggestions about MXNet CI.
   1. Allow trusty contributors or committers to get access to the machines of MXNet CI by ssh
     Contributors may could not reproduce issues on their local machines. They don't have the server, as the same as that on MXNet CI. When some unit-tests fail on CI, they can only read the log, but they couldn't look for the reason in detail. For example, we met the problem about CI driver, like PR #16985. Since of no permission, other contributors couldn't address the issue. Contributos may need to access to the CI machine, in order to solve the problem.
   
   It is better to provide some machines to debug : )
   
   2. Allow users to do single run or stop the unit-test.
   Because of network error or precision problem, unit-tests may fail. Contributors need to restart all tests recently. If CI supports single run, the cost of CI will be reduced. If contributors submit a new commit, the old CI test should be stopped. When contributors realize that there is a mistake in this PR, they should have the permission to stop the CI test.
   For document update (such as fixing typo), it will be better to build the documents only.
   
   Thanks.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services