Summary: | webkitgtk-1.2.1: testwebresource.c failed | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Pacho Ramos <pachoramos1> | ||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED INVALID | ||||||
Severity: | Normal | CC: | gnome, gustavo | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
Attachments: |
|
Description
Pacho Ramos
2010-06-12 14:39:57 PDT
We are running libsoup-2.30.2 I'm unable to reproduce this problem locally with any of my webkit builds. It might be worth noting that most of the developers and the buildbots run debian, and ubuntu. Yes, it works ok when building manually from sources :-/ Sorry for the inconvenience (Also note that tests still need X for running, or they will fail with: make check-am make[1]: Entering directory `/home/pacho/Desktop/webkit-1.2.1' /bin/mkdir -p ./.deps/DerivedSources make check-local make[2]: Entering directory `/home/pacho/Desktop/webkit-1.2.1' gtester --verbose Programs/unittests/testhttpbackend Programs/unittests/testloading Programs/unittests/testglobals Programs/unittests/testmimehandling Programs/unittests/testnetworkrequest Programs/unittests/testnetworkresponse Programs/unittests/testwebframe Programs/unittests/testwebbackforwardlist Programs/unittests/testwebhistoryitem Programs/unittests/testwindow Programs/unittests/testdownload Programs/unittests/testatk Programs/unittests/testhittestresult Programs/unittests/testwebsettings Programs/unittests/testwebresource Programs/unittests/testwebdatasource Programs/unittests/testwebview Programs/unittests/testkeyevents; TEST: Programs/unittests/testhttpbackend... (pid=4050) Gtk-WARNING **: cannot open display: aborting... FAIL: Programs/unittests/testhttpbackend make[2]: *** [test] Terminado make[2]: Leaving directory `/home/pacho/Desktop/webkit-1.2.1' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/home/pacho/Desktop/webkit-1.2.1' make: *** [check] Error 2 ) The original problem was caused by affected test trying to create /root/.recently-used.xbel and not being able to since portage compiles and run tests into a sandbox. We now have workarounded it downstream setting a different XDG_DATA_HOME |