rbd bench on the images created

There is a 3% space overhead on the RBD data pool. 6TB data, 3TB parity = 9TB. Actual 9.3TB, i.e. ~+3%.

https://www.grid5000.fr/w/Grenoble:Network shows the network topology

Complete rewrite to:

This should help:

12:08 <+ardumont> fwiw, i don't see swh-dataset in the jenkins ci declaration so that won't get published
12:08 <+ardumont> https://forge.softwareheritage.org/source/swh-jenkins-jobs/browse/master/jobs/swh-packages.yaml
12:10 <+ardumont> (relatedly without ^ that won't show up in jenkins)
12:10 <+ardumont> related docs https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_repository_on_Phabricator and https://wiki.softwareheritage.org/wiki/Debian_packaging#Setting_up_the_repository_on_Phabricator

I'm confused about the status of this task. I've just rebuilt the docs for docs.s.o and it says "build succeeded, 83 warnings.". So is the fix for this not yet "deployed" somehow? Also, why is the build succeeding even with all those warnings? Because as long as that's the case, we will for sure keep reintroducing warnings as time goes by.

Should I add the names of other contributors as well?

Should I add the names of other contributors as well?

There is no hg origin for now but this is configurable so as soon as one one is found, this will be checked as well.

In the mean time, this error should not be too blocking on pergamon.

Damn, I tried to deploy the end to end save code now check but computer says no [1]

Adapt according to suggestion

just one question inline regarding the icinga test name.
Otherwise, looks good

Build is green

squashing of commits

rebase

Build is green

For the fun, 100% coverage on the module now ;)

lgtm

Build is green

Rework failed scenario docstring

Build is green

Rework commit message

Rework commit message

Build is green

yes, great ;)

Reuse variable instead of duplicating (i forgot to reuse it)

@rdicosmo great summary, I'm certainly on that page :)

Build is green

Reformat assertion a bit

Build is green

Last conditional scenario, plain failure

Build is green

Exceeding threshold scenario

Build is green

Update conditional paths

\o/ https://jenkins.softwareheritage.org/job/DDOC/job/dev/5528/

Build is green

I fixed the unit tests that didn't work because of the default argument value of max_edges (it was None instead of 0) in graph.py

Build is green

Start testing

Build is green

Build has FAILED

Use :file: role instead of escaping *.

Build was aborted

• he was not in the list of members of the swh-team (thanks @ardumont for adding me to the owners of the list)

In D5544#140552, @anlambert wrote:

Arf, still two warnings remaining but no clear indication where they come from: https://jenkins.softwareheritage.org/job/DDOC/job/dev/5526/artifact/swh-docs/docs/errors.log/*view*/

reword in a clearer way