bug#35521: Mariadb test suite failures on x86_64-linux

2019-07-13 Thread Mark H Weaver
Hello again, > Could it be that you don't have enough disk space for this test? Do you > have the log file available still? I made another build attempt on my X200, this time logging the output of "df --si" every 10 seconds. The free space started at ~11 GB free and never went below 7 GB, but t

bug#35521: Mariadb test suite failures on x86_64-linux

2019-07-13 Thread Mark H Weaver
Hi Marius, > Could it be that you don't have enough disk space for this test? Do you > have the log file available still? Yes, I have not only the log file, but also the failed build directory. My log file contains the same error in the 'tokudb_bugs.mdev4533' test: mysqltest: At line 6: query

bug#35521: Mariadb test suite failures on x86_64-linux

2019-07-13 Thread Marius Bakke
Mark H Weaver writes: > Hi Marius, > >> Update: Berlin built mariadb twice on core-updates with this patch: >> >> --8<---cut here---start->8--- >> diff --git a/gnu/packages/databases.scm b/gnu/packages/databases.scm >> index 6bfeaad9a2..64bc0938b6 100644 >> ---

bug#35521: Mariadb test suite failures on x86_64-linux

2019-07-13 Thread Mark H Weaver
Earlier, I wrote: >> Mark, Chris: Can you try this change with MariaDB 10.1.40 and see if it >> works for you? > > I tried it, but it made no difference on my Thinkpad X200, which still > fails the same way as before with 10.1.38: > > Failing test(s): tokudb_bugs.mdev4533 I should clarify that

bug#36640: guix pull compile-files failure doesn't identify failed file

2019-07-13 Thread Robert Vollmert
Specifically, building guix-packages.drv locally, I got the output below. As far as I can tell, the problematic file’s name is not contained in the output at all. The file is certainly available where we call compile-file — no idea whether it would be better to print the filename while handling the

bug#35521: Mariadb test suite failures on x86_64-linux

2019-07-13 Thread Mark H Weaver
Hi Marius, > Update: Berlin built mariadb twice on core-updates with this patch: > > --8<---cut here---start->8--- > diff --git a/gnu/packages/databases.scm b/gnu/packages/databases.scm > index 6bfeaad9a2..64bc0938b6 100644 > --- a/gnu/packages/databases.scm > +

bug#36517: 'guix deploy' does not restart services

2019-07-13 Thread Jakob L. Kreuze
Heyo, Ludovic Courtès writes: > Oh, I see. To me that’s completely orthogonal to ‘guix deploy’ though, > in that ‘guix system reconfigure’ and ‘guix deploy’ should use the > same code for that. > > Thanks, > Ludo’. Yeah, I believe it would be safe to close this once the code for 'guix deploy' a

bug#36636: Tell users to update/reconfigure regularly

2019-07-13 Thread pelzflorian (Florian Pelz)
When installing Guix System from the iso image, users should be told to pull and reconfigure regularly. Even though it is mentioned in the manual, not everyone reads manuals. I believe Guix’ target users include inexperienced users who do not know that they should update and upgrade regularly. T

bug#36511: extraneous recompiles of scm files while editing gnu/packages/

2019-07-13 Thread Ludovic Courtès
Hello, Robert Vollmert skribis: > Things do seem to work stably with the patch, although I still don’t see an > improvement. I do repeatedly get the following warnings now, though they don’t > seem to break things: > > [ 75%] GUILEC guix/build/elm-build-system.go > warning: unknown warning typ