Page MenuHomeSoftware Heritage

Fix bug on the isochrone graph creation function
ClosedPublic

Authored by aeviso on Dec 13 2021, 4:36 PM.

Details

Summary

Isochrone frontiers with the same timestamp as the revision being
processes need to be invalidated to guarantee that the first
occurrence of a blob always ends up in the content-early-in-revision
relation. A new test is added that test the case of an incorrectly
processed revision leading to inconsistencies.

Diff Detail

Repository
rDPROV Provenance database
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Build is green

Patch application report for D6829 (id=24755)

Rebasing onto 68ccaba838...

Current branch diff-target is up to date.
Changes applied before test
commit 29933f7bb18faac840c4482eac1cea4c543f64bb
Author: Andres Ezequiel Viso <aeviso@softwareheritage.org>
Date:   Mon Dec 13 16:31:58 2021 +0100

    Fix bug on the isochrone graph creation function
    
    Isochrone frontiers with the same timestamp as the revision being
    processes need to be invalidated to guarantee that the first
    occurrence of a blob always ends up in the content-early-in-revision
    relation. A new test is added that test the case of an incorrectly
    processed revision leading to inconsistencies.

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

This revision is now accepted and ready to land.Dec 13 2021, 5:07 PM

Build is green

Patch application report for D6829 (id=24768)

Rebasing onto 68ccaba838...

Current branch diff-target is up to date.
Changes applied before test
commit eb48f7960d06f12788a5e16f84f03527fac8b504
Author: Andres Ezequiel Viso <aeviso@softwareheritage.org>
Date:   Mon Dec 13 16:31:58 2021 +0100

    Fix bug on the isochrone graph creation function
    
    Isochrone frontiers with the same timestamp as the revision being
    processes need to be invalidated to guarantee that the first
    occurrence of a blob always ends up in the content-early-in-revision
    relation. A new test is added that test the case of an incorrectly
    processed revision leading to inconsistencies.

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