[Gtk2-perl-bugs] [Bug 342444] 'make test' for Gnome2-Print-0.951 fails with "Can't locate object method "signal_connect" via package "Gnome2::Print::Dialog" at t/04.GnomePrintDialog.t line 32" message

[gnome-perl (bugzilla.gnome.org) <bug...@bu...>]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D342444
 gnome-perl | Gnome2::Print | Ver: unspecified





------- Comment #16 from muppet  2006-05-23 00:03 UTC -------
(In reply to comment #12)
> Well, it's not that simple - apparently something intercepts STDOUT
> and STDERR of the tests.
>=20
> Any simple way not to intercept STDOUT and STDERR ?

Perl's test suite traps STDOUT as part of its defined function.  The test
programs print out lines like "ok 1" and "not ok 4", possibly with commen=
ts
that give names to tests.  The test runner (invoked by the makefile) pars=
es all
of this output and collects statistitics about the tests.

STDERR is not intercepted.

When you run the test script by itself from the command line, STDOUT is n=
ot
intercepted, and you can see all of this status output.  This is what i w=
anted
to see.  To do this, you must go into the source tree after building, wit=
h the
same shell environment as was used to build, and execute the script with =
this
command:

   $perl -Mblib t/testscript.t

where $perl is the same interpreter used to build the code.  The -Mblib t=
ells
perl to prepend to its library search path the staging area in which the
uninstalled extension resides.


--=20
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=3Demail
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.