I don't know if it's related, but I got a segmentation fault when running the archiver's tests in asynchronous mode.

Could you please try to test when you move all the softwareheritage-related configs away?

This can be set in the archiver config file.
However, this is just a flag in the archiver director constructor that is set to false to allow the tests to run without celery.

Could you please try to test when you move all the softwareheritage-related configs away?

In T436#6870, @olasd wrote:

What does "when tests run in synchronous mode" mean? Is that a configuration variable? Where is it supposed to be set?

What does "when tests run in synchronous mode" mean?

Definitely a celery issue :

In T436#6866, @qcampos wrote:

Definitely a celery issue : make test run without any error on my side when tests runs in synchronous mode (using run_sync_worker).

@olasd I don't reproduce this.
make test is ok on my side.
(I'm on the last commit of every repository from swh-environment.)

Definitely a celery issue : make test run without any error on my side when tests runs in synchronous mode (using run_sync_worker).

@qcampos: I'm running make test in the swh-storage repo. I believe @jbertran had the same test failures when we looked at it yesterday.

I can't recreate the same bug, when I run the archiver test in asynchronous mode.
Maybe this is a celery configuration issue ? Seems like the task is not registered into a worker.

In T304#6389, @qcampos wrote:

I see two options for the checker : it can run on each backup server, or only in the master storage which will manage the check scheduling and order.

• The first option means whe won't increase the master's load, but require the slaves to have some softs (celery, cron ?)

I see two options for the checker : it can run on each backup server, or only in the master storage which will manage the check scheduling and order.

Ready to be deployed on banco.

In T405#5935, @zack wrote:

I'm not sure if the archiver @qcampos is developing uses objstorage for both read and write. If so, both tasks are at the same priority; if not depoying on banco (for the write end of the archival) is more urgent.

Note that there are at least 2 separate sub-tasks here, with potentially different priorities: