jennifer-shehane
commented
3 months ago @AlexAutoation Could you provide information around that test where it's hanging in the same spot?
Open AlexAutoation opened 3 months ago
jennifer-shehane
commented
3 months ago @AlexAutoation Could you provide information around that test where it's hanging in the same spot?
1g0s
commented
3 months ago Hello,
I can assist, we are from the same company with reporter.
Would you please explain what details specifically do you need? There are couple suits which would always stuck with the same cypress hang. We didn’t change any versions when that started… it happens for all of us on separate systems. Our DevOps didn’t do anything specifically which could cause this issue on application side.
Please, let me know what should I provide so you can proceed with support?
Thanks, — Igor
On 16 Apr 2024, at 20:26, Jennifer Shehane @.***> wrote:
@AlexAutoation https://github.com/AlexAutoation Could you provide information around that test where it's hanging in the same spot?
— Reply to this email directly, view it on GitHub https://github.com/cypress-io/cypress/issues/29336#issuecomment-2059783051, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWSB33I3L6AKUIFQ6P4XFDY5V3OLAVCNFSM6AAAAABGHSWGKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZG44DGMBVGE. You are receiving this because you are subscribed to this thread.
jennifer-shehane
commented
3 months ago @1g0s Just some information around what that test is doing. Ideally, to address a hang, having a way for us to run and see the hang is the best way to debug why.
1g0s
commented
2 months ago Hello Jennifer,
Unfortunately we didn’t get permission to share the code… but I have an update, if that make sense. So I was able to find that actually commenting all the lines where cy.url() has been used resolve the freeze issue for almost all tests.
Would that be helpful?
Thanks, — Igor
On 19 Apr 2024, at 18:53, Jennifer Shehane @.***> wrote:
@1g0s https://github.com/1g0s Just some information around what that test is doing. Ideally, to address a hang, having a way for us to run and see the hang is the best way to debug why.
— Reply to this email directly, view it on GitHub https://github.com/cypress-io/cypress/issues/29336#issuecomment-2067040227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWSB33TOXHFP43Y7CQXB73Y6FKY3AVCNFSM6AAAAABGHSWGKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGA2DAMRSG4. You are receiving this because you were mentioned.
jennifer-shehane
commented
2 months ago Could you share some psuedo code on how the cy.url() command is being used to get some idea of why this might hang? We have tests around this command, so it doesn't hang within our tests.
1g0s
commented
2 months ago Hello Jennifer,
Yes, I can do that… here is the snippet.
// Entry point Broker Portal > Relay Direct "sender/broker-portal/payments"
// Use action to Generate, Upload Payments from CSV file, Validate upload and get back to entry point
const uploadPayments = (payoutType, amount, carrier) => {
const targetUrl = appUrls.broker.payments;
cy.url().then((currentUrl) => {
if (currentUrl !== targetUrl) {
cy.visit(targetUrl);
}
});
commonHelper.setPaymentDate(payoutType);
***@***.***').then(paymentDate => {
commonHelper.getPaymentUploadCsv(amount, carrier, paymentDate);
***@***.***').then(filePath => {
senderPage.uploadPayments(filePath);
});
});
***@***.***').then((payment) => {
carriersPage.searchPayments(payment.invoiceNumber)
});
}
Or in this case with just basic call.
it(`[${user.userRole}]: Broker Lock : Locked broker accounts can't onboard a carrier`, () => {
authorize(user.userName, commonPassword);
cy.visit(appUrls.broker.carriers);
carriersPage.elements.closeIconBtn().should("be.visible").click();
cy.url().should("be.include", appUrls.common.login);
});really don’t know if that is related or not, but for some reason commenting all this lines where cy.url() has been used is actually not freezing cypress run
Thanks, — Igor
jennifer-shehane
commented
2 months ago I'm not having any luck trying to replicate this unfortunately - pulling out the parts you provided and visiting some of our sites.
1g0s
commented
2 months ago Is there a way I can reproduce with verbose logs and send to you?
— Igor
On 25 Apr 2024, at 19:58, Jennifer Shehane @.***> wrote:
I'm not having any luck trying to replicate this unfortunately - pulling out the parts you provided and visiting some of our sites.
— Reply to this email directly, view it on GitHub https://github.com/cypress-io/cypress/issues/29336#issuecomment-2077970723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKWSB34U6N7AX7XU6AVZFFTY7FG6BAVCNFSM6AAAAABGHSWGKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXHE3TANZSGM. You are receiving this because you were mentioned.
jennifer-shehane
commented
2 months ago @1g0s You can run Cypress in debug mode mode and provide the logs in this issue or send to jennifer@cypress.io
Current behavior
Cypress stops to execute at some point after several tests and provides any output. It starts to happen from April 11. It works fine if test spec contains 5 tests but if test spec contains more tests it hangs. Usually, it hangs in the same place. I tried to change the node version (18, 20. 21) I tried to use Chrome and Electron I tried to change Cypress ver to 12.17.4 I tried to clear Cypress cache. I tried to revert code to several days when the tests were 100% working. The same behavior is observed on CI (Gitlab). The same behaviour is observed on another laptop. But nothing helped. Please let me know if I need to provide more info.
Desired behavior
Cypress should fail with specific error if something is wrong.
Test code to reproduce
I can not share the code due to company regulations
Cypress Version
13.7.3
Node version
v20.9.0
Operating System
macOS 14.4.1
Debug Logs
Other
No response