[Xapian-tickets] [Xapian] #767: Make testcases using different backends run in parallel

Xapian nobody at xapian.org
Tue Jul 31 21:35:47 BST 2018


#767: Make testcases using different backends run in parallel
--------------------+---------------------------
 Reporter:  gp1308  |             Owner:  gp1308
     Type:  task    |            Status:  new
 Priority:  normal  |         Milestone:
Component:  Other   |           Version:
 Severity:  normal  |        Resolution:
 Keywords:          |        Blocked By:
 Blocking:          |  Operating System:  All
--------------------+---------------------------

Comment (by gp1308):

 Updates about `leak summary` error mentioned in comment: All Valgrind
 errors are reported for backend `honey`.

 All erros are similar to the one below, I am not sure to which testcase
 this error is related, since outputs are mixed.

 {{{
 ==7621== 304 bytes in 1 blocks are possibly lost in loss record 64 of 70
 ==7621==    at 0x4C2EEF5: calloc (vg_replace_malloc.c:711)
 ==7621==    by 0x40112B2: allocate_dtv (in /usr/lib/ld-2.27.so)
 ==7621==    by 0x4011C3D: _dl_allocate_tls (in /usr/lib/ld-2.27.so)
 ==7621==    by 0x6B8DBAA: pthread_create@@GLIBC_2.2.5 (in
 /usr/lib/libpthread-2.27.so)
 ==7621==    by 0x5673E6F: ??? (in /usr/lib/librt-2.27.so)
 ==7621==    by 0x6B94A5E: __pthread_once_slow (in
 /usr/lib/libpthread-2.27.so)
 ==7621==    by 0x5672CDB: timer_create (in /usr/lib/librt-2.27.so)
 ==7621==    by 0x53B2B9F: TimeOut (matchtimeout.h:84)
 ==7621==    by 0x53B2B9F: ProtoMSet (protomset.h:159)
 ==7621==    by 0x53B2B9F: Matcher::get_local_mset(unsigned int, unsigned
 int, unsigned int, Xapian::Weight const&, Xapian::MatchDecider const*,
 Xapian::KeyMaker const*, unsigned int, unsigned int, int, double, double,
 Xapian::Enquire::docid_order, unsigned int,
 Xapian::Enquire::Internal::sort_setting, bool, double,
 std::vector<Xapian::Internal::opt_intrusive_ptr<Xapian::MatchSpy>,
 std::allocator<Xapian::Internal::opt_intrusive_ptr<Xapian::MatchSpy> > >
 const&) (matcher.cc:315)
 ==7621==    by 0x53B4611: Matcher::get_mset(unsigned int, unsigned int,
 unsigned int, Xapian::Weight::Internal&, Xapian::Weight const&,
 Xapian::MatchDecider const*, Xapian::KeyMaker const*, unsigned int,
 unsigned int, int, double, Xapian::Enquire::docid_order, unsigned int,
 Xapian::Enquire::Internal::sort_setting, bool, double,
 std::vector<Xapian::Internal::opt_intrusive_ptr<Xapian::MatchSpy>,
 std::allocator<Xapian::Internal::opt_intrusive_ptr<Xapian::MatchSpy> > >
 const&) (matcher.cc:440)
 ==7621==    by 0x528EDA8: Xapian::Enquire::Internal::get_mset(unsigned
 int, unsigned int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider
 const*) const (enquire.cc:327)
 ==7621==    by 0x528F293: Xapian::Enquire::get_mset(unsigned int, unsigned
 int, unsigned int, Xapian::RSet const*, Xapian::MatchDecider const*) const
 (enquire.cc:205)
 ==7621==    by 0x2462CB: test_matchtimelimit1() (api_postingsource.cc:657)
 ==7621==
 ==7621== 304 bytes in 1 blocks are possibly lost in loss record 65 of 70
 ==7621==    at 0x4C2EEF5: calloc (vg_replace_malloc.c:711)
 ==7621==    by 0x40112B2: allocate_dtv (in /usr/lib/ld-2.27.so)
 ==7621==    by 0x4011C3D: _dl_allocate_tls (in /usr/lib/ld-2.27.so)
 ==7621==    by 0x6B8DBAA: pthread_create@@GLIBC_2.2.5 (in
 /usr/lib/libpthread-2.27.so)
 ==7621==    by 0x5673D33: ??? (in /usr/lib/librt-2.27.so)
 ==7621==    by 0x6B8D0BB: start_thread (in /usr/lib/libpthread-2.27.so)
 ==7621==
 ==7621== LEAK SUMMARY:
 ==7621==    definitely lost: 0 bytes in 0 blocks
 ==7621==    indirectly lost: 0 bytes in 0 blocks
 ==7621==      possibly lost: 608 bytes in 2 blocks
 ==7621==    still reachable: 175,526 bytes in 68 blocks
 ==7621==         suppressed: 0 bytes in 0 blocks
 ==7621== Reachable blocks (those to which a pointer was found) are not
 shown.
 ==7621== To see them, rerun with: --leak-check=full --show-leak-kinds=all
 ==7621==
  304 bytes in 1 blocks are possibly lost in loss record 64 of 70

 }}}
 I tried running only backend `honey` in a separate process (using
 `-bhoney`) that gives no error. A single process might not trigger this
 error, but this is one observation.

--
Ticket URL: <https://trac.xapian.org/ticket/767#comment:4>
Xapian <https://xapian.org/>
Xapian



More information about the Xapian-tickets mailing list