configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
--- configs/freescale_p1025twr_defconfig | 1 + 1 file changed, 1 insertion(+)
configs/freescale_p1025twr_defconfig +1 -0
@@ -12,6 +12,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.15.7" BR2_LINUX_KERNEL_DEFCONFIG="mpc85xx_smp" BR2_LINUX_KERNEL_DTS_SUPPORT=y BR2_LINUX_KERNEL_INTREE_DTS_NAME="fsl/p1025twr" +BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y # Filesystem BR2_TARGET_ROOTFS_CPIO=y
Signature · 1 line
2.14.3
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Quoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355Signed-off-by Thomas Petazzoni <[email protected]>
Committed, thanks.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
In reply to Thomas PetazzoniThomas,
Quoted 4 lines · Thomas Petazzoni
Fixes:
Sorry, I didn't realize this failed. Is there an automated email on this sort of failure?
Matt
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Hello,
Quoted 6 lines · Matthew Weber
Quoted 3 lines
Fixes:
Sorry, I didn't realize this failed. Is there an automated email on this sort of failure?
No, there isn't. Unfortunately, the Gitlab CI infra is not very reliable, and a number of failures are not related to real problems in Buildroot, but to Gitlab CI infrastructure problems.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Quoted 6 lines · Thomas Petazzoni
Hello,
Quoted 2 lines · Matthew Weber
Quoted 2 lines
Fixes:
Quoted 8 lines
Quoted 4 lines
Sorry, I didn't realize this failed. Is there an automated email on this sort of failure?
No, there isn't. Unfortunately, the Gitlab CI infra is not very reliable, and a number of failures are not related to real problems in Buildroot, but to Gitlab CI infrastructure problems.
Well, to be completely fair, it's not really the Gitlab CI infra which is
unreliable. Rather, it's the free runners that are unreliable. I expect that if we would have a dedicated runner, we wouldn't see these problems. At least, that's how it looks to me (I'm not really an expert though).
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 configs/freescale_p1025twr: needs host-openssl for the Linux kernel build
Arnout, Thomas,
Quoted 14 lines · Arnout Vandecappelle
Quoted 11 lines · Thomas Petazzoni
Hello,
Quoted 6 lines · Matthew Weber
Quoted 3 lines
Fixes:
Sorry, I didn't realize this failed. Is there an automated email on this sort of failure?
Quoted 9 lines
Quoted 3 lines
No, there isn't. Unfortunately, the Gitlab CI infra is not very reliable, and a number of failures are not related to real problems in Buildroot, but to Gitlab CI infrastructure problems.
Well, to be completely fair, it's not really the Gitlab CI infra which is
unreliable. Rather, it's the free runners that are unreliable. I expect that if we would have a dedicated runner, we wouldn't see these problems. At least, that's how it looks to me (I'm not really an expert though).
Has anyone setup a Gitlab console/REST client? We could build a script on top of that which monitors the failed builds and does log analysis (not sure what output our .gitlab-ci.yml is setup for capturing). Hopefully using that we could discard the bad jobs. Then we should be able to at least get the stage of failure from the API too, which if each defconfig is a stage we could then map to maintainer. Similarly for the test cases....
If there isn't a console/REST client setup....
- Could we generate some test API keys for the Buildroot Gitlab instance?
- Do we have a spot we could run this script if someone was to develop it?
Matt