Another possibility: Use qemu to simulate the target arch... Needs usually a good portion of patience, but helped me a couple times already.
Paul Wise <[email protected]> schrieb: >On Thu, Jan 23, 2014 at 3:59 AM, L.C. Karssen wrote: > >> What I can't see is their exact error messages. This is because >automake >> by default runs tests in parallel and sends the output of the >individual >> tests to a file called test-suite.log. Is there a way to get access >to >> that file on the build machine? >> Or is there another way to find out why the checks fail (short of >> uploading a package where I run the tests serially and send output to >> the screen)? > >You can choose one in decreasing order of preference: > >Ask your sponsor to login to the porterboxen, do a build and send you >the results. > >https://db.debian.org/machines.cgi > >Get access to the porterboxen yourself, do a build and inspect the >results. > >https://dsa.debian.org/doc/guest-account/ > >Override dh_auto_test to output test-suite.log when it fails, reupload. > >> Please CC me in any replies as I'm not subscribed to this list. > >Done (I'm subscribed). -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
