Sentry issue: SWH-LOADER-SVN-54

In D7039#183023, @olasd wrote:

Thanks.

--build-dep-resolver=aptitude should only be used when building with an extra-repository which has a non-default priority, that is only when using a -backports suite (so only for the bullseye and buster instructions). It should probably be documented in the list of "useful options" rather than as the default.

Build is green

Rebase

Build has FAILED

couple of question/suggestion inline.

Rebase

couple of question/suggestion inline.

• a visit_type 'https' (record 3 below [1]).

*that* is fishy. I'm investigating.

Ok, got it: unluckily this one string is viciously malformed (it's wrong, but fits the
regexp anyway), and I had not considered this very case. Looking at the bright side,
this shows a tricky bug that will be fixed.

In T3746#77610, @ardumont wrote:

• missing last_update entries in the task (I recalled we discussed and fixes those in the related diffs)

@vsellier already did this to benchmark cassandra. it's indeed necessary to see how the backends behave with real loader and vault workloads. (less so for the objstorage, since the workloads should be much more uniform)

In T3746#77695, @borisbaldassari wrote:

Still, there is something fishy about:

• a visit_type 'https' (record 3 below [1]).

*that* is fishy. I'm investigating.

I'mt not exactly sure why I thought that would be necessary for benchmarking. In any case... it's not ;-)

The documentation is at:

It's documented in the winery test environment and was actually able to use the instructions successfully (after a few fixes...). It does work an this can be closed as resolved.

Added a wiki page to be a more accessible version of the benchmark process than the README in the sources.

Build is green

Add special case for revisions, compress with ZST

Build is green

Adjust the disk names on grid5000 to reflect changes at https://www.grid5000.fr/w/Grenoble:Hardware#dahu