Bug#1001611: 1.30 FTBFS in debian/sid, segfaults when running self-tests after build

[Christian Ehrhardt]

Package: glom
Version:1.30.4-6.1+b4

Hi,
I've found that current glom if no change rebuilt in sid fails a lot
when running its self tests.
Please do note that this might - at least partially - be caused by [1]
which happens due to [2] not yet being fixed. But since neither of
those two reports contains the signatures I've seen I thought I better
report this as well. If OTOH eventually just the fix for the python
versions fixes all three bugs that is great, but if not we have proper
bugs to track each of them.

Many of the build time tests crash, but overall there are only two
different signatures.
For the curious I attached the full build log to this mail as bzip2.

First there is something related to initdb (might be a red herring, I
tried PG-13 / PG-14 both fail the same way) eventually leading to a
segfault.

```
 locale is not properly installed or configured.
initdb: error: cannot be run as root
Please log in (using, e.g., "su") as the (unprivileged) user that will
own the server process.
virtual Glom::ConnectionPoolBackends::Backend::InitErrors
Glom::ConnectionPoolBackends::PostgresSelfHosted::initialize(const
SlotProgress&, const Glib::ustring&, const Glib::ustring&, bool):
Error while attempting to create self-hosting database.
**
ERROR:tests/test_selfhosting_utils.cc:223:bool
test_create_and_selfhost_new_empty(Glom::Document&,
Glom::Document::HostingMode, const string&): assertion failed:
(initialized_errors ==
Glom::ConnectionPool::Backend::InitErrors::NONE)
Bail out! ERROR:tests/test_selfhosting_utils.cc:223:bool
test_create_and_selfhost_new_empty(Glom::Document&,
Glom::Document::HostingMode, const string&): assertion failed:
(initialized_errors ==
Glom::ConnectionPool::Backend::InitErrors::NONE)
Aborted (core dumped)
```


Then the other more directly points to a potential relation to [1][2]
with python related error messages.

```
./tests/python/test_python_execute_func
boost::python::api::object Glom::import_module(const char*):
boost::python::import() failed while importing module: glom_1_30
void Glom::ShowTrace(): Glom: Python Error:
Glib::ustring Glom::get_traceback(): traceback = 0
ModuleNotFoundError: No module named 'glom_1_30'

boost::python::api::object Glom::import_module(const char*): Glom: A
python import of a module failed: glom_1_30

** (process:3790001): WARNING **: 07:23:40.353: Could not import
python glom module.
**

ERROR:tests/python/test_python_execute_func.cc:48:int main():
assertion failed: (value.get_value_type() == GDA_TYPE_NUMERIC)
Bail out! ERROR:tests/python/test_python_execute_func.cc:48:int
main(): assertion failed: (value.get_value_type() == GDA_TYPE_NUMERIC)
Aborted (core dumped)
```

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956709

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: glom_1.30.4-6.1_amd64-2021-12-10T07:22:31Z.build.bz2
Type: application/x-bzip
Size: 121499 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20211213/15dd5bda/attachment-0001.bin>