Age | Commit message (Collapse) | Author | Files | Lines |
|
XSetModfierMapping reports FAIL due to a different ordering of the modifiers
in the return value.
The server keeps the modifiers in a different format than used by the core
protocol. The modifier map returned by XGetModifierMapping(3) always has the
keycodes in ascending order for each modifier.
A straight input_map[i] == output_map[i] comparison is not enough if the
input map is not in order. Instead, all values for each modifier need to be
compared to find the right modifier.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Force them to be int, return 0 where necessary.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
../../../../xts5/src/libproto/DfltVals.c: In function ‘Gen_Good_Event’:
../../../../xts5/src/libproto/DfltVals.c:395: warning: control reaches end of non-void function
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
../../../../xts5/src/libproto/DfltVals.c:391: warning: return type defaults
to ‘int’
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
../../../../xts5/src/lib/nextvinf.c: In function ‘resetvinf’:
../../../../xts5/src/lib/nextvinf.c:162: warning: suggest parentheses around
comparison in operand of ‘&’
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
xts5/bin/ may not exist when we're trying to put xts-config into it. Create
it.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
fixes
../../../../src/tet3/tcm/tcmfuncs.c: In function ‘tet_tcminit’:
../../../../src/tet3/tcm/tcmfuncs.c:137: warning: unused variable ‘envmsg’
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
tpstartup() is called by all library tests (I think). If ScreenCount for the
current display is less than 2, reset alt_screens - we have to skip the
multi-display tests then.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
sed -e "s|wbcopy[ ]*(\(.*\),[ ]*\(.*\),[ ]*\(.*\))|memcpy(\2, \1, \3)|"
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
It's not assigned to anything anywhere, so just stop the cast. Fixes
warnings like:
pPolyArc.c:131: warning: cast from pointer to integer of different size
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
sed -e "s/\([ ]\)(void) \(.*\)/\1\2/"
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
The pBell-2 test sets the test type to BAD_LENGTH, which attempts to
create a request with a size that is too small by one long (4 bytes).
However, it tries to do this with an xBellReq, which is exactly 4
bytes in size. This results in a request with a length field of 0,
which triggers the big request handling in the X server. This makes
the server interpret the next request as the size part of the Bell
request, and hilarity ensues.
Instead, detect this case and bail out with an UNTESTED result.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Acked-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
The 'distclean' target deletes all of the .c files that were generated
during the dist step. Since the .m files are not shipped in the
tarball, it becomes impossible to rebuild after that.
Fix this by shipping the .m files in the tarball along with the .mc
helper libraries that mc needs to rebuild the .c files.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
We distribute the generated .c files, so we shouldn't clean them when
the user runs "make clean". They should be cleaned as part of the
"distclean" target.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
These four directories are not included in their respective SUBDIRS,
which means they aren't built and aren't included in the distribution
tarball. configure.ac still tries to generate their Makefiles,
though, which causes configure failures when run from the dist
tarball:
config.status: error: cannot find input file: `src/tet3/inetlib/Makefile.in'
config.status: error: cannot find input file: `src/tet3/servlib/Makefile.in'
config.status: error: cannot find input file: `xts5/src/libXtaw/Makefile.in'
config.status: error: cannot find input file: `xts5/src/libXtmu/Makefile.in'
Fix this by just deleting those line. The corresponding Makefiles
aren't used.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
mc is used to compile the .m files into .c files at dist time. If
dist is run from a clean build directory, mc is not built and the dist
fails in xts5/Xproto when it tries to run it.
Add a dependency on mc for dist-hook to make sure that mc is built
before the tests.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
* 'master' of git://anongit.freedesktop.org/git/xorg/test/xts:
Clean xts-config, xts-run, and tetexec.cfg
Delete the Xt scenarios from 'all'
Include libxts5.la in Xproto and XIproto's LDADD lines
Build mc using the build architecture compiler
Reviewed-by: Joe Kain <jkain@nvidia.com>
Reviewed-by: Adam Cheney <acheney@nvidia.com>
|
|
xts-run, in particular, has $bindir baked into it. If it's not
cleaned, then a build with srcdir == destdir, followed by a distclean,
followed by a build with srcdir != destdir will pick up the
previously-generated xts-run with the wrong bindir in it.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Joe Kain <jkain@nvidia.com>
|
|
The Xt tests currently aren't built, so including them in the 'all'
scenario causes a lot of failures.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Adam Cheney <acheney@nvidia.com>
|
|
Normally, the linker picks up libxts5.so from libxts5proto.so's RPATH.
However, apparently cross-compilers don't do that, and the linker
complains about not being able to find it. To work around that,
specify it manually on the libtool command line.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Adam Cheney <acheney@nvidia.com>
|
|
When cross-compiling, we need to use the build compiler instead of the
host compiler because mc is run during the build step to generate .c
files from .m files.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Joe Kain <jkain@nvidia.com>
|
|
xts-run, in particular, has $bindir baked into it. If it's not
cleaned, then a build with srcdir == destdir, followed by a distclean,
followed by a build with srcdir != destdir will pick up the
previously-generated xts-run with the wrong bindir in it.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
The Xt tests currently aren't built, so including them in the 'all'
scenario causes a lot of failures.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
Normally, the linker picks up libxts5.so from libxts5proto.so's RPATH.
However, apparently cross-compilers don't do that, and the linker
complains about not being able to find it. To work around that,
specify it manually on the libtool command line.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
When cross-compiling, we need to use the build compiler instead of the
host compiler because mc is run during the build step to generate .c
files from .m files.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
* master:
xts-config.in: ":n" is a valid display name
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
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>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
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>
|
|
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
TET_EXIT_SKIP is considered higher priority than TET_EXIT_SUCCESS in tcc, but
only TET_EXIT_FAILURE really counts as a failure return code. _SKIP just means
that some of the assertions couldn't be reliably tested.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
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>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
TET_EXIT_SKIP is considered higher priority than TET_EXIT_SUCCESS in tcc, but
only TET_EXIT_FAILURE really counts as a failure return code. _SKIP just means
that some of the assertions couldn't be reliably tested.
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>
|
|
Ensure $(builddir)/bin directory exists before trying to create xts-run/xts-config scripts in it
Run xts-config from $(builddir) to create tetexec.cfg
Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
links successfully for linkers which work -as-needed
Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
"It is not be necessary".
I did notice that some of the tests, such as XCreateGlyphCursor, fail with
UNRESOLVED because XT_FONTPATH is "../xts5/fonts" so the server can't find the
font files. I still need to figure out why that's happening. The test runs
fine if the suite is installed, or if I modify tetexec.cfg to contain the
absolute path to the fonts.
Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Dan Nicholson <dbn.lists@gmail.com>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Dan Nicholson <dbn.lists@gmail.com>
|