You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Happens both with the GUI and on the command line.
Is this a Feature or Bug?
Bug
Current behavior:
About 9 times out of 10, the test slows down dramatically then hangs when trying to fill in a text input. Using el.clear seems to increase the issue but it may just be any input being typed in. Other tests work fine, but 2 consistently fail. They are on pages with more DOM elements so it may be a memory issue. The 1 time out of 10 it passes, everything is fast and works fine, so the test does pass and there does not seem to be a problem with the test itself; it appears to be flake, related to CPU or memory overuse (my computer will start to hum loudly due to the fan working hard).
Note this same type of things happens on a 2nd test, also for a number input, that one with a clear. I've attached information, screenshots, and a video for the 1st case; happy to add the 2nd example if that helps.
In both cases, the entry point url for the test is the same - perhaps something on that initial page is causing cypress to crash / memory leak?
Desired behavior:
The tests pass consistently all the time and are fast.
How to reproduce:
I have only been able to reproduce with these 2 tests, but I can reproduce each time. I've attached a video recording and screenshots. When they hang, they hang indefinitely. Our Continuous Integration waits about 50 minutes until the 1 hour max then fails.
Test code:
The actual lines where it hangs is one of these 3 (not always the same line).
plInputText.setValue(`${selector} .x-qa-metric-short-description`,metricShortDescription,{skipClear: true});plInputTextArea.setValue(`${selector} .x-qa-metric-long-description`,'METRIC LONG DESCRIPTION',{skipClear: true});plInputText.setValue(`${selector} .x-qa-metric-goal`,10,{skipClear: true});
These use the following helper functions / files:
plInputText.clear=(el)=>{returnel.type('{ctrl}a{backspace}');// 2017.07.14 - backspace was hanging; back to clear.// return el.clear();};plInputText.setValue=(selector,value,options={skipClear: false})=>{constel=cy.get(`${selector}${inputSelector}`);letelCleared;if(options.skipClear){elCleared=el;}else{elCleared=plInputText.clear(el);}if(typeof(value)!=='string'||value.length){if(options.blurAfter){elCleared.type(value).blur();}else{elCleared.type(value);}}else{if(options.blurAfter){elCleared.blur();}}};plInputTextArea.setValue=(selector,value,options={skipClear: false})=>{constel=cy.get(`${selector}${inputSelector}`);letelCleared;if(options.skipClear){elCleared=el;}else{elCleared=plInputText.clear(el);}elCleared.type(value);if(options.blurAfter){elCleared.blur();}};
The actual CI output for the same fail - the test starts around 9 minutes into the build, nothing happens for 51 minutes, then the build is canceled at 60 minutes.
Edited: Removed image w/ key
The text was updated successfully, but these errors were encountered:
Hi, @lukemadera I'm going to close this issue since I think it was fixed by spec Isolation in #681 , feel free to update this issue if you're still having problems
Happens both with the GUI and on the command line.
Is this a Feature or Bug?
Bug
Current behavior:
About 9 times out of 10, the test slows down dramatically then hangs when trying to fill in a text input. Using
el.clear
seems to increase the issue but it may just be any input being typed in. Other tests work fine, but 2 consistently fail. They are on pages with more DOM elements so it may be a memory issue. The 1 time out of 10 it passes, everything is fast and works fine, so the test does pass and there does not seem to be a problem with the test itself; it appears to be flake, related to CPU or memory overuse (my computer will start to hum loudly due to the fan working hard).Note this same type of things happens on a 2nd test, also for a number input, that one with a
clear
. I've attached information, screenshots, and a video for the 1st case; happy to add the 2nd example if that helps.In both cases, the entry point url for the test is the same - perhaps something on that initial page is causing cypress to crash / memory leak?
Desired behavior:
The tests pass consistently all the time and are fast.
How to reproduce:
I have only been able to reproduce with these 2 tests, but I can reproduce each time. I've attached a video recording and screenshots. When they hang, they hang indefinitely. Our Continuous Integration waits about 50 minutes until the 1 hour max then fails.
Test code:
The actual lines where it hangs is one of these 3 (not always the same line).
These use the following helper functions / files:
Additional Info (images, stack traces, etc)
Video of failure in the GUI:
http://recordit.co/jHejsA0MG3
CI fail, on Cypress Dashboard:
The actual CI output for the same fail - the test starts around 9 minutes into the build, nothing happens for 51 minutes, then the build is canceled at 60 minutes.
Edited: Removed image w/ key
The text was updated successfully, but these errors were encountered: