| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The perl mongers have retroactively marked this construct
"experimental", five and a half years after it was marked stable.
http://perldoc.perl.org/perl5180delta.html#The-smartmatch-family-of-features-are-now-experimental
Acked-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Peter Harris <pharris@opentext.com>
|
|
xdpyinfo reports NO, WHEN MAPPED or YES, but XT_DOES_BACKING_STORE
expects a 0, 1, or 2.
Signed-off-by: Peter Harris <pharris@opentext.com>
|
|
Xlib3/XOpenDisplay may segfault if XT_DISPLAY is set and XT_DISPLAYHOST
is not.
Signed-off-by: Peter Harris <pharris@opentext.com>
Tested-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
XT_FONTPATH has to be a valid font path.
Also trim at least one remote path from XT_FONTPATH_GOOD, so it
isn't the same as XT_FONTPATH.
Signed-off-by: Peter Harris <pharris@opentext.com>
|
|
In Perl before 5.14, the following syntax was happily accepted:
foreach my $foo qw(bar baz)
but that's been deprecated and that now generates a warning:
Use of qw(...) as parentheses is deprecated at ./xts5/bin/xts-config line 118.
The correct form has always been:
foreach my $foo (qw(bar baz))
and that's compatible with older Perl releases, so let's use that.
Reference:
http://perldoc.perl.org/perl5140delta.html
Signed-off-by: Cyril Brulebois <kibi@debian.org>
Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
When determining whether the connection is local and you can connect to the
server via TCP, don't try to parse out ":n.m" and then reconstruct it as
"hostname:n.m", because ":n" is a valid display name. Instead, check for the
optional ".m" part and if it matches, just tack the complete $DISPLAY value
(including the leading colon) onto the hostname.
Fixes XOpenDisplay-10 when $DISPLAY is missing the optional screen number part.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
This fixes tests such as XCreateGlyphCursor that fail with UNRESOLVED when run
while the test suite is not installed because the tests pass "../xts5/fonts" as
a font path to the server, which fails because the server doesn't look in the
same directory.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
Allows moving the location of the results directory without having to
recreate the dated subdirectory. For example, "xts-run -o ~/xts-results"
will give you results in ~/xts-results/$date and subsequent runs will
not conflict.
|
|
Collect all the results under one directory instead of cluttering the
current directory. Also, add the seconds to the date in the directory
name to reduce the chance of conflict.
|
|
Give users a quick summary of the test results with the xts-report
"no details" mode. This will appear next to the journal as summary.
|
|
Use the package version for reporting the version of xts-run and
xts-report.
|
|
|
|
We want to use the tcc built with xts, so default to setting the full
path instead of hoping to find it in $PATH.
|
|
The journal file will default to $results_dir/journal, which is what we
want anyway.
|
|
tet is really built around the notion that all the source, programs, data
and output will all live in a single tree. However, often times the test
programs are built and/or installed in a separate location. This can be
worked around with various environment variables or command line options,
but it would be better to build this behavior in by default.
This introduces TET_EXEC_ROOT, which specifies the base directory for tet
test programs. The tests will be found in the test suite subdirectory of
TET_EXEC_ROOT. E.g., $TET_EXEC_ROOT/xts. The default here is to have
TET_ROOT=$datadir and TET_EXEC_ROOT=$libexecdir.
|
|
Requiring an environment variable to be set in order to get any behavior
is an obnoxious trait. Instead, a sane default TET_ROOT is built into
the programs that use it. Users such as "make check" that need more
control can continue using the environment variable.
The scripts are now substituted from make so that we get full variable
resolution.
|
|
xts-run is a simple wrapper script to generate a tetexec.cfg and run tcc
with the appropriate arguments.
|
|
Welcome to the wooorld of tomorrow!
|
|
Let's use DISPLAY like every other sane X application does, not through a
variable set at configure time.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
|
|
The tset directory was mostly useless and causes extra baggage if the
scenario files are going to be used on an installed package. The test
directories are now flattened into xts5.
|
|
Ensure that the user has xset and xdpyinfo and that xts-config uses
those tools. Additionally, move the generation of tetexec.cfg to the
Makefile to handle all the environment variables and prerequisites.
|
|
It's pretty likely the user doesn't have TCP connections allowed, so
suppress xset errors when checking.
|
|
when xts-config is run instead.
|
|
|
|
|
|
'wbuild clean'. tetclean.cfg will soon get the axe as well.
|
|
|
|
cvsignore output from make build.
|
|
|
|
|
