[BUG] UEFI profile deadline conflicts with original command admission #7

Closed
opened 2026-10-14 13:40:27 +02:00 by erikinkinen · 1 comment
Owner

Summary

The UEFI profile build driver leaves a custom alarm callback installed while entering the selected command owner. Its native admission requires an owned raise-only alarm, so a profile command can be refused before its child or streams are acquired.

Reproduction

Run the original Bootloader CI at 433a16bfdeba1e1bbd0ae916bf9413b92742a333, including uefi_profile_build_test.py. The total-expiry control tries to read a command stdout receipt that was never created and raises FileNotFoundError.

Expected and actual behavior

Keep the original absolute build deadline active while admitting, running and retiring the original command. Preserve the first error and independently restore owned timer and action state. Instead, admission refuses the custom callback; the fixture then masks that refusal by assuming the command launched.

Environment and identity

Bootloader revision above; Linux 6.14 x86-64 Docker CI, selected Integration Python owner 4a87840c0343314fdc1957dc64bcf07c1d4c9a2a. This is a host build-driver failure; no guest or firmware boot was reached. No working profile-driver revision is established here.

Evidence and prior checks

The original CI failure is retained. Source inspection correlates the alarm conflict with the missing receipt. The proposed repair uses the selected owner's existing native alarm interfaces; its controls require a real child launch and original retirement across deadline expiry.

Tracking

Repository audit, artifact PR, phase completion.

  • Bind the selected original alarm without suspending or renewing the total deadline.
  • Preserve exact first and restoration failures, pending-alarm handling and uncertain holders.
  • Require actual launch and cleanup evidence, then complete the original profile workflow.
## Summary The UEFI profile build driver leaves a custom alarm callback installed while entering the selected command owner. Its native admission requires an owned raise-only alarm, so a profile command can be refused before its child or streams are acquired. ## Reproduction Run the original [Bootloader CI](https://git.erikinkinen.fi/erix/bootloader/actions/runs/171) at `433a16bfdeba1e1bbd0ae916bf9413b92742a333`, including `uefi_profile_build_test.py`. The total-expiry control tries to read a command stdout receipt that was never created and raises FileNotFoundError. ## Expected and actual behavior Keep the original absolute build deadline active while admitting, running and retiring the original command. Preserve the first error and independently restore owned timer and action state. Instead, admission refuses the custom callback; the fixture then masks that refusal by assuming the command launched. ## Environment and identity Bootloader revision above; Linux 6.14 x86-64 Docker CI, selected Integration Python owner `4a87840c0343314fdc1957dc64bcf07c1d4c9a2a`. This is a host build-driver failure; no guest or firmware boot was reached. No working profile-driver revision is established here. ## Evidence and prior checks The original CI failure is retained. Source inspection correlates the alarm conflict with the missing receipt. The proposed repair uses the selected owner's existing native alarm interfaces; its controls require a real child launch and original retirement across deadline expiry. ## Tracking [Repository audit](https://git.erikinkinen.fi/erix/bootloader/issues/2), [artifact PR](https://git.erikinkinen.fi/erix/bootloader/pulls/3), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Bind the selected original alarm without suspending or renewing the total deadline. - [x] Preserve exact first and restoration failures, pending-alarm handling and uncertain holders. - [x] Require actual launch and cleanup evidence, then complete the original profile workflow.
Author
Owner

Fixed in b2dfe005. The profile driver keeps the original admitted alarm active through command startup and retirement, restores owned state once, and retains uncertainty. The launch and expiry controls now require actual child receipts. The complete push workflow passes with no warnings.

Fixed in [b2dfe005](https://git.erikinkinen.fi/erix/bootloader/commit/b2dfe005bed164e0e69574dadd4907b7089ccbc5). The profile driver keeps the original admitted alarm active through command startup and retirement, restores owned state once, and retains uncertainty. The launch and expiry controls now require actual child receipts. [The complete push workflow](https://git.erikinkinen.fi/erix/bootloader/actions/runs/172) passes with no warnings.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:34 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/bootloader#7
No description provided.