| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
GLib 2.62+ outputs TAP by default, which breaks the tap-gtester
script's expectations. In older GLib versions since 2.38, --tap is an
opt-in to the TAP output mode, so use that.
This is essentially the same issue as
https://github.com/cockpit-project/cockpit/pull/11998 (cockpit was the
source of the tap-gtester script), GNOME/gcr!19, and GNOME/libsecret!5.
Signed-off-by: Simon McVittie <smcv@debian.org>
Bug-Debian: https://bugs.debian.org/940157
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces tap-driver and tap-gtester with fresh versions from Cockpit.
https://github.com/cockpit-project/cockpit/pull/9500
https://wiki.gnome.org/Initiatives/GnomeGoals/Python3Porting
Also returned the following commits that are not included in Cockpit:
* 918ab836fd23f9b2c0bf655c7f4f575bffff3189
* 7e75a62e846551c19b9c875f7b237a07ee3b93e1
* 7120f44ceedd5c10802781d64a5829b3c6d8e13f
Maybe they should be upstreamed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In pam/test-pam.c, the skip_test function either prints the status
itself, or relies on g_test_skip (depending on GLib version).
The tap-gtester script should handle both cases, not only the first
one.
https://bugzilla.gnome.org/show_bug.cgi?id=755873
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=726909
|
|
|
|
|
|
|
| |
This allows tests to detect whether they're running under a harness
or not.
In addition handle the way GTests skips better.
|
|
|
|
|
| |
Also build in a 'make check-memory' and related functionality
which drives valgrind.
|
|
Coverage also goes to build/coverage instead of testing/
|