On 29/01/17 at 17:00 +0100, Michael Biebl wrote:
> Hi Lucas
>
> Am 29.01.2017 um 08:15 schrieb Lucas Nussbaum:
> > On 28/01/17 at 10:40 +0100, Michael Biebl wrote:
> >> The package built fine on the buildds just a couple of days ago. Do you
> >> have an idea how the aws build environment differs?
> >
> > No, sorry
>
> I had a closer look at the log files today. The relevant test failure
> messages are
>
> Assertion 'r >= 0 && u == expect' failed at
> ../src/test/test-calendarspec.c:78, function test_next(). Aborting.
>
> FAIL test-calendarspec (exit status: 134)
>
>
> Assertion 'timezone_is_valid("Europe/Berlin")' failed at
> ../src/test/test-time.c:165, function test_timezone_is_valid(). Aborting.
>
> FAIL test-time (exit status: 134)
>
>
> I vaguely remembered something about test-builds where tzdata was not
> installed. Creating a chroot without tzdata did produce the same test
> suite failure. So I assume the AWS build chroots do not have tzdata
> installed (whereas the official buildds do). Can you confirm that?
Yes, tzdata is no longer build-essential, and is not installed in the
chroot.
> If so, updating the wiki in that regard might help others to spot such
> an error more quickly (if they know certain packages are missing
> compared to a chroot that was created via debootstrap --variant=buildd)
Actually, I did a rebuild specifically for that some time ago (to file
all bugs in that category). I assume that something changed on the
systemd side, causing it to succeed some time ago, but to fail now.
Maybe that test is new?
Anyway, I added a note to the wiki.
Lucas
