-
The SegFault also occurs with STAF 3.2.5.
2009-11-09 15:03:38 UTC in SW Test Automation Framework
-
On my system, I also get a SegFault when using STAF 3.3.3 (the connection timeout feature was added in STAF 3.3.4) and when using STAF 3.3.0. Can you try the STAFLoop test on your custom STAF 3.3.0 build and verify if the SegFault occurs?.
2009-11-05 23:00:06 UTC in SW Test Automation Framework
-
We've been able to reproduce the problem, and are investigating.
2009-11-05 21:01:32 UTC in SW Test Automation Framework
-
So with the updated STAFLoop, you can recreate the problem by just running the command sequentially about 5 times (not in parallel)? I've tried both ways with a similarly updated STAFLoop, and I don't get the SegFault (I do get a lot of RC 22 when running in parallel).
Can you try running your updated STAFLoop on a system where the problem is occurring, but using the STAF335-linux-amd64...
2009-11-05 15:23:47 UTC in SW Test Automation Framework
-
As documented in the [STAF TCL User's Guide][1], the TCLSTAF.dll that is provided with STAF only supports Tcl 8.0 - 8.3.
The following support request prvovides a TCLSTAF.dll for Tcl 8.4 that you can try:
[Support Request #2794262 "STAF V3.3.3 Support for Tcl 8.4 (Win32) "][2]
[1]: http://staf.sourceforge.net/current/STAFTcl.htm
[2]...
2009-11-05 14:59:32 UTC in SW Test Automation Framework
-
I've been using STAFLoop to simulate a stress environment on our Linux AMD64 system with STAF 3.3.5, but I have not seen this problem. Could you try running a similar test with STAFLoop on a system where the problem is occurring and see if this recreates the problem? On the test system, run the following command multiple times in parallel (for my tests I ran the command 8 times in parallel):
2009-11-04 21:36:13 UTC in SW Test Automation Framework
-
Certain Windows applications can have issues when a subset of its 3 I/O streams (standard input, standard error, standard output) are redirected. The workaround is to redirect all 3 I/O streams or use the SAMECONSOLE option. This is documented in the STAF User's Guide [section 8.12.2 START][1]:
======================================
On Windows systems, if you are redirecting...
2009-10-28 14:00:38 UTC in SW Test Automation Framework
-
The LOG service has the following requests which allow you to delete a log or purge some/all records from a log:
DELETE - Delete a log file
PURGE - Purge records from a log file
Note that when you use the CLEARLOGS option with STAX, it uses the LOG DELETE request to clear the log of previous runs.
2009-10-28 13:43:52 UTC in SW Test Automation Framework
-
I think you misunderstood my previous posting. There is no STAF/Service/STAX/Mask variable. The STAF/Service/<Name>/Mask variable is used for the Log service (<Name> just indicates the name you are using for the "Log" service, which most likely is "Log"). So if you have the STAF/Service/Log/Mask variable set, it will be used as the log mask for all logs on the...
2009-10-22 13:12:01 UTC in SW Test Automation Framework
-
You can do a silent or console install so that a UI is not required. See the [STAF Installation Guide][1] for more information.
It's also possible that you are running into a known InstallAnywhere issue where you need to install the required X libraries to run Swing applications on your system. Section 6.1 "Linux Installation" of the STAF Installation Guide has more information.
2009-10-21 22:02:56 UTC in SW Test Automation Framework
