Hypothesis can generate chain of aliases in a snapshot content. We could also encounter
such cases in real world data so we need to handle it.
Details
- Reviewers
olasd - Group Reviewers
Reviewers - Commits
- rDWAPPS11cf6b1b2766: api/snapshot: Handle aliases chain when resolving real branch target
This issue was discovered by an already written test when using the slow hypothesis
profile mode.
Depends on D2382
Diff Detail
- Repository
- rDWAPPS Web applications
- 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/DWAPPS/job/cypress-diff/419/
See console output for more information: https://jenkins.softwareheritage.org/job/DWAPPS/job/cypress-diff/419/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/820/
See console output for more information: https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/820/console
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/821/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/cypress-diff/420/ for more details.
This is crying for a "lazy-loaded snapshot object" abstraction in swh.storage, but I guess that's a good step up from the status quo :)
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/825/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/cypress-diff/423/ for more details.