This is a migrated thread and some comments may be shown as answers.

broken pipe

16 Answers 405 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

Jem asked on 19 Sep 2013, 01:44 PM

with version 2013.1.827 of testing framework we keep getting broken pipe errors after searching for a window:
This works fine in 2012.2.1420

it works the first time the code is called - the window is freshly created and we get a new window event, but when the window is re-used it fails. (The dock guide window has no caption - it is from the ActiPro docking framework) The window exists and is visible.

var dockGuideWindow = AtlasApp.Application.WaitForWindow(string.Empty, 10000);
var location = dockGuideWindow.Window.Location;
--->> var dockGuides = dockGuideWindow.Find.AllByType<T>(); (where T : DockGuideBase)

Exception thrown during the wait for a condition. Error: Unexpected error while waiting on condition. Error: System.IO.IOException: Pipe is broken.
at System.IO.Pipes.PipeStream.CheckWriteOperations()
at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.WriteCommandToPipe(PipeCommand command, PipeStream pipe, Boolean waitForDrain)
at ArtOfTest.WebAii.Messaging.Process.BrowserRemoted.ProcessBrowserRequest(BrowserCommand command, String requestId)
at ArtOfTest.WebAii.Wpf.WpfProxy.ExecuteSLCommand(SilverlightCommand cmd)
at ArtOfTest.WebAii.Wpf.WpfProxy.GetAllVisualTrees()
at ArtOfTest.WebAii.Wpf.WpfWindow.RefreshVisualTrees()
at ArtOfTest.WebAii.Silverlight.VisualFind.RefreshRoot()
at ArtOfTest.WebAii.Silverlight.VisualWait.WaitForExistsByFindInfo(VisualFindInfo findInfo)
at ArtOfTest.Common.WaitAsync._worker_DoWork[T,V](Object waitParam)

What has changed?
I have tried numerous workarounds (delays, doEvents,) to no avail

16 Answers, 1 is accepted

answered on 25 Sep 2013, 06:51 AM

Hello Jem,

The "Pipe is broken" error indicates that the application under test/recording has crashed and TS is unable to connect to it. Unfortunately this is app. specific so in order for us to investigate a possible fix we will require your WPF application and the scenario that is causing the crash.

Could you please go ahead and send us your application? If it is not possible you can create some sample one where we can reproduce the issue.

Please also upgrade the framework to our latest version which is 911.

Hope to hear from you soon.

Regards,
Boyan Boev
Telerik

The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!

answered on 18 Nov 2013, 04:32 PM

TestModalDialog.zip

Hi,

Further to this, I have had some time to put a demo solution together which shows some of our problem.

(We reverted to the previous version to work around it last time - Note this solution works fine with the previous version of the framework 2012.1.1420)
This fails on version 2013.1.1002.0

Please run the attached solution.
In essence it's a simple console application (VStudio 2012 .NET 4.5) which wraps the Telerik test framework. It monitors a simple WPF application which has a single main window with a single button. On pressing the button a mode-less dialog window is opened. The framework waits for this and then finds the close button which it User.Clicks(). The window should then close.
This models the way our developers have created dialog boxes in our application.

This works only on the first time that the mode-less window is open. On subsequent iterations the dialog box cannot be found and the code fails.

(please see the comments in the code)

Let me know if you receive this OK and if you have any difficulty running it

Regards
Jem Prince

answered on 18 Nov 2013, 08:37 PM

TestModelDialog.png

Repeatedly, it was run without issue on my machine. I changed the iterations from 50 to 10 as...well 50 is a bit much for me to sit through :) Repeated a few times, no issues. Running Windows 7 w/ .net 4.5 and VS 2012.

Code all looks good to me. I even laughed a bit at "//[Missing <summary> documentation for "P:ArtOfTest.WebAii.Core.Settings.DisableDialogMonitoring"] wtf is it?"

DisableDialogMonitoring - whether to disable dialog handling. (http://www.telerik.com/automated-testing-tools/support/documentation/user-guide/modifying-tests/test-properties.aspx - Same for VS version).

Can you post the exact error message just for reference?

answered on 19 Nov 2013, 09:02 AM

TestModalDialog.zip

Hi Daniel,

Thanks for the quick response.
We have tried it now on several machines and they always eventually get the error.
Running the compiled exe lasts for about 30 iterations on most machines (others it will do 15) , but running in the ide using the debugger only does 1. Running in the IDE without debugging usually lasts longer but eventually fails.

The exact error is:
{"Unable to find the window 'Modeless' inside application 'C:\\Users\\jem.prince\\Documents\\Visual Studio 2012\\Projects\\TestModalDialog\\WpfApplication1\\bin\\Debug\\WpfApplication1.exe'\r\n---- Current Windows: ----\r\nMainWindow\r\n--------------------------\r\n"}
Stacktrace:
at ArtOfTest.WebAii.Wpf.WpfApplication.WaitForWindow(String caption, Int32 timeout)
at TestModalDialog.MainWindow.FindModeless() in c:\Users\jem.prince\Documents\Visual Studio 2012\Projects\TestModalDialog\TestModalDialog\MainWindow.cs:line 57

Are you absolutely sure you are using the same telerik dlls' that we are?
2013.1.1002.0 - as I said we get no errors with the previous version(s).
We are running Windows 7 enterprise ServicePack 1 on a 8gb 64 bit Xeon processors with 8 cores.

You could try putting the value up to 250 ?

I have added the built exe from my machine in the zip file

Regards
Jem

PS I still don't know what 'Dialog Handling' is...

answered on 01 Apr 2015, 06:26 AM

testmodaldialog.zip

telerikerror.png

Annoyingly yesterday I downloaded Jems application linked in a previous post and tried it once with the TestModalDialog console app and it failed with the problem then every subsequent attempt afterwards it did not. I then thought...ok lets create n MSTest project and do multiple iterations the way we are doing it in our actual tests and again it failed first time and then worked for every subsequent attempt.
This morning i have tried it again using the Console project and it happened after 10 loops and then second time it happened on loop 2. see attached image of the error happening and also a very slightly updated zip of the projects Jem originally posted.

answered on 01 Apr 2015, 11:55 PM

Hi Max,

You need to make 2 changes to your code to make it work reliably:

1) After opening any popup window you need to refresh the visual trees:

public WpfWindow FindModeless()

{

var retries = 0;

WpfWindow window = null;

while (retries++ < MaxRetries)

{

Console.WriteLine("Attempt to FindModeless {0}", retries);

try

{

if (window == null)

{

AppWrap.Application.MainWindow.RefreshVisualTrees();

window = AppWrap.Application.WaitForWindow("Modeless", TimePeriod.OneSecond * retries); // increasing wait time

if (window == null)

{

continue;

}

return window;

}

catch (Exception ex)

{

Console.WriteLine(ex.Message);

}

return null;

}

2) After clicking the button that closes the window you need to tell Test Studio that the window is closed. It is not able to automatically track this:

public void HideModeless()

{

// exception here...

WpfWindow popup = FindModeless();

popup.Find.ByType<Button>().User.Click();

popup.Window.Close();

}

Regards,
Cody
Telerik

The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting

Testing & Mocking

CMS

UI/UX Tools

Debugging

Free Tools

broken pipe

16 Answers, 1 is accepted