Summary: | media-gfx/gimp-2.99.6 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paolo Pedroni <paolo.pedroni> |
Component: | Current packages | Assignee: | Sergey Torokhov <torokhov-s-a> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jstein, proxy-maint |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gimp-2.99.6:20210518-084752.log.gz
test-suite.log |
Description
Paolo Pedroni
2021-05-18 09:20:42 UTC
Created attachment 709638 [details]
test-suite.log
As I imagined, if I first emerge gimp-2.99.6 with FEATURES=-test, and then, again, with FEATURES=test, tests succeed. Could you please check if this issue is reproduced foryou with distcc being disabled? FEATURES="-distcc". Some of failed tests require virtual display and could failed due to long delay. But currently I more confuced by "Skipping unknown file" warnings. (In reply to Sergey Torokhov from comment #3) > Could you please check if this issue is reproduced foryou with distcc being > disabled? FEATURES="-distcc". Same exact thing happens on another machine without distcc. Same thing with 2.99.10... (In reply to Paolo Pedroni from comment #5) > Same thing with 2.99.10... Soryy, I only now see the > /usr/lib64/gimp/2.99/extensions/org.gimp.extension.goat-exercises/goat-exercise-vala: symbol lookup error: /usr/lib64/libgimp-3.0.so.0: undefined symbol: gimp_int16_array_get_type Bail out! LibGimpBase-FATAL-WARNING: /var/tmp/portage/media-gfx/gimp-2.99.6/work/gimp-2.99.6/app/tests/.libs/test-core: gimp_wire_read(): error and > CFLAGS="... -frecord-gcc-switches ... -flto=6" The `/usr/lib64/libgimp-3.0.so.0: undefined symbol: gimp_int16_array_get_type` could be related to LTO optimization. I should try compile gimp on my PC with this falgs to reproduce. But this looks like too high level optiomisation. And I need to learn about `record-gcc-switches` flag. The gimp-2.99.12 uses meson build system now, but I think the issue is reproduced there too. *** This bug has been marked as a duplicate of bug 867856 *** |