-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI function do not behave the same as local #390
Comments
I think i found my issue it was not exactly the same env |
I had sadly to re-open it, it still happening. |
Let me move this to functions repo who might have better knowledge of deno testing. @nyannyacha 502 seems like a server side error from edge runtime. Are there any concurrency caveats with running edge runtime locally? |
I can see from the CI's logs that the status code was 502. However, this doesn't tell us much. To determine the exact cause, it's a good idea to have the body returned by the edge runtime endpoint also be printed to the log.
I'm guessing from the flags given to the deno test that all test files and tests will be run sequentially.
I don't think I can advise anything at this point, as this command evaluates all tests sequentially as far as I know, so there's nothing to comment on for concurrency caveats in the edge runtime. 😓 |
Describe the bug
All functions test pass 100% of the time in local but often fail in CI/CD env.
*To Reproduce
Steps to reproduce the behavior:
In this repo: https://github.com/Cap-go/capgo
In local, if I do :
Both env run the same way and yet the CI/CD fail, you can see the history of github actions, some endpoint timeout weirdly
Expected behavior
Localhost should fail the same way as CI/CD
The text was updated successfully, but these errors were encountered: