Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Flaky test(scala): test_arange #10387

Closed
anirudh2290 opened this issue Apr 3, 2018 · 10 comments
Closed

Flaky test(scala): test_arange #10387

anirudh2290 opened this issue Apr 3, 2018 · 10 comments

Comments

@anirudh2290
Copy link
Member

*** 1 TEST FAILED ***

[INFO] ------------------------------------------------------------------------

[INFO] Reactor Summary:

[INFO] 

[INFO] MXNet Scala Package - Parent ....................... SUCCESS [  2.834 s]

[INFO] MXNet Scala Package - Initializer .................. SUCCESS [  0.947 s]

[INFO] MXNet Scala Package - Initializer Native Parent .... SUCCESS [  0.497 s]

[INFO] MXNet Scala Package - Initializer Native Linux-x86_64 SUCCESS [ 11.852 s]

[INFO] MXNet Scala Package - Macros ....................... SUCCESS [  0.728 s]

[INFO] MXNet Scala Package - Core ......................... FAILURE [ 48.518 s]

[INFO] MXNet Scala Package - Native Parent ................ SKIPPED

[INFO] MXNet Scala Package - Native Linux-x86_64 CPU-only . SKIPPED

[INFO] MXNet Scala Package - Inference .................... SKIPPED

[INFO] MXNet Scala Package - Examples ..................... SKIPPED

[INFO] MXNet Scala Package - Spark ML ..................... SKIPPED

[INFO] MXNet Scala Package - Full Parent .................. SKIPPED

[INFO] MXNet Scala Package - Full Linux-x86_64 CPU-only ... SKIPPED

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 01:05 min

[INFO] Finished at: 2018-04-02T22:07:11+00:00

[INFO] Final Memory: 54M/2143M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.scalatest:scalatest-maven-plugin:1.0:test (test) on project mxnet-core_2.11: There are test failures -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

[ERROR] 

[ERROR] After correcting the problems, you can resume the build with the command

[ERROR]   mvn <goals> -rf :mxnet-core_2.11

Makefile:543: recipe for target 'scalatest' failed

make: *** [scalatest] Error 1

build.py: 2018-04-02 22:07:12,537 Running of command in container failed: docker run --rm -v /home/jenkins_slave/workspace/ut-scala-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-scala-cpu/build:/work/build -u 1001:1001 mxnet/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_cpu_scala

build.py: 2018-04-02 22:07:12,537 You can try to get into the container by using the following command: docker run --rm -v /home/jenkins_slave/workspace/ut-scala-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-scala-cpu/build:/work/build -u 1001:1001 -ti --entrypoint bash mxnet/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_cpu_scala

Traceback (most recent call last):

  File "ci/build.py", line 179, in <module>

    sys.exit(main())

  File "ci/build.py", line 159, in main

    container_run(platform, docker_binary, command)

  File "ci/build.py", line 110, in container_run

    raise subprocess.CalledProcessError(ret, cmd)

subprocess.CalledProcessError: Command 'docker run --rm -v /home/jenkins_slave/workspace/ut-scala-cpu:/work/mxnet -v /home/jenkins_slave/workspace/ut-scala-cpu/build:/work/build -u 1001:1001 mxnet/build.ubuntu_cpu /work/runtime_functions.sh unittest_ubuntu_cpu_scala' returned non-zero exit status 2

script returned exit code 1

Please see: http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-10374/1/pipeline/

@marcoabreu
Copy link
Contributor

See #8383 for reference

@ThomasDelteil
Copy link
Contributor

@ThomasDelteil
Copy link
Contributor

ThomasDelteil commented Apr 20, 2018

@lanking520
Copy link
Member

Any more reports? I cannot reproduce the 'Flaky', tried to run 100 times on a single Ubuntu machine and all passed.

@szha szha added this to To Do in Tests Improvement via automation Jun 21, 2018
@marcoabreu
Copy link
Contributor

@haojin2
Copy link
Contributor

haojin2 commented Jul 13, 2018

@marcoabreu Have we observed more occurrence of this?

@haojin2
Copy link
Contributor

haojin2 commented Jul 13, 2018

Plus, seems like a duplicate issue for #8834

@marcoabreu
Copy link
Contributor

I don't know. Let's come back when we see it again.

Duplicate of #8834

Tests Improvement automation moved this from To Do to Done Jul 13, 2018
@haojin2
Copy link
Contributor

haojin2 commented Mar 11, 2019

@lanking520
Copy link
Member

This is something different, with strange value came from the op

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

6 participants