comedilib/testing
Frank Mori Hess 8fdb92784a patch from Ian Abbott <abbotti@mev.co.uk>:
I was running "comedi_test -v" on my new analog output driver and
noticed that it was getting stuck in a loop during the
"cmd_write_fast_1_chan" test.

It turned out that the test had written more data to the buffer than was
required to complete the acquisition (it was using cmd->stop_src =
TRIG_COUNT) and then got stuck in a loop waiting for the buffer to empty.

The attached patch stops the test_cmd_write_fast_1chan function writing
more data than is required to complete the acquisition.
2005-02-27 22:45:14 +00:00
..
results new files 2003-11-20 18:40:30 +00:00
bufconfig.c additional tests, fixes, move some functions to ../lib 2001-05-28 02:39:00 +00:00
cmd_1.c patch from Ian Abbott <abbotti@mev.co.uk>: 2005-02-27 22:45:14 +00:00
cmd_2.c Disabled streaming output on many of the command tests 2002-02-06 22:08:50 +00:00
cmd_3.c Change prototype of comedi_get_cmd_generic_timed 2001-07-15 22:39:54 +00:00
comedi_test.h fix internal trigger when testing write command, and fix test when 2004-07-24 16:09:01 +00:00
info.c add "serial" to subdevice_types 2004-08-14 20:33:46 +00:00
insn_read.c test reading 0 samples 2002-06-06 00:38:54 +00:00
insn_read_time.c additional tests, fixes, move some functions to ../lib 2001-05-28 02:39:00 +00:00
inttrig.c Disabled streaming output on many of the command tests 2002-02-06 22:08:50 +00:00
lib.c staging area for moving functions from here to ../lib 2001-05-28 02:38:09 +00:00
main.c fixing includes for exit(), memset() for gcc 2.96 compiler warnings 2003-01-01 23:07:02 +00:00
Makefile.am need headers 2003-05-02 07:53:02 +00:00
mmap.c fix test_segfault() so it works with 2.6 kernel signal handling behaviour 2004-07-24 15:47:30 +00:00
mode0_read.c fix for compiler warning about strict aliasing rules 2004-06-19 19:55:26 +00:00
README testing additions 2000-11-30 22:57:04 +00:00
select.c Disabled streaming output on many of the command tests 2002-02-06 22:08:50 +00:00

The results directory contains last-known testing results that have
been contributed by users.  If your board is listed there,
please compare it the output of comedi_test and if it differs
significantly, send me a copy and/or diff.  I'll either update
the file, or it indicates that there is a bug.  If your board
is not listed here, send me a copy of the output so it can
be included.

comedi_test tends to create a lot of output.  The important
information has lines beginning with either I:, W:, or E:,
indicating information, warning, or error, respectively.
You can grep for this information using the regexp '^.:'.
Errors are usually problems that need to be fixed, but are
not necessarily significant bugs.  Warnings need to be
audited by ds to know whether or not they are significant,
since comedi_test isn't very smart about some checks.  (That's
why they're warnings and not errors.)