Hi both,
Thanks so much for doing this.
On 27.05.2024 19.49, Dr. Tobias Quathamer wrote:
Am 27.05.24 um 15:38 schrieb IOhannes m zmölnig (Debian GNU|Linux):
On 5/26/24 23:56, Dr. Tobias Quathamer wrote:
The package builds on my machine, although I had to disable a single
test for now. You'll find it in the newly created patch. Maybe you
have an idea what's causing the failure, so it can be fixed properly.
https://gramps-project.org/bugs/view.php?id=13305
i think this is just a wrong assumption on the side of the upstream
testsuite (shadowed by their workflows).
upstream evades this by ensuring that "~/.gramps/" is there before
running the tests (both in their GitHub action, and in their debian/
packaging).
i think that for now the proper resolution for the problem is to
simply do a `mkdir "$CURDIR)/build/.gramps` before running the tests.
(which i've now pushed to the 'experimental' branch)
Great, thanks! That's a cleaner approach.
as a sidenote: the testsuite now creates a *very* verbose buildlog
(~420MB).
is that ok?
gf,madsr
IOhannes
Hm, I guess that's because of the "--verbose" option when running the
tests. However, the buildlog has been similarly large in v5.1.6 as
well. Could that to be due to the switch from nosetest to unittest?
Maybe the --verbose option should be dropped? The buildlog gets
shrinked to 1.4 MB, but the tests are only displayed as dots.
Yes the build log is huge, and has been for a while. If you try and view
it in a browser it never loads!
I would be happy to turn the --verbose option off until it is needed one
day.
Regards,
Tobias
I will try and take a look this week. But if I fail, either of you are
welcome to lose patience, merge it to master, and upload it for me. :-)
Regards
Ross
