On Mon, Oct 19, 2020 at 04:12:12PM -0400, Don Zickus wrote: > On Mon, Oct 19, 2020 at 11:09:57AM +0200, Jiri Benc wrote: > > On Thu, 15 Oct 2020 12:20:41 +0200, Jiri Benc wrote: > > > On Thu, 15 Oct 2020 09:13:27 -0000, CKI Project wrote: > > > > Overall result: FAILED (see details below) > > > > Merge: OK > > > > Compile: FAILED > > > > > > Given the failure emails are sent to [email protected] > > > daily, I wonder, is there any value in them? I'm just ignoring them and > > > considering setting up a filter, as they are not actionable for anyone > > > and thus are just noise. > > > > CKI team, could you please comment on this? > > Sorry about that. I thought things were failing because of ARK infra but > now they are failing due to libbpf on s390x. Does bpf compile there? > > 00:01:13 BUILDING A KERNEL FOR s390x... > 00:01:13 ++ perl -e 'print "42.test.fc34" =~ s/\.pr\.[0-9A-Fa-f]{32}//r' > 00:01:13 + ShortRel=42.test.fc34 > 00:01:13 + perl -p -i -e 's/^EXTRAVERSION.*/EXTRAVERSION = > -42.test.fc34.s390x/' Makefile > 00:01:13 + perl -p -i -e 's/^PATCHLEVEL.*/PATCHLEVEL = 9/' Makefile > 00:01:13 + /usr/bin/make CROSS_COMPILE=s390x-linux-gnu- -s HOSTCFLAGS= > HOSTLDFLAGS= -j30 mrproper > 00:01:16 + cp configs/kernel-5.9.0-s390x.config .config > 00:01:16 + cp /tmp/rpmbuild/SOURCES/x509.genkey certs/. > 00:01:16 ++ head -1 .config > 00:01:16 ++ cut -b 3- > 00:01:16 + Arch=s390 > 00:01:16 + echo USING ARCH=s390 > 00:01:16 USING ARCH=s390 > 00:01:16 + KCFLAGS= > 00:01:16 + '[' '' == '' ']' > 00:01:16 + KCFLAGS=' ' > 00:01:16 + /usr/bin/make CROSS_COMPILE=s390x-linux-gnu- -s HOSTCFLAGS= > HOSTLDFLAGS= ARCH=s390 olddefconfig > 00:01:18 + perl -p -i -e > 's/^CONFIG_BUILD_SALT.*/CONFIG_BUILD_SALT="5.9.0-42.test.fc34.s390x"/' .config > 00:01:18 + /usr/bin/make CROSS_COMPILE=s390x-linux-gnu- -s HOSTCFLAGS= > HOSTLDFLAGS= ARCH=s390 'KCFLAGS= ' WITH_GCOV=0 -j30 bzImage > 00:01:23 > 00:01:23 Auto-detecting system features: > 00:01:23 ... libelf: [ [32mon[m ] > 00:01:23 ... zlib: [ [32mon[m ] > 00:01:23 ... bpf: [ [32mon[m ] > 00:01:23 > 00:01:25 LINK resolve_btfids > 00:04:11 libbpf: non-native ELF endianness is not supported
there was recent change for libbpf that should fix this: 3289959b97ca libbpf: Support BTF loading and raw data output in both endianness jirka > 00:04:12 FAILED: load BTF from vmlinux: Unknown error -4001make: *** > [Makefile:1166: vmlinux] Error 255 > 00:04:12 error: Bad exit status from /var/tmp/rpm-tmp.dfy0KE (%build) > > Cheers, > Don > _______________________________________________ > kernel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] _______________________________________________ kernel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
