-
Notifications
You must be signed in to change notification settings - Fork 159
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
Track/adjust for test failure with genno 1.23.0 #788
Comments
@glatterf42 my preferred temporarily mitigation here would be to install |
We currently have two failed tests, but when all tests first started failing, there was only one. This was on Saturday and I found these version changes:
On Sunday, the second test failure was introduced when some additional dependency updates came along:
|
The relevant changes in pytest might be detailed here: https://docs.pytest.org/en/stable/changelog.html#old-deprecations-are-now-errors |
Partially/temporarily addressed by #789. |
This should be addressed in genno 1.23.1, just released. |
(Apparently) with genno 1.23.0, we see failures like this:
This may actually be a regression in
genno
due to some housekeeping in khaeru/genno#115, that adapted AttrSeries.__init__ to address deprecation warnings with pandas 2.2. What appears to have happened is that the code now skips this block that ensures a pd.MultiIndex. Soobs
in this test, while functionally identical todemand
, has a different index class and thus fails assert_qty_equal().This fix is probably upstream, this is just to track.
The text was updated successfully, but these errors were encountered: