Hello,
(I'm the maintainer for upstream meli)
On Sun, 22 Dec 2024 11:29, Lucas Nussbaum <lu...@debian.org> wrote:
>Source: meli
>Version: 0.8.10+dfsg-1
>Severity: serious
I'm not familiar with the semantics here, is the Severity "serious"
because it failed the entire build?
Technically speaking this is a failure in the text fixture from
dependency "rusty-fork" used only when compiling tests. So it's not
originating from meli.
Was this failure reproducible in subsequent build jobs? If not, could we
repeat the build to make sure it was not some temporary flakiness in the
build runner machine?
In the case where it's reproducible, the test can be disabled with a
quilt patch. In any case, it's not really a bug in the package itself,
but in the test dependency.
Thanks,
Manos
>Justification: FTBFS
>Tags: trixie sid ftbfs
>User: lu...@debian.org
>Usertags: ftbfs-20241222 ftbfs-trixie
>
>Hi,
>
>During a rebuild of all packages in sid, your package failed to build
>on amd64.
>
>
>Relevant part (hopefully):
>> running 1 test
>> test test_cli_subcommands ... FAILED
>>
>> failures:
>>
>> ---- test_cli_subcommands stdout ----
>> thread 'test_cli_subcommands' panicked at
>> /<<PKGBUILDDIR>>/debian/cargo_registry/rusty-fork-0.3.0/src/fork_test.rs:135:9:
>> child exited unsuccessfully with exit status: 70
>> stack backtrace:
>> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
>> backtrace.
>>
>> running 1 test
>> thread 'test_cli_subcommands' panicked at
>> /usr/src/rustc-1.83.0/library/core/src/ops/function.rs:250:5:
>> Unexpected return code, failed var == 0
>> └── var: 101
>>
>> code=101
>> stdout=""
>> stderr=```
>> thread \'main\' panicked at melib/src/utils/logging.rs:190:37:
>> Could not create log file in XDG_DATA_DIR: Os { code: 13, kind:
>> PermissionDenied, message: \"Permission denied\" }
>> stack backtrace:
>> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
>> backtrace.
>> ```
>>
>>
>> stack backtrace:
>> note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
>> backtrace.
>>
>>
>> failures:
>> test_cli_subcommands
>>
>> test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered
>> out; finished in 0.85s
>>
>> error: test failed, to rerun pass `-p meli --test test_cli_subcommands`
>> dh_auto_test: error: /usr/share/dh-rust/bin/cargo test returned exit code 101
>
>
>The full build log is available from:
>http://qa-logs.debian.net/2024/12/22/meli_0.8.10+dfsg-1_unstable.log
>
>All bugs filed during this archive rebuild are listed at:
>https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241222;users=lu...@debian.org
>or:
>https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241222&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
>
>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 mark 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 mine
>so that we can identify if something relevant changed in the meantime.
>
