[jallib build] buildbot failure in jallib on jallib-standard

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD
Blamelist: mattsc...@hotmail.com

BUILD FAILED: failed svn
Logs are attached.

sincerely,
-The Buildbot

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason: The web-page 'force build' button was pressed by 'seb': let's try again

Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed svn

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason: The web-page 'force build' button was pressed by 'seb': yet another time

Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed validate compile

[Sebastien Lelong]

This one is has succeeded to fail :)

2010/4/3 <bu...@sirloon.net>

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org

[Joep Suijs]

It sure did. SNV messages... is you wireless connection troubling you again?

Btw, I saw you pushed a button. Is there a public page with
build-button or latest build results available?

Joep

2010/4/3 Sebastien Lelong <sebastie...@gmail.com>:

[Sebastien Lelong]

2010/4/3 Joep Suijs <jsu...@gmail.com>

It sure did. SNV messages... is you wireless connection troubling you again?

No, I mean the build has gone to the end, but the failure (validate step) is a real one, it's not related to my wireless connection this time.

 

Btw, I saw you pushed a button. Is there a public page with
build-button or latest build results available?

No, this is private

Cheers,

Seb

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD
Blamelist: jsuijs,wattymage

[mattschinkel]

sorry, i'll fix this soon

>  svn.stdio
> < 1KViewDownload
>
>  validate.stdio
> < 1KViewDownload
>
>  compile.stdio
> < 1KViewDownload

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD

Blamelist: sebastien.lelong

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD

Blamelist: mattsc...@hotmail.com

BUILD FAILED: failed compile

[Sebastien Lelong]

Buildbot reaches compilation timeout again (60min). I've increase delay to 90min, this won't work long... 

2010/4/4 <bu...@sirloon.net>

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.
To unsubscribe from this group, send email to jallib+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

[mattschinkel]

Seb, I think some of my samples could be the problem. I think my mp3
sample takes quite a long time if you don't use -no-variable-reuse. I
think you know this already.

Recently, I added 1 more sample for it so there is a sample with sd
card and one with hard disk.

I would add samples for it on other pics, but I don't think build bot
will like them. Can you please compile one of my samples from 18f4620
mp3 and tell me how long it takes your server to compile it?

Maybe you should use -no-variable-reuse for all 18f samples, and maybe
it should be a requirement that all 18f should be able to compile with
-no-variable-reuse

Matt.

On Apr 4, 4:03 pm, Sebastien Lelong <sebastien.lel...@gmail.com>
wrote:

> Buildbot reaches compilation timeout again (60min). I've increase delay to
> 90min, this won't work long...
>
> 2010/4/4 <bu...@sirloon.net>
>
>
>
>
>
> > Hi guys,
>
> > This is buildbot speaking. I have finished a build of jallib-standard on
> > jallib.
> > Buildslave for this Build: sebbot
>
> > Build Reason:
> > Build Source Stamp: HEAD

> > Blamelist: mattschin...@hotmail.com

>
> > BUILD FAILED: failed compile
> > Logs are attached.
>
> > sincerely,
> >  -The Buildbot
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "jallib" group.
> > To post to this group, send email to jal...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > jallib+un...@googlegroups.com<jallib%2Bunsu...@googlegroups.com>

> > .
> > For more options, visit this group at
> >http://groups.google.com/group/jallib?hl=en.
>
> --

> Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org- Hide quoted text -
>
> - Show quoted text -

[Mike@watty]

On Apr 4, 9:44 pm, mattschinkel <mattschin...@hotmail.com> wrote:
> Seb, I think some of my samples could be the problem. I think my mp3
> sample takes quite a long time if you don't use -no-variable-reuse. I
> think you know this already.

I have found compile times for my CatpadV2 vary between 21s and 340s
with small variation in the way I put the same program.

The compiler seems to get a bit lost with nested ifs and certain
variable with a default value and only changed in one clause.

I haven't totally tracked down what causes it. I once had compiler
time out after 20mins and slight re-arrangement on structure &
declarations brought to to 22s.

But I can't yet reproduce, so I have not yet "filed" bug report.

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason: The web-page 'force build' button was pressed by 'seb': increased timeout, should be ok

Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed compile

[mattschinkel]

Here's an idea seb...

compile all samples with -no-variable-reuse, if any fail to compile
(due to lack of ram/program space), do a second compile attempt on the
failed samples without -no-variable-reuse

Matt.

[Sebastien Lelong]

Great idea, I'll try this.

Thanks

Seb

2010/4/5 mattschinkel <mattsc...@hotmail.com>

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.

To unsubscribe from this group, send email to jallib+un...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--

[Sebastien Lelong]

Maybe I'll first grep "^include 18f" in sample file in order to know if it needs -no-variable-reuse. If a 18F sample fails to compile, it'll try without -no-variable-reuse, and takes long to compile. "grep" should do the trick.

Cheers,

Seb

2010/4/5 mattschinkel <mattsc...@hotmail.com>

--
You received this message because you are subscribed to the Google Groups "jallib" group.
To post to this group, send email to jal...@googlegroups.com.

To unsubscribe from this group, send email to jallib+un...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/jallib?hl=en.

--

[Sebastien Lelong]

On my server, compiling 18f4620_mp3_decoder_sta015_sd_card.jal:

  - with -no-variable-reuse: 12s

  - without -no-variable-reuse: 470s

Cheers,

Seb

2010/4/5 Sebastien Lelong <sebastie...@gmail.com>

[Rob Hamerling]

Hi Seb,

On 04/05/10 10:28 am, Sebastien Lelong wrote:
> Great idea, I'll try this.

Sounds as if you hear about '-no-variable-reuse' for the first time,
while this option has been discussed several times. For example in a msg
here of 3 Jan 2010 I said:

> Similar experience here. But for bulk sample compilation I use
> -no-variable-reuse *only* for samples of the 18F series. For smaller
> PICs it may give 'Out of data space' (e.g. 16f676_hd4480__4_1 and
> _4_4).

BTW I check on '18' as first 2 characters of the filename. A grep for
'include 18f' in the source seems safer, but there may be more than one
space between 'include' and '18f', and there may be (or come) samples
which include an '18lf' PIC.

Regards, Rob.

>
> 2010/4/5 mattschinkel <mattsc...@hotmail.com
> <mailto:mattsc...@hotmail.com>>

>
> Here's an idea seb...
>
> compile all samples with -no-variable-reuse, if any fail to compile
> (due to lack of ram/program space), do a second compile attempt on
> the failed samples without -no-variable-reuse
>
> Matt.
>

--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)

[Sebastien Lelong]

hi rob

yes i'm aware of this, i didn't forget, it was more about the logic
test within buildbot. i wanted to avoid detecting 18f samples, but a
grep will do the trick (lazy i am). i also have preserve cpu on my
server.

cheers,
seb

--
Sébastien Lelong

Le 5 avr. 2010 à 12:27, Rob Hamerling <robham...@gmail.com> a
écrit :

[Joep Suijs]

Hi Seb,

A better sollution to reduce the load of buildbot is to keep the hex
file and check if it needs rebuild. This does require a 'depend' tool
to see if any of the included files are newer then the hex files.

Joep

2010/4/5 Sebastien Lelong <sebastie...@gmail.com>:

[Sebastien Lelong]

2010/4/5 Joep Suijs <jsu...@gmail.com>

Hi Seb,

A better sollution to reduce the load of buildbot is to keep the hex
file and check if it needs rebuild. This does require a 'depend' tool
to see if any of the included files are newer then the hex files.

Looks like more complex than grep... (lazy I am)

Cheers,

Seb

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD
Blamelist: jsuijs

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD

Blamelist: eur.van.andel

BUILD FAILED: failed validate

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD

Blamelist: mattsc...@hotmail.com

[Eur van Andel]

On 8 Apr 2010, at 19:55 , bu...@sirloon.net wrote:

Build Source Stamp: HEAD

Blamelist: eur.van.andel

OK, so here I am on the blamelist. Now what?

I updated svn and there is nothing in casualties?

ERROR: mcp3424.jal:Cannot find end of field content Description

OK. This is shown in the buildbot post as one of four attachments, which I have to open separately. To be honest, I don't even know what the end of field delimiter looks like. 

Example:

-- Title: USART hardware control
-- Author: Stef Mientki, Copyright (c) 2002..2008, all rights reserved.
-- Adapted-by: Sebastien Lelong, Someone Else
-- Compiler: >=2.4g
-- 
-- This file is part of jallib (http://jallib.googlecode.com)
-- Released under the BSD license (http://www.opensource.org/licenses/bsd-license.php)
-- 
-- Description: Routines for sending and receiving through the PIC-usart,
-- both RS232 and SPI are supported (for SPI see spi_hardware.jal)
-- Baudrate can simply be set through a human constant,
-- because the baudrate depending registers are calculated by this unit.
-- Baudrate is calculated, starting at the high baudrate flag,
-- which will ensure the highest possible accuracy.
-- --
-- SPI routines are setup for more SPI-devices,
-- in which case CS should be controled outside this unit.
-- 
-- Sources: excellent article on USART: http://www.google.fr/search?q=usart
-- 
-- Notes: an incredible note
--

http://code.google.com/p/jallib/wiki/JallibStyleGuide

So I assume this is just "--" on an empty line?

-- Title: mcp342, 18-bit, multi-channel delta-sigma AD converter with I2C output

-- Author: Eur van Andel, e...@fiwihex.nl Copyright (c) 2010

-- Compiler: =2.4m

-- 

-- This file is part of jallib (http://jallib.googlecode.com)

-- Released under the ZLIB license (http://www.opensource.org/licenses/zlib-license.html)

--

-- Description: this library works with the MCP3424 AD converter from Microchip with up to 18 bits accuracy

-- Datasheet: DS22088B

--

-- Declare this in main program:

I have this two minus signs on an empty line? Maybe someone else fixed it?

OK. I understand that jallib needs neat code and that it needs to be checked. What I don't understand is that several people write page long emails about this problem instead of fixing just TWO chars. 

I work hard and as much as I love JAL, I don't have the time (anymore) to discuss meta-JAL in this detail. If my errors are two characters, it might be a lot easier to fix those than send me emails about it or postings here. 

About those emails: can you send me the headers of those? I can't understand why they did not reach me. 

And yes, the buildbot should email me directly on e...@fiwihex.nl. I don't read eur.va...@gmail.com and I have tried several times to remove the jallist mail overload from that account, to no avail. 

---

ir EE van Andel e...@fiwihex.nl  http://www.fiwihex.nl

Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands

tel+31-546-491106 fax+31-546-491107

[Sebastien Lelong]

I have this two minus signs on an empty line? Maybe someone else fixed it?

Yes, Vasile did.

 

OK. I understand that jallib needs neat code and that it needs to be checked. What I don't understand is that several people write page long emails about this problem instead of fixing just TWO chars. 

This is something you should give more thoughts about...

 

I work hard and as much as I love JAL, I don't have the time (anymore) to discuss meta-JAL in this detail. If my errors are two characters, it might be a lot easier to fix those than send me emails about it or postings here. 

OK, since you only focus on this "two" chars, forget about them, and think about buildbot failures in general. Shouldn't they be fixed ? And what about Rob's remarks about libraries containing hard-coded pins ? 

 

About those emails: can you send me the headers of those? I can't understand why they did not reach me. 

And yes, the buildbot should email me directly on e...@fiwihex.nl.

No

 

I don't read eur.va...@gmail.com and I have tried several times to remove the jallist mail overload from that account, to no avail. 

Update your google account, or create a new one with this new email address, I'll update commiter list.

Cheers,

Seb

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD
Blamelist: jsuijs,sebastien.lelong,vsurducan

BUILD FAILED: failed compile

[bu...@sirloon.net]

Hi guys,

This is buildbot speaking. I have finished a build of jallib-standard on jallib.
Buildslave for this Build: sebbot

Build Reason:
Build Source Stamp: HEAD

Blamelist: eur.van.andel

BUILD FAILED: failed validate

[Eur van Andel]

On 12 Apr 2010, at 20:55 , bu...@sirloon.net wrote:

Build Source Stamp: HEAD

Blamelist: eur.van.andel

Well, the mailfilter didn't work. Can buildbot put something in the subject?

-- jsg output --

File: /home/build/jallib/slave/standard/build/include/external/temperature/mcp9800.jal

1 errors found

ERROR: mcp9800.jal:Cannot find end of field content Description

0 warnings found

-- -- --

This time the two dashes were actually missing. I added them. 

How can I run a validator locally? I browsed the trunk and found validate.sh. It wanted a "sample" and an "include" directory, so I ran it in my "jallib" directory. This didn't work:

G5-fiwihex:~/jalv2/jallib eur$ tools/build/validate.sh 

1 samples to validate...

1 libraries to validate...

1113 files can't be validated...

List:

10f200_blink.jal

10f202_blink.jal

10f204_blink.jal

Is there a way to run this validate.sh properly? How? I can't find anything on the jallib google pages (and I can't search them either!) and searching the last 4000 jallib msgs doesn't give much explanation either. 

[Joep Suijs]

Hi Eur,

Validate with:
jallib.py validate <filename>

Joep

2010/4/12 Eur van Andel <e...@fiwihex.nl>: