comment out flaky SchedulerJobsTest (FINERACT-852)#764
Conversation
Also adds a new assertion for a clearer failure message than the confusing low-level technical ArrayIndexOutOfBoundsException for whenever this test will be re-activated later.
Adds a new assertion for a hopefully clearer failure message than the confusing low-level technical ArrayIndexOutOfBoundsException we regularly hit on Travis CI. Similar to apache#764
|
@awasum what's your view re. just ignoring a test? Ideally we should fix it, of course, but in the meantime... merge this? |
Ideally someone more familiar with the code should help us fix this. @Nayan , @nazeer1100126 , @vishwasbabu , @avikganguly01 . Help with resolving a flaky test as seen here: #756 so that we dont comment this out. If we cannot find anyone to help fix this, we may ignore the test by this weekend. Is that too far? Once we ignore this, we may forget that we did like in the other ignored test for data import and others. |
awasum
left a comment
There was a problem hiding this comment.
Merging this in a few minutes time. @vorburger , @thesmallstar , @xurror , @Nayan , @vishwasbabu , @avikganguly01 . We will need to come back to fixing this in the near future. For now..I am merging this to keep development going.
Also adds a new assertion for a clearer failure message than the
confusing low-level technical ArrayIndexOutOfBoundsException for
whenever this test will be re-activated later.