synpress: tests hang up with SIGTRAP error message in the browser and core dump

Seems related to a known cypress issue.

This is the test that leads to core dump and SIGTRAP error in the browser. This is the line that triggers it.

    it(`Should proceed to contract write via wallet`, () => {
       cy.get('input[name="goalTitle"]').type('Complete Milestone 10')
       cy.get('input[name="deadline"]').type('2222-12-31')
       cy.get('[data-cy="submit-button"]').click()          <<<<<<<< causes synpress/cypress to hang up

https://user-images.githubusercontent.com/2234901/186439294-7aeae609-d576-4743-b265-5caa60a3b903.mov

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 17 (4 by maintainers)

Most upvoted comments

@ivelin can you retry with @synthetixio/synpress@2.0.1?

Ok, I just retried and still resulting in core dumps. The video recording is a little different this time. See attached.

With synpress 1.0.2 it appeared that wagmi contractWrite hook was not communicating back with the app. However with synpress 2.0.1 the app pop-up is updating which is evidence that contractWrite is talking to the app. This time appears that synpress is unable to interact with metamask.

The easiest way to reproduce is to open this gitpod environment:

https://gitpod.io/#https://github.com/SporosDAO/sweat-token/pull/134

then

cd e2e-tests
yarn test --spec "tests/e2e/specs/project-tribute-spec.js"

The command will run the first 3 checks quickly and then hang up on the 4th here:

cy.rejectMetamaskTransaction()

The behavior is similar if I replace rejectMetamaskTransaction() with

cy.confirmMetamaskTransaction()

Screen Shot 2022-09-06 at 9 03 07 PM

This video is with reject tx:

https://user-images.githubusercontent.com/2234901/188772198-10047eae-7844-435d-b664-ab0b4dae75e9.mp4

This video is with confirm tx:

https://user-images.githubusercontent.com/2234901/188773534-ec66cc9c-7e96-459a-be0f-aee411a4c202.mp4

This issue is not related to synpress, but cypress and chromium itself.

You can follow original issue here and find some workarounds until it’s fixed in next Chrome version (107): https://github.com/cypress-io/cypress/issues/23391#issuecomment-1266895628

One of the workarounds is to use older version of Chrome until it’s fixed in new one. Not perfect, I know. However I went ahead and downgraded Chrome inside docker-e2e, so if you’re using this container, feel free to try and run your tests again to see if it fixes your issue.

Also added a discussion in the wagmi repo to see if it can be resolved on their end: https://github.com/wagmi-dev/wagmi/discussions/897

I’m facing the exact same issue. Tested it with different browsers and it’s all the same crash.