generated from erix/meta
[BUG] TLS image fixture mutates an output without observing the result #6
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/lib-dynlink#6
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
TLS image fixture mutates an output without observing the result. Maintained validation cannot reach its intended successful boundary.
Reproduction
Run cargo clippy --all-targets --all-features -- -D warnings at the linked original revision. The strict CI test job compiles src/tls/tests.rs. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. The short-image/retry fixture assigns first[16]=0 and checks only the unchanged second image and original module. The compiler denies unused_assignments because it never reads the mutated first image, so the unit suite cannot run.
Environment and identity
Evidence and prior checks
Observe that the two independently initialized images now differ after mutation, while retaining the checks that the second image and immutable original module are unchanged. This strengthens the intended independent-image control without suppressing a warning or removing coverage.
Original failing CI job.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.