Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    gaurav180
    @gaurav180
    Hi
    i had setup sorry cypress and able to run in my local
    i am facing one issue that unable to upload screenshot and videos
    (Uploading Results)
    • Failed Uploading (1/3) /home/gaurav/Desktop/cypress try/sorry-cypress-master/example/cypress/videos/c.spec.js.mp4
    • Failed Uploading (2/3) /home/gaurav/Desktop/cypress try/sorry-cypress-master/example/cypress/screenshots/c.spec.js/Suite C -- Shows 404 (failed).png
    • Failed Uploading (3/3) /home/gaurav/Desktop/cypress try/sorry-cypress-master/example/cypress/screenshots/c.spec.js/Suite C -- Welcomes you (failed).png
    is there any stpes need to be followed to enable it
    gaurav180
    @gaurav180
    i understood we need to use AWS s3 to store screenshots and videos to pull those in dashboard from there, i have another two questions
    1- Why can't we show it from local machine in case we don't give s3, as screenshots and video are getting saved by cypress in my local on failure
    2- Why am i not able to see failure logs on the Dashboard although i am able to see it in command prompt where from i triggered these test
    Jason Martinez
    @jayarc
    Hello I've just upgraded to cypress 7.0.0 and the lastest sorry-cypress master and I'm having difficulty running tests with cy2 and regularly with the manual app.yml edits. I'm running the docker-compose minio setup currently getting this error:

    We encountered an unexpected error talking to our servers.

    Because you passed the --parallel flag, this run cannot proceed because it requires a valid response from our servers.

    The --ciBuildId flag you passed was: hello-cypress5

    The server's response was:

    StatusCodeError: 404 - "<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n<meta charset=\"utf-8\">\n<title>Error</title>\n</head>\n<body>\n<pre>Cannot POST /instances/590c4321-957e-49f8-8388-17dfb2c862fc/tests</pre>\n</body>\n</html>\n"

    The director service and things look normal from the docker-compose containers
    Jason Martinez
    @jayarc
    Director does notice the request even though it seems to return 404, director log:
    director_1 | << RUN_START hook called
    director_1 | << Responding to machine {
    director_1 | groupId: 'hello-cypress5',
    director_1 | machineId: 'b733bddf-aec9-430f-b038-c04fed22e685',
    director_1 | runId: 'e5a79f086d9a4abe38ef5f9137464b1e',
    director_1 | runUrl: 'http://localhost:8080/run/e5a79f086d9a4abe38ef5f9137464b1e',
    director_1 | isNewRun: true,
    director_1 | warnings: []
    director_1 | }
    director_1 | >> Machine is requesting a new task {
    director_1 | runId: 'e5a79f086d9a4abe38ef5f9137464b1e',
    director_1 | machineId: 'b733bddf-aec9-430f-b038-c04fed22e685',
    director_1 | groupId: 'hello-cypress5'
    director_1 | }
    director_1 | << INSTANCE_START hook called 590c4321-957e-49f8-8388-17dfb2c862fc
    director_1 | << Sending new task to machine {
    director_1 | spec: 'admin-utilities.spec.js',
    director_1 | instanceId: '590c4321-957e-49f8-8388-17dfb2c862fc',
    director_1 | claimed: false,
    director_1 | groupId: 'hello-cypress5'
    director_1 | }
    Downgrading Cypress to 6.5.0 works, versions between may too. I'm upgrading to 7.0.0 for a bug fix related to maxRedirect 500s