Details
- Reviewers
olasd vlorentz - Group Reviewers
Reviewers - Commits
- rDLDBASE3c687f0b1aff: core.loader: Migrate to latest snapshot_add, origin_visit_update api
rDLDBASE0c5d99bb76cf: core.loader: Count only the effectively new objects ingested
rDLDBASE29e3573da8f7: core.loader: Adapt according to latest storage api change
pytest
(tox won't work as swh-storage is not tagged yet)
Diff Detail
- Repository
- rDLDBASE Generic VCS/Package Loader
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/97/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/97/console
I wonder if it wouldn't make sense to just turn the counter attribute into a dict compatible with the output of the storage functions...
swh/loader/core/loader.py | ||
---|---|---|
286 | Why this change? I don't think it will play well with a non-remote storage, because they return iterators. |
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/100/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/100/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/101/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/101/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/102/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/102/console
Build is green
See https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/103/ for more details.
It feels a little weird to have different counters in the dict and in the logs, but this is after filtering out the existing objects so the difference should be minimal anyway.
In a further step, it'd be nicer to make the loader-core counters compatible with the parsing done in swh.storage, so we can get a breakdown of operations per loader without jumping through too many hoops
swh/loader/core/loader.py | ||
---|---|---|
431 | I'm not sure this was intended? |
swh/loader/core/loader.py | ||
---|---|---|
431 | no, it was not ;) Your 'weird' feeling about the counter discrepancy was shared and i started something. That's a left over! |
Build is green
See https://jenkins.softwareheritage.org/job/DLDBASE/job/tox/104/ for more details.
In a further step, it'd be nicer to make the loader-core counters compatible with the parsing done in swh.storage, so we can get a breakdown of operations per loader without jumping through too many hoops
i have opened T1626 to track this by the way.
Cheers,