Skip to content

ci(openbsd): exclude feat_require_unix_utmpx - #15736

Open
xtqqczze wants to merge 1 commit into
uutils:mainfrom
xtqqczze:build/openbsd-utmpx
Open

xtqqczze wants to merge 1 commit into
uutils:mainfrom
xtqqczze:build/openbsd-utmpx

Conversation

@xtqqczze

@xtqqczze xtqqczze commented Oct 25, 2026 •

Copy link
Copy Markdown
Collaborator

utmpx not supported for opensbd

@xtqqczze
xtqqczze marked this pull request as draft October 25, 2026 12:36
fail-fast: false
matrix:
job:
- { features: "feat_Tier1,feat_require_unix" }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might hardcoded feat_os_unix at previous PR.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, you removed feat_os_unix in #15547. I don't think that is right though as we now don't check feat_Tier1.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@oech3 matrix build is unnecessary though, how about:

    env:
      FEATURES: "feat_Tier1,feat_require_unix"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It FEATURES something officially supported by cargo? If not, I'd avoid environment variables to avoid sideffects.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It FEATURES something officially supported by cargo?

No it is not. However, using a build matrix makes the job name more complex, for example:

Style and Lint (feat_Tier1,feat_require_unix)

instead of

Style and Lint

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep this thread and wait maintainer's review.

@xtqqczze
xtqqczze force-pushed the build/openbsd-utmpx branch 2 times, most recently from 5241c2a to 17a0ba3 Compare October 26, 2026 02:06
@codspeed

codspeed Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Merging this PR will not alter performance

1 warning, 1 note

⚠️ 123 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

ℹ️ 1 benchmark has no flamegraph

The flamegraph wasn't generated: most of the time was spent in runtime internals, which would leave nothing useful to analyze.

See affected benchmarks

✅ 401 untouched benchmarks
⏩ 70 skipped benchmarks1


Comparing xtqqczze:build/openbsd-utmpx (e19098c) with main (1d6ca65)2

Open in CodSpeed

Footnotes

  1. 70 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

  2. No successful run was found on main (0776385) during the generation of this report, so 1d6ca65 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@xtqqczze
xtqqczze force-pushed the build/openbsd-utmpx branch from 17a0ba3 to b602afe Compare October 26, 2026 03:31
@xtqqczze xtqqczze changed the title openbsd: remove unsupported fallback ci(openbsd): exclude feat_require_unix_utmpx Oct 26, 2026
utmpx not supported for opensbd
@xtqqczze
xtqqczze force-pushed the build/openbsd-utmpx branch from b602afe to e19098c Compare October 26, 2026 03:34
@xtqqczze
xtqqczze marked this pull request as ready for review October 26, 2026 13:57
@xtqqczze
xtqqczze requested a review from sylvestre October 26, 2026 13:57

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants