| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.0 to 4.1.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/8ade135a41bc03ea155e62e844d188df1ea18608...b4ffde65f46336ab88eb53be808477a3936bae11)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
|
|
|
| |
It seems saner to use RbConfig.ruby than using ruby in a random ancestor
directory.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some people encounter an issue that test_yjit uses the installed Ruby
instead of the currently-running Ruby. It's fixed when they remove the
installed Ruby.
However, test_yjit should run the currently-running Ruby for testing
YJIT in subprocesses. EnvUtil is unfortunately used outside tests as
well, so for compatibility reasons, this commit only changes the
argument given to EnvUtil.invoke_ruby to always use RbConfig.ruby.
Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>
|
|
|
|
|
|
| |
> note: `#[deny(clippy::redundant_locals)]` on by default
On Rust 1.73.0.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
You can't encoding a string with more than one encoding so ensure that
the last one wins.
https://github.com/ruby/prism/commit/4182c988c9
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously, the version-controlled `cruby_bindings.inc.rs` file
contained the build-time artifact `id.h`, which nobu mentioned hinders
the goal of having fewer magic numbers in the repository.
Lookup the IDs YJIT needs on boot. It costs cycles, but it's fine since
YJIT only uses a handful of IDs at the moment. No perceptible
degradation to boot time found in my testing.
|
|
|
|
|
|
|
|
|
|
| |
* YJIT: Add a cargo job for Arm64
* YJIT: Use command names as job names
They look more consistent with jobs that use the command name as a job
name, such as `make (check)`, `make (test-bundled-gems)`, etc.
* Remove .cirrus.yml
|
|
|
|
| |
So that the tests can run without updating other than the programs.
|
| |
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/b59ca2f981
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If `RUBY_MN_THREADS=1` is given, this patch shows `+MN` in
`RUBY_DESCRIPTION` like:
```
$ RUBY_MN_THREADS=1 ./miniruby --yjit -v
ruby 3.3.0dev (2023-10-17T04:10:14Z master 908f8fffa2) +YJIT +MN [x86_64-linux]
```
Before this patch, a warning is displayed if `$VERBOSE` is given.
However it can make troubles with tests (with `$VERBOSE`), do not
show any warning with a MN threads configuration.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For some reason, Windows builds are failing quite consistently now.
However, it seems that errors are happening before this directory is
even created, so removal fails, hiding the original error.
Instead, don't let this removal fail due to files not existing.
https://github.com/rubygems/rubygems/commit/7669d6c96e
|
| |
|
|
|
|
| |
https://github.com/ruby/prism/commit/0ea19ed823
|
|
|
|
|
|
| |
`-d` option is basically same with `-h` (`--header`).
The difference is `-h` accept header file name.
Therefore remove `-d` option.
|
|
|
|
| |
https://github.com/ruby/prism/commit/5d189ce33e
|
|
|
|
| |
https://github.com/ruby/prism/commit/bf9bdb9d82
|
|
|
|
| |
https://github.com/ruby/prism/commit/c7ef25a79a
|
|
|
|
| |
https://github.com/ruby/prism/commit/2b3d59f424
|
|
|
|
| |
This reverts commit 67a987f82bc8a2b7ec15581306873530821fcf9e.
|
|
|
|
|
|
|
| |
Amend ScopeNode to point to previous ScopeNode, and to have void*
pointers to constants and index_lookup_table
https://github.com/ruby/prism/commit/0534324312
|
|
|
|
|
|
|
|
|
|
| |
This comment previously specified TLS 1.2, but actually set the
version to TLS 1.0. LibreSSL 3.8.1 (included in OpenBSD 7.4)
dropped support for TLS 1.0/1.1 for security reasons, which
broke this test. Switch the test to use TLS 1.2 as documented
so it will continue to work on OpenBSD 7.4+.
https://github.com/ruby/net-http/commit/97be4de53a
|
| |
|
|
|
|
|
|
|
|
|
| |
Using the same `runs-os` across all jobs in the same workflow makes it
more likely to pass in case one of these runners is experiencing an
outage.
macos-arm-oss is generally not available outside ruby/ruby, so it's
fair to skip it for forks.
|
| |
|
|
|
|
| |
* Fixed ConstantPathWriteNode
* FIxed FlipFlopNode
|
|
|
|
|
| |
prevent underflow on popped splatarray
This only emits the splat array node when not popped
|
|
|
|
|
|
|
| |
This message is displayed if STDIN is not a tty. The parallel test is
the case.
https://github.com/ruby/irb/commit/e26e90e3fb
|
| |
|
|
|
|
| |
https://github.com/ruby/psych/commit/51cc86ff3f
|
|
|
|
|
| |
macos-arm-oss is unavailable for forked reopsitories other than
ruby/ruby.
|
|
|
|
| |
To avoid creating literals for all combinations.
|
|
|
|
|
|
| |
Only remove const prefix from non-pointer types.
https://github.com/ruby/prism/commit/97c9ffeb42
|
| |
|
| |
|
|
|
|
|
| |
Because of a trap of cmd.exe that `echo something > output` prints not
only "something" also the space before `>`, remove unexpected spaces.
|
|
|
|
|
|
| |
resolve under all locked platforms
https://github.com/rubygems/rubygems/commit/25304f3e8d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/40989271dd
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/20460bc1ee
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5f28a68d79
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `lock` command is specifically designed to manage the lockfile, so
running it should take precedence over any "frozen" setting.
Besides that, "frozen" is not specifically designed as "lockfile cannot
be updated" but as "installation of gems should be prevented if gemfile
is not in sync with the lockfile".
The lock command does not install any gems and preserves the property of
the lockfile being in sycn with its gemfile, so I think frozen should
not influence it.
The current behavior is quite confusing when frozen is set. On an app
where rubocop can get lockfile updates
```
$ bundle lock --update rubocop
Writing lockfile to /path/to/Gemfile.lock
```
Completely silent, it makes you think that it has written the lockfile,
but still no updates.
In verbose mode, it gives a bit more information, but still confusing
and unexpected, and does not change the lockfile:
```
$ bundle lock --update rubocop --verbose
Running `bundle lock --update "rubocop" --verbose` with bundler 2.4.20
Frozen, using resolution from the lockfile
Writing lockfile to /path/to/Gemfile.lock
```
With this commit, it updates the lockfile as expected.
https://github.com/rubygems/rubygems/commit/1d501ae8ea
|