(Please CC me on replies since I'm not subscribed.)
Hi all,
Many thanks to everyone who offered suggestions as to what might be
going on with the regina-normal/arm crash that I wrote about in late
December / early January.
An update: It seems that the crash only appears in the presence of
comp
> Is Martin's box arm or armel?
Looks like armel (according to DEB_BUILD_ARCH and DEB_HOST_ARCH).
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi again,
Thanks for rescheduling another regina-normal/arm build. Unfortunately
it looks as though it crashed at the same point in the test suite as
last time.
I did try to reproduce this problem myself -- Martin Guy was good enough
to give me access to a box of his with enough oomph to actual
Hi,
The latest upload of regina-normal (4.4-1) is failing to build on arm
because of a crash in the test suite [1]. I tried to reproduce the
problem in the sid chroot on leisner.d.o, but I couldn't even get past
the first few files in the build:
g++: Internal error: Killed (program cc1plus)
Hi. Is it at all possible for someone to requeue magnus for an arm
rebuild with a very long timeout? I'd build it myself, except that
AFAICT none of the arm machines are available for general developer use.
The 4.1.1-beta-7 package was uploaded in April and still hasn't built
successfully on ar
Hi again.
The Boost.Python packages are currently broken on arm (#245893). Since
Boost.Python is a development library, this is in fact creating FTBFS
for kdeedu/arm and regina-normal/arm (the only two debian packages that
use libboost-python-dev, both of which I maintain).
I'd love to help fix
Hi. The buildds are failing to build magnus on arm, due to the _very_
large C++ file SA.C that needs to be compiled.
The last failure was with a 500 minute timeout; is it possible to retry
this with a much larger timeout? Based on past logs I have every reason
to believe that the magnus build w
Hi.. could someone please give magnus a rebuild on arm? It would be
great also if it could be rebuild with a longer inactivity timeout.
The C++ file on which it's timing out is *very* large, which is what's
caused the current build failure (from 22 April).
Actually, if there's some way of making
Hi. The magnus build is failing on arm due to 150 minutes of
inactivity, as reported in #200605.
The file on which it breaks (SA.o) is a *very* large C++ file. I
honestly believe that magnus will compile (as it has done on arm in the
past), given more time.
Rather than pull apart the Makfiles
9 matches
Mail list logo