Source: ruby-stackprof Version: 0.2.26-1 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org
Dear ruby-stackprof Maintainer, The package ruby-stackprof build failed on arch riscv64. The crucial buildd log below: ``` Finished in 1.580198s, 19.6178 runs/s, 88.5965 assertions/s. 1) Failure: StackProfTest#test_gc [/<<PKGBUILDDIR>>/test/test_stackprof.rb:252]: Expected |2551 - 2546| (5) to be <= 2. 31 runs, 140 assertions, 1 failures, 0 errors, 0 skips rake aborted! Command failed with status (1): [ruby -w -I"test" /usr/share/rubygems-integration/all/gems/rake-13.2.1/lib/rake/rake_test_loader.rb "test/test_middleware.rb" "test/test_report.rb" "test/test_stackprof.rb" "test/test_truffleruby.rb" -v] /usr/share/rubygems-integration/all/gems/rake-13.2.1/exe/rake:27:in `<top (required)>' Tasks: TOP => default (See full trace by running task with --trace) ERROR: Test "ruby3.1" failed. Exiting. dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-stackprof returned exit code 1 make: *** [debian/rules:7: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 -------------------------------------------------------------------------------- Build finished at 2024-08-09T12:35:03Z Finished ``` The full buildd log is here: https://buildd.debian.org/status/fetch.php?pkg=ruby-stackprof&arch=riscv64&ver=0.2.26-1&stamp=1723206910&raw=0 My solution to this issue: Judging from the logs, test failures during the build process caused the build to fail. Specifically, the StackProfTest#test_gc test failed at /<<PKGBUILDDIR>>/test/test_stackprof.rb:252. The test expected that the result of |2551 - 2546| (i.e. 5) should be less than or equal to 2, but the actual value was outside this range.I don't think this test works on RISC-V，I hope to skip this test on riscv64.After I skip this test, the package build successfully on my machine.Please let me know wheather this solution can be accepted.The patch is in the attachment. Gui-Yue Best Regards
skip_failed_test.patch
Description: Binary data
