Use explicit configuration (without journal writer) for algos tests
ClosedPublic
Actions

Authored by olasd on Jun 4 2020, 4:15 PM.

Details

Reviewers

Commits

rDSTO25f584ffc4d2: Use explicit configuration (without journal writer) for algos tests

Summary

Using the in-memory journal writer sometimes makes the tests hang when (very)
large objects are used. This works around the issue.

Test Plan

tox with the same seed as the debian package build goes through

Diff Detail

Repository

rDSTO Storage manager

Lint

Automatic diff as part of commit; lint not applicable.

Unit

Automatic diff as part of commit; unit tests not applicable.

Event Timeline

olasd created this revision.Jun 4 2020, 4:15 PM

Build is green

Patch application report for D3226 (id=11438)

Rebasing onto f9b2ca3fec...

Current branch diff-target is up to date.

Changes applied before test

commit 25f584ffc4d27017f0ee94a95f9fbdf3e4c5a311
Author: Nicolas Dandrimont <nicolas@dandrimont.eu>
Date:   Thu Jun 4 16:14:07 2020 +0200

    Use explicit configuration (without journal writer) for algos tests
    
    Using the in-memory journal writer sometimes makes the tests hang when (very)
    large objects are used. This works around the issue.

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

Harbormaster completed remote builds in B12642: Diff 11438.Jun 4 2020, 4:23 PM

douardda accepted this revision.Jun 4 2020, 4:28 PM

This revision is now accepted and ready to land.Jun 4 2020, 4:28 PM

Closed by commit rDSTO25f584ffc4d2: Use explicit configuration (without journal writer) for algos tests (authored by olasd). · Explain WhyJun 4 2020, 4:33 PM

This revision was automatically updated to reflect the committed changes.

olasd added a commit: rDSTO25f584ffc4d2: Use explicit configuration (without journal writer) for algos tests.