summaryrefslogtreecommitdiff
path: root/appveyor.yml
AgeCommit message (Collapse)Author
2019-04-30Add Reline as a fallback library for Readlineaycabta
* 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-28Isolate test_gc_compact on AppVeyor mswin as wellTakashi Kokubun
because it makes the CI unstable https://ci.appveyor.com/project/ruby/ruby/builds/24143365/job/yrx7b8ce2qg9wro2
2019-04-27Isolate test_gc_compact on msys2 AppVeyorTakashi Kokubun
as it's unstable on the environment https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey
2019-04-06appveyor.yml: try porting r67454 to msys2k0kubun
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-06appveyor.yml: Use pre-generated headers and tablesnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-04-05appveyor.yml: download beta version for testnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67449 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-17Drop invalid trailing comma in JSON objectk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2019-03-16Notify AppVeyor results to multiple channelsk0kubun
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-15Increase the number of curl retriesk0kubun
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-02-07appveyor.yml: retry zlib downloadsk0kubun
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
2018-11-28Try with TZInfo and Timezone gemsnobu
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-20configure.ac: disable native-fiber for MinGWk0kubun
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-20appveyor.yml: exclude TestEnumerable.rb on msys2k0kubun
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-20appveyor.yml: native-fiber crashes Enumeratork0kubun
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-19appveyor.yml: separately execute test_bignumk0kubun
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-16appveyor.yml: skip reverting comment improvement [ci skip]k0kubun
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-16appveyor.yml: give up running test_push_over_ary_maxk0kubun
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-13appveyor.yml: run memory-exchausting test separatelyk0kubun
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-10-28appveyor.yml: fix wrong path to test directoryk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65418 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-28appveyor.yml: run test_open-uri separatelyk0kubun
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-26appveyor.yml: run second half of vs with -vk0kubun
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-23appveyor.yml: give up using mspec -jk0kubun
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.travis.yml: run the slowest jobs firstk0kubun
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-23appveyor.yml: separately execute problematic test casek0kubun
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-21appveyor.yml: workaround wrong command line escapek0kubun
backslash in %APPVEYOR_BUILD_FOLDER% is somehow dropped somewhere when being passed to test runner via mingw32-make. Anyway we know the relative path to the project directory, so we can specify that with slash. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65262 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-21appveyor.yml: fix wrong spec directoryk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65259 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-20appveyor.yml: don't run win32ole with -jk0kubun
since it lets worker crash https://ci.appveyor.com/project/ruby/ruby/builds/19659321/job/swnu2b5yj960t9gr git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65255 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-20appveyor.yml: increase timeout for mswink0kubun
because https://ci.appveyor.com/project/ruby/ruby/builds/19643041/job/jlqs65wsvoqdguj0 failed with timeout on vs140 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65187 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19test/lib/jit_support.rb: fire test_jit everywherek0kubun
That was a workaround to make rubyci green for a short term after the MJIT merge. As we've done many portability fixes for MJIT, let's try running test_jit on all rubyci platforms. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65175 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-19appveyor.yml: use -fs for test-speck0kubun
to debug silent death on vs120 builds https://ci.appveyor.com/project/ruby/ruby/builds/19630104/job/tm8at8kfnvwxwe58 https://ci.appveyor.com/project/ruby/ruby/builds/19631779/job/qpjanaho1lc1e5a0 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65172 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-14appveyor.yml: test open-uri separatelyk0kubun
This randomly crashes test worker https://ci.appveyor.com/project/ruby/ruby/builds/19488746/job/pf1c78dlh8lqcj06 and running it without -j is suggested. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65071 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-13appveyor.yml: reorder jobsk0kubun
to reduce time to get all green. As we have 3 parallelism on AppVeyor, running the slow msys2 job first doesn't have significant impact on job priorities, but at the same time this would reduce the time that only msys2 is running alone at last. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65052 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12Disable fast_finishnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65029 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12Remove debug printnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65022 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12use APPVEYOR_BUILD_WORKER_IMAGEnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65021 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12escapenaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65020 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12Quote pathnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12debug printnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12Define VS140COMNTOOLS by itselfnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65017 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11Specify vm image on appveyor.ymlnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65016 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11show envvars before use itnaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65005 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11Show VS*COMNTOOLS environment variable on appveyornaruse
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65004 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-08appveyor.yml: execute test_syntax separatelyk0kubun
because NoMemoryError tends to be caused by TestSyntax#assert_syntax_files. https://ci.appveyor.com/project/ruby/ruby/build/1.0.8525 https://ci.appveyor.com/project/ruby/ruby/build/1.0.8795 https://ci.appveyor.com/project/ruby/ruby/builds/19334828/job/s1960qssxnk1lpoi git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64962 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-07appveyor.yml: completely separate win32ole testsk0kubun
because r64938 was not enough and another win32ole test file (`test_win32ole_type.rb`) crashed worker. https://ci.appveyor.com/project/ruby/ruby/builds/19321161/job/ue1qrphi5j1xxgu6 Let's run whole win32ole test suite separately. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64948 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-07appveyor.yml: give up running TestThreadQueue#test_queue_with_trapk0kubun
for mswin. We tried to increase timeout and execute separately but both didn't work. Let me skip this until somebody starts to work on fixing this behavior, since this makes AppVeyor almost impossible to be used as CI. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64943 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-07appveyor.yml: separately execute unstable testsk0kubun
without -j option. Those 2 tests are too unstable on AppVeyor. test/excludes/TestThreadQueue.rb: The most unstable test ever. That even fails on my machine too. This may be possibly because recent SIGCHLD-related changes. https://ci.appveyor.com/project/ruby/ruby/build/9795/job/l9t4w9ks7arsldb1 test/excludes/TestWin32OLE.rb: I saw that win32ole crashes test-all several times. https://ci.appveyor.com/project/ruby/ruby/build/9811/job/ra5uxf2cg6v7ohag git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64938 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-07revert r64935k0kubun
that didn't work at all. So the so file should be open at the time. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64937 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-07appveyor.yml: use ./tmp as TMPDIR for test-allk0kubun
on VS. On AppVeyor, we seem to fail to remove so file due to permission error. C:/projects/ruby/test/ruby/test_jit.rb:419: warning: MJIT warning: failed to remove "C:\Users\appveyor\AppData\Local\Temp\1/_ruby_mjit_p3580u0.so": Permission denied https://ci.appveyor.com/project/ruby/ruby/builds/19317520/job/sh8s6tw6ayxvtl33 But this is not reproductive on my local mswin environment at all. To identify the cause, let me try changing the TMPDIR. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64935 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-25appveyor.yml: increase timeout for vsk0kubun
because `TestThreadQueue#test_queue_with_trap` is too unstable especially on vs140. https://ci.appveyor.com/project/ruby/ruby/build/9731/job/sevjm9lrmssg4dub Increasing timeout may not fix the issue, but let me test this first to check if it's true or not. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64840 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-13appveyor.yml: increase timeout for vsk0kubun
vs140 tends to die with 10s timeout on TestThreadQueue#test_queue_with_trap https://ci.appveyor.com/project/ruby/ruby/build/9610/job/di9durc5rv0dwhor https://ci.appveyor.com/project/ruby/ruby/build/9598/job/t7wugyn1sm57lbw3 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64708 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-30 12:09:50 +0000