[BUG] Native members tests cannot compile without IPC block tracing #51
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/kernel#51
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
Hosted Kernel tests with the native members feature fail to compile when IPC block tracing is disabled. The disabled-feature control imports an enabled predicate that is excluded by its feature gate.
Reproduction
From Kernel
3f9ba9cd357bcd4474e24e1d9cc62e83891b9dab:An independent unchanged signed checkout reproduces the collection failure.
Expected and actual behavior
The cap-free predicate should be available to its disabled-feature test and return false. Actual tracing should stay disabled. Instead, rustc reports E0432 at
syscall/reporting_tests.rs:2:ipc_block_trace_enabledis configured out bydispatch_trace.rs. Cargo exits 101 before tests execute.Environment and identity
3f9ba9cd357bcd4474e24e1d9cc62e83891b9dab, unchanged signed dependency graph.Evidence and prior checks
The independent signed checkout and current implementation checkout both expose the same unresolved import. An explicitly trace-enabled graph compiles, but that does not satisfy the disabled-feature control. The repair compiles only the cap-free
cfg!predicate for tests or the trace feature. Every production trace cache, selection helper and emitter remains feature-gated. The enabled/disabled predicate control is moved out of the console-gated reporting module and stays active in every hosted feature graph, including default. No dead-code allowance is added.Tracking
Discovered while adding independent source-byte controls for the native terminal fixture. This is a separate test-collection defect; it does not establish a guest runtime failure.
The fix makes only the cap-free tracing predicate available to hosted tests and moves its selection control next to that predicate. The default, dedicated members and all-feature configurations now compile and pass. Production trace caches and emitters still require the explicit tracing feature.