Hello.Yes I tried to fix the tests -- the tests output separate kyua test output which the buildd doesn't output. I had to create an emulated VM to compile it manually in to send upstream, and the debug output is apparently not enough for upstream to figure out reasons for the test failures. I'm not familiar with the atf-sh and/or kyua test methods, this is my first experience with them. These aren't autopkgtests. In terms of "fixing the tests", I'm stuck.
I'm attaching the kyua build files that I could find that I sent upstream. Upstream said that kyua should output an .html report, but I did not find any HTML files in the environment where I did the build. I asked upstream if there was a way of manually running kyua to create the HTML report, and I also searched the web but did not find an answer and did not receive a reply.
I'm doing what I can do. :-/ -- Chris Chris Knadle chris.kna...@coredump.us On 5/20/25 13:21, Paul Gevers wrote:
Control: tags -1 moreinfo On 20-05-2025 17:57, Chris Knadle wrote:Please unblock package mlmmjThe package can't migrate as it is right now, so there's nothing to unblock now.MLMMJ 1.5.0 fails to build on a number of architectures due to certain post-compile tests timing out. I have added a workaround to the debian/ rules file to avoid the build tests for the architectures where the build tests fail, to allow the build to succeed and continuing to the the build tests for the architectures where the build tests work.Have you even tried fixing the tests?In the proposed upload I have also included fixes to the debian/ copyright file to fix Lintian errors.You don't need our (pre) approval, as your package isn't blocked yet by the freeze (it's only blocked by the missing binaries). Having said that, aren't you afraid that the autopkgtest will fail in the same way?Paul
kyua-mlmmj-1.5.0-arm64.tar.xz
Description: application/xz
