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

39 Коммитов

Автор SHA1 Сообщение Дата
Takashi Kokubun 6a5e89e23c
Set git config to commit mjit-debug
As it failed to commit like:
https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cefd8a8105780001c4f2d5d?step=5cefdd1e48fad200077fa3f8
2019-05-31 07:24:11 +09:00
Takashi Kokubun 67f75d5b43
Add TESTOPTS=-v for Wercker test-all --jit-wait
because it's hard to identify which test causes a hang for now.
2019-05-29 08:04:49 +09:00
Takashi Kokubun 187ef00a41
wercker.yml: Commit MJIT debug logs to another repository
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.
2019-05-23 08:41:19 -07:00
Takashi Kokubun b80adde359
wercker.yml: Notify master branch instead of trunk 2019-05-22 09:07:22 -07:00
Takashi Kokubun 4fe0961dca
Fix typo in debugged C source name
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.
2019-05-14 16:45:19 +09:00
Takashi Kokubun a1bab3d1a3
Escape $@ in mjit-debug-on-fail 2019-05-08 16:51:39 +09:00
Takashi Kokubun b0965cc2d6
Add missing chmod for mjit-debug-on-fail 2019-05-08 16:26:53 +09:00
Takashi Kokubun 60869ebd00
Wrap mjit-debug-on-fail for Wercker failure
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
2019-05-08 16:26:01 +09:00
k0kubun 4eda7e1d14 Stop sharding --jit-wait testing
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
2019-03-01 14:09:41 +00:00
k0kubun 9edbcbcba1 wercker.yml: debug problematic test on test-all
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-18 09:32:29 +00:00
k0kubun e2074a359e test/excludes/_wercker: remove obsoleted pipeline name
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-16 06:52:12 +00:00
k0kubun bec184b5e6 wercker.yml: use pipeline name for notification [ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-03 00:44:04 +00:00
k0kubun f6d44b59c6 wercker.yml: stop allowing webrick failure
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-01 13:49:33 +00:00
k0kubun 187b5e7176 TestDelegateClass.rb: skip test_frozen for --jit-wait
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-01 07:49:06 +00:00
k0kubun 992f6f940e wercker.yml: improve parallelism more
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-01 06:03:29 +00:00
k0kubun a140e17f12 wercker.yml: improve CI step message [ci skip]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65484 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01 05:17:08 +00:00
k0kubun cab1e6bf01 wercker.yml: change pipeline names
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-01 05:03:59 +00:00
k0kubun 44c39702fb wercker.yml: delete obsoleted test definition
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01 04:46:46 +00:00
k0kubun 22fa141d05 wercker.yml: improve parallelism of test-mjit and test-mjit-wait
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65481 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-11-01 04:43:40 +00:00
k0kubun bd68968d80 wercker.yml: harder test-mjit-wait testing
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-11-01 02:50:10 +00:00
k0kubun a4cfd15a73 revert r65441
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-30 23:16:16 +00:00
k0kubun 5662e709f4 wercker.yml: try testing wercker again
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-30 15:39:18 +00:00
k0kubun 2160c4dead wercker.yml: skip webrick for test-mjit-wait for now
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-25 03:25:19 +00:00
k0kubun 0fbc28dec5 wercker.yml: rearrange test split times
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-24 15:49:03 +00:00
k0kubun f84c318420 revert r65353 [ci skip]
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-24 12:19:39 +00:00
k0kubun beec400d9e wercker.yml: run slower job first
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-24 12:14:26 +00:00
k0kubun 4b0273886a wercker.yml: skip TestParallel::TestParallel#test_separate
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-24 10:29:39 +00:00
k0kubun 9d93d8b15e wercker.yml: try to split test-all again
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-24 09:52:01 +00:00
k0kubun e3bd6ef7c4 wercker.yml: skip test_queue_with_trap on -wait as well
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-24 03:05:43 +00:00
k0kubun 9641ff43d1 wercker.yml: skip #test_queue_with_trap for now
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-23 22:51:28 +00:00
k0kubun fd63a5c52c wercker.yml: increase timeout scale
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-23 16:49:55 +00:00
k0kubun 29207a939f wercker.yml: run both --jit and --jit-wait
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65338 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 16:23:55 +00:00
k0kubun 5714b2ce8c wercker.yml: stop using my personal Docker container
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65337 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 15:54:11 +00:00
k0kubun abfc5470c0 wercker.yml: stop splitting test-all
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-23 15:09:49 +00:00
k0kubun f2dfe96d17 wercker.yml: profile slow tests
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 14:06:36 +00:00
k0kubun bc8c89de3d wercker.yml: explain the usage of Wercker
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-23 13:34:50 +00:00
k0kubun 3b196eee56 wercker.yml: setup MJIT wait CI
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
2018-10-23 13:22:07 +00:00
k0kubun 58ec197eef wercker.yml: pending for now
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-23 00:27:08 +00:00
k0kubun 369f529acf wercker.yml: run --jit-wait test on Wercker
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
2018-10-23 00:19:53 +00:00