-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
PRs are failing because of 'bad argument (expected URI object or URI string)' error #9756
Comments
thanks for reporting this @Manasa2850 ..looking into it |
I think this is caused by one of the libraries updates because I can see the tests all pass with no failures |
could be puma because its HTTP related...I will try to revert the puma latest version update |
but I see PRs created after that , and they passed build 🤔 |
sometimes it fails on all types of tests...sometimes passes on all but system (fail --no failures or errors are recorded it displays the above error) just before the tests report |
okay was able to get #9757 to pass with 3 restarts |
@cesswairimu closing and reopening doesn't seem to work always. I tried it a couple of times on #9733 but the tests are still failing 😢 |
Yeah you are right, seems like its a codecov pipeline problem |
Looks like this is now resolved...Found this conversation other people were having the same prob with codecov codecov/codecov-action#330 and looks like a fix was deployed 5 hours ago. Closing this. Thanks |
Thanks for helping figure this out @cesswairimu 🎉 |
A lot of the recent PRs are failing because of this error. This causes all 4 tests - unit, functional, integration and system tests to fail.
Closing and reopening the PR is not solving this error.
The text was updated successfully, but these errors were encountered: