Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 650774 Details for
Bug 733922
dev-ruby/kramdown-parser-gfm-1.1.0: fails test (TestFiles#test_gfm_header_ids_to_html)
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
file_733922.txt (text/plain), 3.51 KB, created by
Sam James
on 2020-07-26 03:16:54 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Sam James
Created:
2020-07-26 03:16:54 UTC
Size:
3.51 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: dev-ruby/kramdown-parser-gfm-1.1.0 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: ruby@gentoo.org >[32;01m * [39;49;00mUSE: arm64 elibc_glibc kernel_linux ruby_targets_ruby25 ruby_targets_ruby26 test userland_GNU >[32;01m * [39;49;00mFEATURES: network-sandbox preserve-libs sandbox test userpriv usersandbox >>>> Unpacking source... > [32;01m*[0m Running unpack phase for all ... > [32;01m*[0m Unpacking .gem file... ... >[A[173C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Uncompressing metadata ... >[A[173C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Unpacking data.tar.gz ... >[A[173C [34;01m[ [32;01mok[34;01m ][0m >>>> Source unpacked in /var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work >>>> Preparing source in /var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work ... > [32;01m*[0m Running prepare phase for all ... > [32;01m*[0m Running prepare phase for all ... > [32;01m*[0m Running source copy phase for ruby25 ... > [32;01m*[0m Running source copy phase for ruby26 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work ... > [32;01m*[0m Running compile phase for all ... >>>> Source compiled. >>>> Test phase: dev-ruby/kramdown-parser-gfm-1.1.0 > [32;01m*[0m Running test phase for ruby25 ... >Run options: --seed 29712 > ># Running: > >.....F...... > >Finished in 0.630977s, 19.0181 runs/s, 19.0181 assertions/s. > > 1) Failure: >TestFiles#test_gfm_header_ids_to_html [/var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work/ruby25/kramdown-parser-gfm-1.1.0/test/test_files.rb:32]: >--- expected >+++ actual >@@ -24,5 +24,5 @@ > > <h3 id=\"with--typographic--symbols\">with â « typographic » ⦠symbols</h3> > >-<h3 id=\"with-m5\">with <script type=\"math/tex\">m=5</script></h3> >+<h3 id=\"with-m5\">with \\(m=5\\)</h3> > " > > >12 runs, 12 assertions, 1 failures, 0 errors, 0 skips > [31;01m*[0m ERROR: dev-ruby/kramdown-parser-gfm-1.1.0::gentoo failed (test phase): > [31;01m*[0m (no error message) > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 125: Called src_test > [31;01m*[0m environment, line 2056: Called ruby-ng_src_test > [31;01m*[0m environment, line 1717: Called _ruby_each_implementation 'each_ruby_test' > [31;01m*[0m environment, line 506: Called _ruby_invoke_environment 'ruby25' 'each_ruby_test' > [31;01m*[0m environment, line 627: Called each_ruby_test > [31;01m*[0m environment, line 814: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m ${RUBY} -Ilib:. -e 'Dir["test/test_*.rb"].each{|f| require f}' || die > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=dev-ruby/kramdown-parser-gfm-1.1.0::gentoo'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-ruby/kramdown-parser-gfm-1.1.0::gentoo'`. > [31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work/ruby25/kramdown-parser-gfm-1.1.0' > [31;01m*[0m S: '/var/tmp/portage/dev-ruby/kramdown-parser-gfm-1.1.0/work/ruby25/kramdown-parser-gfm-1.1.0'
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 733922
: 650774