Repository navigation
Release v0.31.1: ffmpeg on the runners for the packed-tarball smoke - #159
Merged
Merged
Conversation
…e packed-tarball smoke
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's in it
Fixed
packed tarball installs and runsjob and the release workflow install ffmpeg beforesmoke:package. The smoke compiles a project from a generated 89.28 s WAV and checks the material durationcompilereads through ffprobe; the hosted Ubuntu runner has no ffprobe, socompilefell back to the clip's own range (26 s) and the v0.31.0 release stopped beforenpm publish.0.31.1 carries everything listed under 0.31.0 in the changelog, which never reached npm.
Checks
actual: 26000000, expected: 89280000, the same assertion the v0.31.0 release run stopped on.npm test,npm run lint, the packed-tarball smoke, the Wasm verify and the Python client tests run on this branch.