| Subject: | some tests fails on dragonflybsd |
May I force install?
I've tried to run failed test:
lap# pwd
/root/.cpan/build/Gtk2-1.200-wEdAf1
lap# perl -Mblib t/GtkFileChooserButton.t
1..9
ok 1 - The object isa Gtk2::FileChooserButton
ok 2 - GInterface versus @ISA for Gtk2::FileChooserButton
ok 3 - The object isa Gtk2::FileChooserButton
ok 4 - The object isa Gtk2::FileChooser
ok 5 - The object isa Gtk2::FileChooserButton
ok 6 - The object isa Gtk2::FileChooser
ok 7
ok 8
ok 9
lap# perl -Mblib t/GtkFileChooserDialog.t
1..6
ok 1 - The object isa Gtk2::FileChooserDialog
ok 2 - GInterface versus @ISA for Gtk2::FileChooserDialog
ok 3
ok 4 - The object isa Gtk2::FileChooserDialog
ok 5 - The object isa Gtk2::FileChooser
ok 6
lap# perl -Mblib t/GtkFileChooserWidget.t
1..6
ok 1 - The object isa Gtk2::FileChooserWidget
ok 2 - GInterface versus @ISA for Gtk2::FileChooserWidget
ok 3
ok 4 - The object isa Gtk2::FileChooserWidget
ok 5 - The object isa Gtk2::FileChooser
ok 6
lap# perl -Mblib t/GtkSocket-GtkPlug.t
1..12
ok 1
ok 2
ok 3
ok 4 # skip new 2.14 stuff
ok 5 # skip new 2.14 stuff
The program 'GtkSocket-GtkPlug.t' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 184 error_code 3 request_code 149 minor_code 1)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
lap# perl -Mblib t/GtkSocket-GtkPlug.t --sync
1..12
ok 1
ok 2
ok 3
ok 4 # skip new 2.14 stuff
ok 5 # skip new 2.14 stuff
and it doens't end until I send a kill signal to it.
| Subject: | test_log.txt |
Message body is not shown because it is too large.