summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authork0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-03-11 09:32:48 +0000
committerk0kubun <k0kubun@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2018-03-11 09:32:48 +0000
commit31b6ac1b9a6ebc0f97cc0ceea11ad3e488fa6561 (patch)
treef0502831c89020e8c136c4297d3fab57753e1837 /test
parent6679ffd3b5a60ebc13fdefeff6d066b43854029b (diff)
test_jit.rb: add debugging output
Sometimes gcc fails to exec cc1 like this: https://gist.github.com/ko1/c3db8b193e9cc65c39c541e10d957509 I'm not sure why it happens at all. Please let me add this debugging output to inspect the random failure on CI for now. I'll remove this after we confirm it's not helpful. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@62720 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'test')
-rw-r--r--test/ruby/test_jit.rb7
1 files changed, 7 insertions, 0 deletions
diff --git a/test/ruby/test_jit.rb b/test/ruby/test_jit.rb
index a53f89bd66..55c03f72d8 100644
--- a/test/ruby/test_jit.rb
+++ b/test/ruby/test_jit.rb
@@ -545,6 +545,13 @@ class TestJIT < Test::Unit::TestCase
def assert_eval_with_jit(script, stdout: nil, success_count:, min_calls: 1)
out, err = eval_with_jit(script, verbose: 1, min_calls: min_calls)
actual = err.scan(/^#{JIT_SUCCESS_PREFIX}:/).size
+
+ # Debugging on CI
+ if stderr.include?("gcc: error trying to exec 'cc1': execvp: No such file or directory")
+ puts "test/ruby/test_jit.rb: ENV content:"
+ pp ENV
+ end
+
assert_equal(
success_count, actual,
"Expected #{success_count} times of JIT success, but succeeded #{actual} times.\n\n"\