On Sep 15 2023, Maxim Kuvyrkov wrote:
> For background, both aarch64 and aarch32 testing is done in docker containers
> with very similar-looking rootfs images constructed from the same Dockerfile
> template [3]. Therefore, it's unlikely that we forgot to include a tool or
> binary in the aarc
On Sep 14 2023, Siddhesh Poyarekar wrote:
> I'm looking at the logs and all it has is:
>
> original exit status 127
> running post-clean rsync
>
> for the new test.
127 is command not found in the shell.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 25
On 2023-09-14 16:32, ci_not...@linaro.org wrote:
Dear contributor, our automatic CI has detected problems related to your
patch(es). Please find some details below. If you have any questions, please
follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's
#linaro-tcwg channel
On 9/14/23 17:04, Siddhesh Poyarekar wrote:
>
>
> On 2023-09-14 16:32, ci_not...@linaro.org wrote:
>> Dear contributor, our automatic CI has detected problems related to your
>> patch(es). Please find some details below. If you have any questions,
>> please follow up on linaro-toolchain@lists
Hi All,
As Siddhesh has pointed out, 32-bit ARM has other similar nss/* tests failing
with "original exit status 127". We do not have these failures for 64-bit
AArch64.
There seems to be a problem unrelated to Siddhesh's patch.
Adhemerval, would you please investigate what's causing it? I see
