Menu

#170 Incomplete SAS log reading in assertLog

default
closed
nobody
None
v1.6
not_relevant
Defect_Report
Assertions
3-moderate
2016-03-31
2016-03-31
No

I wondered why %assertlog did not show any errors or warnings, whereas in the HTML log view, a warning was reported.
This warning should have been also recognized by %assertlog since it would have been caught by the respective regex in %_checklog.
But: When I read the SASUnit log, it revealed that only the first 1000 lines of the test scenario log were read.
And the warning appeared in the remainder of the log file (which has 1688 lines in total), so it was not found by %assertlog.

Why is _checklog reading only 1000 lines of the respective log file?

MPRINT(CHECKLOG): DATA _null;
MPRINT(_CHECKLOG): INFILE
"C:\HMS\Projekte\kaiser_kraft\00759-001_konzeption_analysetoolbox\SVN\SASBackend\opt\datamart\default\sas\sourcesastest\testr
esult/log/015_001.log" TRUNCOVER end=eof IGNOREDOSEOF;
[...]
NOTE: The infile
"C:\HMS\Projekte\kaiser_kraft\00759-001_konzeption_analysetoolbox\SVN\SASBackend\opt\datamart\default\sas\sourcesastest
\testresult/log/015_001.log" is:

  Dateiname=C:\HMS\Projekte\kaiser_kraft\00759-001_konzeption_analysetoolbox\SVN\SASBackend\opt\datamart\default\sas\sour
  cesastest\testresult\log\015_001.log,
  RECFM=V,LRECL=32767,Dateigröße (Byte)=102834,
  Zuletzt geändert=31. ¤rz 2016 09.40 Uhr,
  Erstellungsuhrzeit=31. ¤rz 2016 09.40 Uhr

NOTE: 1000 records were read from the infile
"C:\HMS\Projekte\kaiser_kraft\00759-001_konzeption_analysetoolbox\SVN\SASBackend\opt\datamart\default\sas\sourcesastest
\testresult/log/015_001.log".

The minimum record length was 0.
The maximum record length was 125.
NOTE: DATA statement used (Total process time):
real time 0.01 seconds
cpu time 0.01 seconds

regards,
Johannes

Discussion

  • Klaus Landwich

    Klaus Landwich - 2016-03-31

    I can't see any reason concerning SASUnit source code checking only 1000 observations.

    Here is an excerpt of _checklog reading 120.000+ observations:

    MPRINT(_CHECKLOG): RUN;

    NOTE: The infile "C:\Projekte\CZM\SASUnit\Report-System\en/log/054_009.log" is:
    Filename=C:\Projekte\CZM\SASUnit\Report-System\en\log\054_009.log,
    RECFM=V,LRECL=32000,File Size (bytes)=8167603,
    Last Modified=25. Februar 2016 12.07 Uhr,
    Create Time=25. Februar 2016 12.06 Uhr

    NOTE: 120333 records were read from the infile "C:\Projekte\CZM\SASUnit\Report-System\en/log/054_009.log".
    The minimum record length was 0.
    The maximum record length was 257.
    NOTE: DATA statement used (Total process time):
    real time 0.07 seconds
    cpu time 0.07 seconds

    MLOGIC(_CHECKLOG): Ending execution.

    I need to investigate deeper. Do you have any additional information about your run-time environement like operating system, SAS Version etc.

    regards,
    Klaus

     
  • Klaus Landwich

    Klaus Landwich - 2016-03-31

    I this a problem with reading UNIX-Files under Windows regarding CR/LF?

     
    • Johannes Lang

      Johannes Lang - 2016-03-31

      Thank you, I found the reason: It was in my test scenario, where I placed an OBS=1000 option statement in order to speed up my test data processing.
      Didnt know that this will also influence the log parsing :-/
      Sorry, I will close the ticket, since it has nothing to do with SASUnit itself.

       
  • Johannes Lang

    Johannes Lang - 2016-03-31
    • status: open --> closed
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB