Граф коммитов

82 Коммитов

Автор SHA1 Сообщение Дата
k0kubun 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
k0kubun 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
k0kubun 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
k0kubun 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
k0kubun 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
k0kubun 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
k0kubun 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
k0kubun 94792dbbc4 appveyor.yml: workaround wrong command line escape
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-21 02:18:39 +00:00
k0kubun f5bf1a32d0 appveyor.yml: fix wrong spec directory
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65259 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-21 00:31:46 +00:00
k0kubun e77fdcd81d appveyor.yml: don't run win32ole with -j
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-20 23:58:02 +00:00
k0kubun 0c1684eb73 appveyor.yml: increase timeout for mswin
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-20 01:00:37 +00:00
k0kubun 2baf760cc2 test/lib/jit_support.rb: fire test_jit everywhere
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-19 14:03:37 +00:00
k0kubun 6458ae1bba appveyor.yml: use -fs for test-spec
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-19 13:05:05 +00:00
k0kubun 0e9466df2d appveyor.yml: test open-uri separately
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-14 01:24:21 +00:00
k0kubun 2e4d149d31 appveyor.yml: reorder jobs
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-13 01:47:55 +00:00
naruse 54e99c7cd8 Disable fast_finish
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65029 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 08:45:05 +00:00
naruse 3b3b2091d8 Remove debug print
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65022 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 01:21:45 +00:00
naruse 9d1aab4301 use APPVEYOR_BUILD_WORKER_IMAGE
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65021 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 00:45:07 +00:00
naruse 865b0c2372 escape
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65020 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 00:31:24 +00:00
naruse 0ce33fd897 Quote path
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 00:25:41 +00:00
naruse 918ce88b9c debug print
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 00:20:14 +00:00
naruse c1d78bc42e Define VS140COMNTOOLS by itself
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65017 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-12 00:09:19 +00:00
naruse c0e5f06d7d Specify vm image on appveyor.yml
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65016 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11 23:59:09 +00:00
naruse 0cb0835581 show envvars before use it
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65005 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11 23:23:16 +00:00
naruse f873de6a60 Show VS*COMNTOOLS environment variable on appveyor
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65004 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-11 23:21:11 +00:00
k0kubun 6a7df0ecc8 appveyor.yml: execute test_syntax separately
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-08 10:46:36 +00:00
k0kubun 2c276c1950 appveyor.yml: completely separate win32ole tests
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-07 16:45:16 +00:00
k0kubun cdffad515c appveyor.yml: give up running TestThreadQueue#test_queue_with_trap
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-07 14:05:56 +00:00
k0kubun 686a12a6a4 appveyor.yml: separately execute unstable tests
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-07 12:03:49 +00:00
k0kubun 6b596cc219 revert r64935
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-07 11:46:26 +00:00
k0kubun 86e09265b6 appveyor.yml: use ./tmp as TMPDIR for test-all
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-10-07 08:15:48 +00:00
k0kubun 989fc2de9a appveyor.yml: increase timeout for vs
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-25 17:26:34 +00:00
k0kubun 63130b2348 appveyor.yml: increase timeout for vs
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
2018-09-13 01:45:38 +00:00
nobu 9024509410 appveyor.yml: try VS140
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64674 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-10 13:05:34 +00:00
nobu e4b1172833 appveyor.yml: fix PATH and env for msys2
based on the patch by MSP-Greg at #1945.

Co-authored-by: MSP-Greg <greg.mpls@gmail.com>

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64627 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-04 02:19:39 +00:00
nobu 2cbf44e55b appveyor.yml: reduce matrix factors
* appveyor.yml (environment): separate matrix factors by `build` (`vs`
  or `msys2`), and `build` (and `vs` version if VS build).
  now `MSYS2_ARCH` and `MSYSTEM` are derived from `Platform` if msys2
  build.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64626 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-09-04 02:18:51 +00:00
nobu 9c827bd051 appveyor.yml: run on all branches
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64395 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-16 16:11:54 +00:00
kazu 1f0f2ae2a0 Remove outdated comment [ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64394 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-16 12:14:11 +00:00
nobu 425a820d17 appveyor.yml: no MSYS path conversion
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64370 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-15 04:10:19 +00:00
nobu 5a149052fe appveyor.yml: get rid of msys sh as possible
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64368 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-15 02:15:13 +00:00
k0kubun 1684a1bd71 appveyor.yml: remove broken --name option
Currently all tests are skipped by the --name option.
V=1 is for debugging this issue.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64364 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-14 23:23:44 +00:00
k0kubun 490838959b appveyor.yml: install gdbm
which is missing on AppVeyor environment

6a1e323ae8 (commitcomment-30056791)

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64350 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-13 16:03:47 +00:00
k0kubun 6a1e323ae8 appveyor.yml: add MinGW build
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64348 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-13 15:29:40 +00:00
k0kubun 7496672904 appveyor.yml: drop unnecessary 1.0. prefix
from version.

Also I fixed the wrong way of using `for:`.
Specifying `for` without `matrix.only` was just useless.
This fix is for adding MinGW matrix in the future.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64342 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-13 13:46:06 +00:00
k0kubun b1ecbf8e02 appveyor.yml: customize icon_url
We're using "x" sign as an icon for incoming webhook, but the success
notification by `on_build_status_changed` should not be an "x" asign.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64311 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-11 23:33:36 +00:00
nobu 591b2566d7 appveyor.yml: show the OS version
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64300 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-11 14:15:58 +00:00
k0kubun 63145476e8 appveyor.yml: don't notify PR failure to Slack
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-10 12:55:18 +00:00
k0kubun 29ccaf6ea9 appveyor.yml: make sure MJIT is tested on AppVeyor
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@64222 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-08-07 16:49:34 +00:00
k0kubun 8c8d298c88 appveyor.yml: refactor r62402
We have good feature to share common configuration between branches:
https://www.appveyor.com/docs/branches/#sharing-common-configuration-between-branches
Let's try this.

By the way, the intention of r62402 was excluding PR notifications while
it wasn't written in the commit message.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62403 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-14 14:09:32 +00:00
k0kubun 7da8fa1cb7 appveyor.yml: notify slack only for trunk
Using conditional build configuration.
https://www.appveyor.com/docs/branches/#conditional-build-configuration

This copy-pasting is so ugly, but AppVeyor doesn't have a feature to
filter notification based on branch.
https://github.com/appveyor/ci/issues/272

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62402 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-02-14 12:34:49 +00:00