-
Notifications
You must be signed in to change notification settings - Fork 277
BUG: hotfix report defects in logs and HTML summaries #2512
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
Conversation
3ee69aa
to
e25855f
Compare
looks like I should have run tests locally after all... sorry for the time this wasted. Let's try again, this time including test changes. |
2c26c82
to
4221741
Compare
Unrelated to this PR, but @mhsmith all PRs are getting this warning:
Pylint is detecting a circular import that Python is able to handle at runtime. Maybe there's a way to remove the circular pattern, or we can just silence the warning. |
In this context the circular import is perfectly safe, so I've silenced it in #2515. |
@@ -242,11 +242,11 @@ def print_summary(self, *, options: "Options") -> Generator[None, None, None]: | |||
github_summary = self._github_step_summary(duration=duration, options=options) | |||
Path(summary_path).write_text(filter_ansi_codes(github_summary), encoding="utf-8") | |||
|
|||
n = len(self.summary) | |||
s = "s" if n > 1 else "" | |||
n_wheels = len([info for info in self.summary if not info.filename]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@neutrinoceros The not
here is looking wrong to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh my, definitely 🤦🏻♂️ I'll fix this in a minute
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#2517 👀
close #2511
disclaimer: I have not attempted to run tests locally yet (I have very limited battery at the moment), but I did run typechecking via
pre-commit
, which correctly caught a mistake in my initial iteration, so I'm reasonably confident in this patch.