4068be1d9f
appveyor.yml - msys2 update 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.
2019-09-07 10:48:40 +09:00
fa5f7771f2
Drop duration from AppVeyor notification
...
The format is a little weird, and not so helpful either.
2019-08-25 20:10:25 +09:00
1d6a31f3d5
Make AppVeyor notification similar to Travis
2019-08-23 09:45:49 +09:00
235d810c2e
Deprecate alerting multiple channels
...
Some CIs report to two channels, and some others report to only one.
This makes it consistent. Only alert channel should be alerted.
2019-08-20 22:33:32 +09:00
4c13368972
Make AppVeyor notification colors consistent
...
It was using the same one as original AppVeyor's notification, but it's
just inconsistent with others like Travis and GitHub Actions.
2019-08-19 09:47:05 +09:00
ad0ea708ca
Drop before_test for mswin too
...
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.
2019-08-18 15:50:03 +09:00
cba8166cc1
Appveyor - vc120 use OpenSSL 1.0.2, vc140 use 1.1.1 ( #1998 )
...
* appveyor.yml - OpenSSL vc120 -> 1.0.2, vc140 -> 1.1.1
* Try just using build_script
2019-08-18 15:47:19 +09:00
1c7eadf754
Debug which test hangs on mswin
...
debugging failure of
https://ci.appveyor.com/project/ruby/ruby/builds/26613960/job/nemi6pvc5s5843io
2019-08-11 14:15:49 +09:00
a9b9f9d157
Revert "Drop -j from msys2 build for debugging"
...
This reverts commit b1594ca3d6fa29f65416
2019-08-08 22:36:34 +09:00
2a6d7fad13
Arrange installed packages like ruby-loco
...
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>
2019-08-08 22:18:50 +09:00
b1594ca3d6
Drop -j from msys2 build for debugging
2019-08-08 20:37:12 +09:00
fa29f65416
Debug appveyor mingw failure
...
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
2019-08-08 00:10:27 +09:00
4b4d8a662b
Stop isolating test_gc_compact on CI
...
I think it's been stable these days.
2019-07-29 19:45:32 +09:00
3d1536e618
Build AppVeyor only on master
2019-07-01 00:24:14 +09:00
eb016d8353
Generalize timeout_scale
...
* 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"]`.
2019-06-11 23:15:46 +09:00
aeb9a0ca77
appveyor.yml again!
...
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'...
2019-06-01 02:16:34 +09:00
f60a59ed20
appveyor.yml - update for msys2 - pdcurses, force toolchain
...
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
2019-05-29 09:14:01 +09:00
2562b7d7cd
Unify RELINE_TEST_ENCODING setting
2019-05-28 14:38:31 +09:00
d5f408403f
Set read-only with attrib command
2019-05-28 14:38:31 +09:00
cf904d9f9f
Avoid doubly building Travis and AppVeyor
...
but on "master" branch.
For Pull Request, I changed the approach from
d9b338a53f277e68825a
2019-05-28 10:02:31 +09:00
7c507345a7
Build trunk branch too to trigger AppVeyor on PR
2019-05-25 07:26:35 -07:00
1ccc2eeba0
Pretend to update all Unicode files
2019-05-23 14:18:26 +09:00
c210c68d39
Revert "Revert CI deduplication on Wercker / Azure for debugging"
...
This reverts commit 1ebe9a2f82
2019-05-22 11:14:54 -07:00
1ebe9a2f82
Revert CI deduplication on Wercker / Azure for debugging
...
CI seems to have a weired behavior now. Debugging.
Revert "azure-pipelines.yml: Fix typo"
This reverts commit f69d28fbca709756d897bec877b46fd9b338a53f
2019-05-22 10:01:36 -07:00
d9b338a53f
appveyor.yml: Do not doubly run CI on trunk
2019-05-22 08:40:09 -07:00
4d9c3a8c23
Update include files on msys2 too
2019-05-18 09:40:03 +09:00
17350c7e55
Add Reline as a fallback library for Readline
...
* 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.
2019-04-30 11:44:20 +09:00
14f004d396
Isolate test_gc_compact on AppVeyor mswin as well
...
because it makes the CI unstable
https://ci.appveyor.com/project/ruby/ruby/builds/24143365/job/yrx7b8ce2qg9wro2
2019-04-28 02:18:17 +09:00
afb361dfd0
Isolate test_gc_compact on msys2 AppVeyor
...
as it's unstable on the environment
https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey
2019-04-27 20:15:08 +09:00
a26d525ae4
appveyor.yml: try porting r67454 to msys2
...
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
2019-04-06 01:25:15 +00:00
b5df5296a4
appveyor.yml: Use pre-generated headers and tables
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-06 00:08:04 +00:00
9dcc6f0810
appveyor.yml: download beta version for test
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67449 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-05 14:44:13 +00:00
407cd5cc54
Drop invalid trailing comma in JSON object
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-17 04:13:13 +00:00
8ce6748fc8
Notify AppVeyor results to multiple channels
...
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
2019-03-16 04:11:54 +00:00
e4c184c6ae
Increase the number of curl retries
...
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
2019-03-15 13:25:06 +00:00
6c574d4be4
appveyor.yml: retry zlib downloads
...
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
2019-02-07 14:58:37 +00:00
2d0833e101
Try with TZInfo and Timezone gems
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-28 14:08:34 +00:00
c6d0892fa2
configure.ac: disable native-fiber for MinGW
...
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
2018-11-20 14:40:55 +00:00
aee857e427
appveyor.yml: exclude TestEnumerable.rb on msys2
...
because it SEGVs on setup like:
https://ci.appveyor.com/project/ruby/ruby/builds/20431217/job/97no5h1gqv50k1vf
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65889 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-20 13:39:50 +00:00
94438bcbec
appveyor.yml: native-fiber crashes Enumerator
...
test on MinGW.
https://ci.appveyor.com/project/ruby/ruby/builds/20427662/job/tnnw50opqtj6x0xq
https://ci.appveyor.com/project/ruby/ruby/builds/20429129/job/dpgbx5atkxjiwh7q
To investigate issues, let's try running this without -j.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65888 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-20 12:59:32 +00:00
9c336391f2
appveyor.yml: separately execute test_bignum
...
because that may crash worker with -j.
https://ci.appveyor.com/project/ruby/ruby/builds/20403179/job/mkdcb6uy8qn2djgl
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65811 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-19 14:21:55 +00:00
f98e323ef3
appveyor.yml: skip reverting comment improvement [ci skip]
...
This part was not intended in r65760
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65762 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-16 06:47:37 +00:00
c2ed1edebb
appveyor.yml: give up running test_push_over_ary_max
...
because separately running it without -j didn't work.
Revert "appveyor.yml: run memory-exchausting test separately"
This reverts commit r65703.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65760 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-16 06:45:16 +00:00
5f376ce0a7
appveyor.yml: run memory-exchausting test separately
...
r65690 had no impact
https://ci.appveyor.com/project/ruby/ruby/builds/20253561/job/p5u235m8xx85t9o5 .
Gave up to solve the issue inside the test.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65703 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-13 05:46:41 +00:00
de925b4f3c
appveyor.yml: fix wrong path to test directory
...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65418 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-28 09:06:54 +00:00
323ecafe04
appveyor.yml: run test_open-uri separately
...
on msys2 because it sometimes crashes worker like
https://ci.appveyor.com/project/ruby/ruby/builds/19853558/job/8v1ehnv40bggiode
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65417 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-28 07:44:59 +00:00
0c289a7f22
appveyor.yml: run second half of vs with -v
...
because it may silently die like
https://ci.appveyor.com/project/ruby/ruby/builds/19813015/job/a99c4hrs69g4iorg
and we can't know which test was bad.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65375 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-26 08:34:42 +00:00
a740fa1b25
appveyor.yml: give up using mspec -j
...
for all Windows environments. It also hanged on msys2 build
https://ci.appveyor.com/project/ruby/ruby/builds/19719943/job/cxg00jgvt1ifml97
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65331 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 14:43:19 +00:00
3675920c1e
.travis.yml: run the slowest jobs first
...
to shorten time taken for finishing overall builds.
appveyor.yml: comment the same intention in AppVeyor as well
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65328 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 14:10:12 +00:00
353c86eed4
appveyor.yml: separately execute problematic test case
...
that may crash worker like:
https://ci.appveyor.com/project/ruby/ruby/builds/19706703/job/5dmi22mgua9r2qfu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65322 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 12:48:21 +00:00
MSP-Greg
Takashi Kokubun
Nobuyoshi Nakada
aycabta
k0kubun
nobu
