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

Flaky Test Issue of GPU Operator #11592

Description

@zhanghang1989

Description

kernel_error_check_imperative() and kernel_error_check_symbolic() in test_operator_gpu.py have flaky issues.

test_operator_gpu.test_kernel_error_checking ... Process SpawnProcess-1:

Traceback (most recent call last):

  File "/usr/lib/python3.5/multiprocessing/process.py", line 249, in _bootstrap

    self.run()

  File "/usr/lib/python3.5/multiprocessing/process.py", line 93, in run

    self._target(*self._args, **self._kwargs)

  File "/work/mxnet/tests/python/gpu/test_operator_gpu.py", line 1832, in kernel_error_check_imperative

    c = (a / b).asnumpy()

  File "/work/mxnet/tests/python/unittest/../../../python/mxnet/ndarray/ndarray.py", line 1910, in asnumpy

    ctypes.c_size_t(data.size)))

  File "/work/mxnet/tests/python/unittest/../../../python/mxnet/base.py", line 210, in check_call

    raise MXNetError(py_str(_LIB.MXGetLastError()))

mxnet.base.MXNetError: [19:32:53] src/operator/tensor/././../mxnet_op.h:586: Check failed: err == cudaSuccess (9 vs. 0) Name: mxnet_generic_kernel_ex ErrStr:invalid configuration argument

Activity

  1. marcoabreu commented on Jul 6, 2018

    @marcoabreu
    Contributor

    Hi, would you mind looking a CI run where this occurred?

  2. zhanghang1989 commented on Jul 6, 2018

    @zhanghang1989
    ContributorAuthor

    This fails at "/work/mxnet/tests/python/gpu/test_operator_gpu.py", line 1832, in kernel_error_check_imperative http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-11502/25/pipeline/799

  3. haojin2 commented on Jul 11, 2018

    @haojin2
    Contributor

    I cannot reproduce this error on my local machine, are you sure that this failure is not related to your PR? Seems like this is happening to other environments for the same build as well.

  4. zhanghang1989 commented on Jul 11, 2018

    @zhanghang1989
    ContributorAuthor

    I am closing this issue, since I don't have this issue any more. My PR just passed CI test.

  5. marcoabreu commented on Jul 11, 2018

    @marcoabreu
    Contributor

    Agree with @haojin2 , the error seems to be related to the PR. Thanks everybody!

  6. szha commented on Jul 27, 2018

    @szha
    Member
  7. ChaiBapchya commented on Nov 2, 2018

    @ChaiBapchya
    Contributor
  8. ChaiBapchya commented on Feb 1, 2019

    @ChaiBapchya
    Contributor

    @szha Can we reopen this issue? Your latest PR on Notice #14043 has the same CI issue.

  9. reopened this on Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions