[pull] master from ruby:master#1168
Merged
Merged
Conversation
Make `VRegId` u32 instead of usize and make `StackIdx` u32 instead of usize.
Shrink `lir::Insn` from 80 to 72 bytes.
Shrink `lir::Insn` from 72 to 64 bytes.
Shrink `lir::Insn` from 64 to 56 bytes.
Co-authored-by: Jeremy Evans <code@jeremyevans.net> Co-authored-by: tompng <tomoyapenguin@gmail.com>
Set BUNDLER_SPEC_RUNTIME_LOG to a path and each parallel worker appends a "<seconds>\t<file>" line per example to "<path>.<TEST_ENV_NUMBER>", so the heaviest specs can be found after a full run. turbo_tests only writes its own --runtime-log for the bare "spec" path, which the build never passes, so otherwise no timing data survives. Per-worker files avoid Windows cross-process append contention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The shared `before` runs for all 283 examples and spawned three `git config --global` subprocesses each; write the global .gitconfig directly instead. The nested `git config --global --unset` and `init.defaultBranch` calls still operate on the same file. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The conservative-update setup and the remove-platform example (whose lockfile is immediately overwritten) only check the generated lockfile, never installed gems, so `lock_gemfile` produces the same result without extracting gems. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Two back-to-back `update_repo2` calls each re-index the whole repo; building both gems in one block produces the same index in one pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Hoist the duplicated `revision_for` git calls into a local in the two --ref examples, and resolve-only (`lock_gemfile`) the duplicate-gem-error setups that assert only on err, never on installed gems. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Three examples assert only on the generated lockfile (locked_platforms / locked_gems / lockfile), never on installed gems, so `lock_gemfile` resolves and writes the same lockfile without materializing foreign precompiled gems. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The removed-flag deprecations for check/binstubs/cache/install raise before the Gemfile is resolved, so the setup only needs the Gemfile written, not gems installed. Use `gemfile` (and `lock_gemfile` for the path-source resolution error) instead of `install_gemfile`, and drop the redundant first install in the install-flags block. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Drop a duplicated `include_gems` assertion (the same check ran twice in one example), and lock instead of install in the path-source example that only asserts on the lockfile. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The "lockfile format" examples assert only on the generated Gemfile.lock, never on installed gems or install output, so resolve-and-write with `lock_gemfile` instead of installing. `bundle lock` writes the same lockfile (CHECKSUMS included) without extracting gems. Examples that assert on out/err, installed gems, packaging, credentials, frozen-mode errors, or install-time lockfile auto-healing keep `install_gemfile`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
`include_gems` spawns one subprocess per gem name; "activesupport 2.3.2" was listed twice in the same call, spawning a redundant check. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Re-aggregate using per-example runtimes from a full parallel run. The shards had drifted to a +7% imbalance (shard_d 6290s vs shard_a 5153s); moving three files (lockfile_spec, inline_spec, install/path_spec) levels all four shards to ~5900s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )