Summary: | dev-python/matplotlib-1.5.0: qt4agg: no [Check timed out] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-python:matplotlib-1.5.0:20151206-085058.log
emerge-history.txt environment |
Description
Toralf Förster
2015-12-06 09:54:45 UTC
Created attachment 418632 [details]
dev-python:matplotlib-1.5.0:20151206-085058.log
Created attachment 418634 [details]
emerge-history.txt
Created attachment 418636 [details]
environment
Which USE do you have set for dev-python/PyQt4? (In reply to Justin Lecher from comment #4) > Which USE do you have set for dev-python/PyQt4? that package is not installed. Your history says Sun Dec 6 00:27:10 2015 >>> dev-python/PyQt4-4.11.4 If it is not installed you somehow didn't fulfill the DEPEND. Ough, I#m stupid, forget comment #5(In reply to Justin Lecher from comment #4) > Which USE do you have set for dev-python/PyQt4? ough - forget comment #5 (I had 2 images with same name but just within the minutes a difference) - here you go : ================================================================= Package Settings ================================================================= dev-python/PyQt4-4.11.4::gentoo was built with the following: USE="X dbus declarative designer kde opengl phonon script sql svg webkit -debug -doc -examples -help -multimedia -scripttools -testlib -xmlpatterns" ABI_X86="64" PYTHON_TARGETS="python2_7 python3_4 -python3_3 -python3_5" Are you test enviroments slow or have high load? The check times out after 10 sec. Could load be the reason for that? (In reply to Justin Lecher from comment #8) > Are you test enviroments slow or have high load? The check times out after > 10 sec. Could load be the reason for that? Pffr, it emerges fine today 2x in a row - but I cannot understood what happened in the first run. From the sysstat values it seems that the chroot image itself hang about 20 min around that time. No other image was affected nor anything interesting in the log files. Nevertheless, sry for bothering you - the issue is definitely not package related. *** Bug 569296 has been marked as a duplicate of this bug. *** |