summaryrefslogtreecommitdiff
path: root/wercker.yml
AgeCommit message (Collapse)Author
2018-11-18wercker.yml: debug problematic test on test-allk0kubun
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
2018-11-16test/excludes/_wercker: remove obsoleted pipeline namek0kubun
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
2018-11-03wercker.yml: use pipeline name for notification [ci skip]k0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01wercker.yml: stop allowing webrick failurek0kubun
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
2018-11-01TestDelegateClass.rb: skip test_frozen for --jit-waitk0kubun
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
2018-11-01wercker.yml: improve parallelism morek0kubun
mjit-test2 is taking more time now. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65486 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01wercker.yml: improve CI step message [ci skip]k0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65484 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01wercker.yml: change pipeline namesk0kubun
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
2018-11-01wercker.yml: delete obsoleted test definitionk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01wercker.yml: improve parallelism of test-mjit and test-mjit-waitk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65481 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01wercker.yml: harder test-mjit-wait testingk0kubun
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
2018-10-30revert r65441k0kubun
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
2018-10-30wercker.yml: try testing wercker againk0kubun
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
2018-10-25wercker.yml: skip webrick for test-mjit-wait for nowk0kubun
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
2018-10-24wercker.yml: rearrange test split timesk0kubun
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
2018-10-24revert r65353 [ci skip]k0kubun
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
2018-10-24wercker.yml: run slower job firstk0kubun
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
2018-10-24wercker.yml: skip TestParallel::TestParallel#test_separatek0kubun
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
2018-10-24wercker.yml: try to split test-all againk0kubun
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
2018-10-24wercker.yml: skip test_queue_with_trap on -wait as wellk0kubun
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
2018-10-23wercker.yml: skip #test_queue_with_trap for nowk0kubun
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
2018-10-23wercker.yml: increase timeout scalek0kubun
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
2018-10-23wercker.yml: run both --jit and --jit-waitk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23wercker.yml: stop using my personal Docker containerk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65337 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23wercker.yml: stop splitting test-allk0kubun
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
2018-10-23wercker.yml: profile slow testsk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23wercker.yml: explain the usage of Werckerk0kubun
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
2018-10-23wercker.yml: setup MJIT wait CIk0kubun
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23wercker.yml: pending for nowk0kubun
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
2018-10-23wercker.yml: run --jit-wait test on Werckerk0kubun
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.25.1) at 2024-04-30 15:14:43 +0000