Skip to content

zstd: add test-version.sh to fix CI version check failure#29422

Closed
commodo wants to merge 1 commit into
openwrt:masterfrom
commodo:zstd-fix-version-check
Closed

zstd: add test-version.sh to fix CI version check failure#29422
commodo wants to merge 1 commit into
openwrt:masterfrom
commodo:zstd-fix-version-check

Conversation

@commodo
Copy link
Copy Markdown
Contributor

@commodo commodo commented May 11, 2026

📦 Package Details

Maintainer: me

Description:

zstdgrep and zstdless are shell script wrappers around the zstd binary; they do not output a version string. The generic CI version checker warns on both, which causes a "Some tests failed" exit in the CI runner.

Add test-version.sh to override per-file version checks. The override verifies that /usr/bin/zstd --version contains the expected version and exits 0, which satisfies the CI infrastructure without falsely flagging the shell wrapper scripts.


🧪 Run Testing Details

  • OpenWrt Version:
  • OpenWrt Target/Subtarget:
  • OpenWrt Device:

✅ Formalities

  • I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

zstdgrep and zstdless are shell script wrappers around the zstd binary;
they do not output a version string.  The generic CI version checker
warns on both, which causes a "Some tests failed" exit in the CI runner.

Add test-version.sh to override per-file version checks.  The override
verifies that /usr/bin/zstd --version contains the expected version and
exits 0, which satisfies the CI infrastructure without falsely flagging
the shell wrapper scripts.

Signed-off-by: Alexandru Ardelean <alex@shruggie.ro>
@GeorgeSapkin
Copy link
Copy Markdown
Member

GeorgeSapkin commented May 11, 2026

There is probably some confusion with the final log output. The PKG_NAME is not being cleared so if there are failures with any packages, the last PKG_NAME (e.g. zstd, because it starts with a z) is being reported in the final status. I'm adding a PR with a fix:

@commodo
Copy link
Copy Markdown
Contributor Author

commodo commented May 11, 2026

So, then does this need to be closed?
I am bit confused about this transient state of CI failures.
I'm happy to help, but I'm also a bit ¯\_(ツ)_/¯ about the CI failures which don't seem to be related to my changes.

@GeorgeSapkin
Copy link
Copy Markdown
Member

If you look at the recent runs, the tests for zstd seem to pass:

But the final status is not clearing the package name.

So AFAICT this can be closed.

@commodo commodo closed this May 11, 2026
@commodo commodo deleted the zstd-fix-version-check branch May 11, 2026 17:44
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