Hi again,
This is still a problem.
Regards,
Mike
On Thu, Jul 25, 2019 at 1:36 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> Hi,
>
> This is still a problem.
>
>
> Regards,
> Mike
>
> On Mon, Jul 22, 2019 at 6:40 PM Bertrand Jacquin
> wrote:
>
>> Hey,
>>
>> I just removed Jen
Hi,
This is still a problem.
Regards,
Mike
On Mon, Jul 22, 2019 at 6:40 PM Bertrand Jacquin
wrote:
> Hey,
>
> I just removed Jenkins notification since e5 is now gone from previous
> install.
>
> On Mon, Jul 22, 2019 at 09:10:24AM -0400, Mike Blumenkrantz wrote:
> > Hi,
> >
> > I'm still gett
Thanks!
On Mon, Jul 22, 2019 at 6:40 PM Bertrand Jacquin
wrote:
> Hey,
>
> I just removed Jenkins notification since e5 is now gone from previous
> install.
>
> On Mon, Jul 22, 2019 at 09:10:24AM -0400, Mike Blumenkrantz wrote:
> > Hi,
> >
> > I'm still getting a long delay while pushing to the
Hey,
I just removed Jenkins notification since e5 is now gone from previous
install.
On Mon, Jul 22, 2019 at 09:10:24AM -0400, Mike Blumenkrantz wrote:
> Hi,
>
> I'm still getting a long delay while pushing to the git server along with
>
> remote: post-receive-020-notify-jenkins: Notifying Jenk
Hi,
I'm still getting a long delay while pushing to the git server along with
remote: post-receive-020-notify-jenkins: Notifying Jenkins
remote: curl: (28) Connection timed out after 10006 milliseconds
Can this be disabled/fixed?
Thanks,
Mike
___
en
hi guys,
seems jenkins is already down, I would like to save the python-efl build
configuration, it was part of the release process and now I miss some info.
Is someone able to find the jenkins python-efl script in some way?
Thanks in advance
Il giorno mer 24 apr 2019 alle ore 09:49 Stefan Schmi
Hello.
[Beber CC'ed]
On 17.04.19 17:22, Mike Blumenkrantz wrote:
> Hi,
>
> I've been getting this when pushing to the efl repo lately:
>
> remote: post-receive-020-notify-jenkins: Notifying Jenkins
> remote: curl: (28) Connection timed out after 10004 milliseconds
>
> Does anyone know how to r
Hi,
I've been getting this when pushing to the efl repo lately:
remote: post-receive-020-notify-jenkins: Notifying Jenkins
remote: curl: (28) Connection timed out after 10004 milliseconds
Does anyone know how to resolve this?
Thanks,
Mike
___
enligh
Hi all, Beber in particular
we have jenkins failing to build python-efl in the last months, this is
caused by a too recent Cython version on the slave.
Python-efl do not support (yet) the >0.23.0 versions of cython
Is it possible to downgrade Cython to a 0.22.x version on the
e5-build-gentoo-x86
On 25/01/2015 17:42, Tom Hacohen wrote:
> On 25/01/15 17:03, Bertrand Jacquin wrote:
>> Hi,
>>
>> A new version of Jenkins in now available on
>> https://build.enlightenment.org which looks a bit more 2015 and fix a
>> lot of security issues.
>>
>> Coverity 7.6.0 is also there now, no ChangeLog a
On 25/01/15 17:03, Bertrand Jacquin wrote:
> Hi,
>
> A new version of Jenkins in now available on
> https://build.enlightenment.org which looks a bit more 2015 and fix a
> lot of security issues.
>
> Coverity 7.6.0 is also there now, no ChangeLog available.
>
Good job, thanks. :)
I see a message
Hi,
A new version of Jenkins in now available on
https://build.enlightenment.org which looks a bit more 2015 and fix a
lot of security issues.
Coverity 7.6.0 is also there now, no ChangeLog available.
--
Bertrand
--
Hello.
On 14/01/15 15:30, Bertrand Jacquin wrote:
> Hi,
>
> On 2015-01-14 09:40, Stefan Schmidt wrote:
>> Hello.
>>
>> On 13/01/15 16:13, Bertrand Jacquin wrote:
>>> Hello,
>>>
No new builds have been done now for a while since the x86_64 slave is
not able
to be authenticated correc
Hello.
On 13/01/15 16:13, Bertrand Jacquin wrote:
> Hello,
>
>> No new builds have been done now for a while since the x86_64 slave is
>> not able
>> to be authenticated correctly.
>
> Now fixed, the public keys has vanished.
>
> See https://build.enlightenment.org/computer
>
I was able to get mos
On 2015-01-13 16:07, Stefan Schmidt wrote:
> Hello.
>
> On 13/01/15 16:52, Bertrand Jacquin wrote:
>> On 2015-01-13 15:21, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 13/01/15 16:13, Bertrand Jacquin wrote:
Hello,
> No new builds have been done now for a while since the x86_64 slav
Hello.
On 13/01/15 16:52, Bertrand Jacquin wrote:
> On 2015-01-13 15:21, Stefan Schmidt wrote:
>> Hello.
>>
>> On 13/01/15 16:13, Bertrand Jacquin wrote:
>>> Hello,
>>>
No new builds have been done now for a while since the x86_64 slave is
not able
to be authenticated correctly.
>>>
On 2015-01-13 15:21, Stefan Schmidt wrote:
> Hello.
>
> On 13/01/15 16:13, Bertrand Jacquin wrote:
>> Hello,
>>
>>> No new builds have been done now for a while since the x86_64 slave
>>> is
>>> not able
>>> to be authenticated correctly.
>>
>> Now fixed, the public keys has vanished.
>>
>> Se
Hello.
On 13/01/15 16:13, Bertrand Jacquin wrote:
> Hello,
>
>> No new builds have been done now for a while since the x86_64 slave is
>> not able
>> to be authenticated correctly.
>
> Now fixed, the public keys has vanished.
>
> See https://build.enlightenment.org/computer
>
Thanks. The space pro
2013/6/5 Bertrand Jacquin
> Hi,
>
> > ok, thanks. I created the base_efl_build_python job (not sure I
> > correctly
> > followed
> > your standards tought). The job checkout from git well, the workspace
> > is
> > created and the first command I try run (python setup.py build_ext),
> > but
> > it
Hi,
> ok, thanks. I created the base_efl_build_python job (not sure I
> correctly
> followed
> your standards tought). The job checkout from git well, the workspace
> is
> created and the first command I try run (python setup.py build_ext),
> but
> it fail because it can't find eo.pc.
> How tha
2013/5/30 Daniel Willmann
> Hi,
>
> On 29/05/13 23:30, Davide Andreoli wrote:
> > 2013/5/29 Stefan Schmidt
>
> > Now I'm officially asking if someone that manage jenkins would like to
> > include python-efl... or give me instructions on how to do it myself...
> or
> > just say: no we will not in
Hi,
On 29/05/13 23:30, Davide Andreoli wrote:
> 2013/5/29 Stefan Schmidt
> Now I'm officially asking if someone that manage jenkins would like to
> include python-efl... or give me instructions on how to do it myself... or
> just say: no we will not include it, so that I can move in other
> dire
2013/5/29 Stefan Schmidt
> Hello.
>
> On Wed, 2013-05-29 at 21:21, Davide Andreoli wrote:
> > 2013/5/16 Kai Huuhko
> >
> > > 03.05.2013 01:10, Davide Andreoli kirjoitti:
> > > > 2013/5/2 Bertrand Jacquin
> > > >
> > > >>> I would like to use jenkis for python-efl, so I'm requesting more
> work
On 2013-05-29 21:21, Davide Andreoli wrote:
> 2013/5/16 Kai Huuhko
>
>> 03.05.2013 01:10, Davide Andreoli kirjoitti:
>>> 2013/5/2 Bertrand Jacquin
>>>
> I would like to use jenkis for python-efl, so I'm requesting more
> work
> for
> you.
>
> Ideally this is what I lik
Hello.
On Wed, 2013-05-29 at 21:21, Davide Andreoli wrote:
> 2013/5/16 Kai Huuhko
>
> > 03.05.2013 01:10, Davide Andreoli kirjoitti:
> > > 2013/5/2 Bertrand Jacquin
> > >
> > >>> I would like to use jenkis for python-efl, so I'm requesting more work
> > >>> for
> > >>> you.
> > >>>
> > >>> Idea
2013/5/16 Kai Huuhko
> 03.05.2013 01:10, Davide Andreoli kirjoitti:
> > 2013/5/2 Bertrand Jacquin
> >
> >>> I would like to use jenkis for python-efl, so I'm requesting more work
> >>> for
> >>> you.
> >>>
> >>> Ideally this is what I like to see implemented:
> >>> 1. build of the bindings with
03.05.2013 01:10, Davide Andreoli kirjoitti:
> 2013/5/2 Bertrand Jacquin
>
>>> I would like to use jenkis for python-efl, so I'm requesting more work
>>> for
>>> you.
>>>
>>> Ideally this is what I like to see implemented:
>>> 1. build of the bindings with both python2 and python3
>> What we have
2013/5/2 Bertrand Jacquin
> > I would like to use jenkis for python-efl, so I'm requesting more work
> > for
> > you.
> >
> > Ideally this is what I like to see implemented:
> > 1. build of the bindings with both python2 and python3
>
> What we have an all slaves :
> - python2.5
> - python2.6
> I would like to use jenkis for python-efl, so I'm requesting more work
> for
> you.
>
> Ideally this is what I like to see implemented:
> 1. build of the bindings with both python2 and python3
What we have an all slaves :
- python2.5
- python2.6
- python2.7
- python3.1
- python3.2 (d
2013/5/2 Daniel Willmann
> Hello,
>
> it has now been almost 2 months since we started setting up the first
> jobs on Jenkins and I want to thank you all.
>
> Out of 750 builds (the last 50 of each job) only 2% actually failed
> which I think is really great.
>
> We are currently building efl, el
Good job everyone, and many thanks to Daniel and Stefan for doing this
awesome work.
On Thu, May 2, 2013 at 4:38 PM, Daniel Willmann wrote:
> Hello,
>
> it has now been almost 2 months since we started setting up the first
> jobs on Jenkins and I want to thank you all.
>
> Out of 750 builds (the
Hello,
it has now been almost 2 months since we started setting up the first
jobs on Jenkins and I want to thank you all.
Out of 750 builds (the last 50 of each job) only 2% actually failed
which I think is really great.
We are currently building efl, elm and e on 32 and 64-bit Linux both
with g
Hello,
On Sun, Apr 28, 2013 at 5:13 AM, Daniel Willmann
wrote:
> On Sat, 27 Apr 2013 00:33:06 +0200
> Bertrand Jacquin wrote:
>
>> clang is 3.2 as the 3.3 trunk does not build.
> [...]
>> no qemu-guest-agent, as does not build
>
> Sounds like we're not the only project struggling :-)
>
>> D'ar s
> no udisk/upower yet
In now :)
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and
On 2013-04-27 22:13, Daniel Willmann wrote:
> Hey Beber,
>
> On Sat, 27 Apr 2013 00:33:06 +0200
> Bertrand Jacquin wrote:
>
>> clang is 3.2 as the 3.3 trunk does not build.
> [...]
>> no qemu-guest-agent, as does not build
>
> Sounds like we're not the only project struggling :-)
Yeah ! There
Hey Beber,
On Sat, 27 Apr 2013 00:33:06 +0200
Bertrand Jacquin wrote:
> clang is 3.2 as the 3.3 trunk does not build.
[...]
> no qemu-guest-agent, as does not build
Sounds like we're not the only project struggling :-)
> D'ar sadorn 27 a viz Ebrel 2013 e 00 eur 22, « Bertrand Jacquin » he
> de
For you dan & stef,
Library are installed on {,/usr}/libx32
clang is 3.2 as the 3.3 trunk does not build.
only gcc-4.7 as support as started with this release.
ruby 1.8 only as 1.9 does not build.
ffmpeg is not linked to pthread as the build fail. no xine-lib either.
no udisk/upower yet
imag
Hi guys,
A new build VM is now available on jenkins nodes. This one is a
ARCH=amd64 with x32 ABI.
This new ABI may lead to some ASM inconstancy.
The main advantage is this new ABI is that all the x86_64 registers are
used while pointers are 32bits only. This lead to some performances
gains at ab
On 21/03/13 17:21, David Seikel wrote:
> On Thu, 21 Mar 2013 17:09:49 + Daniel Willmann
> wrote:
>
>> On 19/03/13 17:43, Daniel Willmann wrote:
>>> All was fine until earlier today when the Jenkins bot got kicked
>>> from #edevelop for use of colors and excessive messaging. I
>>> disabled col
On Thu, 21 Mar 2013 17:09:49 + Daniel Willmann
wrote:
> On 19/03/13 17:43, Daniel Willmann wrote:
> > All was fine until earlier today when the Jenkins bot got kicked
> > from #edevelop for use of colors and excessive messaging. I
> > disabled colors and reduced the message to only report suc
On 19/03/13 17:43, Daniel Willmann wrote:
> All was fine until earlier today when the Jenkins bot got kicked from
> #edevelop for use of colors and excessive messaging. I disabled colors
> and reduced the message to only report success of failure in order to
> have the bot in the channel again.
[.
On Wed, Mar 20, 2013 at 12:17 AM, Cedric BAIL wrote:
> On Wed, Mar 20, 2013 at 2:49 AM, Michael Blumenkrantz
> wrote:
>> On Tue, 19 Mar 2013 17:43:41 +
>> Daniel Willmann wrote:
>>> as you know we have had Jenkins running and reporting build issues for
>>> almost two weeks now. After initial
On 20/03/13 09:53, Michael Blumenkrantz wrote:
> On Wed, Mar 20, 2013 at 9:36 AM, Tom Hacohen wrote:
>
>> On 19/03/13 17:43, Daniel Willmann wrote:
>>> Hello,
>>>
>>> as you know we have had Jenkins running and reporting build issues for
>>> almost two weeks now. After initial hiccups I think it ha
On Wed, Mar 20, 2013 at 9:36 AM, Tom Hacohen wrote:
> On 19/03/13 17:43, Daniel Willmann wrote:
> > Hello,
> >
> > as you know we have had Jenkins running and reporting build issues for
> > almost two weeks now. After initial hiccups I think it has performed
> > quite well so far. I know of only o
On 19/03/13 17:43, Daniel Willmann wrote:
> Hello,
>
> as you know we have had Jenkins running and reporting build issues for
> almost two weeks now. After initial hiccups I think it has performed
> quite well so far. I know of only one occasion where Jenkins blamed the
> wrong commit for failing (
On Wed, Mar 20, 2013 at 2:49 AM, Michael Blumenkrantz
wrote:
> On Tue, 19 Mar 2013 17:43:41 +
> Daniel Willmann wrote:
>> as you know we have had Jenkins running and reporting build issues for
>> almost two weeks now. After initial hiccups I think it has performed
>> quite well so far. I know
On Wed, 20 Mar 2013 04:14:49 +1000
David Seikel wrote:
> On Tue, 19 Mar 2013 14:58:32 -0300 Iván Briano
> wrote:
>
> > On Tue, Mar 19, 2013 at 2:43 PM, Daniel Willmann
> > wrote:
> > > Hello,
> > >
> > > as you know we have had Jenkins running and reporting build issues
> > > for almost two we
* Michael Blumenkrantz [2013-03-19 17:49:30
+]:
> On Tue, 19 Mar 2013 17:43:41 +
> Daniel Willmann wrote:
>
> > Hello,
> >
> > as you know we have had Jenkins running and reporting build issues for
> > almost two weeks now. After initial hiccups I think it has performed
> > quite well
On Tue, 19 Mar 2013 14:58:32 -0300 Iván Briano
wrote:
> On Tue, Mar 19, 2013 at 2:43 PM, Daniel Willmann
> wrote:
> > Hello,
> >
> > as you know we have had Jenkins running and reporting build issues
> > for almost two weeks now. After initial hiccups I think it has
> > performed quite well so f
I like the bot.
On Tue, Mar 19, 2013 at 3:02 PM, Bruno Dilly wrote:
> On Tue, Mar 19, 2013 at 2:55 PM, Rafael Antognolli
> wrote:
> > Same here, the messages don't bother me at all.
> >
> > +1 for the old messages and colors (as long as it's R, G or B)
> >
> > On Tue, Mar 19, 2013 at 2:49 PM,
On Tue, Mar 19, 2013 at 2:55 PM, Rafael Antognolli wrote:
> Same here, the messages don't bother me at all.
>
> +1 for the old messages and colors (as long as it's R, G or B)
>
> On Tue, Mar 19, 2013 at 2:49 PM, Michael Blumenkrantz
> wrote:
>> On Tue, 19 Mar 2013 17:43:41 +
>> Daniel Willman
On Tue, Mar 19, 2013 at 2:43 PM, Daniel Willmann wrote:
> Hello,
>
> as you know we have had Jenkins running and reporting build issues for
> almost two weeks now. After initial hiccups I think it has performed
> quite well so far. I know of only one occasion where Jenkins blamed the
> wrong commi
Same here, the messages don't bother me at all.
+1 for the old messages and colors (as long as it's R, G or B)
On Tue, Mar 19, 2013 at 2:49 PM, Michael Blumenkrantz
wrote:
> On Tue, 19 Mar 2013 17:43:41 +
> Daniel Willmann wrote:
>
>> Hello,
>>
>> as you know we have had Jenkins running and
On Tue, 19 Mar 2013 17:43:41 +
Daniel Willmann wrote:
> Hello,
>
> as you know we have had Jenkins running and reporting build issues for
> almost two weeks now. After initial hiccups I think it has performed
> quite well so far. I know of only one occasion where Jenkins blamed the
> wrong c
Hello,
as you know we have had Jenkins running and reporting build issues for
almost two weeks now. After initial hiccups I think it has performed
quite well so far. I know of only one occasion where Jenkins blamed the
wrong commit for failing (and that was only because the segfault didn't
happen
55 matches
Mail list logo
