Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ruby: Update to 3.3.7 #5135

Merged
merged 1 commit into from
Jan 16, 2025
Merged

ruby: Update to 3.3.7 #5135

merged 1 commit into from
Jan 16, 2025

Conversation

yasuhirokimura
Copy link
Contributor

Update ruby to 3.3.7.

@yasuhirokimura
Copy link
Contributor Author

BTW, at first I tried to update to 3.4.1 but it failed because of build phase error.
So could somebody please take a look at it?

@lazka lazka merged commit 6cd6d03 into msys2:master Jan 16, 2025
2 checks passed
@jeremyd2019
Copy link
Member

jeremyd2019 commented Jan 16, 2025

BTW, at first I tried to update to 3.4.1 but it failed because of build phase error. So could somebody please take a look at it?

That's odd - I got a bunch of fhandler_dev_zero::fixup_mmap_after_fork errors from miniruby, but when I re-ran the build with the existing source directory, everything finished successfully. I ran make test, and all tests passed. Very strange.

     0 [main] miniruby 9272 fhandler_dev_zero::fixup_mmap_after_fork: requested 0x6FFFE6A60000 != 0x0 mem alloc base 0x0, state 0x10000, size 17545331867648, Win32 error 1455
   2717 [main] miniruby 9272 D:\S\ruby\src\build-x86_64-pc-msys\miniruby.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed
      0 [main] miniruby 9241 dofork: child -1 - forked process 24744 died unexpectedly, retry 0, exit code 0x100, errno 11

I didn't see this on upstream Cygwin 3.5.4

@jeremyd2019
Copy link
Member

#5144

@yasuhirokimura yasuhirokimura deleted the ruby branch January 17, 2025 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants