svn: An error occurred when running svnrdump and no exploitable dump file has been generated.
This is a recurring problem. It also seems to be proeminent one in the sourceforge svn origins dataset to ingest [2] [3]
This needs fixing.
A proper modus operandi which worked for the mercurial loader proposal. First lookout a svn origin with that problem. Wrap a test which tries to load that repository and fail the same way. Then debug it the pdb way to determine the source of the issue.
-
[1] https://sentry.softwareheritage.org/share/issue/4295e7cc58884f528e73c5ea9ff6e235/
-
[2] no data to show but to lookup a kibana dashboard with it, the workers (worker[17-18] running that dataset does not push issues to sentry because of a current systemd limitation in our puppet manifests regarding one env variable for sentry...)
-
[3]
Sep 28 08:04:03 worker18 python3[58950]: [2021-09-28 08:04:03,449: INFO/MainProcess] Received task: swh.loader.svn.tasks.DumpMountAndLoadSvnRepository[decc664e-ed22-45ff-931b-a8ed02e1075b]
Sep 28 08:04:03 worker18 python3[105921]: [2021-09-28 08:04:03,516: INFO/ForkPoolWorker-232] Load origin 'https://svn.code.sf.net/p/white-rats-studios/svn' with type 'svn'
Sep 28 08:04:04 worker18 python3[105921]: [2021-09-28 08:04:04,177: ERROR/ForkPoolWorker-232] Loading failure, updating to `failed` status
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/swh/loader/core/loader.py", line 335, in load
self.prepare()
File "/usr/lib/python3/dist-packages/swh/loader/svn/loader.py", line 756, in prepare
dump_path = self.dump_svn_revisions(self.svn_url, last_loaded_svn_rev)
File "/usr/lib/python3/dist-packages/swh/loader/svn/loader.py", line 745, in dump_svn_revisions
"An error occurred when running svnrdump and "
Exception: An error occurred when running svnrdump and no exploitable dump file has been generated.
Migrated from T3613 (view on Phabricator)