I have one job that keeps on adding new tests as soon as the one before is finished (using the API)
The restart the queue
There's X amount of jobs in waiting state in the database
There were some misconfiguration in the key db setup that didn't have the AOF persistence turned on, but I guess it should also be something in how we add jobs. If the job couldn't be added to the queue, it shouldn't be added to the database.
There's some configuration that can be tuned:
There were some misconfiguration in the key db setup that didn't have the AOF persistence turned on, but I guess it should also be something in how we add jobs. If the job couldn't be added to the queue, it shouldn't be added to the database.