[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#58143] [PATCH 0/2] Update bloomberg-bde.
From: |
Maxim Cournoyer |
Subject: |
[bug#58143] [PATCH 0/2] Update bloomberg-bde. |
Date: |
Wed, 28 Sep 2022 15:10:20 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
Hello,
Greg Hogan <code@greghogan.com> writes:
> * gnu/packages/cpp.scm (bloomberg-bde): Update to 3.108.0.1.
> [source](origin): Update test deletion list.
> ---
> gnu/packages/cpp.scm | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
Oof, this took a long time to build, and eventually failed with one
test:
--8<---------------cut here---------------start------------->8---
s_baltst_testtaggedvalueutil = 0.05 sec*proc (1 test)
s_baltst_testtaggedvalueutil.t = 0.05 sec*proc (1 test)
Total Test time (real) = 922.80 sec
The following tests FAILED:
806 - bsls_timeutil.t (Failed)
Errors while running CTest
make: *** [Makefile:93: test] Error 8
Test suite failed, dumping logs.
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("test") exit-status: 2
term-signal: #f stop-signal: #f>
phase `check' failed after 923.9 seconds
command "make" "test" failed with status 2
builder for
`/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv'
failed with exit code 1
@ build-failed
/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv - 1
builder for
`/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv'
failed with exit code 1
derivation
'/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv'
offloaded to 'localhost' failed: build of
`/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv' failed
build of
/gnu/store/y608pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv failed
View build log at
'/var/log/guix/drvs/y6/08pbn2www99sxhvpa85jqkffh55jm6-bloomberg-bde-3.108.0.1.drv'.
--8<---------------cut here---------------end--------------->8---
Could you please report it upstream (if not already) and disable it?
Thank you,
Maxim