Re: [PATCH] binutils: don't abort debuginfod.exp when the server cleanup kill fails
Project / Subsystem
binutils / binutils
Date
2026-09-05
Proposer
Sam James <sam@gentoo.org>
Source type
public_inbox
Consensus
Committed
Sentiment
—/10
Technical tradeoffs
- • Masking underlying issues with `kill` success/failure in favor of test case continuity.
All attributes
- project
- binutils
- subsystem
- binutils
- patch_id
- —
- discussion_id
- 87tso4drjo.fsf@gentoo.org
- source_type
- public_inbox
- title
- Re: [PATCH] binutils: don't abort debuginfod.exp when the server cleanup kill fails
- headline
- binutils: don't abort debuginfod.exp when the server cleanup kill fails
- tldr
- Fixes a testsuite issue where a failed kill command during debuginfod server cleanup caused the entire test file to abort instead of just failing the specific…
- proposer
- Sam James <sam@gentoo.org>
- consensus
- Committed
- outcome
- committed
- sentiment_score
- —
- technical_tradeoffs
-
- • Masking underlying issues with `kill` success/failure in favor of test case continuity.
- series_id
- —
- series_role
- reply
- series_parts
- []
- tags
-
- • binutils
- • testsuite
- • debuginfod
- • regression
- bugzilla_url
- —
- date
- 2026-09-05T00:00:00.000Z
Re: [PATCH] binutils: don't abort debuginfod.exp when the server cleanup kill fails
A patch addresses a bug in the binutils testsuite where a non-zero exit code from the kill command during debuginfod server cleanup would cause the DejaGnu test framework to abort the entire test file. This prevented subsequent tests from running. The fix wraps the kill commands in catch to prevent this spurious abort, allowing the test to report a failure but continue execution.