Summary: | media-libs/lilv-0.24.10 fails tests: ImportError: Failed to import test module: test_api | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Professional Audio Applications Maintainers <proaudio> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | alexey+gentoo, kripton |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 logs.tbz2 media-libs:lilv-0.24.10:20201110-234956.log temp.tbz2 |
Description
Toralf Förster
![]() Created attachment 670858 [details]
emerge-info.txt
Created attachment 670861 [details]
emerge-history.txt
Created attachment 670864 [details]
environment
Created attachment 670867 [details]
etc.portage.tbz2
Created attachment 670870 [details]
logs.tbz2
Created attachment 670873 [details]
media-libs:lilv-0.24.10:20201110-234956.log
Created attachment 670876 [details]
temp.tbz2
Update summary. [something] is used when something refers to an overlay Hey there, I stumbled upon this rather peculiar issue with media-libs/lilv-0.24.10, and it's got me scratching my head a bit. It seems like you're facing an ImportError when trying to run the test module 'test_api.' That's never a good sign, right? Now, diving into the technical details, it's intriguing to see that you're working with an unstable amd64 chroot image, which can sometimes be a bit finicky. The gcc-config and clang versions look pretty standard, so I don't suspect any major issues there. To address this ImportError, I'd suggest checking your Python environment. I usually do it with this: https://andersenlab.com/services/quality-assurance-services. Given the list of available Python interpreters, it might be a good idea to ensure that you have all the necessary dependencies installed for your Python version. Also, double-check if you've set up the proper environment variables and paths. As for my experience, I've encountered similar import issues in the past, and often, they've been resolved by fine-tuning the Python environment. |