qtcreator displays an error when accessing help, unless we have
installed documentation. That seems like a packaging bug to me and is
definitely unfriendly (default) behaviour.
This change increases the closure size from 56 MiB to 68 MiB.
I had to update all the pyside programs, or freecad failed to build. I picked
the versions advertised in http://qt-project.org/wiki/PySideDownloads . The
rest I took for github latest releases.
Unfortunately, running them in parallel sometimes lead to tests not even
starting up. Probably lock contention is the issue here, but haven't
investigated further so I'm deactivating parallel testing.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
The reason I went through this whole journey of gathering dependencies
and debugging just in order to get i3 tests working was because I wanted
to supply test cases to a small patch I wrote for the upstream project.
This adds/updates quite a few Perl packages and a X dummy helper, which
are all needed in order to successfully run the test suite.
The exit code of the i3 test runner is always 0, regardless of whether
tests were failing or not, so let's quickly grep for a "not ok" in the
test logfile and if it occurs, the whole build is failing now.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Finally, after going through the journey of debugging and gathering
dependencies, we now have tests for i3, hooray!
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is actually a small script which just starts an X server without
any real display. Right now only needed for running the test suite of
the i3 window manager within the Nix chroot, but might be useful for
running other tests needing a DISPLAY.
Usage is just like a regular X server, so in order to start an instance
for display :666, you just run it like this:
xdummy :666
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This is actually needed by X11-XCB, but I only found out after hours of
digging through Perl code from the stone age.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This has been proven to be VERY handy for providing useful stacktraces
in Perl. Just invoke it using:
perl -MCarp::Always yourshinyscript.pl
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
