Bug#869140: casync FTBFS on mips64el: test-casync TIMEOUT

[Felipe Sateler]

Control: forwarded -1 https://github.com/systemd/casync/issues/61

On Thu, Jul 20, 2017 at 4:18 PM, Adrian Bunk <bunk at debian.org> wrote:
> Source: casync
> Version: 1+65-1
> Severity: important
>
> https://buildd.debian.org/status/fetch.php?pkg=casync&arch=mips64el&ver=1%2B65-1&stamp=1500580132&raw=0
>
> ...
>    dh_auto_test -a
>         ninja test
> [0/1] Running all tests.
>  1/14 test-script.sh                          OK      633.39 s
>  2/14 test-script-sha256.sh                   OK      636.46 s
>  3/14 test-nbd.sh                             OK      177.02 s
>  4/14 test-fuse.sh                            OK      305.71 s
>  5/14 test-cachunk                            OK       6.05 s
>  6/14 test-cachunker                          OK       2.25 s
>  7/14 test-cachunker-histogram                OK       2.57 s
>  8/14 test-cadigest                           OK      10.35 s
>  9/14 test-caencoder                          OK       0.62 s
> 10/14 test-camakebst                          OK      19.00 s
> 11/14 test-caorigin                           OK       0.12 s
> 12/14 test-casync                             TIMEOUT 120.20 s
> 13/14 test-cautil                             OK       0.11 s
> 14/14 test-util                               OK       0.11 s
>
> OK:        13
> FAIL:       1
> SKIP:       0
> TIMEOUT:    1
>
>
> The output from the failed tests:
>
> 12/14 test-casync                             TIMEOUT 120.20 s
>
> --- command ---
> /<<BUILDDIR>>/casync-1+65/obj-mips64el-linux-gnuabi64/test-casync
> -------
>
> Full log written to /<<BUILDDIR>>/casync-1+65/obj-mips64el-linux-gnuabi64/meson-logs/testlog.txt
> FAILED: test
> /usr/bin/python3 -u /usr/share/meson/mesontest --no-rebuild --print-errorlogs
> ninja: build stopped: subcommand failed.
> dh_auto_test: ninja test returned exit code 1
> debian/rules:8: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 1
>
>
>
> On mipsel this test succeeded after 108.83 seconds, so this might
> just require an increased timeout (untested).

This test runs faster than test-camakebst on my amd64 machine, so
there may be a real issue.

-- 

Saludos,
Felipe Sateler