171e788ccd
On most filesystems file ctime is limited to 1 second granularity, which means that on faster computers multiple simple jobs (for instance dummy TestJob) can finish within the same second. The execution order test in ActiveJob integration tests relies on multiple TestJobs writing files then comparing the ctime. As a result integration tests would sometimes fail as the ctime of the files written by these TestJobs could have coincidental ctimes making the comparison for job order fail. This commit adds a far more precise execution time (to the extent that the Ruby Time class allows) to the file created by TestJob, and updates the execution order assertion to use it, removing the race condition. |
||
|---|---|---|
| .. | ||
| backburner | ||
| delayed_job/delayed | ||
| integration | ||
| que | ||
| queue_classic | ||
| sneakers | ||
| job_buffer.rb | ||