This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
test_quantization.test_get_optimal_thresholds sometimes fails during testing. #11456
Labels
Comments
KellenSunderland
added a commit
to KellenSunderland/incubator-mxnet
that referenced
this issue
Jun 28, 2018
KellenSunderland
added a commit
to KellenSunderland/incubator-mxnet
that referenced
this issue
Jun 28, 2018
5 tasks
KellenSunderland
added a commit
to KellenSunderland/incubator-mxnet
that referenced
this issue
Jun 28, 2018
Thank you for submitting the issue! We are labeling it so MXNet community members can help resolve it. |
Commands:
|
Confirm reproduction using the above seeds. Seems like a tolerance problem to me from the existing incidents, on average a single run takes 7.1 seconds, verifying the new tolerance in the background now. |
5 tasks
@KellenSunderland @marcoabreu Related fix is merged, should be good to close. |
@sandeep-krishnamurthy Related PR is merged, should be good to close. |
XinYao1994
pushed a commit
to XinYao1994/incubator-mxnet
that referenced
this issue
Aug 29, 2018
…bility. (apache#11422) * NIT: cleanup whitespace in Jenkinsfile * Mark test_get_optimal_thresholds as flaky See apache#11456 * Marking test_hybrid_static_memory_switching as flaky
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Example Run
http://jenkins.mxnet-ci.amazon-ml.com/blue/rest/organizations/jenkins/pipelines/incubator-mxnet/branches/PR-11422/runs/20/nodes/656/log/?start=0
Failing Output
The text was updated successfully, but these errors were encountered: