KalmanFilter gives wrong results on armhf

Bug #1819227 reported by Rebecca Palmer
This bug affects 1 person
Affects Status Importance Assigned to Milestone
statsmodels (Debian)
statsmodels (Ubuntu)

Bug Description

Test log:

(This is probably *not* a regression: upstream tests weren't run in 0.8.0-7.)

As noted in the changelog, I attempted to disable this feature on armhf as I'd rather have an explicit error than silent nonsense. However, as it was an arch-specific patch applied at build time to a part of the package that is arch:all, it made the build-time tests pass but didn't actually do anything to the as-installed package.

Revision history for this message
Graham Inggs (ginggs) wrote :

One option here is to ask in #ubuntu-release for this test failure to be ignored.

force-badtest statsmodels/0.8.0-9/armhf
added to

Another option is to detect the architecture and skip the tests at runtime, similar to what was done in debian/patches/deb_skip_test_ons390

Changed in statsmodels (Debian):
status: Unknown → New
Revision history for this message
Steve Langasek (vorlon) wrote :

the autopkgtests pass on armhf in recent releases.

Changed in statsmodels (Ubuntu):
status: New → Fix Released
Revision history for this message
Rebecca Palmer (rebecca-palmer) wrote :

It's _mostly_ fixed, but not completely: two variants of varmax
test_bse_oim, and test_pickle_fit_sarimax, still fail.

It's no longer a build failure as the affected tests are xfailed.

Changed in statsmodels (Ubuntu):
status: Fix Released → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.