Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 937992 - dev-util/maturin-1.7.0 fails tests
Summary: dev-util/maturin-1.7.0 fails tests
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Ionen Wolkens
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-15 22:04 UTC by Jonathan Lovelace
Modified: 2024-08-16 00:05 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
dev-util:maturin-1.7.0:20240815-202111.log (dev-util:maturin-1.7.0:20240815-202111.log,696.71 KB, text/plain; charset=utf-8)
2024-08-15 22:04 UTC, Jonathan Lovelace
Details
emerge-info.txt (emerge-info.txt,8.68 KB, text/plain; charset=utf-8)
2024-08-15 22:05 UTC, Jonathan Lovelace
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Lovelace 2024-08-15 22:04:12 UTC
=dev-util/maturin-1.7.0 fails its tests on this machine, specifically the following tests: tests/cmd/build.toml, tests/cmd/develop.toml, and tests/cmd/publish.toml in cli_tests. In each case, as far as I can see from the build log, the "expected" TOML file has lines with "[env: CARGO_BUILD_TARGET=]", while the "actual" TOML file has lines with "[env: CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu]".
Comment 1 Jonathan Lovelace 2024-08-15 22:04:59 UTC
Created attachment 900234 [details]
dev-util:maturin-1.7.0:20240815-202111.log
Comment 2 Jonathan Lovelace 2024-08-15 22:05:35 UTC
Created attachment 900235 [details]
emerge-info.txt
Comment 3 Ionen Wolkens gentoo-dev 2024-08-15 23:38:01 UTC
Haven't tried, but most likely due to the cargo.eclass changes which set CARGO_BUILD_TARGET

  93      -           [env: CARGO_BUILD_TARGET=]
       93 +           [env: CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu]

It's just a picky test that expect the cli output to never change by diff'ing it. Caused problems in the past given it expect COLUMNS=100 too.

I'd like to set the variable to blank again only during tests, but can't given this would likely change the target dir and force a rebuild. Given it's not a very interesting test for us and could easily fail for other small reasons, may just be time to skip it.
Comment 4 Larry the Git Cow gentoo-dev 2024-08-16 00:05:08 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4b95aca7d5f0a0b19b3f18cc92bbb813a58ab795

commit 4b95aca7d5f0a0b19b3f18cc92bbb813a58ab795
Author:     Ionen Wolkens <ionen@gentoo.org>
AuthorDate: 2024-08-15 23:45:11 +0000
Commit:     Ionen Wolkens <ionen@gentoo.org>
CommitDate: 2024-08-16 00:04:36 +0000

    dev-util/maturin: skip test broken by cargo.eclass changes
    
    Bug: https://bugs.gentoo.org/936968
    Closes: https://bugs.gentoo.org/937992
    Signed-off-by: Ionen Wolkens <ionen@gentoo.org>

 dev-util/maturin/maturin-1.6.0.ebuild | 3 ++-
 dev-util/maturin/maturin-1.7.0.ebuild | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)