subject:"Patchy report"

Patchy report

2012-12-13 Thread grenouille

22:58:02 (UTC) Begin LilyPond compile, previous commit at   
bad0e5f6c8a3e5a40284e4120cb9753b77a8d7b3
22:58:11 Another instance (PID 32424) is already running.
23:28:21 Another instance (PID 32424) is already running.
23:58:34 From git.savannah.gnu.org:/srv/git/lilypond
   39f14fb..cb05c49  translation -> translation
23:59:15 Merged staging, now at:bad0e5f6c8a3e5a40284e4120cb9753b77a8d7b3
23:59:18Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
00:00:05Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
00:00:15Success:sudo -u lilybuild nice make clean
00:17:14Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:39:58Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
03:07:49 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  bad0e5f6c8a3e5a40284e4120cb9753b77a8d7b3
03:07:49 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
03:07:49 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-12-10 Thread grenouille

22:58:02 (UTC) Begin LilyPond compile, previous commit at   
ad43ff26f5ac375cfb70a2238a3cb770e4854936
22:58:47 Merged staging, now at:ad43ff26f5ac375cfb70a2238a3cb770e4854936
22:58:51Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:59:24Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:59:34Success:sudo -u lilybuild nice make clean
23:16:31Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:31:09 *** FAILED BUILD ***
sudo -u lilybuild nice make test -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  ad43ff26f5ac375cfb70a2238a3cb770e4854936
23:31:09 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
23:31:09 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 323, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report

2012-11-14 Thread John Mandereau

Il giorno mar, 13/11/2012 alle 23.32 +, grenoui...@lilynet.net ha
scritto:
> 22:58:02 (UTC) Begin LilyPond compile, previous commit at 
> f0cd2f7e65a3af000a6001298fd820dda85f6d7a
> 22:58:20 Merged staging, now at:  f0cd2f7e65a3af000a6001298fd820dda85f6d7a
> 22:58:22  Success:sudo -u lilybuild ./autogen.sh 
> --noconfigure
> 22:59:00  Success:sudo -u lilybuild 
> /home/lilybuild/staging/configure --disable-optimising
> 22:59:09  Success:sudo -u lilybuild nice make clean
> 23:16:11  Success:sudo -u lilybuild nice make -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 23:32:10 *** FAILED BUILD ***
>   sudo -u lilybuild nice make test -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>   Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
>   Current broken commit:  f0cd2f7e65a3af000a6001298fd820dda85f6d7a
> 23:32:10 *** FAILED STEP ***
>   merge from staging
>   Failed runner: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file 
> log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
> 23:32:10 Traceback (most recent call last):
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 523, in handle_staging
> self.build (issue_id=issue_id)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 323, in build
> issue_id)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 266, in runner
> raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
> this_logfilename))
> FailedCommand: Failed runner: sudo -u lilybuild nice make test -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> See the log file 
> log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

FWIW that time it was a random segfault on some reg test; as the build
passed last time, I won't investigate that crash by looking at LilyPond
code.

-- 
John Mandereau 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-13 Thread grenouille

22:58:02 (UTC) Begin LilyPond compile, previous commit at   
f0cd2f7e65a3af000a6001298fd820dda85f6d7a
22:58:20 Merged staging, now at:f0cd2f7e65a3af000a6001298fd820dda85f6d7a
22:58:22Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:59:00Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:59:09Success:sudo -u lilybuild nice make clean
23:16:11Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:32:10 *** FAILED BUILD ***
sudo -u lilybuild nice make test -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  f0cd2f7e65a3af000a6001298fd820dda85f6d7a
23:32:10 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
23:32:10 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 323, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-test--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-12 Thread grenouille

22:58:02 (UTC) Begin LilyPond compile, previous commit at   
f0cd2f7e65a3af000a6001298fd820dda85f6d7a
22:58:09 From git.savannah.gnu.org:/srv/git/lilypond
   bba1403..f0cd2f7  master -> master
22:58:18 Merged staging, now at:f0cd2f7e65a3af000a6001298fd820dda85f6d7a
22:58:20Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:58:49Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:58:59Success:sudo -u lilybuild nice make clean
23:15:55Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:38:02Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:16:13 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  f0cd2f7e65a3af000a6001298fd820dda85f6d7a
00:16:13 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:16:13 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-11 Thread grenouille

22:58:01 (UTC) Begin LilyPond compile, previous commit at   
19033189f6f38fbd5dac798f151ede79fcad657e
22:58:30 Merged staging, now at:19033189f6f38fbd5dac798f151ede79fcad657e
22:58:33Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:59:11Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:59:24Success:sudo -u lilybuild nice make clean
23:16:19Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:38:06Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:16:20 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  19033189f6f38fbd5dac798f151ede79fcad657e
00:16:20 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:16:20 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-09 Thread grenouille

22:58:01 (UTC) Begin LilyPond compile, previous commit at   
a49f2bc12dc1ebf3de6da4573c3b296643d27e40
22:58:08 From git.savannah.gnu.org:/srv/git/lilypond
 * [new tag] release/2.16.1-1 -> release/2.16.1-1
22:58:17 Merged staging, now at:a49f2bc12dc1ebf3de6da4573c3b296643d27e40
22:58:19Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:58:48Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:58:58Success:sudo -u lilybuild nice make clean
23:15:57Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:37:45Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:15:44 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  a49f2bc12dc1ebf3de6da4573c3b296643d27e40
00:15:44 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:15:44 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-08 Thread grenouille

22:58:01 (UTC) Begin LilyPond compile, previous commit at   
823403a0718dfdf09124089ce1b32763ca6f4cf1
22:58:10 From git.savannah.gnu.org:/srv/git/lilypond
   823403a..a49f2bc  master -> master
   823403a..a49f2bc  staging-> staging
22:58:19 Merged staging, now at:a49f2bc12dc1ebf3de6da4573c3b296643d27e40
22:58:21Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:58:53Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:59:03Success:sudo -u lilybuild nice make clean
23:16:36Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:38:34Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:16:40 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  a49f2bc12dc1ebf3de6da4573c3b296643d27e40
00:16:40 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:16:40 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-11-07 Thread grenouille

22:58:01 (UTC) Begin LilyPond compile, previous commit at   
823403a0718dfdf09124089ce1b32763ca6f4cf1
22:58:30 Merged staging, now at:823403a0718dfdf09124089ce1b32763ca6f4cf1
22:58:36Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:59:14Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:59:26Success:sudo -u lilybuild nice make clean
23:16:22Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:38:13Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:16:18 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   bacfb43c79623bf26bd59187a6d8e7ea1b9557e2
Current broken commit:  823403a0718dfdf09124089ce1b32763ca6f4cf1
00:16:18 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:16:18 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread David Kastrup

Francisco Vila  writes:

> 2012/10/22 Francisco Vila :
>> 2012/10/22 David Kastrup :
>>> In Documentation/es/notation/text.itely I find
>>>
>>> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
>>> cabeceras}.
>>>
>>> (the ref being distributed across two lines, so easy to miss using
>>> grep).
>>>
>>> Maybe that is the problem?
>>
>> Yes. I'm sorry. That's why @ref arguments should not break across lines.
>
> A quick patch that fixes it. Please apply it or wait until tonight.

Pushed.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Francisco Vila

2012/10/22 Francisco Vila :
> 2012/10/22 David Kastrup :
>> In Documentation/es/notation/text.itely I find
>>
>> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
>> cabeceras}.
>>
>> (the ref being distributed across two lines, so easy to miss using
>> grep).
>>
>> Maybe that is the problem?
>
> Yes. I'm sorry. That's why @ref arguments should not break across lines.

