Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
borg test failure on Ubuntu yakkety armhf #1310
Comments
|
What's the file system mounted at /tmp? Principially this is not a critical test failure. We're aware that this test depends on completely unspecified filesystem behaviour, it was only recently adjusted to work on more FSes. |
|
mount |grep tmp this is on a qemu-based pbuilder environment, not sure if offical buildds have a different configuration |
|
Hmm, strange. Normally tmpfs on Linux has no issues with this test, since it has sparse file support with page-granularity. The system doesn't have any odd page size ( |
|
I would wild guess 4096 but I can't be sure until I get official answers. |
|
I have been told to check this log to see the armhf environment does this answer your questions? |
|
so, 4096 but tmp is not under tmpfs
|
|
Strange... I thought rootfs == tmpfs, therefore there should be no problem. If rootfs != tmpfs then whatever rootfs is doesn't support sparse files as we expected (SEEK_HOLE => 83 MiB = EOF, no hole in the output file), but somehow the input file was still sparse. Huh? Or maybe the whatever-rootfs-really-is somehow doesn't expose/implement SEEK_HOLE/DATA correctly, since the check above that with the stat data succeeded. |
|
BTW I'll upload in Ubuntu any patch you give me :) |
|
@LocutusOfBorg can you try #1312? |
ThomasWaldmann
self-assigned this
Jul 11, 2016
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Jul 11, 2016
added a commit
to ThomasWaldmann/borg
that referenced
this issue
Jul 11, 2016
added a commit
that referenced
this issue
Jul 11, 2016
|
it seems good so far! closing and I'll reopen if it doesn't migrate in a few hours. thanks! |
LocutusOfBorg commentedJul 11, 2016
Hi, not sure what is wrong, in the meanwhile I'm retrying the build and attaching the log: