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

Flaky test test_io:test_ImageRecordIter_seed_augmentation #11359

Closed
marcoabreu opened this issue Jun 22, 2018 · 10 comments
Closed

Flaky test test_io:test_ImageRecordIter_seed_augmentation #11359

marcoabreu opened this issue Jun 22, 2018 · 10 comments

Comments

@marcoabreu
Copy link
Contributor

https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-11340/8/pipeline

test_io.test_ImageRecordIter_seed_augmentation ... [21:50:02] src/io/iter_image_recordio_2.cc:170: ImageRecordIOParser2: data/cifar/train.rec, use 4 threads for decoding..
[21:50:02] src/io/iter_image_recordio_2.cc:228: Load mean image from data/cifar/cifar10_mean.bin
[21:50:02] src/io/iter_image_recordio_2.cc:246: Load mean image from data/cifar/cifar10_mean.bin completed
[21:50:02] src/io/iter_image_recordio_2.cc:170: ImageRecordIOParser2: data/cifar/train.rec, use 4 threads for decoding..
[21:50:02] src/io/iter_image_recordio_2.cc:228: Load mean image from data/cifar/cifar10_mean.bin
[21:50:02] src/io/iter_image_recordio_2.cc:246: Load mean image from data/cifar/cifar10_mean.bin completed
FAIL


======================================================================
FAIL: test_io.test_ImageRecordIter_seed_augmentation
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/nose/case.py", line 198, in runTest
    self.test(*self.arg)
  File "/work/mxnet/tests/python/unittest/test_io.py", line 381, in test_ImageRecordIter_seed_augmentation
    assert(np.array_equal(data,data2))
AssertionError

Probably due to missing tolerances

@marcoabreu
Copy link
Contributor Author

14 out of 225 runs failed -> 6% failure rate

@wenyangchu
Copy link
Contributor

Hi @marcoabreu, can it be that the multithreading of this iterator does not guarantee the order of the patches?

@marcoabreu
Copy link
Contributor Author

I would have to check, but that could be a good start for further investigation.

@DickJC123
Copy link
Contributor

I posted a reply to a different issue here, then removed it. Sorry for the confusion.

@perdasilva
Copy link
Contributor

@marcoabreu this issue can now be closed =)

@lebeg
Copy link
Contributor

lebeg commented Jan 21, 2019

@marcoabreu would you close this issue as it has been resolved?

@lebeg
Copy link
Contributor

lebeg commented Feb 20, 2019

@marcoabreu ping

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

No branches or pull requests

7 participants