[LLC/Data Plane Client] Tests slow down in playback mode beyond timeout limit
See original GitHub issueHey all, The tests with issues are @christothes, @pakrym, @heaths have worked with me on debugging this issue. Our findings are as follows:
- The following test is severely slowed down if
waitForCompletion
is set to true. - The same applies for the following sample.
- However, for the sync version of the previous sample, the test is significantly slowed regardless of whether the
waitForCompletion
flag is set to true or false.
@christothes believes this may have to do with instrumentation not correctly handling scenarios where the operation is being returned by a helper class rather than the client itself.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Which Settings to change to speed up or slow down a Test ...
Remember that the default timeout is the LONGEST amount of time that Ranorex will spend searching for an item BEFORE IT THROWS A...
Read more >Stop shrink phase after timeout when progress is very slow
Mostly the test suite finishes in about a minute, but sometimes it ... Stop shrink phase after timeout when progress is very slow...
Read more >Project Properties - Playback Options | TestComplete ...
Timeout property. Delay between events, ms - Milliseconds to wait after the test simulates any user action (click, keystroke, window command, and so...
Read more >Playback Settings | LoadNinja Documentation
This setting overrides the Event timeout setting of simulated API tests. It specifies the number of seconds the test engine waits for a...
Read more >Browser Test Steps
By default, browser tests wait for a page to be fully loaded before performing a step or the next step with a timeout...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think more likely that this is a problem with how we proxy Operations. We currently transform the return value by instrumenting the returned operation. However, in the case of
waitForCompletion: true
, the operation is waited prior to it being returned by the method.I think we should explore a different approach to how we instrument operations to handle this case.
This was fixed in https://github.com/Azure/azure-sdk-for-net/pull/30112