A quick patch that fixes it. Please apply it or wait until tonight.
-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
From 7cb7c6f3ecf35829f4202cbb2ab377bf54e8720f Mon Sep 17 00:00:00 2001
From: Francisco Vila 
Date: Mon, 22 Oct 2012 11:39:01 +0200
Subject: [PATCH] Doc-es: fix xref.

---
 Documentation/es/notation/text.itely |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/es/notation/text.itely b/Documentation/es/notation/text.itely
index 8c4bc28..4462a6b 100644
--- a/Documentation/es/notation/text.itely
+++ b/Documentation/es/notation/text.itely
@@ -20,8 +20,8 @@ formateo) en las partituras.
 
 @noindent
 Ciertos elementos de texto de los que no nos ocupamos aquí se tratan
-en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
-cabeceras}.
+en otras secciones específicas: @ref{Música vocal},
+@ref{Títulos y encabezamientos}.
 
 @menu
 * Escritura del texto::
-- 
1.7.2.5

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Francisco Vila

2012/10/22 David Kastrup :
> In Documentation/es/notation/text.itely I find
>
> en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
> cabeceras}.
>
> (the ref being distributed across two lines, so easy to miss using
> grep).
>
> Maybe that is the problem?

Yes. I'm sorry. That's why @ref arguments should not break across lines.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread David Kastrup

Francisco Vila  writes:

> 2012/10/22 Federico Bruni :
>>> *** Undefined node `Títulos y cabeceras' in @ref (in
>>> out-www/notation/editorial.texi l. 1293 in @funindex)
>>> Max error number exceeded
>>
>> this should be the error which makes the build fail
>
> Wait half a moment: there is no @ref{Títulos y cabeceras} in
> Documentation/es/notation/editorial.itely
>
> and git grep "Títulos y cabeceras" gives no occurrence but an entry in
> Documentation/po/es.po
>
> I think that error is caused by and old texi file left out in out-www
> . A clean doc build should not show this error.
>
> Am I missing something?

I did "make clean".

In Documentation/es/notation/text.itely I find

en otras secciones específicas: @ref{Música vocal}, @ref{Títulos y
cabeceras}.

(the ref being distributed across two lines, so easy to miss using
grep).

Maybe that is the problem?

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Francisco Vila

2012/10/22 Federico Bruni :
>> *** Undefined node `Títulos y cabeceras' in @ref (in
>> out-www/notation/editorial.texi l. 1293 in @funindex)
>> Max error number exceeded
>
> this should be the error which makes the build fail

Wait half a moment: there is no @ref{Títulos y cabeceras} in
Documentation/es/notation/editorial.itely

and git grep "Títulos y cabeceras" gives no occurrence but an entry in
Documentation/po/es.po

I think that error is caused by and old texi file left out in out-www
. A clean doc build should not show this error.

Am I missing something?

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Federico Bruni

2012/10/22 Phil Holmes :
> WARNING: Unable to find node 'Alturas' in book snippets.
> WARNING: Unable to find node 'Alturas' in book snippets.
> [snip]
> WARNING: Unable to find node 'Anotaciones editoriales' in book snippets.

That's issue 2266.
I added some comments in August with some hints about the problems..
It would be nice to fix it, but I think it's a build bug... muddy waters...

> *** Undefined node `Títulos y cabeceras' in @ref (in
> out-www/notation/editorial.texi l. 1293 in @funindex)
> Max error number exceeded

this should be the error which makes the build fail

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Francisco Vila

2012/10/22 Francisco Vila :
> Yes the warnings are harmless but the undefined node is a real
> problem. I did some node renaming yesterday. My fault probably. In
> 12--14 hours I will have some time and will fix it.

BTW I am trying to do some translations at work, but I am behind a
stupid and slow corporate wifi and git clone says

Receiving objects:  91% (321716/351428), 83.77 MiB | 11 KiB/s

for two hours'  time already.
-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Francisco Vila

2012/10/22 Phil Holmes :
> grenoui...@lilynet.net writes:
> WARNING: Unable to find node 'Alturas' in book snippets.
> [snip]
>
> WARNING: Unable to find node 'Anotaciones editoriales' in book snippets.
> *** Undefined node `Títulos y cabeceras' in @ref (in
> out-www/notation/editorial.texi l. 1293 in @funindex)
> Max error number exceeded

>
> AFAIK those type of warnings have always been there and have never prevented
> a successful build.  Perhaps there used to be just fewer than 999 and now
> there are just over 1000?

Yes the warnings are harmless but the undefined node is a real
problem. I did some node renaming yesterday. My fault probably. In
12--14 hours I will have some time and will fix it.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread Phil Holmes

- Original Message - 
From: "David Kastrup" 

To: 
Sent: Monday, October 22, 2012 9:12 AM
Subject: Re: Patchy report


grenoui...@lilynet.net writes:

01:00:02 (UTC) Begin LilyPond compile, previous commit at 
7df3f88192dbfc331aba1e06e7114794a1e1209a

01:00:16 From git.savannah.gnu.org:/srv/git/lilypond
   71827c7..7270930  master -> master
   7df3f88..f5c01cc  translation -> translation
01:00:16 Another instance (PID 11935) is already running.
01:30:24 Another instance (PID 11935) is already running.
02:00:31 Another instance (PID 11935) is already running.
02:31:29 Merged translation, now at: 
f5c01cc2221a5dc56c463de50275e4a6f2d69b8f

02:31:32 Success: sudo -u lilybuild ./autogen.sh --noconfigure
02:32:14 Success: sudo -u lilybuild 
/home/lilybuild/translation/configure --disable-optimising

02:32:34 Success: sudo -u lilybuild nice make clean
02:49:11 Success: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
03:08:43 Success: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1

05:36:07 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit: 2784264fda1124e0db8fb9b1385905e48e2650b9
Current broken commit: f5c01cc2221a5dc56c463de50275e4a6f2d69b8f
05:36:07 *** FAILED STEP ***
build translation
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-translation-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

05:36:07 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 591, in build_branch

self.build (patch_prepare=patch_prepare, issue_id=self.branch)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build

issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % 
(command, this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
See the log file 
log-translation-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt


WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
[snip]
WARNING: Unable to find node 'Anotaciones editoriales' in book snippets.
*** Undefined node `Títulos y cabeceras' in @ref (in 
out-www/notation/editorial.texi l. 1293 in @funindex)

Max error number exceeded


--
David Kastrup


AFAIK those type of warnings have always been there and have never prevented 
a successful build.  Perhaps there used to be just fewer than 999 and now 
there are just over 1000?


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-10-22 Thread David Kastrup

grenoui...@lilynet.net writes:

> 01:00:02 (UTC) Begin LilyPond compile, previous commit at 
> 7df3f88192dbfc331aba1e06e7114794a1e1209a
> 01:00:16 From git.savannah.gnu.org:/srv/git/lilypond
>71827c7..7270930  master -> master
>7df3f88..f5c01cc  translation -> translation
> 01:00:16 Another instance (PID 11935) is already running.
> 01:30:24 Another instance (PID 11935) is already running.
> 02:00:31 Another instance (PID 11935) is already running.
> 02:31:29 Merged translation, now at:  f5c01cc2221a5dc56c463de50275e4a6f2d69b8f
> 02:31:32  Success:sudo -u lilybuild ./autogen.sh 
> --noconfigure
> 02:32:14  Success:sudo -u lilybuild 
> /home/lilybuild/translation/configure --disable-optimising
> 02:32:34  Success:sudo -u lilybuild nice make clean
> 02:49:11  Success:sudo -u lilybuild nice make -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 03:08:43  Success:sudo -u lilybuild nice make test -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 05:36:07 *** FAILED BUILD ***
>   sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>   Previous good commit:   2784264fda1124e0db8fb9b1385905e48e2650b9
>   Current broken commit:  f5c01cc2221a5dc56c463de50275e4a6f2d69b8f
> 05:36:07 *** FAILED STEP ***
>   build translation
>   Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file 
> log-translation-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
> 05:36:07 Traceback (most recent call last):
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 591, in build_branch
> self.build (patch_prepare=patch_prepare, issue_id=self.branch)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 328, in build
> issue_id)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 266, in runner
> raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
> this_logfilename))
> FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file 
> log-translation-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Clave' in book internals.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Tesitura' in book internals.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Alturas' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'slurs' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Notación de los pentagramas' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Duraciones' in book snippets.
WARNING: Unable to find node 'Expresiones' in book snippets.
WARNING: Unable to fi

Re: [Lilypond-auto] Patchy report

2012-10-09 Thread John Mandereau

Il giorno mar, 09/10/2012 alle 09.57 +0200, David Kastrup ha scritto:
> John Mandereau  writes:
> 
> > Hi,
> >
> > I quote some of the logs below...
> > Il giorno mar, 09/10/2012 alle 00.33 +, grenoui...@lilynet.net ha
> > scritto:
> >> 21:58:01 (UTC) Begin LilyPond compile, previous commit at  
> >> c7a3623a056891d48b13fe14fd6ee042ac666822
> >> 21:58:27 Merged staging, now at:   c7a3623a056891d48b13fe14fd6ee042ac666822
> >> 21:58:29   Success:sudo -u lilybuild ./autogen.sh 
> >> --noconfigure
> >> 21:59:05   Success:sudo -u lilybuild 
> >> /home/lilybuild/staging/configure --disable-optimising
> >> 21:59:15   Success:sudo -u lilybuild nice make clean
> >> 22:16:12   Success:sudo -u lilybuild nice make -j2 
> >> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >> 22:38:05   Success:sudo -u lilybuild nice make test -j2 
> >> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >> 00:33:31 *** FAILED BUILD ***
> >>sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> >>Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
> 
> That's several weeks ago.

Indeed, this is crazy, because you can see on lilypond-auto list that
Patchy successfully built the same Git committish
c7a3623a056891d48b13fe14fd6ee042ac666822 one day ago.


> indicates that it has not changed at all in the (considerable) time span
> involved.  Either your build system, your version of Patchy, or your
> hardware is broken.

This could be well a hardware problem (again).  The system administrator
of the MSHPN may propose a replacement computer this month or in
November.

John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report

2012-10-09 Thread David Kastrup

John Mandereau  writes:

> Hi,
>
> I quote some of the logs below...
> Il giorno mar, 09/10/2012 alle 00.33 +, grenoui...@lilynet.net ha
> scritto:
>> 21:58:01 (UTC) Begin LilyPond compile, previous commit at
>> c7a3623a056891d48b13fe14fd6ee042ac666822
>> 21:58:27 Merged staging, now at: c7a3623a056891d48b13fe14fd6ee042ac666822
>> 21:58:29 Success:sudo -u lilybuild ./autogen.sh 
>> --noconfigure
>> 21:59:05 Success:sudo -u lilybuild 
>> /home/lilybuild/staging/configure --disable-optimising
>> 21:59:15 Success:sudo -u lilybuild nice make clean
>> 22:16:12 Success:sudo -u lilybuild nice make -j2 
>> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>> 22:38:05 Success:sudo -u lilybuild nice make test -j2 
>> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>> 00:33:31 *** FAILED BUILD ***
>>  sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>>  Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb

That's several weeks ago.

>>  Current broken commit:  c7a3623a056891d48b13fe14fd6ee042ac666822

> logfile lilypond-multi-run-1.log (exit 1):
> Processing `/home/lilybuild/build-staging/out/lybook-db/e2/lily-19b5eb79.ly'
> Parsing...
> Interpreting
> music.../home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
> In expression (ly:context-property context (quote keySignature)):
> /home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
> Unbound variable: ly:context-property
> logfile lilypond-multi-run-0.log (exit 1):
> Processing `/home/lilybuild/build-staging/out/lybook-db/6a/lily-e9632604.ly'
> Parsing...
> Interpreting
> music.../home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
> In expression (ly:context-property context (quote keySignature)):
> /home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
> Unbound variable: ly:context-property
> fatal error: Children (1 0) exited with errors.

git grep ly:context-property c7a3623a056891d48b13fe14fd6ee042ac666822

[...]
c7a3623a056891d48b13fe14fd6ee042ac666822:lily/context-scheme.cc:LY_DEFINE 
(ly_context_property, "ly:context-property",
[...]

This is defined just fine.  In fact,

git log 
6addf21b5bc485d30e63bf2f04d371c10b902cdb..c7a3623a056891d48b13fe14fd6ee042ac666822
 lily/context-scheme.cc

indicates that it has not changed at all in the (considerable) time span
involved.  Either your build system, your version of Patchy, or your
hardware is broken.

I'd have guessed that possibly the wrong dependencies are autogenerated,
but lily/context-scheme.cc has not changed its location one bit.

-- 
David Kastrup


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report

2012-10-08 Thread John Mandereau

Hi,

I quote some of the logs below...
Il giorno mar, 09/10/2012 alle 00.33 +, grenoui...@lilynet.net ha
scritto:
> 21:58:01 (UTC) Begin LilyPond compile, previous commit at 
> c7a3623a056891d48b13fe14fd6ee042ac666822
> 21:58:27 Merged staging, now at:  c7a3623a056891d48b13fe14fd6ee042ac666822
> 21:58:29  Success:sudo -u lilybuild ./autogen.sh 
> --noconfigure
> 21:59:05  Success:sudo -u lilybuild 
> /home/lilybuild/staging/configure --disable-optimising
> 21:59:15  Success:sudo -u lilybuild nice make clean
> 22:16:12  Success:sudo -u lilybuild nice make -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 22:38:05  Success:sudo -u lilybuild nice make test -j2 
> CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> 00:33:31 *** FAILED BUILD ***
>   sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>   Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
>   Current broken commit:  c7a3623a056891d48b13fe14fd6ee042ac666822
> 00:33:31 *** FAILED STEP ***
>   merge from staging
>   Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file 
> log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
> 00:33:31 Traceback (most recent call last):
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 523, in handle_staging
> self.build (issue_id=issue_id)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 328, in build
> issue_id)
>   File 
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 266, in runner
> raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
> this_logfilename))
> FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file 
> log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

$ tail 
/opt/buildroot-sid/home/lilybuild/lilypond-log/log-staging-nice-make-doc--j2-CPU_COUNT\=2-ANTI_ALIAS_FACTOR\=1.txt
 

Please see 
/home/lilybuild/build-staging/out/lybook-db/snippet-names--155810202.log

make[3]: *** [out-www/essay.texi] Error 1
make[3]: Leaving directory `/home/lilybuild/build-staging/Documentation/de'
make[2]: *** [WWW-1] Error 2
make[2]: Leaving directory `/home/lilybuild/build-staging/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/lilybuild/build-staging'
make: *** [doc-stage-1] Error 2
jmandereau@srv-lilypond:~$ tail -n50 
/opt/buildroot-sid/home/lilybuild/build-staging/out/lybook-db/snippet-names--155810202.log

Forking into jobs:  (28679 28678)
logfile lilypond-multi-run-1.log (exit 1):
Processing `/home/lilybuild/build-staging/out/lybook-db/e2/lily-19b5eb79.ly'
Parsing...
Interpreting 
music.../home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
 In expression (ly:context-property context (quote keySignature)):
/home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
 Unbound variable: ly:context-property
logfile lilypond-multi-run-0.log (exit 1):
Processing `/home/lilybuild/build-staging/out/lybook-db/6a/lily-e9632604.ly'
Parsing...
Interpreting 
music.../home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
 In expression (ly:context-property context (quote keySignature)):
/home/lilybuild/build-staging/out/share/lilypond/current/scm/music-functions.scm:1599:18:
 Unbound variable: ly:context-property
fatal error: Children (1 0) exited with errors.


-- 
John Mandereau 


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-10-08 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
c7a3623a056891d48b13fe14fd6ee042ac666822
21:58:27 Merged staging, now at:c7a3623a056891d48b13fe14fd6ee042ac666822
21:58:29Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:05Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:15Success:sudo -u lilybuild nice make clean
22:16:12Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
22:38:05Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:33:31 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
Current broken commit:  c7a3623a056891d48b13fe14fd6ee042ac666822
00:33:31 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:33:31 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-10-06 Thread grenouille

21:58:02 (UTC) Begin LilyPond compile, previous commit at   
c3656fce28382903c7d2c18500f74e624e4a
21:58:12 From git.savannah.gnu.org:/srv/git/lilypond
 * [new tag] release/2.17.4-1 -> release/2.17.4-1
21:58:12 Another instance (PID 29551) is already running.
22:29:01 Merged staging, now at:c3656fce28382903c7d2c18500f74e624e4a
22:29:04Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:29:43Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:29:53Success:sudo -u lilybuild nice make clean
22:45:17Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:07:22Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
01:42:12 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
Current broken commit:  c3656fce28382903c7d2c18500f74e624e4a
01:42:12 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
01:42:12 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-10-04 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
38a4081efa4a8ee2f5da780ca0ed2991627afc46
21:58:13 From git.savannah.gnu.org:/srv/git/lilypond
   66f9cbc..e5a609e  translation -> translation
21:58:30 Merged staging, now at:38a4081efa4a8ee2f5da780ca0ed2991627afc46
21:58:32Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:10Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:23Success:sudo -u lilybuild nice make clean
22:14:43Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
22:36:49Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:21:55 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
Current broken commit:  38a4081efa4a8ee2f5da780ca0ed2991627afc46
23:21:55 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
23:21:55 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-09-27 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
9de1c7467d9fceec1150156236b50bd7c668185a
21:58:23 Merged staging, now at:9de1c7467d9fceec1150156236b50bd7c668185a
21:58:27Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:05Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:15Success:sudo -u lilybuild nice make clean
22:00:36 *** FAILED BUILD ***
sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   6addf21b5bc485d30e63bf2f04d371c10b902cdb
Current broken commit:  9de1c7467d9fceec1150156236b50bd7c668185a
22:00:36 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
22:00:36 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 311, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-09-18 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
6addf21b5bc485d30e63bf2f04d371c10b902cdb
21:58:27 Merged staging, now at:6addf21b5bc485d30e63bf2f04d371c10b902cdb
21:58:32Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:12Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:25Success:sudo -u lilybuild nice make clean
22:14:48Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
22:36:51Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
01:33:37Success:sudo -u lilybuild nice make doc -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
01:34:03 *** FAILED STEP ***
merge from staging
Command '['git', 'fetch']' returned non-zero exit status 128
ssh: connect to host git.savannah.gnu.org port 22: Connection timed out
fatal: The remote end hung up unexpectedly
01:34:03 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 525, in handle_staging
self.merge_push ()
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 464, in merge_push
run ("git fetch")
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 105, in run
raise FailedCommand ("Command '%s' returned non-zero exit status %d\n%s" % 
(cmd, returncode, stderr.strip ()))
FailedCommand: Command '['git', 'fetch']' returned non-zero exit status 128
ssh: connect to host git.savannah.gnu.org port 22: Connection timed out
fatal: The remote end hung up unexpectedly
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-09-07 Thread grenouille

21:58:02 (UTC) Begin LilyPond compile, previous commit at   
4c1b3e32059b558b9e1c1c25268b7639aef687d4
21:58:10 Another instance (PID 4988) is already running.
22:28:28 Merged staging, now at:4c1b3e32059b558b9e1c1c25268b7639aef687d4
22:28:30Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
22:29:06Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
22:29:16Success:sudo -u lilybuild nice make clean
22:44:35Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
23:06:08Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
00:31:21 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   
Current broken commit:  4c1b3e32059b558b9e1c1c25268b7639aef687d4
00:31:21 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
00:31:21 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-09-06 Thread grenouille

21:58:02 (UTC) Begin LilyPond compile, previous commit at   
3cd24002639b7b48a9f0c7245101bdb721ce21c0
21:58:32 Merged staging, now at:3cd24002639b7b48a9f0c7245101bdb721ce21c0
21:58:34Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:01Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:11Success:sudo -u lilybuild nice make clean
21:59:13 *** FAILED BUILD ***
sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   
Current broken commit:  3cd24002639b7b48a9f0c7245101bdb721ce21c0
21:59:13 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
21:59:13 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 311, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-31 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
236559061d0c32fcbe39492dcb444e41f2804145
21:58:14 From git.savannah.gnu.org:/srv/git/lilypond
   2365590..38b4799  master -> master
   2365590..38b4799  staging-> staging
21:58:14 Warning: exception occured while looking for other running Patchy 
instances: invalid literal for int() with base 10: ''
21:58:14 *** FAILED STEP ***
merge from staging
Command '['git', 'branch', 'test-master-lock', 'master']' returned 
non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.
21:58:14 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 492, in merge_branch
self.merge_git_branch (branch, **kwargs)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 447, in merge_git_branch
raise e
FailedCommand: Command '['git', 'branch', 'test-master-lock', 'master']' 
returned non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-08-31 Thread John Mandereau

Il giorno ven, 31/08/2012 alle 11.10 +0200, David Kastrup ha scritto:
> Some of the recent reports from Grenouille actually might suggest that
> it might be testing against an unrelated test-baseline.

Patchy currently doesn't check, and AFAIK has never checked, whether
master branch has changed between patches tests, so with the build speed
of Grenouille this issue may well have make this issue apparent in some
case.


>   Perhaps you are
> taking wrong shortcuts,

I have taken care in trying to deal with this, but there might be a bug.
Patchy is supposed to verify whether the test-baseline is up to date by
computing the SHA1 sum of the git committish of current master
(test-patches.py pulls just after having downloaded patches) plus the
contents of all files in out-test-baseline directories.  Perhaps  the
file names should be added in this checksum?


>  or are mixing up in-place and out-of-place
> builds

All builds in Patchy are done from a bare git repository, nobody builds
LilyPond manually in the chroot where Patchy runs, and now Patchy does
completely out-of-source builds.


>  or storing your test-baseline in a different place you read it
> from again?

out-test-baselines are never moved away and back by Patchy, so if you
don't simulteneously change the build directory in the configuration
file and move that build directory manually accordingly, that doesn't
happen.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-08-31 Thread David Kastrup

John Mandereau  writes:

> Il giorno ven, 31/08/2012 alle 00.38 +0200, David Kastrup ha scritto:
>> grenoui...@lilynet.net writes:
>> 
>> > 21:58:01 (UTC) Begin LilyPond compile, previous commit at  
>> > e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 21:58:15 From git.savannah.gnu.org:/srv/git/lilypond
>> >5d2bd06..e15e0d2  master -> master
>> >201be86..e593c62  translation -> translation
>> > 21:58:59 Merged staging, now at:   e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 21:59:01   Success:sudo -u lilybuild ./autogen.sh 
>> > --noconfigure
>> > 21:59:37   Success:sudo -u lilybuild 
>> > /home/lilybuild/staging/configure --disable-optimising
>> > 21:59:47   Success:sudo -u lilybuild nice make clean
>> > 22:00:30 *** FAILED BUILD ***
>> >sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>> >Previous good commit:   66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac
>> >Current broken commit:  e15e0d22810063b79da891bbf472ecc39d09c02c
>> > 22:00:30 *** FAILED STEP ***
>> >merge from staging
>> >Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
>> > ANTI_ALIAS_FACTOR=1
>> > See the log file 
>> > log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
>> > 22:00:31 Traceback (most recent call last):
>> >   File
>> > "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init_
>
> This is a GCC segfault with GCC 4.4.7-2 (Debian unstable).  On the
> contrary, the crash of "make doc" this morning on translation branch
> comes from an error in the Czech doc Texinfo source.
>
>
>> Grenouille currently seems to be wrong too often to be useful.  Do you
>> have a way of checking the integrity of its RAM?
>
> I contacted the administrator for checking this, if I need to be
> physically present there we won't be able to check this before Monday.

Some of the recent reports from Grenouille actually might suggest that
it might be testing against an unrelated test-baseline.  Perhaps you are
taking wrong shortcuts, or are mixing up in-place and out-of-place
builds or storing your test-baseline in a different place you read it
from again?

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Grenouille broken leg [was Re: Patchy report]

2012-08-31 Thread John Mandereau

Il giorno mar, 28/08/2012 alle 19.00 +0100, Phil Holmes ha scritto:
> - Original Message - 
> From: 
> To: 
> Cc: 
> Sent: Tuesday, August 28, 2012 5:39 PM
> Subject: Patchy report
> 
> 
> > 13:58:03 (UTC) Begin LilyPond compile, previous commit at 
> > e6073c719af153e80ba9f31ed96040a3782a180a
> > 13:58:11 Another instance (PID 29635) is already running.
> > 14:28:18 Another instance (PID 29635) is already running.
> > 14:58:26 Another instance (PID 29635) is already running.
> > 15:29:06 Merged staging, now at: e6073c719af153e80ba9f31ed96040a3782a180a
> > 15:29:09 Success: sudo -u lilybuild ./autogen.sh --noconfigure
> > 15:29:49 Success: sudo -u lilybuild 
> > /home/lilybuild/staging/configure --disable-optimising
> > 15:29:59 Success: sudo -u lilybuild nice make clean
> > 15:45:29 Success: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
> > ANTI_ALIAS_FACTOR=1
> > 16:07:21 Success: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
> > ANTI_ALIAS_FACTOR=1
> > 16:39:54 *** FAILED BUILD ***
> > sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> > Previous good commit: 30f457de4178d3e049336aaf50afe17b3b3a1135
> > Current broken commit: e6073c719af153e80ba9f31ed96040a3782a180a
>
> Don't know what the problem was, but I ran test-patchy-staging to find out, 
> and all was well.  As of now, master==staging.

When I read that message, the log had already been overwritten by next
Patchy run, but from the timestamps it might well be a crash of LilyPond
in doc build caused by some hardware memory inconsistency: this month
Grenouille have encountered at least two GCC segfaults, one or two
segfaults, some weird typechecking error, an almost uncountable number
of "parsed objects should be dead" warnings... I'll see with Mike and
the MSH admin what we can do, I hope we can find a solution without
buying much or any hardware (making Grenouille run with only one of the
two 1 GB RAM devices, getting in donation a second-hand but well-running
computer suitable as a server possibly putting just a new hard disk on
it...), as I think LilyPond users and developers would preferably spend
money in funding development by humans.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-08-31 Thread John Mandereau

Il giorno ven, 31/08/2012 alle 00.38 +0200, David Kastrup ha scritto:
> grenoui...@lilynet.net writes:
> 
> > 21:58:01 (UTC) Begin LilyPond compile, previous commit at   
> > e15e0d22810063b79da891bbf472ecc39d09c02c
> > 21:58:15 From git.savannah.gnu.org:/srv/git/lilypond
> >5d2bd06..e15e0d2  master -> master
> >201be86..e593c62  translation -> translation
> > 21:58:59 Merged staging, now at:e15e0d22810063b79da891bbf472ecc39d09c02c
> > 21:59:01Success:sudo -u lilybuild ./autogen.sh 
> > --noconfigure
> > 21:59:37Success:sudo -u lilybuild 
> > /home/lilybuild/staging/configure --disable-optimising
> > 21:59:47Success:sudo -u lilybuild nice make clean
> > 22:00:30 *** FAILED BUILD ***
> > sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
> > Previous good commit:   66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac
> > Current broken commit:  e15e0d22810063b79da891bbf472ecc39d09c02c
> > 22:00:30 *** FAILED STEP ***
> > merge from staging
> > Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
> > ANTI_ALIAS_FACTOR=1
> > See the log file 
> > log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
> > 22:00:31 Traceback (most recent call last):
> >   File
> > "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init_

This is a GCC segfault with GCC 4.4.7-2 (Debian unstable).  On the
contrary, the crash of "make doc" this morning on translation branch
comes from an error in the Czech doc Texinfo source.


> Grenouille currently seems to be wrong too often to be useful.  Do you
> have a way of checking the integrity of its RAM?

I contacted the administrator for checking this, if I need to be
physically present there we won't be able to check this before Monday.

John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-08-30 Thread David Kastrup

grenoui...@lilynet.net writes:

> 21:58:01 (UTC) Begin LilyPond compile, previous commit at 
> e15e0d22810063b79da891bbf472ecc39d09c02c
> 21:58:15 From git.savannah.gnu.org:/srv/git/lilypond
>5d2bd06..e15e0d2  master -> master
>201be86..e593c62  translation -> translation
> 21:58:59 Merged staging, now at:  e15e0d22810063b79da891bbf472ecc39d09c02c
> 21:59:01  Success:sudo -u lilybuild ./autogen.sh 
> --noconfigure
> 21:59:37  Success:sudo -u lilybuild 
> /home/lilybuild/staging/configure --disable-optimising
> 21:59:47  Success:sudo -u lilybuild nice make clean
> 22:00:30 *** FAILED BUILD ***
>   sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
>   Previous good commit:   66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac
>   Current broken commit:  e15e0d22810063b79da891bbf472ecc39d09c02c
> 22:00:30 *** FAILED STEP ***
>   merge from staging
>   Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
> 22:00:31 Traceback (most recent call last):
>   File
> "/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init_

[...]

Grenouille currently seems to be wrong too often to be useful.  Do you
have a way of checking the integrity of its RAM?

-- 
David Kastrup


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-30 Thread grenouille

21:58:01 (UTC) Begin LilyPond compile, previous commit at   
e15e0d22810063b79da891bbf472ecc39d09c02c
21:58:15 From git.savannah.gnu.org:/srv/git/lilypond
   5d2bd06..e15e0d2  master -> master
   201be86..e593c62  translation -> translation
21:58:59 Merged staging, now at:e15e0d22810063b79da891bbf472ecc39d09c02c
21:59:01Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
21:59:37Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
21:59:47Success:sudo -u lilybuild nice make clean
22:00:30 *** FAILED BUILD ***
sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   66a7c3e925cbc1a34eaad04f80d4bc42ad9834ac
Current broken commit:  e15e0d22810063b79da891bbf472ecc39d09c02c
22:00:30 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
22:00:31 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 311, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report

2012-08-28 Thread Phil Holmes

- Original Message - 
From: 

To: 
Cc: 
Sent: Tuesday, August 28, 2012 5:39 PM
Subject: Patchy report


13:58:03 (UTC) Begin LilyPond compile, previous commit at 
e6073c719af153e80ba9f31ed96040a3782a180a

13:58:11 Another instance (PID 29635) is already running.
14:28:18 Another instance (PID 29635) is already running.
14:58:26 Another instance (PID 29635) is already running.
15:29:06 Merged staging, now at: e6073c719af153e80ba9f31ed96040a3782a180a
15:29:09 Success: sudo -u lilybuild ./autogen.sh --noconfigure
15:29:49 Success: sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising

15:29:59 Success: sudo -u lilybuild nice make clean
15:45:29 Success: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
16:07:21 Success: sudo -u lilybuild nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1

16:39:54 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit: 30f457de4178d3e049336aaf50afe17b3b3a1135
Current broken commit: e6073c719af153e80ba9f31ed96040a3782a180a
16:39:54 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

16:39:54 Traceback (most recent call last):
 File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging

   self.build (issue_id=issue_id)
 File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build

   issue_id)
 File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
   raise FailedCommand ("Failed runner: %s\nSee the log file %s" % 
(command, this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt

--
grenouille at the Maison des Sciences de l'Homme Paris Nord



Don't know what the problem was, but I ran test-patchy-staging to find out, 
and all was well.  As of now, master==staging.

--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-28 Thread grenouille

13:58:03 (UTC) Begin LilyPond compile, previous commit at   
e6073c719af153e80ba9f31ed96040a3782a180a
13:58:11 Another instance (PID 29635) is already running.
14:28:18 Another instance (PID 29635) is already running.
14:58:26 Another instance (PID 29635) is already running.
15:29:06 Merged staging, now at:e6073c719af153e80ba9f31ed96040a3782a180a
15:29:09Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
15:29:49Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
15:29:59Success:sudo -u lilybuild nice make clean
15:45:29Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
16:07:21Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
16:39:54 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   30f457de4178d3e049336aaf50afe17b3b3a1135
Current broken commit:  e6073c719af153e80ba9f31ed96040a3782a180a
16:39:54 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
16:39:54 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 523, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 328, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-27 Thread grenouille

07:58:05 (UTC) Begin LilyPond compile, previous commit at   
1f364da94cf04f08063c8051dac7359325c58147
07:58:25 From git.savannah.gnu.org:/srv/git/lilypond
 * [new branch]  dev/john-autogen-gub-fix -> dev/john-autogen-gub-fix
   7bb3a5b..63daf4c  dev/skylines -> dev/skylines
   0a12e59..d14e477  master -> master
 + a3b02d1...7612daa release/unstable -> release/unstable  (forced update)
   43cc33a..2b55f81  stable/2.16 -> stable/2.16
   1f364da..d14e477  staging-> staging
   0aa2889..43cc33a  translation -> translation
07:58:25 test-master-lock and PID entry exist but previous Patchy
run (PID 23876) died, resetting test-master-lock anyway.
07:59:00 Merged staging, now at:d14e4770b85b3cacc647e45b9ebfe59cc085753f
07:59:04Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
07:59:44Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
07:59:54Success:sudo -u lilybuild nice make clean
08:04:12 *** FAILED BUILD ***
sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   413eeca26f5baa563b9b866a60831507e8bc0d3e
Current broken commit:  d14e4770b85b3cacc647e45b9ebfe59cc085753f
08:04:12 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
08:04:12 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 521, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 309, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-23 Thread grenouille

13:58:03 (UTC) Begin LilyPond compile, previous commit at   
b512dbe4d29be6b4503c1727d93da6e190fb85c0
13:58:19 From git.savannah.gnu.org:/srv/git/lilypond
   596761e..3faa0be  stable/2.16 -> stable/2.16
13:58:43 Merged staging, now at:b512dbe4d29be6b4503c1727d93da6e190fb85c0
13:58:48Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
13:59:27Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
13:59:49Success:sudo -u lilybuild nice make clean
14:10:32 *** FAILED BUILD ***
sudo -u lilybuild nice make -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   deafba084c8ecf6af02f64455856147821b598c7
Current broken commit:  b512dbe4d29be6b4503c1727d93da6e190fb85c0
14:10:32 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
14:10:32 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 521, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 309, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file log-staging-nice-make--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-23 Thread grenouille

07:58:03 (UTC) Begin LilyPond compile, previous commit at   
b512dbe4d29be6b4503c1727d93da6e190fb85c0
07:58:32 Merged staging, now at:b512dbe4d29be6b4503c1727d93da6e190fb85c0
07:58:36Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
07:59:27Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
08:00:13Success:sudo -u lilybuild nice make clean
08:42:44Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
09:29:35Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
13:58:23 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   deafba084c8ecf6af02f64455856147821b598c7
Current broken commit:  b512dbe4d29be6b4503c1727d93da6e190fb85c0
13:58:23 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
13:58:23 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 521, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 326, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-23 Thread grenouille

01:58:03 (UTC) Begin LilyPond compile, previous commit at   
b512dbe4d29be6b4503c1727d93da6e190fb85c0
01:58:10 Another instance (PID 11680) is already running.
02:28:42 Merged staging, now at:b512dbe4d29be6b4503c1727d93da6e190fb85c0
02:28:45Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
02:29:27Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
02:30:12Success:sudo -u lilybuild nice make clean
03:16:21Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
04:24:45Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
07:58:16 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   deafba084c8ecf6af02f64455856147821b598c7
Current broken commit:  b512dbe4d29be6b4503c1727d93da6e190fb85c0
07:58:16 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
07:58:16 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 521, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 326, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report

2012-08-22 Thread grenouille

19:58:01 (UTC) Begin LilyPond compile, previous commit at   
b512dbe4d29be6b4503c1727d93da6e190fb85c0
19:58:09 Another instance (PID 4835) is already running.
20:28:59 Merged staging, now at:b512dbe4d29be6b4503c1727d93da6e190fb85c0
20:29:01Success:sudo -u lilybuild ./autogen.sh 
--noconfigure
20:29:36Success:sudo -u lilybuild 
/home/lilybuild/staging/configure --disable-optimising
20:30:07Success:sudo -u lilybuild nice make clean
21:00:05Success:sudo -u lilybuild nice make -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
21:38:31Success:sudo -u lilybuild nice make test -j2 
CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
02:28:31 *** FAILED BUILD ***
sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 ANTI_ALIAS_FACTOR=1
Previous good commit:   deafba084c8ecf6af02f64455856147821b598c7
Current broken commit:  b512dbe4d29be6b4503c1727d93da6e190fb85c0
02:28:32 *** FAILED STEP ***
merge from staging
Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
02:28:32 Traceback (most recent call last):
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 521, in handle_staging
self.build (issue_id=issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 326, in build
issue_id)
  File 
"/home/jmandereau/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" % (command, 
this_logfilename))
FailedCommand: Failed runner: sudo -u lilybuild nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
See the log file 
log-staging-nice-make-doc--j2-CPU_COUNT=2-ANTI_ALIAS_FACTOR=1.txt
--
grenouille at the Maison des Sciences de l'Homme Paris Nord

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-16 Thread grenouille

05:54:45 (UTC) Begin LilyPond compile, previous commit at   
f374fa12dd5dd745d8e60afce450b3056c274906
05:55:02 Merged staging, now at:f1baa2d2047dfc44ae7b339cbd64dafc5aebf5ef
05:55:02 *** FAILED STEP ***
merge from staging
Command '['git', 'push', 'local', 'test-staging']' returned non-zero 
exit status 128
fatal: Unable to create 
'/tmp/lilypond-staging/.git/refs/remotes/local/test-staging.lock': Permission 
denied
05:57:52 (UTC) Begin LilyPond compile, previous commit at   
f1baa2d2047dfc44ae7b339cbd64dafc5aebf5ef
05:57:59 *** FAILED STEP ***
merge from staging
[Errno 13] Permission denied: '/tmp/lilypond-staging/.gitignore'

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-16 Thread grenouille

05:54:45 (UTC) Begin LilyPond compile, previous commit at   
f374fa12dd5dd745d8e60afce450b3056c274906
05:55:02 Merged staging, now at:f1baa2d2047dfc44ae7b339cbd64dafc5aebf5ef
05:55:02 *** FAILED STEP ***
merge from staging
Command '['git', 'push', 'local', 'test-staging']' returned non-zero 
exit status 128
fatal: Unable to create 
'/tmp/lilypond-staging/.git/refs/remotes/local/test-staging.lock': Permission 
denied

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-16 Thread grenouille

13:00:01 (UTC) Begin LilyPond compile, previous commit at   
f374fa12dd5dd745d8e60afce450b3056c274906
13:00:19 *** FAILED STEP ***
merge from staging
'int' object has no attribute 'startswith'

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-13 Thread grenouille

01:00:02 (UTC) Begin LilyPond compile, previous commit at   
1dedaf12fb71d557b062412bddcd2ccba75df365
01:00:11 *** FAILED STEP ***
merge from staging
global name 'ActiveLock' is not defined

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread John Mandereau

Le mardi 07 août 2012 à 01:49 +, grenoui...@lilynet.net a écrit :
> 22:24:01 (UTC) Begin LilyPond compile, previous commit at 
> aee96a7ae52324a75ea735d172d2ef028802c860
> 22:24:14 Merged translation, now at:  952705000581a13836e6a733df04511e93c5
> 22:24:17  Success:./autogen.sh --noconfigure
> 22:25:03  Success:../configure --disable-optimising
> 22:25:23  Success:nice make clean 
> 22:47:52  Success:nice make -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 23:05:35  Success:nice make test -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 01:49:28  Success:nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 01:49:28 Installing documentation

This was the first build of translation branch by Patchy the autobot,
docs are available at
http://grenouille.lilynet.net/lilypond-web/translation

In the presence of new commits, this build shall be repeated every 8
hours.  For translation branch, Patchy does not push anything to Git.

Translators, notifications are sent to lilypond-a...@gnu.org; to get
them, you can subscribe or read the archives at your option, knowing
that most messages on lilypond-auto are from our issue tracker.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread John Mandereau

Le lundi 06 août 2012 à 21:59 +, grenoui...@lilynet.net a écrit :
> 18:34:15 (UTC) Begin LilyPond compile, previous commit at 
> 952705000581a13836e6a733df04511e93c5
> 18:34:26 Merged staging, now at:  952705000581a13836e6a733df04511e93c5
> 18:34:28  Success:./autogen.sh --noconfigure
> 18:35:04  Success:../configure --disable-optimising
> 18:35:23  Success:nice make clean 
> 18:57:53  Success:nice make -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 19:15:29  Success:nice make test -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 21:59:24  Success:nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 21:59:41 *** FAILED STEP ***
>   merge from staging
>   Command '['git', 'push', 'origin', 'test-master-lock:master']' returned 
> non-zero exit status 129
> error: --mirror can't be combined with refspecs

As this run failed at the very last step, I manually pushed, and I hope
I have fixed the remote setting for next run (02:00 GMT).

John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-06 Thread grenouille

18:20:13 (UTC) Begin LilyPond compile, previous commit at   
23c3488226827238ec04a089b9b71e709501c807
18:22:01 *** FAILED STEP ***
merge from staging
global name 'origin' is not defined
18:34:15 (UTC) Begin LilyPond compile, previous commit at   
952705000581a13836e6a733df04511e93c5
18:34:26 Merged staging, now at:952705000581a13836e6a733df04511e93c5
18:34:28Success:./autogen.sh --noconfigure
18:35:04Success:../configure --disable-optimising
18:35:23Success:nice make clean 
18:57:53Success:nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
19:15:29Success:nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
21:59:24Success:nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
21:59:41 *** FAILED STEP ***
merge from staging
Command '['git', 'push', 'origin', 'test-master-lock:master']' returned 
non-zero exit status 129
error: --mirror can't be combined with refspecs
usage: git push [] [ [...]]

-v, --verbose be more verbose
-q, --quiet   be more quiet
--reporepository
--all push all refs
--mirror  mirror all refs
--delete  delete refs
--tagspush tags (can't be used with --all or --mirror)
-n, --dry-run dry run
--porcelain   machine-readable output
-f, --force   force updates
--recurse-submodules[=]
  controls recursive pushing of submodules
--thinuse thin pack
--receive-pack 
  receive pack program
--exec 
  receive pack program
-u, --set-upstreamset upstream for git pull/status
--progressforce progress reporting
--prune   prune locally removed refs

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report from grenouille

2012-08-06 Thread John Mandereau

Le lundi 06 août 2012 à 21:00 +0200, Francisco Vila a écrit :
> Dear Grenouille: after merging translation into staging I failed at
> compiling lilypond, but I rm-rf'd regression/ and lily/ , reset hard,
> and all went well.

Dear Paco,

Please, always test a merge translation and staging with a *clean*
build, i.e. after merging and before starting the build do

git clean -f -X

Thanks,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread John Mandereau

Le lundi 06 août 2012 à 13:32 +0200, David Kastrup a écrit :
> And zero exit status (no error): it is conceivable that origin/staging
> has just been deleted (which only is necessary if you want to drop some
> commits from it) and not yet replaced by something else, in which case
> this command will throw an error.

Programs ran inside Patchy that return non-zero generate a FailedCommand
exception, so I think this is straightforward to handle.


> Great!

It turns out to be trickier than what I thought, because main Git repo
(the one used to synchronize with git.sv.gnu.org) on server grenouille
is bare (then local clones with shared Git data are created for various
puroposes), and the trick of fetching then run lilypond-patchy-staging
in chroot then push no longer works with an extra fetch at the end of
the build.  I finally got to start a build, if everything goes well,
you'll see a positive notification on lilypond-auto just before midnight
CET.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Patchy report from grenouille

2012-08-06 Thread Francisco Vila

2012/8/6  :
> 18:20:13 (UTC) Begin LilyPond compile, previous commit at   
> 23c3488226827238ec04a089b9b71e709501c807
> 18:22:01 *** FAILED STEP ***
> merge from staging
> global name 'origin' is not defined

Dear Grenouille: after merging translation into staging I failed at
compiling lilypond, but I rm-rf'd regression/ and lily/ , reset hard,
and all went well.

-- 
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-06 Thread grenouille

18:20:13 (UTC) Begin LilyPond compile, previous commit at   
23c3488226827238ec04a089b9b71e709501c807
18:22:01 *** FAILED STEP ***
merge from staging
global name 'origin' is not defined

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread David Kastrup

John Mandereau  writes:

> Le lundi 06 août 2012 à 10:48 +0200, David Kastrup a écrit :
>> This should actually be more diverse.  Before pushing the new
>> test-staging, Patchy should redo git fetch.
>> 
>> It should then check that
>> 
>> git log -1 origin/staging..test-staging
>> 
>> has _empty_ output

And zero exit status (no error): it is conceivable that origin/staging
has just been deleted (which only is necessary if you want to drop some
commits from it) and not yet replaced by something else, in which case
this command will throw an error.

> Fortunately enough Patchy seldom takes 11 hours like yesterday, but
> very frequent runs make this issue critical indeed.

Well, with very frequent runs, the time window for doing a last-minute
panic button action is the length of a single run.

> I'm working on implementing all this.

Great!

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread John Mandereau

Le lundi 06 août 2012 à 10:48 +0200, David Kastrup a écrit :
> This should actually be more diverse.  Before pushing the new
> test-staging, Patchy should redo git fetch.
> 
> It should then check that
> 
> git log -1 origin/staging..test-staging
> 
> has _empty_ output  If this is _not_ the case, some commits in
> test-staging have been _removed_ from origin/staging.  We've had the
> situation a lot in the past that I tried resetting origin/staging to
> fight bad material getting into master, and then subsequently it was
> still pushed by some already started Patchy.  If we have Patchy
> instances that run for 8 hours, this problem is acerbated.  So Patchy
> should really do a last-minute check that what is going to push is still
> wanted.

Fortunately enough Patchy seldom takes 11 hours like yesterday, but very
frequent runs make this issue critical indeed.


> If it is not empty, abort and send a mail with the message "staging has
> been reset, aborting operation without pushing".
>
> If that's empty, then we can check
> 
> git log -1 origin..test-staging
> 
> If this is empty, pushing will not achieve anything.  Just end without
> sending a mail.

In this last case, it might be good to send an email saying
"origin/staging has a newer revision than test-staging, not pushing", in
case the output of

git log -1 test-staging..origin

is not empty; it would say that an intermediate commit pushed to master
built succesfully, and that's not bad to know (I don't think we should
move commits one by one from staging to master given the current ratio
"available horsepower"/"build time", though).

I'm working on implementing all this.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread David Kastrup

John Mandereau  writes:

>> error: failed to push some refs to '/var/src/lilypond-git'
>
> This is normal and wpuld have happened even without the deletion of
> test-master-lock by the Patchy run at 16:55 UTC: Phil's Patchy picked up
> a revision in staging newer than when my Patchy started, and his run
> completed a lot earlier; in this case I think a message should say
> "Info: origin/staging has been fastforwarded to a newer revision than
> last fetch to the repository of this computer." and not CC
> lilypond-devel.

This should actually be more diverse.  Before pushing the new
test-staging, Patchy should redo git fetch.

It should then check that

git log -1 origin/staging..test-staging

has _empty_ output  If this is _not_ the case, some commits in
test-staging have been _removed_ from origin/staging.  We've had the
situation a lot in the past that I tried resetting origin/staging to
fight bad material getting into master, and then subsequently it was
still pushed by some already started Patchy.  If we have Patchy
instances that run for 8 hours, this problem is acerbated.  So Patchy
should really do a last-minute check that what is going to push is still
wanted.

If it is not empty, abort and send a mail with the message "staging has
been reset, aborting operation without pushing".

If that's empty, then we can check

git log -1 origin..test-staging

If this is empty, pushing will not achieve anything.  Just end without
sending a mail.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Patchy report from grenouille

2012-08-06 Thread John Mandereau

Hi guys,

Sorry to flood -devel with many Patchy failures, but we're still at an
early stage of experimenting concurrent runs of Patchy-staging, ones
on-demand made on fast machines, and ones made on Grenouille that take
hours but (hopefully) runs every 8 hours [1] without human intervention.
Previous failures have come a lot from my experiments on Patchy code,
and a little from bugs in existing code, I'm commenting a bit on this
failure below.

[1] I decreased frequency a bit because a build takes between three and
four hours, and I'm setting up a build of translation branch (without
any merging operation) to be run every 8 hours too, interleaved with
Patchy-staging.

Le dimanche 05 août 2012 à 21:02 +, grenoui...@lilynet.net a écrit :
> 08:55:13 (UTC) Begin LilyPond compile, previous commit at 
> ac0e95c8112250bcaddf0bce57ba2980767a2f43
> 08:55:18 Merged staging, now at:  c28baa15608b96e15ae3971ac2a70cc65282c110
> 08:55:23  Success:./autogen.sh --noconfigure
> 08:56:29  Success:../configure --disable-optimising
> 08:58:45  Success:nice make clean 
> 09:41:03  Success:nice make -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 11:42:29  Success:nice make test -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1
> 21:02:39  Success:nice make doc -j2 CPU_COUNT=2 
> ANTI_ALIAS_FACTOR=1

Wow, I can't figure out why it took so long to build this time, whereas
it went back to normal this morning (3h12min).  It doesn't seem that
there have been other processes with high resource consumption at the
same time, and the hard disk is sane.


> 21:02:41 *** FAILED STEP ***
>   merge from staging
>   Command '['git', 'push', 'origin', 'test-master-lock:master']' returned 
> non-zero exit status 1
> error: src refspec test-master-lock does not match any.

Mmh, I thought I fixed locking functionality in
lilypond-extra:24e9bc986062605022eba75ff168310de2d614c,
but I didn't; a Patchy should not remove test-master-lock branch
if it exists already and another Patchy is running at the same time;
I'll try to fix this with writing PID to $LILYPOND_BUILD_DIR/patchy.pid,
so that Patchy should remove test-master-lock in case some previous
Patchy run died unexpectedly.


> error: failed to push some refs to '/var/src/lilypond-git'

This is normal and wpuld have happened even without the deletion of
test-master-lock by the Patchy run at 16:55 UTC: Phil's Patchy picked up
a revision in staging newer than when my Patchy started, and his run
completed a lot earlier; in this case I think a message should say
"Info: origin/staging has been fastforwarded to a newer revision than
last fetch to the repository of this computer." and not CC
lilypond-devel.

Best,
John


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-05 Thread grenouille

08:55:13 (UTC) Begin LilyPond compile, previous commit at   
ac0e95c8112250bcaddf0bce57ba2980767a2f43
08:55:18 Merged staging, now at:c28baa15608b96e15ae3971ac2a70cc65282c110
08:55:23Success:./autogen.sh --noconfigure
08:56:29Success:../configure --disable-optimising
08:58:45Success:nice make clean 
09:41:03Success:nice make -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
11:42:29Success:nice make test -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
21:02:39Success:nice make doc -j2 CPU_COUNT=2 
ANTI_ALIAS_FACTOR=1
21:02:41 *** FAILED STEP ***
merge from staging
Command '['git', 'push', 'origin', 'test-master-lock:master']' returned 
non-zero exit status 1
error: src refspec test-master-lock does not match any.
error: failed to push some refs to '/var/src/lilypond-git'

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-05 Thread grenouille

16:55:18 (UTC) Begin LilyPond compile, previous commit at   
ac0e95c8112250bcaddf0bce57ba2980767a2f43
16:55:18 *** FAILED STEP ***
merge from staging
Command '['git', 'branch', 'test-master-lock', 'origin/master']' 
returned non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-03 Thread grenouille

02:30:12 (UTC) Begin LilyPond compile, previous commit at   
4c2851d28c0a94a30cc7652b9b0052ce7f0ade7e
02:30:13 *** FAILED STEP ***
merge from staging
Command '['git', 'branch', 'test-master-lock', 'origin/master']' 
returned non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-03 Thread grenouille

20:30:12 (UTC) Begin LilyPond compile, previous commit at   
4c2851d28c0a94a30cc7652b9b0052ce7f0ade7e
20:30:13 *** FAILED STEP ***
merge from staging
Command '['git', 'branch', 'test-master-lock', 'origin/master']' 
returned non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.
20:30:18 *** FAILED STEP ***
install documentation
[Errno 2] No such file or directory: 
'/home/jmandereau/lilypond-autobuild/build/out-www/offline-root'

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Patchy report from grenouille

2012-08-03 Thread grenouille

20:30:12 (UTC) Begin LilyPond compile, previous commit at   
4c2851d28c0a94a30cc7652b9b0052ce7f0ade7e
20:30:13 *** FAILED STEP ***
merge from staging
Command '['git', 'branch', 'test-master-lock', 'origin/master']' 
returned non-zero exit status 128
fatal: A branch named 'test-master-lock' already exists.

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

63 matches

Mail list logo