Long story short, I had an emerge run failing with: 31.64 >>> Running pre-merge checks for sys-kernel/linux-firmware-20240811 31.67 --2024-08-16 19:50:35-- http://127.0.0.1:8787/sys-kernel/linux-firmware/linux-firmware-20240811-1.gpkg.tar 31.67 Connecting to 127.0.0.1:8787... connected. 31.67 HTTP request sent, awaiting response... 404 File not found 31.67 2024-08-16 19:50:35 ERROR 404: File not found. 31.67 31.83 >>> Failed to emerge sys-kernel/linux-firmware-20240811 However, this was followed by tons of verbose binpkg fetching output from other pre-merge checks, and it was really hard to find what actually failed. I think Portage should at least print some summary which pre-merge checks failed at the end.
(In reply to Michał Górny from comment #0) > However, this was followed by tons of verbose binpkg fetching output from > other pre-merge checks, and it was really hard to find what actually failed. Ultimately the fetch output should be suppressed and support retry in the background for bug 936287. > I think Portage should at least print some summary which pre-merge checks > failed at the end. Good plan.
Each pre-merge check failure is supposed to trigger a call to the _record_pkg_failure method, so maybe we should add a parameter there to indicate which phase failed.
