repo:http://121.36.84.172/dailybuild/EBS-openEuler-22.03-LTS-SP1/Alpha_openeuler-2022-11-23-19-40-46
Pending: (Failures listed here are expected and do not affect your suite's status)
Pry::Editor build_editor_invocation_string should shell-escape files
Pry::InputCompleter should not crash if there's a Module that has a symbolic name.
ls on java objects should omit java-esque aliases by default
ls on java objects should include java-esque aliases if requested
Failures:
Pry::Config is expected to equal true or equal false
Failure/Error: specify { expect(subject.auto_indent).to be(true).or be(false) }
expected true
got nil
...or:
expected false
got nil
Pry::Config is expected to equal true or equal false
Failure/Error: specify { expect(subject.color).to be(true).or be(false) }
expected true
got nil
...or:
expected false
got nil
Pry::REPL eval_string and binding_stack should immediately evaluate eval_string after cmd if complete
Failure/Error: expect(last_prompt).to match pattern
expected "[1] pry(main)* " to match /* $/
Diff:
@@ -1,2 +1,2 @@
-/* $/
+"[1] pry(main)* "
Pry::REPL autoindent should raise no exception when indented with a tab
Failure/Error: expect(@pry.output.string.chomp).to match pattern
RegexpError:
premature end of char-class: /do
break #note the tab here
end
\x1B[1B\x1B[0G=> nil/
Finished in 58.14 seconds (files took 0.43855 seconds to load)
1431 examples, 4 failures, 4 pending
Failed examples:
rspec ./spec/config_spec.rb:25 # Pry::Config is expected to equal true or equal false
rspec ./spec/config_spec.rb:17 # Pry::Config is expected to equal true or equal false
rspec ./spec/pry_repl_spec.rb:81 # Pry::REPL eval_string and binding_stack should immediately evaluate eval_string after cmd if complete
rspec ./spec/pry_repl_spec.rb:127 # Pry::REPL autoindent should raise no exception when indented with a tab
Randomized with seed 63824
Hi dongjie110, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: sig-ruby, and any of the maintainers: @木得感情的openEuler机器人 , @small_leek , @薄皮小笼包
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。
该问题为偶现失败。用例执行start函数,start函数内部会获取当前执行线程,根据日志查看该问题属于多线程执行时资源抢占导致返回数据异常导致失败。问题与软件包本身代码无关,
该问题为偶现失败。用例执行start函数,start函数内部会获取当前执行线程,根据日志查看该问题属于多线程执行时资源抢占导致返回数据异常导致失败。问题与软件包本身代码无关,
@吴磊磊 此包在EBS上近期均为构建失败,请继续排查一下
【问题根因】
构建工程框架的TERM=dumb,因为该包的测试用例需要断言颜色,所以导致测试用例失败
【解决方案】
构建工程框架 export TERM=xterm-256color 使用的docker中已包含所有的terminfo
登录 后才可以发表评论