generated from erix/meta
[BUG] UEFI profile deadline conflicts with original command admission #7
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/bootloader#7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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, includinguefi_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.
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.