Skip to content
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

Clean up unit test output #55

Merged
merged 3 commits into from
Jan 27, 2022
Merged

Conversation

pprkut
Copy link
Collaborator

@pprkut pprkut commented Dec 30, 2021

  • Use a mocked logger to remove output spam
  • Fix phpunit deprecation warnings

This should fix all the issues scrutinizer has with the unit tests.

- Use a mocked logger to remove output spam
- Fix phpunit deprecation warnings
@pprkut
Copy link
Collaborator Author

pprkut commented Dec 30, 2021

Well, boo 😞

The OOM error remains, and I can't reproduce that one locally.

@pprkut
Copy link
Collaborator Author

pprkut commented Dec 30, 2021

However, it looks like the OOM isn't actually an issue and it's rather failing on this line:

The coverage file '/home/scrutinizer/build/coverage.xml' was not found.

because

Error:         No code coverage driver is available

The default is phpunit 9.x and that doesn't find any tests.
@pprkut pprkut mentioned this pull request Dec 30, 2021
@danhunsaker danhunsaker merged commit 707ec24 into resque:master Jan 27, 2022
danhunsaker pushed a commit that referenced this pull request Jul 13, 2023
* Clean up unit test output

- Use a mocked logger to remove output spam
- Fix phpunit deprecation warnings

* Migrate phpunit config file to newer format

* Use phpunit 5.x for github actions

The default is phpunit 9.x and that doesn't find any tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants