i have a code that schedules and runs threads as TimerTask-s.
Jenkins controls the sequence of tests it runs-- doesn't run another until one test unit returns.
However - does Jenkins control the threads-started-from-within-test in a similar way?
Our tests are failing, and this the only reason i can think of.
On the other hand, one wouldn't be surprised an integration/build environment has the strict control-- launches one test, waits till the processor clears each&every thread it started, and goes on with the next test.
TIA
Aucun commentaire:
Enregistrer un commentaire