[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Checking build errors



Dear Tobias,


On 23-01-14 07:46, Tobias Frost wrote:
> Another possibility: Use qemu to simulate the target arch... Needs usually a good portion of patience, but helped me a couple times already.
> 

I'd been thinking about that too. I hoped there was a quicker/easier
solution :-).


Thanks,

Lennart.


> Paul Wise <pabs@debian.org> 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).
> 

-- 
-----------------------------------------------------------------
L.C. Karssen
Utrecht
The Netherlands

lennart@karssen.org
http://blog.karssen.org

Stuur mij aub geen Word of Powerpoint bestanden!
Zie http://www.gnu.org/philosophy/no-word-attachments.nl.html
------------------------------------------------------------------

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: