cran: Fix ListedOrigin visit type

CRAN origins must be loaded with the cran visit type and not the tar one.

This is the reason why the CRAN origins are marked as not visited in scheduler metrics.

It also means that CRAN origins currently do not get loaded in production as there is no scheduler task type named load-tar.

Related to swh-scheduler#3675 (closed)

---

Migrated from D6539 (view on Phabricator)

Some references in the commit message have been migrated:

• T3675 is now swh-scheduler#3675 (closed)

Build is green

Patch application report for D6539 (id=23774)

Rebasing onto 5bba1a78...

Current branch diff-target is up to date.

Changes applied before test

commit 20232cc36ea79b9195055ee68a6d0ff789a4d0de
Author: Antoine Lambert <anlambert@softwareheritage.org>
Date:   Fri Oct 22 14:36:02 2021 +0200

    cran: Fix ListedOrigin visit type
    
    CRAN origins must be loaded with the cran visit type and not the tar one.
    
    Related to swh/devel/swh-scheduler#3675

See https://jenkins.softwareheritage.org/job/DLS/job/tests-on-diff/400/ for more details.

mentioned in issue swh-scheduler#3675 (closed)

Thanks.

That makes sense for almost everything.

I don't get how they end up having a snapshot... Maybe the runs happen prior to the lister refactoring.

Merge request was accepted

approved this merge request

Merge request was merged

closed