[Top][All Lists]

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

Re: [libredwg] Hydra progress report + invitation

From: Thien-Thi Nguyen
Subject: Re: [libredwg] Hydra progress report + invitation
Date: Fri, 20 Feb 2015 12:48:53 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

() Thien-Thi Nguyen <address@hidden>
() Sat, 27 Dec 2014 11:22:44 +0100

   () gagan <address@hidden>
   () Tue, 23 Dec 2014 22:33:47 +0530

      > [towards successful "make check"]

      Ping :)

   Pong!  I am still here.  I've added unit-testing/
   and am trying to get it to play nice w/ Automake (run from
   autoreconf, which in turn is run from top-level
   Here is the "warning" message:


   that somehow prevents Automake from proceeding properly to
   create file unit-testing/, as expected.  Hmmm.

OK, i have resolved this problem, and also added unit-testing/
to the "make check" flow (commits 4a16091111e and b8824d58216).

For me, "make check" now fails in unit-testing/ so all the XML
and Python failures don't even show up.  This is because in the
top-level var ‘SUBDIRS’, unit-testing appears early.

Anyway, thanks to everyone for your patience.  I think the major
infrastructure changes are in place such that the "make check"
failures can now be considered meaningful (rather than "due to
broken infrastructure", as before).  There will be other tweaks
going forward, of course, but anyway this lets me now turn to:

      libreDWG architectural changes thread.

   OK; will do. the other thread.  In the meantime, if knowledgable
hackers could (knowledgably) address the "make check" failures,
that would be really cool to this ignorant plumber.

Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]