kdave

> convert tests - 180 minutes 0 seconds (rebuilding btrfs-prog) I've disabled convert tests from the `devel` testing and enabled only for pre-release tests, so you can scratch that too...

> Building btrfs-progs (`./autogen.sh && ./configure && make -j8`) takes 16 seconds. > Running the CLI tests (`sudo make TEST_DEV=/tmp/test.img test-cli`) takes 18 seconds. > > Why is there such...

> According to https://docs.travis-ci.com/user/reference/overview/ it's 7.5G. Should be enough. Might not be enough for xfstests? 7.5 is more than enough, so the tmpfs for scratch image is ok, we just...

> According to https://docs.travis-ci.com/user/reference/overview/ it's 7.5G. Should be enough. Might not be enough for xfstests? Regarding fstests, I'm using VM instances with various memory sizes and 2G works too, the...

> Also it looks like it is barely possible to run all tests without Docker or root, but the approaches I found are hacky at best. I had hoped that...

> The goal I'm aiming for is to make it feasible to run the xfstests as part of CI, so that btrfs contributors can test their code simply by opening...

It's enabled now, thanks for letting me know.

I've started one pipeline manually and it failed at the begining, probably to download some files or configuration problme. @Lakshmipathi can you please have a look?

Container registry enabled in the settings

Docker build phase succeded, but kernel and image did not. Is there some ordering needed? From the logs it looks like they both depend on docker (ie. pulling gitlab-ci from...