wow2006 / cudpp

Automatically exported from code.google.com/p/cudpp
Other
0 stars 0 forks source link

Rand tests need to have a more standard output that says passed/failed #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run random tests
2. Look at output

What is the expected output? What do you see instead?

I see:

128 
number of elements: 128, devOutputSize: 32
number of blocks: 1 blocksize: 32 devOutputsize = 32
number of threads: 32

What I want to see is something more like:
Generating 128 random numbers (1 block, 32 threads) ...
GPU test FAILED (x/y correct)

or something like that. (Look at the other ones.)

Also make sure the -q (quiet) option works, as Mark has previously described.

Original issue reported on code.google.com by jow...@gmail.com on 17 Jun 2009 at 1:53

GoogleCodeExporter commented 9 years ago
Please use "-quiet", not "-q", for consistency.  Setting priority to high since 
this
should be fixed for the milestone.

Original comment by harr...@gmail.com on 17 Jun 2009 at 9:37

GoogleCodeExporter commented 9 years ago
Also note that when any of the cudppRand tests fail, the total tests failed for 
all
of cudpp_testrig doesn't seem to be updated correctly (it becomes a very large 
integer).

Original comment by harr...@gmail.com on 17 Jun 2009 at 11:31

GoogleCodeExporter commented 9 years ago
Fixed now with revision 5559.

Stanley

Original comment by Solgood...@gmail.com on 19 Jun 2009 at 11:07

GoogleCodeExporter commented 9 years ago
I confirm this works on my Mac (8600M GT, CUDA 2.2). W00t!

Original comment by jow...@gmail.com on 19 Jun 2009 at 2:36

GoogleCodeExporter commented 9 years ago

Original comment by Solgood...@gmail.com on 24 Jun 2009 at 12:29

GoogleCodeExporter commented 9 years ago
This is NOT fixed.  It still doesn't say FAILED when regression test files are 
not found.  I want this fixed even 
when the code to find the files is fixed.  A failure to find a file is a 
failure, not a pass.

Changing status back to started.

Original comment by harr...@gmail.com on 25 Jun 2009 at 12:24

GoogleCodeExporter commented 9 years ago
-quiet also doesn't appear to be observed.  With -quiet specified, I get this 
output, even though the files are 
presumably not found:

number of elements: 4194304, devOutputSize: 1048576
number of blocks: 4096 blocksize: 256 devOutputsize = 1048576
number of threads: 1048576
       4194304  1.3070

number of elements: 8388608, devOutputSize: 2097152
number of blocks: 8192 blocksize: 256 devOutputsize = 2097152
number of threads: 2097152
       8388608  2.0430

etc.

It should be 

       4194304  1.3070
       8388608  2.0430

(no spaces between test output lines)

Original comment by harr...@gmail.com on 25 Jun 2009 at 12:27

GoogleCodeExporter commented 9 years ago
Did you recompile cudpp itself?  I originally had some debugging statements in 
the
library and I removed those.  I just tried it on blaze and you should see 
something like:
                39      0.1330
               128      0.0820
               256      0.0670
               512      0.0710
              1000      0.0700
              1024      0.2590
              1025      0.2520
             32768      0.3080
             45537      0.3110
             65536      0.4170
            131072      0.4760
            262144      0.7140
            500001      1.2110
 and so on

Once I integrate tools.h and .cpp into the right places I will make it fail if 
it
does not find a regression file.

Stanley

Original comment by Solgood...@gmail.com on 25 Jun 2009 at 5:24

GoogleCodeExporter commented 9 years ago
-quiet is observed if you recompile cudpp.
Now if the testrig cannot find a regression file it will fail that test.

Original comment by Solgood...@gmail.com on 26 Jun 2009 at 12:57

GoogleCodeExporter commented 9 years ago
Verified.

Original comment by harr...@gmail.com on 26 Jun 2009 at 3:56