[BUG] Native CI omits the pipe client #42

Closed
opened 2026-10-15 11:16:52 +02:00 by erikinkinen · 2 comments
Owner

Summary

Posixd CI omits realm-pipe-client from its native client checks. The SIGPIPE
witness has a native entrypoint, so host tests do not cover all of its code.

Reproduction

At 94e8cb8fbbc05ef1f829aec3a8b5445e74c93d72, compare the declared binaries in
Cargo.toml with the native build loop in .github/workflows/ci.yml.
src/realm_pipe_client.rs selects its implementation for x86_64-unknown-none,
but the workflow checks only the byte, binding and thread clients.

Expected and actual behavior

Every declared native client should receive strict Clippy and debug/release
builds with its existing linker script and fatal linker warnings. The pipe
client receives host tests but none of those native checks.

Environment and identity

  • Posixd: 94e8cb8fbbc05ef1f829aec3a8b5445e74c93d72.
  • Target: x86_64-unknown-none; local checks use Rust 1.97.1.
  • This is a workflow coverage defect. The last working workflow revision is
    unknown.

Evidence and prior checks

The manifest declares realm-pipe-client, and its source uses native
no_std/no_main configuration. The existing workflow's client loop omits it.
The same strict native Clippy and debug/release commands succeed when run for
this client with linker-client.ld.

Tracking

  • Add the pipe client to the existing CI loop without changing its checks.
  • Complete its strict native Clippy and debug/release builds.
  • Confirm a new component workflow executes the added native checks.
## Summary Posixd CI omits `realm-pipe-client` from its native client checks. The SIGPIPE witness has a native entrypoint, so host tests do not cover all of its code. ## Reproduction At `94e8cb8fbbc05ef1f829aec3a8b5445e74c93d72`, compare the declared binaries in `Cargo.toml` with the native build loop in `.github/workflows/ci.yml`. `src/realm_pipe_client.rs` selects its implementation for `x86_64-unknown-none`, but the workflow checks only the byte, binding and thread clients. ## Expected and actual behavior Every declared native client should receive strict Clippy and debug/release builds with its existing linker script and fatal linker warnings. The pipe client receives host tests but none of those native checks. ## Environment and identity - Posixd: `94e8cb8fbbc05ef1f829aec3a8b5445e74c93d72`. - Target: `x86_64-unknown-none`; local checks use Rust 1.97.1. - This is a workflow coverage defect. The last working workflow revision is unknown. ## Evidence and prior checks The manifest declares `realm-pipe-client`, and its source uses native `no_std`/`no_main` configuration. The existing workflow's client loop omits it. The same strict native Clippy and debug/release commands succeed when run for this client with `linker-client.ld`. ## Tracking - [x] Add the pipe client to the existing CI loop without changing its checks. - [x] Complete its strict native Clippy and debug/release builds. - [x] Confirm a new component workflow executes the added native checks.
Author
Owner

The workflow change is published in c702f3bf and included in PR #5. The added pipe-client commands have passed locally; this issue remains open until the new component workflow executes them.

The workflow change is published in [c702f3bf](https://git.erikinkinen.fi/erix/posixd/commit/c702f3bf6f9390fa106289332ac300210ff108b8) and included in [PR #5](https://git.erikinkinen.fi/erix/posixd/pulls/5). The added pipe-client commands have passed locally; this issue remains open until the new component workflow executes them.
Author
Owner

CI 327 executes the repaired workflow at c702f3bf6f9390fa106289332ac300210ff108b8. The pipe client completes strict native Clippy and both debug and release builds, alongside the existing clients. All three criteria are complete.

[CI 327](https://git.erikinkinen.fi/erix/posixd/actions/runs/327) executes the repaired workflow at `c702f3bf6f9390fa106289332ac300210ff108b8`. The pipe client completes strict native Clippy and both debug and release builds, alongside the existing clients. All three criteria are complete.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:35:08 +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/posixd#42
No description provided.