Help with make check (4.3.4)

2013-09-09
2013-10-17
  • All,

    I had an issue with building NCO with UDUNITS2 support that, thankfully, NCO 4.3.4 fixed. Huzzah! I then built without error and tried a 'make check' and got:

    ============================================================================
    Testsuite summary for NCO netCDF Operators 4.3.4
    ============================================================================
    # TOTAL: 0
    # PASS:  0
    # SKIP:  0
    # XFAIL: 0
    # FAIL:  0
    # XPASS: 0
    # ERROR: 0
    ============================================================================
    

    I'm not sure if this is a success or not? Is there something I did during the 'configure' or 'make install' that disabled the check? Or is there a separate tarball of tests I need to get to test this?

    I will note that the compiled executables do seem to work as expected, so I believe they built correctly.

    Thanks,
    Matt

     
  • Charlie Zender
    Charlie Zender
    2013-09-12

    Matt, your confusion is understandable. I admit to not having seen that before. Try 'make test' instead and post the summary, if any.
    cz

     
  • Ah, okay. Make test does work…well, it runs. Works…

    Linux janus.gsfc.nasa.gov 2.6.32-358.14.1.el6.x86_64 #1 SMP Mon Jun 17 15:54:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux; ; 
                        Test Results                Seconds to complete
                 --------------------------   ----------------------------------------
          Test   Success    Failure   Total   WallClock    Real   User  System    Diff
         ncap2:        0         11      11       0.06     0.00   0.00    0.00    0.00
       ncatted:        4          1       5       1.30     0.00   0.00    0.00    0.00
          ncbo:       11         12      23       6.78     0.00   0.00    0.00    0.00
       ncflint:        4          3       7       1.93     0.00   0.00    0.00    0.00
          ncea:        9          1      10       0.27     0.00   0.00    0.00    0.00
        ncecat:        1          6       7       1.03     0.00   0.00    0.00    0.00
          ncks:       16         53      69       6.52     0.00   0.00    0.00    0.00
         ncpdq:       35         10      45      11.90     0.00   0.00    0.00    0.00
          ncra:       20          2      22       1.06     0.00   0.00    0.00    0.00
        ncrcat:        6         15      21       4.94    10.00   0.00    0.00   10.00
          ncwa:       40          5      45      12.54     0.00   0.00    0.00    0.00
    NB:MD5: test passes MD5 checksum on file(s) May be more than one intermediate file.
    SVx: test passes single terminal value check SVn=numeric, SVa=alphabetic
    OK - data NOT sent, thanks for using NCO anyway - bye!
    
     
  • Charlie Zender
    Charlie Zender
    2013-09-13

    Well, the results of make test look terrible but that's probably a diagnostic issue (i.e., a problem with the test) not a problem with the operators themselves. Pedro, please change  "make check" to be synonymous with "make test". Thanks, c

     
  • Thanks for the help!

    Also, Charlie, what is the correct way to "automate" make check/test? That is, I know it says to specify "$DATA" for the directory. I was wondering where I need to pass DATA to get it in. Like, if I did "export DATA=/tmp/nco_test" would it be during configure? Or during the make test call?

    I ask only because for our base libraries, I usually issue a "make check" and it runs it in all the libraries, but nco will break the automation without this…and I'm lazy. I like fire-and-forget make commands. :)

    Matt

     
  • Charlie Zender
    Charlie Zender
    2013-09-18

    matt,
    i simply don't know. i only use autoconf or automake when absolutely necessary. too confusing. hope someone else
    can answer your question and make it automatic.
    cz

     
  • Pedro Vicente
    Pedro Vicente
    2013-09-18

    the regression tests use  these environment variables

    in your start shell script (e.g .bashrc ) define names for

    export DATA=~/data_nco
    export MY_BIN_DIR=~/nco_install/bin

    where ~/nco_install/

    is the location where you installed NCO with

    ./configure -prefix=

    by the way, how did you format the output of the tests in your post #3 above?

    Pedro

     
  • Pedro, I used the "code" tags. It's the icon between the "quote" and "picture" when you add a reply.