Update github-actions - #330
Merged
Merged
Conversation
|
|
||
| - name: "Install bashunit" | ||
| uses: "TypedDevs/bashunit@28ea63c467f1f461a6368c93e5c264051b141c6f" # 0.50.1 | ||
| uses: "TypedDevs/bashunit@860c797a48e34be20b019a70f58c0e06d15c8d33" # 0.51.0 |
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.
This PR contains the following updates:
0.50.1→0.51.0v4.38.0→v4.38.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
TypedDevs/bashunit (TypedDevs/bashunit)
v0.51.0Compare Source
Changed
--parallelrun on a shell withoutEPOCHREALTIMEno longer forksperlonce per test. The clock probe resolved inside a command substitution, so the resolved value died with it and every worker re-probed: 502perlexecs for a 500-test file, now 2. It happened even with per-test timing off, since deciding that timing is off is what asks whether the clock is expensive. Fixed by #1358; this adds the guards that keep it fixed (#1353)adrs/adr-013-bash-version-gated-fast-paths.md(#1352)set_up_before_scriptortear_down_after_scriptcosts about 5.6ms less on Bash 3.2, and a test rendered with--show-execution-timeabout 0.74ms less. Four clock reads per file and the per-test padding no longer go through a capture subshell (#1348)eval, a nestedsourceor a conditional definition keep the old path, so the count can never disagree with the run (#1347)<file>:<line>is resolved on demand instead of forking a subshell per test to read it (#1346)bashunit assert <fn> ...no longer reports a source location belonging to another process. Launched from inside a test, it inherited that test's exported location and printed it as its own (#1346)set_uportear_downis about 2.6x faster, 14.1ms to 5.4ms per test on macOS arm64, bash 3.2, which brings it level with a hookless test. Each hook minted its output file withmktempand removed it withrm, and the ownership marker that left behind made the runner sweep the test's temp files at exit: five forks per test, even for a test that created no temp file (#1345)Fixed
--assertoption names the invocation you typed:bashunit -a,bashunit --assertorbashunit test --assert. It always saidbashunit test --assert, becausebashunit -areaches that path through the inferredtestsubcommand, so it read like a warning about a command you never ran (#1366)assert_contains_ignore_casedocuments what it actually guarantees: ASCII case folding. WhetherñmatchesÑdepends on the shell version, the locale and whichtrthe system ships. Behaviour is unchanged (#1351)test_aalongsidetest_abread as one name twice, which made the whole file select nothing (#1347)--exclude-filterkeeps a comma as part of the test function name. The value was split at the comma, so--exclude-filter 'test_a,{b}'also excludedtest_a. Repeat the flag to exclude several names.BASHUNIT_EXCLUDE_FILTERstays comma-separated (#1340)--parallelrun no longer replays bash'schild setpgidwarning as the stderr of a file that wrote nothing. The child sets its process group first, so only the message was ever wrong (#1344)tear_down. The watchdog allowed a flat 0.3s between SIGTERM and SIGKILL, which a loaded machine missed in about one parallel full-suite run in three. It now polls for the body to exit, capped at 2s (#1344)github/codeql-action (github/codeql-action)
v4.38.1Compare Source
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.