jit ci crash report #737
Closed
jit ci crash report #737
Conversation
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
* Release builds depend only on `rustc` for sake of packaging. Removing it from the image ensures that passing the CI implies that only `rustc` is required.
* ruby.rs should hold the main entrypoint to YJIT and ZJIT * The crate jit will hold code shared between them
* Using the shared jit crate, support for a single global_allocator can function * Solves --zjit-mem-size
If the file option is given but the file not found, raise a GemfileError with a message indicating the file was not found. Currently this is raising a generic Errno::ENOENT error. ruby/rubygems@db61de6b21
It sounds like this should apply to all git sources at this point. ruby/rubygems@b1817f91de
It matches the comment above more naturally and it's consistent with how the same thing is checked in other places. ruby/rubygems@59ec6b4b29
…ource changes When the source used to be git and switches back to rubygems, it is possible that the git source contains a version that ruybgems doesn't know about yet. So don't add the locked spec to the base resolve, and also don't add a lower bound requirement on the version, since the version in the new source may actually be lower. ruby/rubygems@85514e3a1e
Fix: ruby/json#853 Simplecov end up requiring json so we need to start collecting coverage before. ruby/json@ca72019fd3
[Bug #21561] It's preferable if the method is consistent in the encoding in the returned string.
…lock_given_aset_aref
Strings created from the C API with a len but no ptr have a buffer allocated and the length set, but the buffer is not zero'd. This causes use of uninitialized memory and allows reading memory that previously existed there. For example, the rb_str_tmp_new spec fails when we create a string with a large length greater than 24 bytes (since we zero the first 24 bytes of the slot).
Add tests covering edge cases in the current behavior to prevent accidental regressions. The next patches will update the OpenSSL 3.x path. ruby/openssl@468f8ceea2
…t is needed Specify OSSL_DECODER_CTX_set_pem_password_cb() only when we expect a passphrase-protected private key. OSSL_DECODER appears to try to decrypt every PEM block in the input even when the PEM header does not match the requested selection. This can cause repeated prompts for a passphrase in a single OpenSSL::PKey.read call. ruby/openssl@933503f49f
…L_DECODER Continue processing only when OSSL_DECODER_from_bio() returns the error code ERR_R_UNSUPPORTED. Otherwise, raise an exception without retrying decoding the input in another format. This fixes another case where OpenSSL::PKey.read prompts for a passphrase multiple times when the input contains multiple passphrase-protected PEM blocks and the first one cannot be decoded. I am not entirely sure if the error code ERR_R_UNSUPPORTED is considered part of the public interface of OpenSSL, but this seems to be the only option available and is the approach used internally by the PEM_read_bio_*() functions. Fixes ruby/openssl#927 ruby/openssl@985ba27d63
… releases Treat an empty error queue after calling OSSL_DECODER_from_bio() as a retryable error. This is a follow-up to the previous commit ruby/openssl@985ba27d6339 (pkey: stop retrying after non-retryable error from OSSL_DECODER). The commit broke loading public keys on Ubuntu 22.04 LTS, which ships OpenSSL 3.0.2. ruby/openssl@5347880c6e
Since cb419e3 we're no longer testing this case because foo is redefined on obj1.
This reverts commit 5a2cedd. The CI is telling us to revert the diff: https://github.com/ruby/ruby/actions/runs/17679836157/job/50251138515
Make it clear that it parses with the most recent version of Ruby syntax. ruby/prism@7285d1fbab
This commit fills the space that is not initialized with garbage for newly allocated objects on debug mode.
The backslashs in these tests are parsed as escapes in string literals by the parser, but not passed to the `Regexp` methods.
Make this macro condition as compile-time constant instead of a preprocess-time constant, and compile the body always.
Now it is always compiled (and will be optimized away).
Get rid of `File.identical?` on a WebDAV-mounted drive.
It is needed before updating the timestamp for prism/srcs.mk.
These tests are run in the dedicated workflows for JITs.
An unspecified uplevel is not the same as an uplevel of 1:
```
$ irb
irb(main):001> warn("foo")
foo
=> nil
irb(main):002> warn("foo", uplevel: 1)
/home/user/.rbenv/versions/2.7.8/lib/ruby/gems/2.7.0/gems/irb-1.14.0/lib/irb/workspace.rb:121: warning: foo
=> nil
```
ruby/prism@dcedd14357
The performances are: block > proc > method object. ruby/optparse@9ec5d1d582
If a character literal was followed by a string concatenation, then the forced encoding of the string concatenation could accidentally overwrite the explicit encoding of the character literal. We now handle this properly. ruby/prism@125c375d74
Symbol#name is only a thing since Ruby 3.0 ruby/prism@2de82b15fc
imemo_tmpbuf is not write-barrier protected and uses mark maybe to mark the buffer it holds. The normal rb_imemo_new creates a write-barrier protected object which can make the tmpbuf miss marking references.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
17 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.
No description provided.