-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Fix test_reduce_add_coalesced failure
#74027
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
CI Flow Status⚛️ CI FlowRuleset - Version:
|
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit c8a6c6b (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
Co-authored-by: Philip Meier <github.pmeier@posteo.de>
pmeier
left a comment
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.
Change looks good. Thanks @IvanYashchuk! Unfortunately, I have no idea how to verify this apart from doing it locally since the test seems to not be run in CI.
mruberry
left a comment
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.
Stamped! Thanks @IvanYashchuk
|
@mruberry has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: Recent change (#69751) introduced the requirement of using `.coalesce()` explicitly in the tests. Unfortunately, not all tests are run in the current CI configuration and one test failure slipped through. Fixes #74015. Pull Request resolved: #74027 Reviewed By: samdow Differential Revision: D34858112 Pulled By: mruberry fbshipit-source-id: 8904fac5e2b5335684a21f95a22646469478eb81
Recent change (#69751) introduced the requirement of using
.coalesce()explicitly in the tests. Unfortunately, not all tests are run in the current CI configuration and one test failure slipped through.Fixes #74015.