| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
To prevent CI failure like
https://ci.appveyor.com/project/ruby/ruby/builds/36494552/job/a3ow8atl19786tep
|
|
|
|
|
| |
Also install external libraries only, extract-gems does not work
unless base ruby is available.
|
| |
|
| |
|
|
|
|
| |
All Slack alerts have been migrated to a bot made by mame-san
|
| |
|
|
|
|
| |
trunk branch was deleted.
|
|
|
|
|
| |
Similar to 4fb6643f31cdee33184043ce17c42001274c4392.
This is motivated by the lack of the same feature in GitHub Actions.
|
|
|
|
| |
in favor of #2791
|
|
|
|
| |
Not compatible with concurrent-ruby dependency
|
|
|
|
|
| |
MSYS source code comes from both gcc.gnu.org & Mingw-w64. Updates to the Mingw-w64 source broke the MinGW build step.
Fixes the issue until Mingw-w64 updates their source, then it should be reverted, see comments in code.
|
|
|
|
|
|
| |
As AppVeyor's MSYS2 install gets out of date, this may require 'special' code...
This code also adds updating the database, which currently updates gcc from 9.1.0 to 9.2.0.
|
|
|
|
| |
The format is a little weird, and not so helpful either.
|
| |
|
|
|
|
|
| |
Some CIs report to two channels, and some others report to only one.
This makes it consistent. Only alert channel should be alerted.
|
|
|
|
|
| |
It was using the same one as original AppVeyor's notification, but it's
just inconsistent with others like Travis and GitHub Actions.
|
|
|
|
|
|
| |
for consistency. In the pull request, `before_test` was dropped only for
msys2 to fix msys2-only failure. But there's no need to keep it
inconsistent now.
|
|
|
|
|
|
| |
* appveyor.yml - OpenSSL vc120 -> 1.0.2, vc140 -> 1.1.1
* Try just using build_script
|
|
|
|
|
| |
debugging failure of
https://ci.appveyor.com/project/ruby/ruby/builds/26613960/job/nemi6pvc5s5843io
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit b1594ca3d6b72edb60927418482652ce93209499.
Revert "Debug appveyor mingw failure"
This reverts commit fa29f65416f1fb3d734a279855728bb0616dbb34.
Though I preserved V=1 for future debugging.
|
|
|
|
|
|
|
|
|
| |
to fix a build error like:
https://ci.appveyor.com/project/ruby/ruby/builds/26547644/job/4j7n41e7in97a9kx
Basically copy-pasted what's currently done in MSP-Greg/ruby-loco.
Co-Authored-By: MSP-Greg <greg.mpls@gmail.com>
|
| |
|
|
|
|
|
|
|
| |
It has been unstable for recent builds:
https://ci.appveyor.com/project/ruby/ruby/builds/26531442/job/0ycp7woekqqx97x9
https://ci.appveyor.com/project/ruby/ruby/builds/26531687/job/xui3rctcvi7r49iv
https://ci.appveyor.com/project/ruby/ruby/builds/26532019/job/1q0n46ci4g8dplwx
|
|
|
|
| |
I think it's been stable these days.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* test/lib/test/unit.rb (Test::Unit::TimeoutOption): renamed
SubprocessOption.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#setup_options):
prefer `--timeout-scale` option.
* test/lib/test/unit.rb (Test::Unit::TimeoutOption#non_options):
prefer `ENV["RUBY_TEST_TIMEOUT_SCALE"]`.
|
|
|
|
|
| |
This issuse is caused by MSYS2 changing from using ncurses to pdcurses.
Appveyor's MSYS2 is so out-of-date that partial updates are 'troublesome'...
|
|
|
|
|
|
|
| |
Closes: https://github.com/ruby/ruby/pull/2208
Merging the PR for fixing AppVeyor msys2 failure related to GCC 9 like:
https://ci.appveyor.com/project/ruby/ruby/builds/24877992/job/ned5k4k5rwxnld5j
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
but on "master" branch.
For Pull Request, I changed the approach from
d9b338a53f520b2dbb05555f18b8de8072300f40 and
277e68825a8e4d0e6503a32e41f8b1b6c078b567.
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 1ebe9a2f82fef5190454e68d430004282f5da172.
because it did not help.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CI seems to have a weired behavior now. Debugging.
Revert "azure-pipelines.yml: Fix typo"
This reverts commit f69d28fbca1eec8b9722cea1f989ee9554e8dad5.
Revert "azure-pipelines.yml: Use simpler trigger syntax"
This reverts commit 709756d89747bd36664593eda4156a7bf5ad7631.
Revert "azure-pipelines.yml: Do not run CI on trunk"
This reverts commit bec877b46fd4d0f621a75591b519a7e266eaa89b.
Revert "appveyor.yml: Do not doubly run CI on trunk"
This reverts commit d9b338a53f520b2dbb05555f18b8de8072300f40.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* lib/reine.rb, lib/reline/*: Reline is a readline stdlib compatible
library.
* lib/readline.rb: Readline uses a fallback to Reline when ext/readline
doesn't exist.
* tool/sync_default_gems.rb: add ruby/reline as a default gem.
* appveyor.yml: add "set RELINE_TEST_ENCODING=Windows-31J" for test suit
of Reline, and add "--exclude readline" to "nmake test-all" on Visual
Studio builds because of strange behavior.
* spec/ruby/library/readline/spec_helper.rb: skip Reline as with
RbReadline.
|
|
|
|
|
| |
because it makes the CI unstable
https://ci.appveyor.com/project/ruby/ruby/builds/24143365/job/yrx7b8ce2qg9wro2
|
|
|
|
|
| |
as it's unstable on the environment
https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey
|
|
|
|
|
|
|
| |
Trying to fix
https://ci.appveyor.com/project/ruby/ruby/builds/23639998/job/0hm9v79xlryod1ff
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67455 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67449 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
|
|
|
|
|
|
| |
and simplified config by using dedicated webhook URL.
Sadly AppVeyor YAML does not support alias and so we need to copy-paste
the request body.
memo:
https://slack-files2.s3-us-west-2.amazonaws.com/bot_icons/2018-02-10/314363543719_48.png
is the URL used by `provider: Slack`
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67272 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
|
| |
Because retrying 5 times failed.
https://ci.appveyor.com/project/ruby/ruby/builds/23063048/job/k9lykaagfaex74gg
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67269 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
| |
https://ci.appveyor.com/project/ruby/ruby/builds/22196846/job/53xvhv265f8eogl4
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67027 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
because it had already been SEGV-ed in pull request'S CI
https://ci.appveyor.com/project/ruby/ruby/builds/20427065/job/32oahrcd58b8ubb1
and has never worked on trunk either.
Please make sure it does not SEGVs on your MinGW environment or pull
request before enabling native fiber on MinGW.
appveyor.yml: reverted commits to make CI green with native fiber
test/excludes/_appveyor/msys2/TestArray.rb: ditto
test/excludes/_appveyor/msys2/TestEnumerable.rb: ditto
test/excludes/_appveyor/vs/TestArray.rb: ditto
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65892 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|