-
Notifications
You must be signed in to change notification settings - Fork 68
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
#stdout coverage format #480
base: master
Are you sure you want to change the base?
Conversation
@fniephaus |
...itory/SmalltalkCI-Coverage-Core.package/SCIStdoutCoverageWriter.class/instance/export.in..st
Outdated
Show resolved
Hide resolved
Hi @LeonMatthes, |
Ah, it seems Gemstone is actually not loading the Coverage package, which is where the I'll see what I can do to fix this. |
Thanks! |
@fniephaus . It seems the Merge of the master branch into this fork somehow bricked Pharo builds. Do you have any idea what might be causing this? |
Yes, very much possible this is caused by corrupted metadata. Can you fix this by hand? |
Maybe try reproducing locally? |
There's now a GemStone build running on GitHub Actions, maybe that helps to debug the problem. |
Introduce the
#stdout
coverage format.Prints a coverage report before the test summary.
Useful if you don't want to use a separate coverage provider or your coverage provider is not supported.
Also implements the ability to output more than one coverage format.