Closed Floriferous closed 2 months ago
I ran the exact same setup but replaced:
wait-on: 'http://localhost:3000'
with
wait-on: 'npx wait-on --timeout 60000 http://localhost:3000'
And now it works, very strange.
@Floriferous
Can we close this issue now, since you write that you found a workaround?
Well to me there still seems to be an open issue, even though it has a workaround. I've seen repos use a label called "has-workaround" without closing. So I guess it's ultimately a philosophical decision the maintainers have to take :)
@Floriferous
I suspect that the webserver wasn't ready when it was identified as being ready by wait-on: 'http://localhost:3000'
. There is some information in the README Debugging waiting for URL to respond about debugging this situation.
I can't say why wait-on: 'npx wait-on --timeout 60000 http://localhost:3000'
worked whereas wait-on: 'http://localhost:3000'
did not work.
I noticed your logs have a warning, which may or may not be significant:
⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
I'm not sure where the undefined
in the debug log comes from. The action is reporting an error from calls to Node.js network services invoked through the npm module got
debug(
`${elapsed}ms ${error.method} ${error.host} ${error.code} attempt ${attemptCount}`
)
If you want to provide a public repro showing the issue, we can dig in deeper. The benefit would be to understand why there is a failure, but I don't expect this is a bug in the action.
The question about closing or not closing is more a practical one. If the issue is left open it means there is more work to be done and that only makes sense if some further investigation is going to take place and either a documentation change or a fix to the action is expected. If nothing more is going to be done, then closing the issue says the work is finished.
You're right, it works for me so I probably won't investigate further either!
Practical decision, let's close this :) Thank you for the thorough response!
Hello there,
I'm trying to use this github action to run cypress e2e tests on my software. However I'm getting stuck in a redirect loop and don't know how to debug it. There are a bunch of undefined's in the error message as well, so I'm not sure what to do. I can't reproduce it locally either.
Does someone have an idea for how I could address this?
Here's the end of the github action run (currently with
DEBUG: '@cypress/github-action'
:This is the cypress part of my yaml file: