Closed reedy closed 2 years ago
Looks like this is related to https://github.com/GoogleChromeLabs/web-push-testing-service
and @Minishlink wanted to work on this last year, but did not get to it... he would probably welcome help though :)
https://github.com/web-push-libs/web-push-php/pull/228#issuecomment-500021751
It does seem that https://github.com/web-push-libs/web-push-php/commit/682b99f8a11c723099cf918e18350ee6b68f450e at least skips the tests from https://github.com/web-push-libs/web-push-php/pull/228#issuecomment-498856174
Yeah web-push-testing-service is hard to fix.. I tried back in February https://github.com/web-push-libs/web-push-php/tree/try-fix-test-once-more but no luck.
I don't see many solutions, either one of these:
In any way, I can't accept PRs without being sure that core feature doesn't break...
If somebody wants to help, that would be highly appreciated
@Minishlink the best possible solution I see for the moment is to disable the tests that use the https://github.com/GoogleChromeLabs/web-push-testing-service. This will unblock all other tests and allow accepting unrelated to Web Push PRs like the one I've created - https://github.com/web-push-libs/web-push-php/pull/268
Also, it seems that it's worth to mention in README.md's head section that none of bug fixes/feature reqeusts will be accepted until the issue with tests is resolved so the community may not waste their time on contributing or can do that to their forks directly (as I was forced to do). Or otherwise, more people will be aware that help needed.
It seems all recent commits and PR are resulting in test failures from travis. Someone should fix them