summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2010-03-24xts5: Make sure libXR5 preceeds the libraries it depends upon in the link orderJon TURNEY3-6/+6
Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk> Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
2010-03-24xts5: Remove an unneeded $(EXEEXT)Jon TURNEY19-19/+19
tprogs lists the test programs without $(EXEEXT), so substituting the $(EXEEXT) with .c to get BUILD_SOURCES fails to work correctly when $(EXEEXT) isn't empty Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk> Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
2010-03-24xts-run: Handle -o parameter as output base directoryDan Nicholson1-4/+5
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.
2010-03-24xts5: Tweak the default output directoryDan Nicholson4-5/+5
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.
2010-02-21xts5: Really fix silent rules with older automakeDan Nicholson1-1/+2
When using an older automake, the AM_SILENT_RULES macro is not used, but the custom silent rule for mc uses the variable AM_DEFAULT_VERBOSITY. Make sure it's defined even without AM_SILENT_RULES. Tested-by: Pat Kane <pekane52@gmail.com>
2010-02-20xts5: Include summary report in resultsDan Nicholson2-3/+19
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.
2010-02-20xts5: Use package version in xts utilitiesDan Nicholson3-2/+15
Use the package version for reporting the version of xts-run and xts-report.
2010-02-20Add some more information to the READMEDan Nicholson1-10/+35
2010-02-19xts5: Fix mc silent rules like AM_V_GENDan Nicholson1-5/+5
I still can't find the issue, but AM_V_mc_ was causing make to stop on a recursive variable. Now it's basically AM_V_GEN with s/GEN/MC/.
2010-02-18Mention xts-report in the READMEDan Nicholson1-1/+4
2010-02-17xts5: Rename report generator to xts-report and fix some garbageDan Nicholson4-29/+36
xts-report makes a lot more sense than vswrpt since everything else is called xts and you probably couldn't even figure out what vswrpt is. A few fixes along the way: - use DEFAULT_TET_ROOT when $TET_ROOT is not set and use it throughout the code - fix the argv[0] scanner to also accept xts-report - comment out a random form feed (wtf?) and a useless error message - install the docs so xts-report can strip the release data
2010-02-17Add defines for default TET directoriesDan Nicholson2-0/+52
Not used yet, but will be much better than constant getenv("TET_ROOT").
2010-02-17Ignore test result directories named xts-20*Dan Nicholson1-0/+1
Hopefully by the year 2100 XTS will not be necessary...
2010-02-17xts5: Fix comment broken by RCS ID removalDan Nicholson1-0/+1
2010-02-17xts5: Build and install vswrpt report analyzerDan Nicholson6-1/+5
This will be renamed to xts-report, but it has some clever argv[0] matching that prevents it for now. Also fixes a broken comment from an RCS ID removal.
2010-02-17xts5: Set check output directory like xts-runDan Nicholson1-1/+1
2010-02-17xts5: Add some help text to xts-runDan Nicholson1-3/+16
2010-02-17Create a new and relevant READMEDan Nicholson2-0/+22
2010-02-17xts5: Use shared library modules to decrease test program sizeDan Nicholson30-97/+109
Linking the xts libraries statically into each test program results in a massive size for the collection of programs. The libraries have been changed to private libtool modules that default to shared, resulting in a much smaller installed size. One consequence of linking to shared objects is that the linker errors on undefined extern variables. The obsolete and unused startup routines in linkstart.c had one of these, so they have been removed from the build. Next is to create the tet library shared.
2010-02-17xts5: Specify default tcc to use in xts-runDan Nicholson1-1/+1
We want to use the tcc built with xts, so default to setting the full path instead of hoping to find it in $PATH.
2010-02-17xts5: Use XTEST extension for testsDan Nicholson1-1/+1
More tests can be run when using XTEST.
2009-10-14xts5: Drop XP pkg-config checkDan Nicholson4-6/+5
The XP check for protocol tests in configure was grabbing the same packages as the general XTS check. Consolidate them.
2009-10-14xts5: Stop gratuitous use of make variables in common.mkDan Nicholson39-196/+315
The meanings of the variables were confusing or obfuscating. Now it's much clearer which libraries are in use.
2009-10-11xts5: Ignore generated xts-config scriptDan Nicholson1-0/+1
2009-10-10xts5: Add more standard headers to kill implicit declaration warningsDan Nicholson11-18/+29
For some reason, there seems to be an aversion to the standard headers. Mostly this is <string.h>, which unfortunately causes a symbol conflict with index on glibc.
2009-10-10xts-run: No need to pass journal fileDan Nicholson1-1/+1
The journal file will default to $results_dir/journal, which is what we want anyway.
2009-10-10tcc: Print bad errors to stderr, tooDan Nicholson1-1/+2
Having critical errors in the journal is nice, but it's also nice if we can show the to the user at the terminal so they don't wonder what the heck happened.
2009-10-10tet: Allow for executables outside of TET_ROOT by defaultDan Nicholson7-10/+38
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.
2009-10-10xts5: Also install tet_codeDan Nicholson1-1/+1
2009-10-10Use a default TET_ROOT when not in the environmentDan Nicholson6-15/+27
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.
2009-10-10xts5: Install the test fontsDan Nicholson1-1/+2
I'm not sure any of the currently installed tests use the test fonts or not, but tetexec.cfg at least creates a fontpath for them.
2009-10-10xts5: Use xts-run wrapper script for executing testsDan Nicholson4-1/+78
xts-run is a simple wrapper script to generate a tetexec.cfg and run tcc with the appropriate arguments.
2009-10-10xts5: Install xts-config for generating tetexec.cfgDan Nicholson1-0/+1
2009-10-07xts5: Install test data filesDan Nicholson3-0/+9
Many of the tests use data files for verifying pixels in images.
2009-10-07Remove unnecessary fileDan Nicholson1-0/+0
2009-10-07xts5: Use temporary tetexec.cfg in case of failuresDan Nicholson1-1/+1
2009-10-07xts5: Silence tetexec.cfg generationDan Nicholson1-1/+1
2009-10-07Remove DECNET configuration items.Peter Hutterer3-7/+1
Welcome to the wooorld of tomorrow!
2009-10-07xts5: Don't regenerate tetexec.cfg after Makefile updatedDan Nicholson1-4/+2
Before when the display number was set by configure, we wanted to make sure tetexec.cfg was updated with the Makefile. That's not necessary anymore.
2009-10-07Purge XT_DISPLAY config variable, use DISPLAY environment var instead.Peter Hutterer23-96/+69
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>
2009-10-07xts5: Rework in-tree testingDan Nicholson2-846/+16
'make check' was invoking tcc with each test case to get usable results back to automake. Since tcc reporting has now been fixed up, we can just run tcc once with scenario. This is the same way that testing will work when installed.
2009-10-07xts5: Only install tetexec.cfg template fileDan Nicholson1-1/+2
While it would be nice to generate a single tetexec.cfg file for all hosts, some of the details are runtime specific. Part of the test process will have to be generating tetexec.cfg from the template.
2009-10-07xts5: Install test programs to libexec subdirs matching scenariosDan Nicholson19-23/+42
In order to keep the scenarios usable in the source tree and while installed, install the test programs to subdirectories of $(libexecdir) matching the source tree. This gives, for example, /usr/libexec/xts5/Xproto/pAllocColor.
2009-10-07tcc: Print test suite and test case names in reportsDan Nicholson7-30/+62
tcc provides the test suite name (xts5) and test case name (e.g. /Xproto/pAllocColor) to the test program via the environment. The test program uses this information when outputting the results to stdout. TET_TSNAME is a new global variable containing the test suite name provided by tcc. This required a change to the config initialization to only check if the value was an absolute path when necessary. TET_TCNAME is a per-test-exec variable providing the test case name as listed in the scenario file.
2009-09-29xts5: Flatten SHAPE directory moreDan Nicholson13-33/+33
2009-09-29xts5: Flatten XtE directory moreDan Nicholson3-3/+3
2009-09-29xts5: Flatten XtC directory moreDan Nicholson31-87/+87
2009-09-29xts5: Flatten Xt9 directory moreDan Nicholson33-93/+93
2009-09-29xts5: Flatten Xt8 directory moreDan Nicholson8-18/+18
2009-09-29xts5: Flatten Xt7 directory moreDan Nicholson13-33/+33
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-18 12:00:37 +0000