summaryrefslogtreecommitdiff
path: root/appveyor.yml
Commit message (Collapse)AuthorAgeFilesLines
* Debug which test hangs on mswinTakashi Kokubun2019-08-111-1/+1
| | | | | debugging failure of https://ci.appveyor.com/project/ruby/ruby/builds/26613960/job/nemi6pvc5s5843io
* Revert "Drop -j from msys2 build for debugging"Takashi Kokubun2019-08-081-1/+1
| | | | | | | | | | This reverts commit b1594ca3d6b72edb60927418482652ce93209499. Revert "Debug appveyor mingw failure" This reverts commit fa29f65416f1fb3d734a279855728bb0616dbb34. Though I preserved V=1 for future debugging.
* Arrange installed packages like ruby-locoTakashi Kokubun2019-08-081-5/+1
| | | | | | | | | 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>
* Drop -j from msys2 build for debuggingTakashi Kokubun2019-08-081-1/+1
|
* Debug appveyor mingw failureTakashi Kokubun2019-08-081-1/+1
| | | | | | | 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
* Stop isolating test_gc_compact on CITakashi Kokubun2019-07-291-4/+4
| | | | I think it's been stable these days.
* Build AppVeyor only on masterTakashi Kokubun2019-07-011-3/+1
|
* Generalize timeout_scaleNobuyoshi Nakada2019-06-111-4/+4
| | | | | | | | | | | * 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"]`.
* appveyor.yml again!MSP-Greg2019-06-011-2/+2
| | | | | 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'...
* appveyor.yml - update for msys2 - pdcurses, force toolchainMSP-Greg2019-05-291-2/+4
| | | | | | | 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
* Unify RELINE_TEST_ENCODING settingNobuyoshi Nakada2019-05-281-2/+1
|
* Set read-only with attrib commandNobuyoshi Nakada2019-05-281-2/+1
|
* Avoid doubly building Travis and AppVeyorTakashi Kokubun2019-05-281-4/+5
| | | | | | | | but on "master" branch. For Pull Request, I changed the approach from d9b338a53f520b2dbb05555f18b8de8072300f40 and 277e68825a8e4d0e6503a32e41f8b1b6c078b567.
* Build trunk branch too to trigger AppVeyor on PRTakashi Kokubun2019-05-251-3/+4
|
* Pretend to update all Unicode filesNobuyoshi Nakada2019-05-231-2/+3
|
* Revert "Revert CI deduplication on Wercker / Azure for debugging"Takashi Kokubun2019-05-221-0/+3
| | | | | | This reverts commit 1ebe9a2f82fef5190454e68d430004282f5da172. because it did not help.
* Revert CI deduplication on Wercker / Azure for debuggingTakashi Kokubun2019-05-221-3/+0
| | | | | | | | | | | | | | | | | | | | 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.
* appveyor.yml: Do not doubly run CI on trunkTakashi Kokubun2019-05-221-0/+3
|
* Update include files on msys2 tooNobuyoshi Nakada2019-05-181-1/+2
|
* Add Reline as a fallback library for Readlineaycabta2019-04-301-1/+3
| | | | | | | | | | | | | * 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.
* Isolate test_gc_compact on AppVeyor mswin as wellTakashi Kokubun2019-04-281-2/+2
| | | | | because it makes the CI unstable https://ci.appveyor.com/project/ruby/ruby/builds/24143365/job/yrx7b8ce2qg9wro2
* Isolate test_gc_compact on msys2 AppVeyorTakashi Kokubun2019-04-271-2/+2
| | | | | as it's unstable on the environment https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey
* appveyor.yml: try porting r67454 to msys2k0kubun2019-04-061-1/+1
| | | | | | | 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
* appveyor.yml: Use pre-generated headers and tablesnobu2019-04-061-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67454 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* appveyor.yml: download beta version for testnobu2019-04-051-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67449 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Drop invalid trailing comma in JSON objectk0kubun2019-03-171-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Notify AppVeyor results to multiple channelsk0kubun2019-03-161-30/+46
| | | | | | | | | | | | 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
* Increase the number of curl retriesk0kubun2019-03-151-1/+1
| | | | | | | 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
* appveyor.yml: retry zlib downloadsk0kubun2019-02-071-1/+1
| | | | | | 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
* Try with TZInfo and Timezone gemsnobu2018-11-281-0/+3
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66079 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* configure.ac: disable native-fiber for MinGWk0kubun2018-11-201-4/+4
| | | | | | | | | | | | | | | | 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
* appveyor.yml: exclude TestEnumerable.rb on msys2k0kubun2018-11-201-4/+4
| | | | | | | 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
* appveyor.yml: native-fiber crashes Enumeratork0kubun2018-11-201-2/+2
| | | | | | | | | | 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
* appveyor.yml: separately execute test_bignumk0kubun2018-11-191-2/+2
| | | | | | | 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
* appveyor.yml: skip reverting comment improvement [ci skip]k0kubun2018-11-161-2/+2
| | | | | | This part was not intended in r65760 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65762 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* appveyor.yml: give up running test_push_over_ary_maxk0kubun2018-11-161-6/+6
| | | | | | | | | 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
* appveyor.yml: run memory-exchausting test separatelyk0kubun2018-11-131-6/+6
| | | | | | | | 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
* appveyor.yml: fix wrong path to test directoryk0kubun2018-10-281-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65418 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* appveyor.yml: run test_open-uri separatelyk0kubun2018-10-281-2/+2
| | | | | | | 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
* appveyor.yml: run second half of vs with -vk0kubun2018-10-261-1/+1
| | | | | | | | 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
* appveyor.yml: give up using mspec -jk0kubun2018-10-231-2/+2
| | | | | | | 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
* .travis.yml: run the slowest jobs firstk0kubun2018-10-231-0/+1
| | | | | | | | 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
* appveyor.yml: separately execute problematic test casek0kubun2018-10-231-2/+2
| | | | | | | 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
* appveyor.yml: workaround wrong command line escapek0kubun2018-10-211-1/+1
| | | | | | | | | | 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
* appveyor.yml: fix wrong spec directoryk0kubun2018-10-211-1/+1
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65259 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* appveyor.yml: don't run win32ole with -jk0kubun2018-10-201-1/+3
| | | | | | | 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
* appveyor.yml: increase timeout for mswink0kubun2018-10-201-2/+2
| | | | | | | | 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
* test/lib/jit_support.rb: fire test_jit everywherek0kubun2018-10-191-2/+2
| | | | | | | | 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
* appveyor.yml: use -fs for test-speck0kubun2018-10-191-1/+1
| | | | | | | | 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
* appveyor.yml: test open-uri separatelyk0kubun2018-10-141-2/+2
| | | | | | | | 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
View Lorry Controller Status