summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
6 hoursCI: Extract `launchable_setup` functionNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13623
6 hoursCI: Extract `launchable_record_session` functionNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13623
6 hoursCI: Store session info in variables directlyNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13623
31 hoursNow irb is a bundled gem and needs rubygemsNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13651
3 dayslewagon/wait-on-check-action didn't need bot tokenHiroshi SHIBATA
3 daysRun auto-style only when pull-requestNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13634
4 daysCI: Fix spec_optsNobuyoshi Nakada
4 daysLaunchable: Terminate Launchable CLI process quickly by sending singa… ↵Naoto Ono
(#13622) Launchable: Terminate Launchable CLI process quickly by sending singals to a process group Sometimes, the timeout errors occurred in Compilations workflow, this is because Launchable CLI process was not terminated correctly. To address this issue, we'll send signals to a process group. https://github.com/ruby/ruby/actions/runs/15614867686 https://github.com/ruby/ruby/actions/runs/15662906947 Co-authored-by: Kazuhiro NISHIYAMA <[email protected]> Notes: Merged-By: ono-max <[email protected]>
4 daysFix a missing double quoteNobuyoshi Nakada
6 daysWork around CI failures coming from LaunchableTakashi Kokubun
https://github.com/ruby/ruby/actions/runs/15640729145/job/44067161266
6 daysZJIT: Partially enable btest on CI (#13613)Takashi Kokubun
Notes: Merged-By: k0kubun <[email protected]>
6 daysCI: Fix launchable timeoutNobuyoshi Nakada
`setup_launchable` needs to run the current shell, not in a subshell. Notes: Merged: https://github.com/ruby/ruby/pull/13608
8 daysUse artifacts built by vcpkg manifest modeHiroshi SHIBATA
I'm not sure why vcpkg cache is not using while recent weeks. Notes: Merged: https://github.com/ruby/ruby/pull/13582
10 daysUpdate a step name [ci skip]Nobuyoshi Nakada
14 daysCI: Continue without record if Launchable setup failedNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13538
14 daysCI: Split cleanups of Launchable generated filesNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13538
14 daysCI: Fix duplicate timeoutsNobuyoshi Nakada
14 daysCI: Fix redirection errorsNobuyoshi Nakada
14 daysCI: Trap launchable_record_test in the parent processNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13535
14 daysCI: Timeout launchable setup in 3minNobuyoshi Nakada
14 daysCI: Create report files only when Launchable setup succeededNobuyoshi Nakada
2025-06-05Win: Slim down `vcvars_ver` options in the matrixNobuyoshi Nakada
2025-06-04Launchable: Set env variables to prevent CI slowdowns (#13513)Naoto Ono
When Launchable in unstable, the round trip time takes a long time, which slows down CI execution. In this PR I configured the environment variable `LAUNCHABLE_COMMIT_TIMEOUT` to configure the timeout. https://github.com/launchableinc/cli/pull/1015 Notes: Merged-By: ono-max <[email protected]>
2025-06-01Win: Use `VsDevCmd.bat` instead of old `vcvarsall.bat`Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13490
2025-05-30Win: Add scripts to install and setupNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13473
2025-05-28Use the latest version of Windows SDKHiroshi SHIBATA
https://github.com/ruby/ruby/commit/72bda0f981c7136f50254c433bbfb97a953f634b Notes: Merged: https://github.com/ruby/ruby/pull/13453
2025-05-21Reenable MMTk testsPeter Zhu
Notes: Merged: https://github.com/ruby/ruby/pull/13386
2025-05-21Disabled TRAP cache of CodeQL againHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13391
2025-05-21ZJIT: Run `make zjit-test` under combo build with YJITAlan Wu
Notes: Merged: https://github.com/ruby/ruby/pull/13377
2025-05-21YJIT: ZJIT: CI: Smoke test for --[y,z]jit-dump-disasmAlan Wu
Notes: Merged: https://github.com/ruby/ruby/pull/13376
2025-05-20CI: Check if runnable first, before set up directoriesNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13379
2025-05-15CI: Fix revision.h on WindowsNobuyoshi Nakada
- Quote % inside `if` block - Use short branch name
2025-05-15CI: Refine setup on WindowsNobuyoshi Nakada
Get rid of hardcoded paths
2025-05-15Add `continue-on-error` to failed Windows 2025 build.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/13345
2025-05-14Revert "Set WASMTIME_BACKTRACE_DETAILS=1 for WASM basictest"Takashi Kokubun
This reverts commit cb88edf0bfdc2ce6bfbe3b4e0463a4c2dc5d2230. It didn't help. You need to go to a different repository (ruby/ruby.wasm) to see meaningful backtraces. https://github.com/ruby/ruby.wasm/actions/runs/15000135135/job/42144675968#step:16:176
2025-05-15ZJIT: Add CI runs for building with YJITAlan Wu
Notes: Merged: https://github.com/ruby/ruby/pull/13262
2025-05-15YJIT: ZJIT: Allow both JITs in the same buildAlan Wu
This commit allows building YJIT and ZJIT simultaneously, a "combo build". Previously, `./configure --enable-yjit --enable-zjit` failed. At runtime, though, only one of the two can be enabled at a time. Add a root Cargo workspace that contains both the yjit and zjit crate. The common Rust build integration mechanisms are factored out into defs/jit.mk. Combo YJIT+ZJIT dev builds are supported; if either JIT uses `--enable-*=dev`, both of them are built in dev mode. The combo build requires Cargo, but building one JIT at a time with only rustc in release build remains supported. Notes: Merged: https://github.com/ruby/ruby/pull/13262
2025-05-14Use gh cacheHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13330
2025-05-14Purge the oldest TRAP cache with gh actions-cache cliHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13330
2025-05-14Disabled TRAP cache of CodeQLHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13330
2025-05-13Set WASMTIME_BACKTRACE_DETAILS=1 for WASM basictestTakashi Kokubun
https://github.com/ruby/ruby/actions/runs/15008767265/job/42173424631 "error while executing at wasm backtrace" doesn't have meaningful symbols. We can't debug this from just looking at the "[BUG] Cannot malloc during GC" message. As suggested by the error message, this commit sets WASMTIME_BACKTRACE_DETAILS=1. Let me see if this improves the backtrace.
2025-05-13Bump the required BASERUBY version to 3.1 (#13321)Takashi Kokubun
Notes: Merged-By: k0kubun <[email protected]>
2025-05-13Checkout .github on omnibus result for notificationsTakashi Kokubun
It currently fails like: Can't find 'action.yml'
2025-05-12CI: Create proper revision.h on WindowsNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/13304
2025-05-11Skip mmtk/i686 tests for a whileSatoshi Tagomori
2025-05-10ruby/spec has a minimum of Ruby 3.2 nowBenoit Daloze
2025-05-07Enabled debug mode for CodeQLHiroshi SHIBATA
2025-05-01Removed unused OS_VER variableHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13220
2025-05-01windows-2019 will be EOL at end of June, 2025Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13220
2025-04-30Added GCC 15 buildHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/13210
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-19 18:37:16 +0000