Source: ruby-awesome-print Version: 1.8.0-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi, During a rebuild of all packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on amd64. I'm marking this bug as severity:serious since your package has only Architecture:all binary packages, and should thus, in theory, build everywhere. Failure to build on ppc64el might indicate a serious issue in this package or in another package. But feel free to downgrade or close if you believe that this is only a build-time issue. (I would personnally prefer a severity:minor bug just to track that the package can only be built on specific architectures.) Relevant part (hopefully): > [31mFailure/Error: expect(my.ai(plain: true)).to eq("#{my.inspect}\n" > << `ls -alF #{my.path}`.chop)[0m > [31m[0m > [31m expected: "#<My:/tmp>\ntotal 298732\ndrwxrwxrwt 199 root root > 57344 Dec 8 23:45 ./\ndrwxr-xr-x 22 roo...11 Dec 8 23:17 > trim.bam\n-rw-r--r-- 1 root root 299675753 Dec 8 14:21 > unstable-amd64.tar.gz"[0m > [31m got: "#<My:/tmp>\ntotal 298732\ndrwxrwxrwt 199 root root > 57344 Dec 8 23:45 ./\ndrwxr-xr-x 22 roo...11 Dec 8 23:17 > trim.bam\n-rw-r--r-- 1 root root 299675753 Dec 8 14:21 > unstable-amd64.tar.gz"[0m > [31m[0m > [31m (compared using ==)[0m > [31m[0m > [31m Diff:[0m[0m > [31m [0m[34m@@ -51,7 +51,7 @@[0m > [31m [0m[0m -rw------- 1 root root 214 Dec 8 23:44 > ruby-awesome-print20201209-29209-enj8dp[0m > [31m [0m[0m -rw-r--r-- 1 root root 85106 Dec 8 23:45 > ruby-awesome-print_1.8.0-2_unstable.log[0m > [31m [0m[0m -rw------- 1 root root 216 Dec 8 23:44 > ruby-sys-filesystem20201209-29209-1ce3gos[0m > [31m [0m[31m--rw-r--r-- 1 root root 31668 Dec 8 23:45 > ruby-sys-filesystem_1.1.7-2_unstable.log[0m > [31m [0m[32m+-rw-r--r-- 1 root root 31474 Dec 8 23:45 > ruby-sys-filesystem_1.1.7-2_unstable.log[0m > [31m [0m[0m drwx------ 2 user42 user42 4096 Dec 8 22:02 > runtime-user42/[0m > [31m [0m[0m -rw-r--r-- 1 user42 user42 12288 Dec 8 23:14 > sdk_fcp.sqlite[0m > [31m [0m[0m -rw-r--r-- 1 user42 user42 16384 Dec 8 23:14 > sdk_guest.sqlite[0m > [31m [0m[0m > [36m# ./spec/formats_spec.rb:705:in `block (3 levels) in <top > (required)>'[0m > > Finished in 0.41087 seconds (files took 0.58209 seconds to load) > [31m202 examples, 1 failure, 55 pending[0m > > Failed examples: > > [31mrspec ./spec/formats_spec.rb:700[0m [36m# AwesomePrint Inherited from > standard Ruby classes inherited from Dir should be displayed as Dir[0m > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb failed > ERROR: Test "ruby2.7" failed: Apparently the test suite looks at the content of /tmp, and fails if it changes while the test suite is running. The full build log is available from: http://qa-logs.debian.net/2020/12/09/ruby-awesome-print_1.8.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on a Power8 cluster part of the Grid'5000 testbed. Hardware specs: https://www.grid5000.fr/w/Grenoble:Hardware#drac