Summary: | dev-perl/Search-Xapian-1.2.13.0: fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugs, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://tinderboxlogs.s3.amazonaws.com/tbamd64.excelsior.flameeyes.eu/dev-perl%3ASearch-Xapian-1.2.13.0%3A20130121-154232.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300119 |
Description
Diego Elio Pettenò (RETIRED)
2013-01-21 22:40:51 UTC
Johan, I'm not sure what to make of these failures. Should we assume this is against dev-libs/xapian-1.2.13? I'll look into it shortly, but if we can reproduce I'll talk to upstream about it. (In reply to comment #2) > Should we assume this is against dev-libs/xapian-1.2.13? I'll look into it > shortly, but if we can reproduce I'll talk to upstream about it. I tested FEATURES="test" emerge =dev-perl/Search-Xapian-1.2.13.0 and it tests fine for me with perl-5.12.4-r1. Note this was done on a tinderbox which sometimes produces false results. Let's just convince ourselves that nothing bad is happening here as far as Search-Xapian's functionality goes. I start to get pissed with this "false results" bullshit: # Failed test at t/10query.t line 37. # 'USAGE: Search::Xapian::Query->new('term') or Search::Xapian::Query->new(OP, <args>) at t/10query.t line 34. # ' # doesn't match '(?^:^USAGE: Search::Xapian::Query->new\('term'\) or Search::Xapian::Query->new\(OP, <args>\) at \S+/10query\.t line \d+$)' can you read? The regexp looks for: at \S+/10query\.t line \d+$)' while the output says: at t/10query.t line 34. THERE'S A FRIGGING DOT AT THE END OF THE LINE THAT IS NOT MATCHED. I suppose the problem is due to a different (~arch) Perl version that changed the output slightly. But seriously, I'll stop testing your stupid crappy packages if you keep up the "false results" bullshit. (In reply to comment #3) > (In reply to comment #2) > > Should we assume this is against dev-libs/xapian-1.2.13? I'll look into it > > shortly, but if we can reproduce I'll talk to upstream about it. > > I tested > > FEATURES="test" emerge =dev-perl/Search-Xapian-1.2.13.0 > > and it tests fine for me with perl-5.12.4-r1. Note this was done on a > tinderbox which sometimes produces false results. Let's just convince > ourselves that nothing bad is happening here as far as Search-Xapian's > functionality goes. The reduced case failure is this: use Test::More; BEGIN { plan tests => 1 }; use Search::Xapian qw(:standard); eval { Search::Xapian::Query->new("hello", 1, 2, 3, 4); }; ok(defined $@, "Bad query ctor threw exception"); (In reply to comment #4) > THERE'S A FRIGGING DOT AT THE END OF THE LINE THAT IS NOT MATCHED. I suppose > the problem is due to a different (~arch) Perl version that changed the > output slightly. I can (also) reproduce this with ~dev-lang/perl-5.16.1. Reporting upstream. > > But seriously, I'll stop testing your stupid crappy packages if you keep up > the "false results" bullshit. Thanks for your work. Upstream bug: http://trac.xapian.org/ticket/610 this has been fixed for a while upstream. |