Your message dated Mon, 7 Aug 2017 16:30:50 -0700 with message-id <[email protected]> and subject line Re: git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone has caused the Debian Bug report #868738, regarding git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 868738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868738 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: git Version: 1:2.13.3-1 Severity: serious https://buildd.debian.org/status/package.php?p=git&suite=sid ... expecting success: test_must_fail git send-email --dump-aliases [email protected] -1 refs/heads/accounting --dump-aliases incompatible with other options test_must_fail: command not found: git send-email --dump-aliases [email protected] -1 refs/heads/accounting not ok 134 - --dump-aliases must be used alone # # test_must_fail git send-email --dump-aliases [email protected] -1 refs/heads/accounting # ... # failed 1 among 149 test(s) 1..149 Makefile:49: recipe for target 't9001-send-email.sh' failed make[4]: *** [t9001-send-email.sh] Error 1
--- End Message ---
--- Begin Message ---Version: 1:2.14.0-1 Control: tags -1 + unreproducible Jonathan Nieder wrote: > Thanks for reporting. The relevant code is > > die __("--dump-aliases incompatible with other options\n") > if !$help and $dump_aliases and @ARGV; > > test_must_fail prints the "command not found" message if and only if > the status code was 127. I would have expected it to be 1 or 128 > here. [...] > int exitstatus; > if (errno & 255) > STATUS_UNIX_SET(errno); > else { > exitstatus = STATUS_UNIX >> 8; > if (exitstatus & 255) > STATUS_UNIX_SET(exitstatus); > else > STATUS_UNIX_SET(255); > } > > which seems risky (there are many functions that could set errno, so > this is prone to spooky action at a distance if any caller forgets to > set it explicitly). Looking for errno values that could be 127 in > glibc and linux using "git grep --cached -e '#.*define.*E.*127'", I > find > > linux:arch/alpha/include/uapi/asm/errno.h:#define ERESTART 127 > linux:arch/mips/include/uapi/asm/errno.h:#define ENETDOWN 127 > linux:arch/sparc/include/uapi/asm/errno.h:#define ECANCELED 127 > linux:include/uapi/asm-generic/errno.h:#define EKEYEXPIRED 127 > > so that doesn't look likely to be the cause. > > Next step is to ssh into porterboxes and get the output of > > perl -e 'die "testing"'; echo $?" Alas, it doesn't appear to be reproducible. I fully expect this to happen again later, but closing for now.
--- End Message ---
