| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
python-dbusmock will also stop importing all session services that are
installed on the host system by default (as is already the case for
system services). With this change, the dconf service cannot be
activated anymore unless we explicitly enable the service in the
environment.
Add the appropriate call to enable the service, guarded by a check that
the method exists to be compatible with older dbusmock versions.
See: https://github.com/martinpitt/python-dbusmock/pull/108
|
|
|
|
|
|
| |
Otherwise there is a race condition that can cause the FD to be closed
twice. Avoid this by signalling EOF through a separate variable and
always closing the FD from the main thread.
|
| |
|
|
|
|
|
|
| |
This can happen if the watched process has terminated already.
Reported-By: Bastien Nocera <hadess@hadess.net>
|
|
|
|
|
| |
Otherwise settings may leak between tests, which can trigger test
failures.
|
|
|
|
|
| |
The file descriptor may have been closed (and set to -1) already, catch
this.
|
|
|
|
|
| |
This also cleans up the startup logic and ensures we wait for the plugin
to be ready after launching it.
|
|
|
|
|
| |
Theoretically this could cause deadlocks when the kernel buffers are not
large enough to read the command output.
|
|
|
|
|
|
| |
Using a pipe without guaranteeing that it is actually read could
potentially get us into really weird deadlock situations. Switch to use
OutputChecker to avoid the issue (and log the notifications).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The default timeout of 60 seconds is rather long. If we run into that,
we don't necessarily get a proper backtrace from python before meson
kills the process. As such, lower the timeout to ease debugging.
|
|
|
|
| |
Just because poll is the more modern API.
|
|
|
|
|
| |
Otherwise the interpreter can apparently deadlock on shutdown trying to
join the still running thread.
|
|
|
|
|
| |
Exit code 77 means that the test has been skipped and will be
interpreted as such by meson.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Traceback (most recent call last):
File "/builds/GNOME/gnome-settings-daemon/plugins/power/test.py", line 760, in test_lid_close_inhibition
self.check_no_lid_uninhibited(gsdpowerconstants.LID_CLOSE_SAFETY_TIMEOUT - 1)
File "/builds/GNOME/gnome-settings-daemon/plugins/power/test.py", line 327, in check_no_lid_uninhibited
self.plugin_log.check_no_line(b'uninhibiting lid close', wait=timeout)
File "/builds/GNOME/gnome-settings-daemon/tests/output_checker.py", line 143, in check_no_line
return self.check_no_line_re(needle_re, wait=wait, failmsg=failmsg)
File "/builds/GNOME/gnome-settings-daemon/tests/output_checker.py", line 133, in check_no_line_re
raise AssertionError('Found needle %s but shouldn\'t have been there (timeout: %0.2f)' % (str(needle_re), timeout))
NameError: name 'timeout' is not defined
|
|
|
|
|
|
| |
This improves readabilty and means that all output is logged to stdout
(almost) immediately instead of splitting it into files which
potentially causes extra confusion.
|
|
|
|
|
|
| |
This improves logging because everything just goes to stdout directly
which means that the logs are properly interleaved. It also avoids the
need for temporary files.
|
|
|
|
|
|
| |
The environment variables were not correctly cleared. Fix this and also
make sure that we don't have the GNOME_SETUP_DISPLAY environment
variable leaking in from the outside.
|
|
|
|
|
| |
Add the SetBrightness method here for login1.Session, till dbusmock
picks it up.
|
|
|
|
|
| |
This appears to possible trigger crashes *outside* of the test
environment.
|
|
|
|
|
|
| |
Port the test suite to python 3.
Fixes #65
|
|
|
|
|
|
|
|
|
| |
Rather than poke through using XTest, use Mutter's new D-Bus API to do
as if the user pressed a key on a keyboard.
See https://bugzilla.gnome.org/show_bug.cgi?id=705942
https://bugzilla.gnome.org/show_bug.cgi?id=794563
|
|
|
|
|
| |
This adds the required glue code to support it for old dbusmock versions
and allows SuspendAndHibernate to be picked by default.
|
|
|
|
| |
Without this we need to install the GSchema files for testing purposes.
|
|
|
|
|
|
|
| |
If the output (or input) is buffered, then the tests might not be able
to read the log entries right away, causing the test to fail.
Explicitly add buffering=0 to open calles where this might be relevant.
|
|
|
|
|
| |
This simplifies the code quite a bit and makes startup much more robust
as -displayfd is now used rather than badly guessing free X displays.
|
| |
|
|
|
|
|
| |
Moving this is important, as gnome-session (or to be exact the
acceleration check) requires the environment variable to be set already.
|
|
|
|
|
| |
The xorg log fd position will be after the written error, so re-open the
log to read, and check for the expected error.
|
|
|
|
|
| |
Instead of having 2 loops looking for a free display number, we now have
a single one, making the code more comprehensible.
|
|
|
|
| |
Copy/paste error in the logs meant we wrote to the wrong location.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786694
|
|
|
|
|
|
| |
There's more than just a power test now.
https://bugzilla.gnome.org/show_bug.cgi?id=786694
|
|
|
|
|
|
|
| |
To avoid the burden of maintaining multiple build systems, this
patch removes autotools support.
https://bugzilla.gnome.org/show_bug.cgi?id=793087
|
|
|
|
|
|
|
|
| |
meson is a build system focused on speed an ease of use, which
helps speeding up the software development. This patch adds meson
support along autotools.
https://bugzilla.gnome.org/show_bug.cgi?id=793087
|
|
|
|
|
|
|
|
|
|
| |
If mutter is built with Wayland support, it will fail to start up under
our mocked logind because it cannot get information about the session:
mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory
See https://gitlab.gnome.org/GNOME/mutter/merge_requests/15
https://bugzilla.gnome.org/show_bug.cgi?id=793189
|
|
|
|
|
|
|
| |
Works-around a possible error on teardown in some circumstances:
rm: cannot remove '/tmp/gsd-power-testeSVBTD/runtime/gvfs': Transport endpoint is not connected
See https://bugzilla.gnome.org/show_bug.cgi?id=793187
|
| |
|
|
|
|
|
|
| |
Set a more restrictive mode than the default to avoid a warning at
runtime:
dbus[28036]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/tmp/gsd-power-testF7oXJo/runtime" can be written by others (mode 040775)
|
|
|
|
|
|
|
|
|
|
| |
When starting the tests dbus would print a warning as the
XDG_RUNTIME_DIR was not yet created. Simply create this directory to
prevent the warning from being printed.
dbus[2514]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/tmp/gsd-power-testjFVT_p/runtime" not available: No such file or directory
https://bugzilla.gnome.org/show_bug.cgi?id=792210
|
|
|
|
| |
Rather than creating our own.
|
|
|
|
|
|
|
| |
It's easier to setup for our purpose, and now supports XRandR since
support got merged in December 2015.
See https://bugs.freedesktop.org/show_bug.cgi?id=26391
|
|
|
|
|
|
|
| |
Don't skip the tests if python-dbusmock is not installed, fail instead.
That would explain why "make distcheck" passed happily in more recent
releases...
|
| |
|