Bug 15219

Summary:	Submit Toolchain testsuite results to upstream projects e.g. gcc
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Khem Raj <raj.khem>
Component:	devtools / tool chain	Assignee:	Unassigned <unassigned>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, sundeep.kokkonda, Yash.Shinde
Version:	unspecified
Target Milestone:	Future
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Khem Raj 2023-09-25 16:32:44 UTC

Yocto runs toolchain tests regularly, and we have latest maintained release of the toolchain projects usually, these testsuite results can be submitted upstream which can have multiple benefits

1. Increase project visibility in the toolchain community
2. Present OE/Yocto as a possible option for doing toolchain testing for new silicon bringup or new toolchain backend port etc.
3. Validate our results with wider toolchain community

The possible mailing lists are

GCC - https://gcc.gnu.org/mailman/listinfo/gcc-testresults
GLIBC - https://sourceware.org/mailman/listinfo/libc-testresults/
BINUTILS - https://sourceware.org/mailman/listinfo/binutils
GDB - https://sourceware.org/mailman/listinfo/gdb-testers/

Comment 1 Richard Purdie 2023-09-25 16:34:35 UTC

The idea would be to have automated preparation of the results so they could easily be sent upstream with minimal human effort.

Comment 2 Randy MacLeod 2023-09-28 14:34:25 UTC

A good idea, when we have time.

Comment 3 Randy MacLeod 2025-10-02 15:09:15 UTC

We have compared our test failures to upstream results
and we are continuing to minimize the now smaller differences.