Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 518264 Details for
Bug 646830
dev-ruby/fuubar-2.3.1: test failures when stdout is not a tty
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
build.log (text/plain), 6.95 KB, created by
Thomas Deutschmann (RETIRED)
on 2018-02-06 20:12:53 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Thomas Deutschmann (RETIRED)
Created:
2018-02-06 20:12:53 UTC
Size:
6.95 KB
patch
obsolete
> * Package: dev-ruby/fuubar-2.3.1 > * Repository: gentoo > * Maintainer: ruby@gentoo.org > * USE: abi_x86_32 elibc_glibc kernel_linux ruby_targets_ruby22 ruby_targets_ruby23 test userland_GNU x86 > * FEATURES: preserve-libs sandbox test userpriv usersandbox >>>> Unpacking source... > * Running unpack phase for all ... > * Unpacking .gem file... ... > [ ok ] > * Uncompressing metadata ... > [ ok ] > * Unpacking data.tar.gz ... > [ ok ] >>>> Source unpacked in /var/tmp/portage/dev-ruby/fuubar-2.3.1/work >>>> Preparing source in /var/tmp/portage/dev-ruby/fuubar-2.3.1/work ... > * Running prepare phase for all ... > * Running prepare phase for all ... > * Running source copy phase for ruby22 ... > * Running source copy phase for ruby23 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-ruby/fuubar-2.3.1/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-ruby/fuubar-2.3.1/work ... > * Running compile phase for all ... >>>> Source compiled. >>>> Test phase: dev-ruby/fuubar-2.3.1 > * Running test phase for ruby22 ... >..........F....FFFFFF > >Failures: > > 1) Fuubar when it is created and continuous integration is not enabled when processing an example does not output color codes > Failure/Error: expect(fuubar_results).to start_with "\e[32m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > expected " 1/2 |== 50 ==> | ETA: 00:00:00 \r 0/2 |> | ETA: ??:??:?? \r" to start with "\e[32m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > # ./spec/fuubar_spec.rb:145:in `block (5 levels) in <top (required)>' > > 2) Fuubar when it is started and an example passes outputs the proper bar information > Failure/Error: expect(fuubar_results).to start_with "\e[32m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > expected " 1/2 |== 50 ==> | ETA: 00:00:00 \r 0/2 |> | ETA: ??:??:?? \r" to start with "\e[32m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > # ./spec/fuubar_spec.rb:191:in `block (4 levels) in <top (required)>' > > 3) Fuubar when it is started and an example pends outputs the proper bar information > Failure/Error: expect(fuubar_results).to start_with "\e[33m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > expected " 1/2 |== 50 ==> | ETA: 00:00:00 \r 2/2 |===== 100 ======>| Time: 00:00:00 \n" to start with "\e[33m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > # ./spec/fuubar_spec.rb:204:in `block (4 levels) in <top (required)>' > > 4) Fuubar when it is started and an example pends and then an example succeeds outputs the pending bar > Failure/Error: expect(fuubar_results).to start_with "\e[33m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > expected " 2/2 |===== 100 ======>| Time: 00:00:00 \n 0/2 |> | ETA: ??:??:?? \r" to start with "\e[33m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > # ./spec/fuubar_spec.rb:215:in `block (5 levels) in <top (required)>' > > 5) Fuubar when it is started and an example fails outputs the proper bar information > Failure/Error: expect(fuubar_results).to end_with "\e[31m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > expected " \r\n 1) Fuubar when it is started and an example fails \n ...ubar Error\n # /my/filename.rb:4:in `some_method'\n\n 1/2 |== 50 ==> | ETA: 00:00:00 \r" to end with "\e[31m 1/2 |== 50 ==> | ETA: 00:00:00 \r\e[0m" > # ./spec/fuubar_spec.rb:226:in `block (4 levels) in <top (required)>' > > 6) Fuubar when it is started and an example fails and then an example succeeds outputs the failed bar > Failure/Error: expect(fuubar_results).to start_with "\e[31m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > expected " 2/2 |===== 100 ======>| Time: 00:00:00 \n 0/2 |> | ETA: ??:??:?? \r ...ubar Error\n # /my/filename.rb:4:in `some_method'\n\n 1/2 |== 50 ==> | ETA: 00:00:00 \r" to start with "\e[31m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > # ./spec/fuubar_spec.rb:239:in `block (5 levels) in <top (required)>' > > 7) Fuubar when it is started and an example fails and then an example pends outputs the failed bar > Failure/Error: expect(fuubar_results).to start_with "\e[31m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > expected " 2/2 |===== 100 ======>| Time: 00:00:00 \n 0/2 |> | ETA: ??:??:?? \r ...ubar Error\n # /my/filename.rb:4:in `some_method'\n\n 1/2 |== 50 ==> | ETA: 00:00:00 \r" to start with "\e[31m 2/2 |===== 100 ======>| Time: 00:00:00 \n\e[0m" > # ./spec/fuubar_spec.rb:253:in `block (5 levels) in <top (required)>' > >Finished in 0.07732 seconds (files took 0.15962 seconds to load) >21 examples, 7 failures > >Failed examples: > >rspec ./spec/fuubar_spec.rb:144 # Fuubar when it is created and continuous integration is not enabled when processing an example does not output color codes >rspec ./spec/fuubar_spec.rb:190 # Fuubar when it is started and an example passes outputs the proper bar information >rspec ./spec/fuubar_spec.rb:202 # Fuubar when it is started and an example pends outputs the proper bar information >rspec ./spec/fuubar_spec.rb:214 # Fuubar when it is started and an example pends and then an example succeeds outputs the pending bar >rspec ./spec/fuubar_spec.rb:221 # Fuubar when it is started and an example fails outputs the proper bar information >rspec ./spec/fuubar_spec.rb:238 # Fuubar when it is started and an example fails and then an example succeeds outputs the failed bar >rspec ./spec/fuubar_spec.rb:252 # Fuubar when it is started and an example fails and then an example pends outputs the failed bar > > * ERROR: dev-ruby/fuubar-2.3.1::gentoo failed (test phase): > * rspec failed > * > * Call stack: > * ebuild.sh, line 124: Called src_test > * environment, line 4395: Called ruby-ng_src_test > * environment, line 4107: Called _ruby_each_implementation 'each_ruby_test' > * environment, line 447: Called _ruby_invoke_environment 'ruby22' 'each_ruby_test' > * environment, line 572: Called each_ruby_test > * environment, line 791: Called each_fakegem_test > * environment, line 774: Called ruby-ng_rspec > * environment, line 4066: Called die > * The specific snippet of code: > * ${RUBY} -S rspec-${version} ${rspec_params} ${files} || die "rspec failed" > * > * If you need support, post the output of `emerge --info '=dev-ruby/fuubar-2.3.1::gentoo'`, > * the complete build log and the output of `emerge -pqv '=dev-ruby/fuubar-2.3.1::gentoo'`. >!!! When you file a bug report, please include the following information: >GENTOO_VM= CLASSPATH="" JAVA_HOME="" >JAVACFLAGS="" COMPILER="" >and of course, the output of emerge --info =fuubar-2.3.1 > * The complete build log is located at '/var/tmp/portage/dev-ruby/fuubar-2.3.1/temp/build.log'. > * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/fuubar-2.3.1/temp/environment'. > * Working directory: '/var/tmp/portage/dev-ruby/fuubar-2.3.1/work/ruby22/fuubar-2.3.1' > * S: '/var/tmp/portage/dev-ruby/fuubar-2.3.1/work/ruby22/fuubar-2.3.1'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 646830
: 518264