[OpenSTA-devel] [ opensta-Bugs-908947 ] "Call Subroutine: xxxx" logs stop in Test Audit Log

[SourceForge.net <no...@so...>]

Bugs item #908947, was opened at 2004-03-03 04:19
Message generated for change (Comment added) made by faught
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=908947&group_id=10857

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Results Analysis
Group: Inconvenience
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Marc MAZAS (mmazas)
Assigned to: Daniel Sutcliffe (dansut)
Summary: "Call Subroutine: xxxx" logs stop in Test Audit Log

Initial Comment:
OpenSTA 1.4.2.34, W2K SP4, IE 6.0

(very long ~10000 lines) Script with numerous Calls to 
subroutines (every 10/20 lines)

In "Test Audit log", "Call Subroutine: <mysub>(line#)" 
logs start well, but stop ; it seems they stop when my 
script makes an iteration and goes back from near the 
end to near the beginning (Goto).

----------------------------------------------------------------------

Comment By: Danny Faught (faught)
Date: 2006-05-30 14:08

Message:
Logged In: YES 
user_id=576825

I think that the Call Subroutine log entries are a bit of a
nuisance, especially when subroutines are used extensively.
 I'd like to see this logging removed from the code.

Most recently observed in v. 1.4.3.20.

----------------------------------------------------------------------

Comment By: Daniel Sutcliffe (dansut)
Date: 2005-05-09 19:54

Message:
Logged In: YES 
user_id=19748

The "Call Subroutine" logs only occur once for a specific
CALL on a particular line for each individual VU.

Any flow control (GOTO, DO, CALL SCRIPT, etc.) will
illustrate this, as will reusing a script in a TaskGroup by
Task or iteration.

I'm not sure if the "Call Subroutine" should even be logged
once per VU... there is no such log for CALL SCRIPT
commands.  Some consistancy needs to be brought to this
logging situation.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110857&aid=908947&group_id=10857