Build python-gpy.powerpc64le-linux on master is broken.

  • Open
  • quality assurance status badge
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 19 Dec 2023 20:11
(name . bug-guix)(address . bug-guix@gnu.org)
87o7em3t3g.fsf@gmail.com
Hi,

cuirass@gnu.org (Cuirass) writes:

Toggle quote (6 lines)
> <p>The build <b>python-gpy.powerpc64le-linux</b> for specification <b>master</b> is
> broken. You can find the detailed information about this build <a
> href="https://ci.guix.gnu.org/build/2921270/details">here</a>.</p>
>
> https://ci.guix.gnu.org/build/2921270/details

One test is failing on this platform:

Toggle snippet (26 lines)
[...]
test_SparseGPRegression_rbf_white_kern_1d (GPy.testing.model_tests.GradientTests)
Testing the sparse GP regression with rbf kernel with white kernel on 1d data ... initializing Y
initializing inference method
adding kernel and likelihood as parameters
Adding Z as parameter
FAIL
[...]

======================================================================
FAIL: test_SparseGPRegression_rbf_white_kern_1d (GPy.testing.model_tests.GradientTests)
Testing the sparse GP regression with rbf kernel with white kernel on 1d data
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/guix-build-python-gpy-1.10.0.drv-0/GPy-1.10.0/GPy/testing/model_tests.py", line 788, in test_SparseGPRegression_rbf_white_kern_1d
self.check_model(rbf, model_type='SparseGPRegression', dimension=1)
File "/tmp/guix-build-python-gpy-1.10.0.drv-0/GPy-1.10.0/GPy/testing/model_tests.py", line 682, in check_model
self.assertTrue(m.checkgrad())
AssertionError: False is not true

----------------------------------------------------------------------
Ran 274 tests in 466.921s

FAILED (failures=1, skipped=3)

I've forwarded this report upstream in [0].


--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 67912@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 67912
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch