On 30 November 2015 at 09:37, Edmund Grimley Evans wrote: | Source: quantlib | Version: 1.7-1 | User: [email protected] | Usertags: arm64 | | You've probably noticed that quantlib sometimes fails to build on the | arm64 builds: | | https://buildd.debian.org/status/logs.php?pkg=quantlib&arch=arm64 | | The symptoms are: | | make[4]: Entering directory '/«PKGBUILDDIR»/test-suite' | ... | make[4]: *** Deleting file 'quantlib-test-suite.log' | E: Caught signal ‘Terminated’: terminating immediately | ... | Build killed with signal TERM after 150 minutes of inactivity | | | There are two kinds of arm64 buildd at present: Juno and Mustang. On a | Mustang the build typically succeeds, but on a Juno it times out after | "150 minutes of inactivity". There were 332 minutes of inactivity when | I tried it on a different (possibly faster because the entire build | took only 8 hours) machine, so it's missing by a wide margin. | | Since there's currently no mechanism for getting particular packages | to be built by particular buildds you should probably for now just | disable the test suite on arm64 by adding "aarch64" in | https://sources.debian.net/src/quantlib/1.7-1/debian/rules/#L135
Yup. "Been there, done that" in the past dozen+ years for earlier arm, m68k, and others. Should we even consider not building at all? | Alternatively, you could modify the test so that it generates some | kind of output as it runs. A new line character every hour would | presumably be sufficient. (Without a new line other characters might | not get through the buffering so you shouldn't just print dots, for | example.) I do something like that on Travis when I invoke tests for my RQuantLib user of this library. At the source level this may be trickier unless boost-tests can emit some heartbeats... Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
