by hand).
>
>
>
>
> --
> *Van:* jallib@googlegroups.com namens vasi vasi
>
> *Verzonden:* dinsdag 30 mei 2023 15:39
> *Aan:* jallib@googlegroups.com
> *Onderwerp:* Re: [jallib] [jallib build] buildbot failure in jallib on
> jallib-bee
started by hand).
[cid:af156801-2e71-4ae6-bb8c-3f5ff30118b7]
Van: jallib@googlegroups.com namens vasi vasi
Verzonden: dinsdag 30 mei 2023 15:39
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] [jallib build] buildbot failure in jallib on jallib-bee
If the
If the binary files of the compiler are distributed anyway, for Linux what
about compiling it in a musl/llvm based system (as gcc in Linux can't
compile static if math lib from libc is required) as a truly static binary?
On Sun, May 28, 2023 at 4:09 PM wrote:
> Hi guys,
>
> This is buildbot spea
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The web-page 'force build' button was pressed by 'matt': bee
Build Source Stamp: [branch jallib-bee] HEAD
Blamelist:
BUILD FAILED: exception svn
Logs are attache
Alright, this was the last weekly build, I'm deactivating buildbot for
weekly "bee" package (because it mostly needs to be adapted to upload
packages to drive, instead of googlecode).
I'll keep buildbot running (usual, frequent build/check), until it dies.
If someone would like to take of it, let m
manual uploaded to google drive.
cheers
seb
On 25 May 2014 15:16, wrote:
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build: sebbot
>
> Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered
> this build
> Bui
Hi Seb,
I have the same questions, so I will have a look at the files and the
examples.
It's bit more complicated that usual since the rexx scripts have some
issues on windows..
Joep
2014-05-18 23:33 GMT+02:00 Sebastien Lelong :
> Hi Joep,
> I can add them to TORELEASE, but I don't know if it'
Hi Joep,
I can add them to TORELEASE, but I don't know if it's validated or not ?
Should these samples/libs go into last release ?
Cheers
Seb
On 18 May 2014 23:17, Joep Suijs wrote:
> I'll try and fix this some time this week.
>
> Joep
>
> Op zondag 18 mei 2014 heeft Sebastien Lelong
> het vol
I'll try and fix this some time this week.
Joep
Op zondag 18 mei 2014 heeft Sebastien Lelong
het volgende geschreven:
> buildbot is not happy, probably missing lib in TORELEASE:
>
> distrib/jallib-pack-bee/sample/18f2585_oxygen_goel370.jal failed !
> jal jalv24q2 (compiled Jan 23 2014)
> genera
buildbot is not happy, probably missing lib in TORELEASE:
distrib/jallib-pack-bee/sample/18f2585_oxygen_goel370.jal failed !
jal jalv24q2 (compiled Jan 23 2014)
generating p-code
distrib/jallib-pack-bee/sample/18f2585_oxygen_goel370.jal:79: cannot open
'goel370.jal'
distrib/jallib-pack-bee/sample/
guys, there are underscores in filenames in TORELEASE file ? Do you know
where it comes from ??
Cheers
Seb
On 18 May 2014 20:39, wrote:
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build: sebbot
>
> Build Reason: The web-page
sorry i "misread" your email, only the date isn't kept and I don't think
it's fiaxble. i iploaded some files and need to cleanup. i'll let you know
when i think it's ok
cheers!
seb
Le 31 mars 2014 13:31, "Rob Hamerling" a écrit :
>
> Hi Seb,
>
> On 31.03.14 12:51, Sebastien Lelong wrote:
>
>> Wei
Use "justanotherlanguage" or some other hosting
Anything "hosted" on Google is a bad idea.
Google Drive is a bad idea.
They are an advertising company.
if the J A L site isn't got enough storage I have "unlimited" package.
On Sunday, March 30, 2014 6:58:25 PM UTC+1, Sebastien Lelong wrote:
>
Hi Seb,
On 31.03.14 12:51, Sebastien Lelong wrote:
Weird I can see you uploaded a file. Can you check ?
I uploaded jallib_0.9.0.zip at 9:18, and I see you uploaded the same
file at 9:54, which got a ' (1)' after the filename. And you uploaded
some more: I see now 8 files.
All files have 'S
Weird I can see you uploaded a file. Can you check ?
Cheers
Seb
Le 31 mars 2014 09:30, "Rob Hamerling" a écrit :
>
>
> On 30.03.14 21:21, Sebastien Lelong wrote:
>
>> I uploaded latest weekly package on a drive folder, manually. Also added
>> some links on the welcome project page. Download tab s
On 30.03.14 21:21, Sebastien Lelong wrote:
I uploaded latest weekly package on a drive folder, manually. Also added
some links on the welcome project page. Download tab should be
deprecated IMHO once every is moved to this folder.
I hadn't really used google drive, but I noticed that I have e
I can give permissions to whoever is asking, no problem. And any google
drive account can be used, it's really independent from googlecode.
Cheers
Seb
On 30 March 2014 21:28, Joep Suijs wrote:
> Okay, I see the package. I think you (jalu...@gmail.com) are the owner
> and ony you can add/delete
Okay, I see the package. I think you (jalu...@gmail.com) are the owner and
ony you can add/delete files?
If that is the case, I suggest you put all the files from the download area
there too, except for the old bee files.
And once we are working on the relase, we have to ask you to create and
cop
I uploaded latest weekly package on a drive folder, manually. Also added
some links on the welcome project page. Download tab should be deprecated
IMHO once every is moved to this folder.
cheers
Seb
On 30 March 2014 19:58, Sebastien Lelong wrote:
> alright... googlecode upload aren't supported
alright... googlecode upload aren't supported anymore, we need to use
google drive... how do you want to proceed ? I can't script buildbot to
upload to drive but then, what?
cheers
seb
On 30 March 2014 17:36, wrote:
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee
This line was added to to release in r3386. I never added this sample to
torelease, but I un-commented it recently.
# sample/18f4620_rtc_mcp7940.jal
I just removed it from torelease.
Matt.
On Sunday, March 16, 2014 2:53:30 PM UTC-4, RobH wrote:
>
>
>
> On 16.03.14 18:03, Joep Suijs wrote:
> >
On 16.03.14 18:03, Joep Suijs wrote:
Can anyone explain what's wrong?
The rtc_mcp7940 is not in TORELEASE either.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe
On 16.03.14 18:03, Joep Suijs wrote:
Can anyone explain what's wrong?
The log says:
distrib/jallib-pack-bee/sample/18f2620_beep.jal failed !
jal jalv24q2 (compiled Jan 23 2014)
generating p-code
distrib/jallib-pack-bee/sample/18f2620_beep.jal:38: cannot open 'beep.jal'
<...>
The beep library
Can anyone explain what's wrong?
The log says:
distrib/jallib-pack-bee/sample/18f2620_beep.jal failed !
jal jalv24q2 (compiled Jan 23 2014)
generating p-code
distrib/jallib-pack-bee/sample/18f2620_beep.jal:38: cannot open 'beep.jal'
<...>
6 errors, 0 warnings
However, this sample compiles at my m
not updated default compiler to 24q. Kyle released a new version, I'll wait
some more before defaulting to 24q beta (or final release)
Cheers
Seb
On 9 June 2013 15:11, wrote:
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build:
ok, I'll trigger a new build
thanks
seb
On 10 February 2013 20:15, Rob Hamerling wrote:
>
> Hi Seb,
>
>
> On 10-02-13 19:31, Sebastien Lelong wrote:
>
> I notived my xbee_api samples don't compile due to missing lib. I added
>> it to TORELEASE, as of revision 3178. It disappeared on rev 3200,
Hi Seb,
On 10-02-13 19:31, Sebastien Lelong wrote:
I notived my xbee_api samples don't compile due to missing lib. I added
it to TORELEASE, as of revision 3178. It disappeared on rev 3200,
authored by Rob :) Same for other network libraries.
Sorry, my fault! This week I changed the script to
Hi Rob,
I notived my xbee_api samples don't compile due to missing lib. I added it
to TORELEASE, as of revision 3178. It disappeared on rev 3200, authored by
Rob :) Same for other network libraries.
Did you have any issue while commiting ? SVN is supposed to not let you
commit a file if it's been
Hi guys,
Buildbot was broken due to a recent addition into jalapi HTML template.
Soemthing about re.sub() API that has changed between python version < 2.7
and >= 2.7.
Anyway, it seems to be fixed ! A weekly build is underway, it will contain
errors, please have a look (mostly missing lib depenci
Thanks, problem is being solved
Cheers
Seb
Le 17 juin 2012 23:21, "Eur van Andel" a écrit :
> On 17 Jun 2012, at 15:00 , bu...@sirloon.net wrote:
>
> BUILD FAILED: exception svn
> Logs are attached.
> [..]
>
>
>
> *: [Errno 28] No space left on device*
>
> Seb, your disk is full.
>
> ---
>
> ir
On 17 Jun 2012, at 15:00 , bu...@sirloon.net wrote:
BUILD FAILED: exception svn
Logs are attached.
[..]
: [Errno 28] No space left on device
Seb, your disk is full.
---
ir EE van Andel e...@fiwihex.nl http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: exception svn
Logs are attached.
sincere
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: failed svn
Logs are attached.
sincerely,
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: failed svn
Logs are attached.
sincerely,
Guys,
I'm trying to fix bee packages, automatically uploaded to GC. I think it
should work soon. It's been a while since there's weren't any bee, so errors
were just irrelevant.
But errors you can find in package.stdio are real ones: Matt, I think a lib
is missing in TORELEASE, fat32_small.jal
I just can't upload to GC using google_upload.py, even with my own account,
I just don't know why...
2010/10/24
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build: sebbot
>
> Build Reason: The Nightly scheduler named 'weekly bui
Google upload script won't upload bee packages anymore, I don't know why...
2010/10/10
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build: sebbot
>
> Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered
> thi
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: failed package
Logs are attached.
sincer
Bee failed because usb_keyboard.jal library is missing. It's been added in
rev.1752. I added it to TORELEASE, improve the script to print failure, bee
is being re-generated.
Cheers,
Seb
2010/3/14
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Build
>
>
> Hm, I've learned random does not exist in digital world, only
> pseudo-random.
>
>
It's like scopes, analogs are better...
Cheers,
Seb
--
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
On Wed, Mar 10, 2010 at 7:31 AM, Sebastien Lelong <
sebastien.lel...@gmail.com> wrote:
> Hi guys,
>
> random.org said we have to update SVN with beta compiler. I'll update it
> tonight.
>
Hm, I've learned random does not exist in digital world, only pseudo-random.
Vasile
>
>
--
You received
Hi Rob,
2010/3/7 Rob Hamerling
>
>
> The other is an issue with warnings for 'cexpr', which I got when compiling
> ADC samples. I have not tested an ADC sample with warnings, so I don't know
> the effect of these warnings.
>
>
I've seen this, really can't understand why. When compiling an ADC sam
Hi guys,
random.org said we have to update SVN with beta compiler. I'll update it
tonight.
Cheers,
Seb
2010/3/7 Joep Suijs
> Hi Seb,
>
> 2010/3/7 Sebastien Lelong :
> > Maybe this website could help :)
> > http://www.random.org/dice/?num=2
>
> I guess you mean
> http://www.random.org/dice/?num
Hi Seb,
2010/3/7 Sebastien Lelong :
> Maybe this website could help :)
> http://www.random.org/dice/?num=2
I guess you mean
http://www.random.org/dice/?num=3
Since we have three options: yes, no and postpone ;)
Joep
--
You received this message because you are subscribed to the Google Groups
Hi Rob,
>From what I understand, our definitive decision about putting beta compiler
in Jallib SVN is temporarily postponed. Ah, procrastination, my friend :)
2010/3/7 Rob Hamerling
>
> JalV2 2.4n is required for the extended midrange PICs.
> I have reported two issues to Kyle. For one he gav
Hi Seb,
Sebastien Lelong wrote:
[about migrating to 2.4n(-beta)]
I think we didn't make the definitive choice... So, let's update SVN to
beta compiler (binaries, doc, etc... each time), we'll see if there are
too many troubles later.
What's 'definitive'? Everything is temporary ;-)
JalV2
Hi Rob,
I think we didn't make the definitive choice... So, let's update SVN to beta
compiler (binaries, doc, etc... each time), we'll see if there are too many
troubles later.
Cheers,
Seb
2010/3/7 Rob Hamerling
>
>
> bu...@sirloon.net wrote:
>
> This is buildbot speaking. I have finished a
bu...@sirloon.net wrote:
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: failed package
Logs
I've re-generated bee packages, available on download section
Seb
2010/1/3
> Hi guys,
>
> This is buildbot speaking. I have finished a build of jallib-bee on jallib.
> Buildslave for this Build: sebbot
>
> Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered
> this build
> B
Hi guys,
This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot
Build Reason: The Nightly scheduler named 'nightly build' triggered this build
Build Source Stamp: HEAD
Blamelist:
BUILD FAILED: failed svn
Logs are attached.
sincerely,
-The
50 matches
Mail list logo
