Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output

Miklos Vajna <vmiklos -AT- suse.cz>
Mon, 23 Jul 2012 09:27:35 +0200

Hi Noel,

On Fri, Jul 20, 2012 at 10:54:04AM +0200, Noel Grandin <noel@peralex.com> wrote:

Ping?
Anybody have any ideas?
This is driving me nuts during my testing.


So - I think this has been already mentioned in this thread, to just
avoid the pain, the best is to run make check without DEBUGCCPUNIT=TRUE,
and if there is one failing test, then run just that test with this
option. This way it won't hang, and not running all tests in gdb will
make "make check" faster as well.

Miklos

Context

make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin
- Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Michael Meeks
  - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin
    - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Miklos Vajna
    - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Michael Meeks
      - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin
- Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin
  - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin
    - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Miklos Vajna
      - Re: make check with DEBUGCCPUNIT=TRUE is waiting for console output · Noel Grandin

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.