Skip to content

fix: smoke test compile error, run smoke after release #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dfa1 merged 1 commit into from
Aug 4, 2026
Merged

fix: smoke test compile error, run smoke after release #109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/smoke/src/test/java/SmokeTest.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,7 +235,7 @@ void decompressContextAdvanced() {

dctx.reset(ZstdResetDirective.PARAMETERS);
dctx.parameter(ZstdDecompressParameter.WINDOW_LOG_MAX, 24);
byte[] restoredAfterReset = dctx.decompress(cctx.compress(original), original.length);
byte[] restoredAfterReset = dctx.decompress(cctx.compress(original), new ZstdByteSize(original.length));
checkArrayEquals(original, restoredAfterReset, "decompress after PARAMETERS reset + parameter() mismatch");
}
}
Expand Down
14 changes: 13 additions & 1 deletion .github/workflows/release-smoke.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@ name: Release smoke test
# Verifies a PUBLISHED release on Maven Central actually loads and runs on every
# supported OS/arch — one runner per native classifier. Pulls the release jars
# from Central (no source build, no submodule, no zig), so it tests exactly what
# users consume. Trigger manually and pass the version to check.
# users consume. Runs automatically after every publish (see #107), weekly as a
# standing check, and can also be triggered manually with an explicit version.

on:
workflow_dispatch:
Expand All @@ -12,6 +13,9 @@ on:
description: Version to smoke-test. Leave blank to use the latest release on Maven Central.
required: false
default: ""
workflow_run:
workflows: ["Publish to Maven Central"]
types: [completed]
schedule:
# Weekly, Mondays 06:00 UTC. No input on scheduled runs, so the resolve job
# picks the latest release on Maven Central — catches Central / runner-image
Expand All @@ -21,11 +25,19 @@ on:
jobs:
resolve:
name: resolve version
if: ${{ github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success' }}
runs-on: ubuntu-latest
permissions: {}
outputs:
version: ${{ steps.pick.outputs.version }}
steps:
# Central sync isn't instantaneous after the publish job finishes, so a
# run triggered right after a publish gives it a few minutes before
# asking maven-metadata.xml for the "latest" release below.
- name: Wait for Maven Central sync
if: ${{ github.event_name == 'workflow_run' }}
run: sleep 300

- name: Resolve version (input, else latest on Maven Central)
id: pick
shell: bash
Expand Down
Loading