Summary: | media-sound/xmms2-0.9.3-r1 - waf: error: no such option: --notests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Ionen Wolkens <ionen> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.clang.tar.xz etc.portage.tar.xz logs.tar.xz media-sound:xmms2-0.9.3-r1:20240313-021323.log qlist-info.txt.xz temp.tar.xz |
Description
Toralf Förster
2024-03-13 18:38:57 UTC
Created attachment 887521 [details]
emerge-info.txt
Created attachment 887522 [details]
emerge-history.txt
Created attachment 887523 [details]
environment
Created attachment 887524 [details]
etc.clang.tar.xz
Created attachment 887525 [details]
etc.portage.tar.xz
Created attachment 887526 [details]
logs.tar.xz
Created attachment 887527 [details]
media-sound:xmms2-0.9.3-r1:20240313-021323.log
Created attachment 887528 [details]
qlist-info.txt.xz
Created attachment 887529 [details]
temp.tar.xz
No idea what's going on here at a glance, waf is bundled so should be no variance there. Likewise I get the command: "/tmp/portage/media-sound/xmms2-0.9.3-r1/work/xmms2-0.9.3/waf" build --verbose --jobs=8 --notests But it proceeds to build. Then again maybe the arguments bit is a red herring and it's instead because of: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). That's something I don't have locally. Tried a few things, even with the same environment file loaded but cannot reproduce. And looking closer, I also doubt it's related to git. Unfortunately no ideas at the moment. I find it curious that --notests is not listed in that output too. xmms2-0.9.3$ ./waf --help | grep notests fatal: not a git repository (or any of the parent directories): .git --notests Exec no unit tests It's like it failed to find that there's tests and then dropped the options or something? Still no idea how that may have happened though. (In reply to Ionen Wolkens from comment #12) > I find it curious that --notests is not listed in that output too. This is where I got up to but couldn't really see anything interesting in the tests module that would mean it couldn't import it or whatever it does.. toralf, would you mind tarballing the image for us? Given it's waf, I wouldn't be surprised if it managed to hit some weird internal race and parsed options before the test options were added. |