-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Broken tests for Node@8 and Node@9 #159 #48
Comments
carpasse
added a commit
to carpasse/on-finished
that referenced
this issue
Mar 27, 2024
… action closes jshttp#48 Similar fix as jshttp/http-errors#109
carpasse
added a commit
to carpasse/on-finished
that referenced
this issue
Mar 27, 2024
… action closes jshttp#48 Similar fix as jshttp/http-errors#109
carpasse
added a commit
to carpasse/on-finished
that referenced
this issue
Mar 27, 2024
… action closes jshttp#48 Similar fix as jshttp/http-errors#109
I approved the PR, lets close this and just use that. Lets just wait for a bit to ensure things pass then we can merge. |
carpasse
added a commit
to carpasse/on-finished
that referenced
this issue
Mar 28, 2024
closes jshttp#48 Similar fix as jshttp/http-errors#109
carpasse
added a commit
to carpasse/on-finished
that referenced
this issue
Mar 28, 2024
closes jshttp#48 Similar fix as jshttp/http-errors#109
UlisesGascon
pushed a commit
that referenced
this issue
Apr 29, 2024
PR-URL: #49 REF: #48 and jshttp/http-errors#109
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Seems like the current master branch have some broken tests when running Node@8 and Node@9.
Issue is similar to jshttp/http-errors#109
I can not provide a failed build because the workflow is waiting for approval
But I can see the ci-test action failing in my forked repo
https://github.com/carpasse/on-finished/actions/runs/8433556449
The text was updated successfully, but these errors were encountered: