You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
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 #18244 (now the test relies on MXNet numpy, whereas it relied on upstream numpy before)
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/mxnet-validation/pipelines/unix-cpu/branches/PR-18284/runs/6/nodes/364/steps/731/log/?start=0
metric now rely on mxnet numpy implementation and may be slower until mxnet overhead is reduced.
@acphile should the timeout on this test be temporarily increased?
The text was updated successfully, but these errors were encountered: