squashfs tests flaky?
Hi,
I am playing around with the U-Boot CI, mostly to make sure my patches don't break things. To that end I created a fork of u-boot on GitLab and started the CI pipeline on the current master (8ddaf94358).
I see on the official repo the job passes [0]. But on my fork, the job fails due to squashfs failures [1]. Both jobs are using the same commit. I looked at the failure logs and it seems to be because of some I/O errors but I'm not sure what exactly is going on.
[0] https://source.denx.de/u-boot/u-boot/-/jobs/263093 [1] https://gitlab.com/prati0100/uboot/-/jobs/1234264642
On Tue, May 04, 2021 at 04:31:57PM +0530, Pratyush Yadav wrote:
Hi,
I am playing around with the U-Boot CI, mostly to make sure my patches don't break things. To that end I created a fork of u-boot on GitLab and started the CI pipeline on the current master (8ddaf94358).
I see on the official repo the job passes [0]. But on my fork, the job fails due to squashfs failures [1]. Both jobs are using the same commit. I looked at the failure logs and it seems to be because of some I/O errors but I'm not sure what exactly is going on.
[0] https://source.denx.de/u-boot/u-boot/-/jobs/263093 [1] https://gitlab.com/prati0100/uboot/-/jobs/1234264642
Flaky, no. But needs a fix for some files not being cleaned up, which the free runners on gitlab.com always trigger? Yes. Someone addressing that would be most welcome.
participants (2)
-
Pratyush Yadav -
Tom Rini