Bug#839444: libgda5: FTBFS: tests failures annotations:

Emilio Pozuelo Monfort pochu at debian.org
Mon Dec 12 19:12:00 UTC 2016


Hi Santiago,

On 21/10/16 17:32, Santiago Vila wrote:
> retitle 839444 libgda5: FTBFS sometimes (check_data_proxy fails)
> thanks
> 
> Hello Lucas.
> 
> You are reporting two different things here, this usually makes things
> more difficult to maintainers. It is usually a lot better to report
> different things in different reports.
> 
> This is what you reported first:
> 
>> ../../test-driver: line 107: 29666 Segmentation fault      "$@" > $log_file 2>&1
>> FAIL: check_data_proxy
> 
> Then you reported this:
> 
>> FAIL: test-input-parsers
> 
> Even if you can't reproduce the first failure anymore, I can,
> so I guess the failure happen randomly (see backtrace below).
> 
> If you don't mind, let's consider this to be the first thing you
> reported (which does not seem fixed) and please file a separate bug
> for the second issue regarding tzdata.
> 
> I'm retitling this bug to reflect the first problem only.
> 
> Thanks.
> 
> The backtrace I got:
> 
> #0  0x00007ff8af745fdf in raise () from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007ff8af74740a in abort () from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007ff8af783bd0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x00007ff8af789fa6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #4  0x00007ff8af78c3c1 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007ff8af78dd94 in malloc () from /lib/x86_64-linux-gnu/libc.so.6
> #6  0x00007ff8aa62b3b7 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #7  0x00007ff8aa5fbb98 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #8  0x00007ff8aa5fd720 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #9  0x00007ff8aa5fdcdf in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #10 0x00007ff8aa60352e in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #11 0x00007ff8aa68cc6d in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #12 0x00007ff8aa6918d2 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #13 0x00007ff8aa6957a7 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #14 0x00007ff8aa68be19 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #15 0x00007ff8aa68fb91 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #16 0x00007ff8aa6900ea in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #17 0x00007ff8aa6903d6 in sqlite3_prepare_v2 () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #18 0x00007ff8aa676543 in sqlite3_exec () from /usr/lib/x86_64-linux-gnu/libsqlite3.so
> #19 0x00007ff8b0307a70 in gda_vconnection_data_model_add (cnc=0x55efb4785a70, spec=<optimized out>, 
>     spec_free_func=spec_free_func at entry=0x7ff8b0306e40 <spec_destroy_func>, 
>     table_name=table_name at entry=0x7ff8b0324cce "proxy", error=error at entry=0x7fff499301c0)
>     at gda-vconnection-data-model.c:331
> #20 0x00007ff8b0307c07 in gda_vconnection_data_model_add_model (cnc=<optimized out>, model=model at entry=0x55efb47a76e0, 
>     table_name=table_name at entry=0x7ff8b0324cce "proxy", error=error at entry=0x7fff499301c0)
>     at gda-vconnection-data-model.c:256
> #21 0x00007ff8b028e893 in apply_filter_statement (proxy=proxy at entry=0x55efb4794900, error=error at entry=0x7fff499301c0)
>     at gda-data-proxy.c:3096
> #22 0x00007ff8b02945c9 in gda_data_proxy_set_filter_expr (proxy=0x55efb4794900, filter_expr=<optimized out>, 
> ---Type <return> to continue, or q <return> to quit---
>     error=0x7fff499301c0) at gda-data-proxy.c:3265
> #23 0x000055efb3616d1e in check_proxy_set_filter (proxy=<optimized out>, filter=0x55efb361b6a8 "countrycode = 'BGD'")
>     at check_data_proxy.c:1577
> #24 0x000055efb3617689 in do_test_common_read (proxy=0x55efb4794900) at check_data_proxy.c:769
> #25 0x000055efb361616a in main (argc=<optimized out>, argv=<optimized out>) at check_data_proxy.c:119

Unfortunately you're missing libc6-dbg and libsqlite3-0-dbg. Could you get a
backtrace with those, so that I can forward this upstream?

I tried a build to do it myself, but the tests pass here.

Thanks,
Emilio



More information about the pkg-gnome-maintainers mailing list