aboutsummaryrefslogtreecommitdiffstats
path: root/wercker.yml
Commit message (Collapse)AuthorAgeFilesLines
* Generalize timeout_scaleNobuyoshi Nakada2019-06-111-2/+2
| | | | | | | | | | | * 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"]`.
* Set git config to commit mjit-debugTakashi Kokubun2019-05-311-1/+3
| | | | | As it failed to commit like: https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cefd8a8105780001c4f2d5d?step=5cefdd1e48fad200077fa3f8
* Add TESTOPTS=-v for Wercker test-all --jit-waitTakashi Kokubun2019-05-291-1/+1
| | | | because it's hard to identify which test causes a hang for now.
* wercker.yml: Commit MJIT debug logs to another repositoryTakashi Kokubun2019-05-231-6/+16
| | | | | | | because too-large Wercker output is truncated. ruby/mjit-debug is a private repository for now, because the person fixing it is likely to be me or another committer.
* wercker.yml: Notify master branch instead of trunkTakashi Kokubun2019-05-221-2/+2
|
* Fix typo in debugged C source nameTakashi Kokubun2019-05-141-1/+1
| | | | | | | I failed to collect any debug info in https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cda57fcab79a30008f195f6?step=5cda6a4e1090c4000800772e It seems that it's due to this typo.
* Escape $@ in mjit-debug-on-failTakashi Kokubun2019-05-081-1/+1
|
* Add missing chmod for mjit-debug-on-failTakashi Kokubun2019-05-081-0/+1
|
* Wrap mjit-debug-on-fail for Wercker failureTakashi Kokubun2019-05-081-1/+16
| | | | | | for debugging failure like https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cc98936ab79a30008eb86fa?step=5cc990d73d81fb0007bb04c3 https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cd18efa23fcb70008ddfd45?step=5cd1908603f4460007076c5a
* Stop sharding --jit-wait testingk0kubun2019-03-011-206/+7
| | | | | | | | | | | | | | | | | | | | by just randomizing test order. The original motivation to shard --jit-wait tests was forcing to test major parts of code without actually stopping to test MJIT after TracePoint enablement. But it tends to increase the test time because we often compile the same thing in different shards. I made this decision because we seem to hit 1.5h timeout of Wercker these days, and Wercker is really bad at handling timeout (it does not report timeout as failure, but just keeps it "pending" state) https://app.wercker.com/ruby/ruby/runs/mjit-test2/5c78f15cc9e725000805b86c?step=5c79031d6c1e2c0008ac41c3 By randomizing this, we could test things randomly. The downside of this approach is that we may not be able to find a specific commit that caused a future failure by having TracePoint in a very early phase. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67158 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: debug problematic test on test-allk0kubun2018-11-181-1/+1
| | | | | | | Some test seems to hang https://app.wercker.com/ruby/ruby/runs/mjit-test1/5bf1221c183106002855989c?step=5bf1225987436a0006192c31 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65789 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* test/excludes/_wercker: remove obsoleted pipeline namek0kubun2018-11-161-63/+63
| | | | | | | | | from excludes directory names. test-mjit-wait / test-mjit are combined and distributed as mjit-test1 and mjit-test2 now. So the subdirectory names are changed to option names, --jit and --jit-wait. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65766 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: use pipeline name for notification [ci skip]k0kubun2018-11-031-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: stop allowing webrick failurek0kubun2018-11-011-71/+72
| | | | | | | | | Failure seems no longer reproductive recently... Also I wrote a comment about this complicated test matrix and improved parallelism a little more again. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65494 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* TestDelegateClass.rb: skip test_frozen for --jit-waitk0kubun2018-11-011-9/+9
| | | | | | | | | for now. Investigating. https://app.wercker.com/ruby/ruby/runs/mjit-test2/5bda979a191eda000655a8d2?step=5bda9fe4591ca80007653f64 wercker.yml: improve parallelism again. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65489 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: improve parallelism morek0kubun2018-11-011-28/+28
| | | | | | mjit-test2 is taking more time now. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65486 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: improve CI step message [ci skip]k0kubun2018-11-011-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65484 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: change pipeline namesk0kubun2018-11-011-2/+2
| | | | | | because the name "-wait" is no longer distinguishing these pipelines git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65483 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: delete obsoleted test definitionk0kubun2018-11-011-24/+0
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: improve parallelism of test-mjit and test-mjit-waitk0kubun2018-11-011-35/+67
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65481 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: harder test-mjit-wait testingk0kubun2018-11-011-6/+201
| | | | | | | Currently TracePoint enablement may cancel all JITs. So for now, separating test executions would reveal more failures. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65478 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* revert r65441k0kubun2018-10-301-1/+2
| | | | | | | | | | I could collect 2 test failure information: https://app.wercker.com/ruby/ruby/runs/test-mjit-wait/5bd8a253191eda0006545d47?step=5bd8a29387436a0006842ef0 https://app.wercker.com/ruby/ruby/runs/test-mjit-wait/5bd8c6e0191eda0006547273?step=5bd8c71a591ca8000756f4a3 I'll skip this again to make it functional as CI git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65459 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: try testing wercker againk0kubun2018-10-301-2/+1
| | | | | | | | I don't think we fixed that, but if so, I would like to see more test failures. Previous failures didn't keep enough C-backtrace information about the failure and it's hard to debug for now. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65441 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: skip webrick for test-mjit-wait for nowk0kubun2018-10-251-1/+2
| | | | | | | | as failing https://app.wercker.com/ruby/ruby/runs/test-mjit-wait/5bd092a89b1e440006d5780d?step=5bd092e3591ca80007258400 now and it needs some fix. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65363 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: rearrange test split timesk0kubun2018-10-241-4/+4
| | | | | | test-all2 is taking much longer time than test-all1 now. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65358 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* revert r65353 [ci skip]k0kubun2018-10-241-20/+20
| | | | | | | | As Wercker is managing workflow by GUI, the commit had no impact for behavior... I already fixed the workflow on GUI. Let revert that to change it back to natural order. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65354 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: run slower job firstk0kubun2018-10-241-20/+20
| | | | | | to reduce time taken for finishing all jobs. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65353 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: skip TestParallel::TestParallel#test_separatek0kubun2018-10-241-6/+6
| | | | | | for now. It's randomly failing on test-mjit-wait. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65348 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: try to split test-all againk0kubun2018-10-241-2/+6
| | | | | | | TestParallel in test/testunit/... seems to be slow. Let's see if this contributes to loosen timeout or not. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65347 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: skip test_queue_with_trap on -wait as wellk0kubun2018-10-241-2/+2
| | | | | | | It randomly failed. https://app.wercker.com/ruby/ruby/runs/test-mjit-wait/5bcfd19aa9806e000655c598?step=5bcfd1d5acc4510006e00f77 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65346 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: skip #test_queue_with_trap for nowk0kubun2018-10-231-1/+1
| | | | | | only on --jit CI. This test doesn't work on AppVeyor mswin either. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65340 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: increase timeout scalek0kubun2018-10-231-2/+2
| | | | | | | | | mainly for test-mjit. TestThreadQueue#test_queue_with_trap timed out with 10s. https://app.wercker.com/ruby/ruby/runs/test-mjit/5bcf4b5c9065740006f790ca?step=5bcf4b9787436a000648fbb7 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65339 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: run both --jit and --jit-waitk0kubun2018-10-231-6/+38
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: stop using my personal Docker containerk0kubun2018-10-231-10/+12
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65337 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: stop splitting test-allk0kubun2018-10-231-6/+2
| | | | | | | since it actually doesn't contribute to CI build time so much, rather it seems making it worse. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65335 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: profile slow testsk0kubun2018-10-231-2/+2
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: explain the usage of Werckerk0kubun2018-10-231-2/+10
| | | | | | | | | at ruby repository. I also added a woraround to loosen timeout for test-all. I resolved the issue that lets --jit-wait CI timeout, so this workaround is not strictly needed, but this might make it easier to debug when things go wrong. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65325 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: setup MJIT wait CIk0kubun2018-10-231-20/+18
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: pending for nowk0kubun2018-10-231-15/+19
| | | | | | | | | As the Wercker integration is already enabled, I added wercker.yml but it's not working due to migration to this repository and I don't have enough time to fix it immediately. I'll make it work in this evening. Let me show green status on GitHub commit logs. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65314 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* wercker.yml: run --jit-wait test on Werckerk0kubun2018-10-231-0/+33
New. This was formerly https://github.com/k0kubun/mjit-test. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65313 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-07 22:45:50 +0000