[GitHub] [incubator-mxnet] leezu commented on issue #18330: test_metric_performance
leezu commented on issue #18330: URL: https://github.com/apache/incubator-mxnet/issues/18330#issuecomment-629077891 The test doesn't actually enforce anything. It's output is not monitored (AFAIK) so it may be best to simply delete this test. 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: us...@infra.apache.org
[GitHub] [incubator-mxnet] leezu commented on issue #18330: test_metric_performance
leezu commented on issue #18330: URL: https://github.com/apache/incubator-mxnet/issues/18330#issuecomment-629062928 Notice that this timeout only happens on Python3: MKL-CPU jobs. The job there times out after 1200 seconds (global timeout), whereas it finishes in under 300 seconds on the non-MKL Python 3 CPU job. So the problem is due to https://github.com/apache/incubator-mxnet/issues/18244 (now the test relies on MXNet numpy, whereas it relied on upstream numpy before) cc @TaoLv 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: us...@infra.apache.org
[GitHub] [incubator-mxnet] leezu commented on issue #18330: test_metric_performance
leezu commented on issue #18330: URL: https://github.com/apache/incubator-mxnet/issues/18330#issuecomment-629063001 Suggest we mark this test as xfail for MKL builds for now 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: us...@infra.apache.org
