While testing the job, I sometimes have some flaky tests.
So looking at the logs I discovered that when failing I can see saq is running the very same cron job on a very short interval, I'm talking microseconds according to the logs, while my test fixture is supposed to run it every second.
Below this is the way I'm using the fixture below in this test
so at first I thought I may have another saq process (my dev env) that interferes with my tests, but I'm pretty confident it doesnt pick any job, queues names are different, I dont see any jobs processed in it,
I secondly thought maybe invoking await worker.schedule() would "add" jobs but it is flaky commented or not.
So I'm at a loss as to why the very same job supposed to run every second is running twice milliseconds appart sometimes
Greetings, I have saq running cron jobs only.
While testing the job, I sometimes have some flaky tests.
So looking at the logs I discovered that when failing I can see saq is running the very same cron job on a very short interval, I'm talking microseconds according to the logs, while my test fixture is supposed to run it every second.
Below this is the way I'm using the fixture below in this test
so at first I thought I may have another saq process (my dev env) that interferes with my tests, but I'm pretty confident it doesnt pick any job, queues names are different, I dont see any jobs processed in it,
I secondly thought maybe invoking
await worker.schedule()
would "add" jobs but it is flaky commented or not.So I'm at a loss as to why the very same job supposed to run every second is running twice milliseconds appart sometimes
Hope you may have an idea :)