From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>,
Romain Naour <romain.naour@smile.fr>,
Peter Korsgaard <peter@korsgaard.com>,
Arnout Vandecappelle <arnout@rnout.be>,
Julien Olivain <ju.o@free.fr>
Subject: [Buildroot] Status of defconfigs
Date: Sat, 30 Aug 2025 08:11:50 +0200 [thread overview]
Message-ID: <20250830081150.294e40e0@windsurf> (raw)
Hello,
I analyzed the results of the Gitlab CI pipeline for the last defconfig
build. The full details are below, but the summary is:
- 2 more patches sent to drop two additional at91/atmel defconfigs
- pine64_star64 has some patches on the mailing list from Thomas
Bonnefille that fix the issues => to be reviewed/merged
- raspberrypi3_qt5we is always too long to build (it includes Webkit).
Drop the defconfig? Exclude it from Gitlab CI testing?
- beagleboneai and roseapplepi are waiting for fixes from Peter
- snps_archs38_hsdk has only very recently started failing (a week ago)
and I don't see what recent changes could have broken it. Ideas?
- ts4900 has a build failure in glibc due to the version of the kernel
headers being used. But that seems like a real issue in glibc, not
actually a defconfig issue as any other build using the same kernel
headers version would fail in the same way
Thomas
at91sam9260eknf_defconfig => patch sent to drop
orangepi_lite2_defconfig => removed after pipeline was started
pcengines_apu2_defconfig => removed after pipeline was started
imx6ulz_bsh_smm_m2_defconfig => false positive, job restarted
at91sam9g45m10ek_defconfig => removed after pipeline was started
at91sam9rlek_defconfig => removed after pipeline was started
atmel_sama5d3xek_defconfig => patch sent to drop
beelink_gs1_defconfig => removed after pipeline was started
bananapro_defconfig => removed after pipeline was started
engicam_imx6qdl_icore_defconfig => removed after pipeline was started
engicam_imx6qdl_icore_rqs_defconfig => removed after pipeline was started
rock64_defconfig => removed after pipeline was started
pine64_star64_defconfig => patches from Thomas Bonnefille to review/merge
at91sam9g20dfc_defconfig => removed after pipeline was started
pine64_sopine_defconfig => removed after pipeline was started
raspberrypicm4io_64_defconfig => false positive, job restarted
raspberrypi3_qt5we_defconfig => this job is too long. Should we drop from CI testing?
engicam_imx6ul_geam_defconfig => removed after pipeline was started
chromebook_snow_defconfig => removed after pipeline was started
beagleboneai_defconfig => waiting for fixes from Peter Korsgaard
engicam_imx6ul_isiot_defconfig => removed after pipeline was started
engicam_imx6qdl_icore_qt5_defconfig => removed after pipeline was started
galileo_defconfig => removed after pipeline was started
odroidxu4_defconfig => removed after pipeline was started
orangepi_one_plus_defconfig => removed after pipeline was started
riotboard_defconfig => removed after pipeline was started
ts7680_defconfig => removed after pipeline was started
rock_pi_n8_defconfig => removed after pipeline was started
snps_archs38_hsdk_defconfig => this defconfig was building a week ago. Weird?!?
https://gitlab.com/buildroot.org/buildroot/-/jobs?name=T%3Dsnps_archs38_hsdk&kind=BUILD
sipeed_licheepi_zero_defconfig => fixed by Julien
toradex_apalis_imx6_defconfig => removed after pipeline was started
ts4900_defconfig => causing a glibc build failure, not due to the defconfig
roseapplepi_defconfig => waiting for fixes from Peter Korsgaard
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2025-08-30 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 6:11 Thomas Petazzoni via buildroot [this message]
2025-09-05 6:34 ` [Buildroot] Status of defconfigs Thomas Petazzoni via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250830081150.294e40e0@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@rnout.be \
--cc=ju.o@free.fr \
--cc=peter@korsgaard.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.