Lakshmipathi Ganapathi

@kdave I will explore Gitlab CI, have some experience with it.

I agree with using nest virtualization. Previously I tired something like [btrfsqa](https://github.com/Lakshmipathi/btrfsqa) but it uses aws instance. Something like Gitlab docker/qemu will be a good alternative. We can utilize gitlab...

Gitlab doesn't allow forked project to have CI runs. So imported btrfs-progs from github and added gitlab-ci scripts https://gitlab.com/giis/btrfs-progs/commits/gitlabci gitlab-ci flow: 1. Create qemu image using debootstrap with appropriate pkgs....

Successful job running `make test-cli` with above setup https://gitlab.com/giis/btrfs-progs/-/jobs/230278586

okay. I'll create gitlab repo to host recent kernel bzImage file. We can fetch it from there and use with btrfs-progs testing. Is that fine?

Hi @adam900710, thats a good idea. Let me check whether I can extract kernel from docker image of OpenSUSE tumbleweed and then use that with QEMU.

Hi @CyberShadow . I was busy with work for last few week and just this Friday I started looking into this again. (https://gitlab.com/giis/btrfs-progs/pipelines) . Plan is to skip every day...

> Why is there such a dramatic difference when running them on CI? That's because its run inside docker with qemu. Nested virutalization slowing things. >I've disabled convert tests from...

This pipeline with parallel tests took less than 30 mins. https://gitlab.com/giis/btrfs-progs/pipelines/77289785

Thats nice. yes , UML another alternative which is in-between bare-metal and complete VM approach. I'm under the assumption that using qemu inside Docker may be helpful in future testing...