Summary: | kde-base/perlqt-4.7.4 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paweł Hajdan, Jr. (RETIRED) <phajdan.jr> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 241922 | ||
Attachments: |
build.log.gz
Test log with X and DBUS, 20 of 21 failed Test log with X and DBUS, 2 of 21 failed Test log with X and DBUS, kde-4.8.1, 2 of 21 failed |
Description
Paweł Hajdan, Jr. (RETIRED)
![]() * ERROR: kde-base/perlqt-4.7.3 failed (test phase): * Tests failed. When you file a bug, please attach the following file: * /var/tmp/portage/kde-base/perlqt-4.7.3/work/perlqt-4.7.3_build/Testing/Temporary/LastTest.log For the future... You know, I did not just add that to the eclass for fun... the build log is completely useless here. Created attachment 294603 [details]
Test log with X and DBUS, 20 of 21 failed
Tests fail because Perl cannot find the not-yet-installed modules. This should be fixable. Restricted pending further improvement. (In reply to comment #1) > * ERROR: kde-base/perlqt-4.7.3 failed (test phase): > * Tests failed. When you file a bug, please attach the following file: > * > /var/tmp/portage/kde-base/perlqt-4.7.3/work/perlqt-4.7.3_build/Testing/Temporary/LastTest.log > > For the future... You know, I did not just add that to the eclass for fun... > the build log is completely useless here. I know, but: I'm using test-fail-continue (without that and with all test failures FEATURES=test would be unusable), so I just don't have that file. Sorry about that, and then if you can reproduce the failures locally, why have the packages been committed to the tree, and presented as candidates for stabilization? (In reply to comment #4) > Sorry about that, and then if you can reproduce the failures locally, why have > the packages been committed to the tree, and presented as candidates for > stabilization? a) I'm doing nothing different from the previous KDE stabilizations. b) Arch teams used to treat KDE test failures as "ugly but nonblocking", at least I remember one arch team member instructing an AT like that c) If you dont use a dev profile, kde4-base.eclass hard-disables the tests anyway. But let's continue this better somewhere on IRC... Created attachment 295469 [details]
Test log with X and DBUS, 2 of 21 failed
Most tests are fixed now by adding the correct module search path. New test log attached.
Created attachment 307371 [details]
Test log with X and DBUS, kde-4.8.1, 2 of 21 failed
Disabled the two failing tests (both were failing with "tried to modify read-only variable", which seems more like an error in the test). |