You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2013/12/09 08:52:34 UTC
[Builds/Jenkins] Help and advise needed
Hi,
I'm having some difficulty getting the 'regular' builds on 'build@a.o'
working. For those not subscribed to the builds list, the situation is
as follows:
- there are supposedly 9 admins for the windows1 slave, but only one
is sporadically active. I've requested access to the machine, but got
the answer: "nine is enough." A suggestions there was actually only
one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to
remove old, inactive admins and add new, active ones
- since the windows1 slave is old, full and overworked, it regularly
went down for days on end. We are one of the few projects that uses
the windows slaves, so I ended up being the guy who always complains
the slave is down...
- the one active admin is now working on a second slave (windows2). In
itself, that is a very good thing. However, in his own words, "he
feels entitled to use our builds to experiment." I feel that is wrong,
but I know better than to further aggravate my relation with him by
objecting too strongly.
The point of this elaborate introduction is this: somewhere in his
experiments he broke the Windows slaves for our builds. We have not
had a successful build in a week. Normally, not that big a deal, but
with the third party IDE people working on FlexJS and the very active
mobile development both relying on nightly builds, I feel this is not
a time to NOT have clean, daily builds of all our projects...
Anything 'negative' I say on the builds list will certainly make
things worse - my NL temperament and lack of finesse often does not
sit well with US recipients ;-) - so I would ask you to please chime
in on the builds list and that we together get our builds back to
functioning.
Thanks!
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 10, 2013 12:42 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> I would suggest that if you have a functioning VM, we use it to run
> the builds that are currently on 'builds@a.o'. That is just too high
> maintenance (I spend about 2 hrs a week on the various issues there).
>
> EdB
Okay, will do.
But still want to make the VM itself easily clonable first.
Thanks,
Om
>
>
>
> On Tue, Dec 10, 2013 at 9:36 AM, OmPrakash Muppirala
> <bi...@gmail.com> wrote:
> > On Dec 9, 2013 11:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >>
> >>
> >> On 12/9/13 11:12 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
> >>
> >> >Remember, Gavin (builds@a.o) claim he changed nothing on the slave
> >> >that's now failing. I'm sure we didn't change anything on the Jenkins
> >> >job that is now failing. It isn't something in the SDK that's causing
> >> >this, lot's of people and the Mustella VM are building that regularly.
> >> >
> >> >Anyway: I'm not familiar with Pixelbender at all, is there some way we
> >> >can ask Gavin to test it on the slave that doesn't involve Jenkins?
> >> >Like a command line that he can simply copy-paste into a shell and
> >> >give us the results from?
> >> Yeah, it is a pretty simple compiler. All we do is give it a command
that
> >> is effectively pbutil <input> <output> as in:
> >> "$PIXELBENDER_HOME\pbutil.exe"
> >>
> >
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
> >> r.pbk
> >>
> >
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
> >> r.pbj
> >>
> >> If you have a windows machine please verify that I didn't type that
wrong,
> >> I'm on my mac right now.
> >>
> >> I know everyone claims "nothing changed". But I'm wondering if we can
> >> compare Om's VM setup against yours and fix Om's setup before we go
back
> >> and bug Gavin. Meanwhile, I'm trying to find the source to the
compiler.
> >
> > Unfortunately I had to kill the VM and recreate a new one. I went
through
> > the whole setup and PB runs like a champ now.
> >
> > Good news is that I can start working on making this the second slave to
> > Erik's VM.
> >
> > I am also planning on creating a public clonable image so that other
> > committers can start creating their VMsand bring them online as well.
> >
> > This way, we could continue to reduce our dependence on builds@a.o.
> >
> > Thanks,
> > Om
> >
> >>
> >> I have a wild guess that the aif dlls have some silly check for graphic
> >> cards or some other Photoshop or After Effects dependency. Or maybe
some
> >> OpenGL library that comes with newer versions of Windows. If it is a
> >> graphics card thing then some hardware change or configuration outside
the
> >> slave itself could have caused things to fail. Then everyone would
> >> technically be right that the nothing changed in the Slave or our code.
> >>
> >>
> >> -Alex
> >>
> >> >
> >> >EdB
> >> >
> >> >
> >> >
> >> >On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
> >> >> I tried to reproduce the failure on my machine but couldn't. I
tried
> >> >> different path statements, removing the aif_* dlls, and changing
> > execute
> >> >> rights on those dlls. I did find that the string "Internal
Exception"
> >> >>is
> >> >> in the aif_core.dll.
> >> >>
> >> >> Not sure what to do next, but now I'm thinking: maybe nobody has
seen
> >> >>this
> >> >> on their local computers? Only on the Jenkins Windows Slave and
> > Windows
> >> >> VM? What do they have in common? What version of Windows are they
> >> >> running? What kind of graphics cards do they have?
> >> >>
> >> >> -Alex
> >> >>
> >> >> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com>
> > wrote:
> >> >>
> >> >>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >>>>
> >> >>>> Ah, that thread looked like it was a year old. Did you work
around
> > it
> >> >>>>or
> >> >>>> just stop working on it?
> >> >>>
> >> >>>I just stopped working on it because I hit a dead end. I was
clueless
> >> >>>as
> >> >>>to how to fix it.
> >> >>>
> >> >>>>
> >> >>>> Other than checking the path, I don't have any ideas to try at the
> >> >>>>moment.
> >> >>>>
> >> >>>> On your Azure VM, if you manually launch the compiler from Windows
> >> >>>>command
> >> >>>> prompt you get this error, right?
> >> >>>>
> >> >>>
> >> >>>I will try it out tonight and let you know.
> >> >>>
> >> >>>Thanks,
> >> >>>Om
> >> >>>
> >> >>>> -Alex
> >> >>>>
> >> >>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
> >> >>>>wrote:
> >> >>>>
> >> >>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >> >>>> >>
> >> >>>> >> We keep hitting this error, but the mail archives do not
document
> >> >>>>how
> >> >>>we
> >> >>>> >> fix it. This time, we should write down the answer. Om's hit
it,
> >> >>>> >>Justin
> >> >>>> >> hit it, I think I had it once. The emails seem to indicate
that
> > it
> >> >>>> >>ispath
> >> >>>> >> related, but the build.xml does at least check if the
pbutil.exe
> >> >>>>exists
> >> >>>> >> and is passing on that.
> >> >>>> >>
> >> >>>> >
> >> >>>> >In my case, I have not been able to fix it. In fact, if we are
> >> >>>>trying
> >> >>>>to
> >> >>>> >reproduce the problem, we could use my Mustella VM on Azure and
see
> >> >>>>if
> >> >>>>we
> >> >>>> >can figure out what is happening.
> >> >>>> >We can then apply that fix to the windows1 slave on
> > builds.apache.org
> >> >>>> >
> >> >>>> >Thanks,
> >> >>>> >Om
> >> >>>> >
> >> >>>> >> I'll try to see if I can repro on my windows box tonight.
> >> >>>> >>
> >> >>>> >> -Alex
> >> >>>> >>
> >> >>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
> >> >>>><ma...@systar.com>
> >> >>>> >> wrote:
> >> >>>> >>
> >> >>>> >> >Thanks Erik for the clarification.
> >> >>>> >> >
> >> >>>> >> >I confirm to you, I had to send the updated swc manually for
> >> >>>>testing
> >> >>>> >> >because the nightly build was down.
> >> >>>> >> >
> >> >>>> >> >Sorry, I didn't follow the thread from the beginning, so I
> > checked
> >> >>>>the
> >> >>>> >> >archives, maybe have missed something.
> >> >>>> >> >
> >> >>>> >> >I can see from the build logs that pixel bender build failed
and
> >> >>>>it
> >> >>>> >>seems
> >> >>>> >> >to be a path issue.
> >> >>>> >> >If that's correct, this is the path I am using on my local
build
> >> >>>>in
> >> >>>>my
> >> >>>> >> >env.properties:
> >> >>>> >> >
> >> >>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
> >> >>>>Utilities -
> >> >>>> >> >CS5\\Pixel Bender Toolkit 2
> >> >>>> >> >
> >> >>>> >> >I can see that in the build log, the path is:
> >> >>>> >> >
> >> >>>> >> >check-pixelbender-home:
> >> >>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
> > (x86)/Adobe/Adobe
> >> >>>> >> >Utilities - CS5/Pixel Bender Toolkit 2
> >> >>>> >> >
> >> >>>> >> >When I run it on my local env, it gives the following:
> >> >>>> >> >
> >> >>>> >> >[echo]
> >> >>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
Utilities
> > -
> >> >>>> >> >CS5\Pixel Bender Toolkit 2
> >> >>>> >> >
> >> >>>> >> >So maybe using "\" instead of "/" could fix the issue ?
> >> >>>> >> >
> >> >>>> >> >WDYT?
> >> >>>> >> >
> >> >>>> >> >Maurice
> >> >>>> >> >
> >> >>>> >> >-----Message d'origine-----
> >> >>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> >> >>>> >> >Envoyé : lundi 9 décembre 2013 08:53
> >> >>>> >> >À : dev@flex.apache.org
> >> >>>> >> >Objet : [Builds/Jenkins] Help and advise needed
> >> >>>> >> >
> >> >>>> >> >Hi,
> >> >>>> >> >
> >> >>>> >> >I'm having some difficulty getting the 'regular' builds on
> >> >>>>'build@a.o'
> >> >>>> >> >working. For those not subscribed to the builds list, the
> >> >>>>situation
> >> >>>>is
> >> >>>> >>as
> >> >>>> >> >follows:
> >> >>>> >> >
> >> >>>> >> >- there are supposedly 9 admins for the windows1 slave, but
only
> >> >>>>one
> >> >>>is
> >> >>>> >> >sporadically active. I've requested access to the machine, but
> > got
> >> >>>>the
> >> >>>> >> >answer: "nine is enough." A suggestions there was actually
only
> >> >>>>one,
> >> >>>> >>with
> >> >>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
> >> >>>>remove
> >> >>>> >>old,
> >> >>>> >> >inactive admins and add new, active ones
> >> >>>> >> >
> >> >>>> >> >- since the windows1 slave is old, full and overworked, it
> >> >>>>regularly
> >> >>>> >>went
> >> >>>> >> >down for days on end. We are one of the few projects that uses
> > the
> >> >>>> >> >windows slaves, so I ended up being the guy who always
complains
> >> >>>>the
> >> >>>> >> >slave is down...
> >> >>>> >> >
> >> >>>> >> >- the one active admin is now working on a second slave
> >> >>>>(windows2).
> >> >>>>In
> >> >>>> >> >itself, that is a very good thing. However, in his own words,
"he
> >> >>>feels
> >> >>>> >> >entitled to use our builds to experiment." I feel that is
wrong,
> >> >>>>but I
> >> >>>> >> >know better than to further aggravate my relation with him by
> >> >>>objecting
> >> >>>> >> >too strongly.
> >> >>>> >> >
> >> >>>> >> >The point of this elaborate introduction is this: somewhere in
> > his
> >> >>>> >> >experiments he broke the Windows slaves for our builds. We
have
> >> >>>>not
> >> >>>> >>had a
> >> >>>> >> >successful build in a week. Normally, not that big a deal, but
> >> >>>>with
> >> >>>the
> >> >>>> >> >third party IDE people working on FlexJS and the very active
> >> >>>>mobile
> >> >>>> >> >development both relying on nightly builds, I feel this is
not a
> >> >>>>time
> >> >>>> >>to
> >> >>>> >> >NOT have clean, daily builds of all our projects...
> >> >>>> >> >
> >> >>>> >> >Anything 'negative' I say on the builds list will certainly
make
> >> >>>things
> >> >>>> >> >worse - my NL temperament and lack of finesse often does not
sit
> >> >>>>well
> >> >>>> >> >with US recipients ;-) - so I would ask you to please chime
in on
> >> >>>>the
> >> >>>> >> >builds list and that we together get our builds back to
> >> >>>>functioning.
> >> >>>> >> >
> >> >>>> >> >Thanks!
> >> >>>> >> >
> >> >>>> >> >EdB
> >> >>>> >> >
> >> >>>> >> >
> >> >>>> >> >
> >> >>>> >> >--
> >> >>>> >> >Ix Multimedia Software
> >> >>>> >> >
> >> >>>> >> >Jan Luykenstraat 27
> >> >>>> >> >3521 VB Utrecht
> >> >>>> >> >
> >> >>>> >> >T. 06-51952295
> >> >>>> >> >I. www.ixsoftware.nl
> >> >>>> >>
> >> >>>>
> >> >>
> >> >
> >> >
> >> >
> >> >--
> >> >Ix Multimedia Software
> >> >
> >> >Jan Luykenstraat 27
> >> >3521 VB Utrecht
> >> >
> >> >T. 06-51952295
> >> >I. www.ixsoftware.nl
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I would suggest that if you have a functioning VM, we use it to run
the builds that are currently on 'builds@a.o'. That is just too high
maintenance (I spend about 2 hrs a week on the various issues there).
EdB
On Tue, Dec 10, 2013 at 9:36 AM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> On Dec 9, 2013 11:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>
>>
>> On 12/9/13 11:12 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> >Remember, Gavin (builds@a.o) claim he changed nothing on the slave
>> >that's now failing. I'm sure we didn't change anything on the Jenkins
>> >job that is now failing. It isn't something in the SDK that's causing
>> >this, lot's of people and the Mustella VM are building that regularly.
>> >
>> >Anyway: I'm not familiar with Pixelbender at all, is there some way we
>> >can ask Gavin to test it on the slave that doesn't involve Jenkins?
>> >Like a command line that he can simply copy-paste into a shell and
>> >give us the results from?
>> Yeah, it is a pretty simple compiler. All we do is give it a command that
>> is effectively pbutil <input> <output> as in:
>> "$PIXELBENDER_HOME\pbutil.exe"
>>
> $FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
>> r.pbk
>>
> $FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
>> r.pbj
>>
>> If you have a windows machine please verify that I didn't type that wrong,
>> I'm on my mac right now.
>>
>> I know everyone claims "nothing changed". But I'm wondering if we can
>> compare Om's VM setup against yours and fix Om's setup before we go back
>> and bug Gavin. Meanwhile, I'm trying to find the source to the compiler.
>
> Unfortunately I had to kill the VM and recreate a new one. I went through
> the whole setup and PB runs like a champ now.
>
> Good news is that I can start working on making this the second slave to
> Erik's VM.
>
> I am also planning on creating a public clonable image so that other
> committers can start creating their VMsand bring them online as well.
>
> This way, we could continue to reduce our dependence on builds@a.o.
>
> Thanks,
> Om
>
>>
>> I have a wild guess that the aif dlls have some silly check for graphic
>> cards or some other Photoshop or After Effects dependency. Or maybe some
>> OpenGL library that comes with newer versions of Windows. If it is a
>> graphics card thing then some hardware change or configuration outside the
>> slave itself could have caused things to fail. Then everyone would
>> technically be right that the nothing changed in the Slave or our code.
>>
>>
>> -Alex
>>
>> >
>> >EdB
>> >
>> >
>> >
>> >On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>> >> I tried to reproduce the failure on my machine but couldn't. I tried
>> >> different path statements, removing the aif_* dlls, and changing
> execute
>> >> rights on those dlls. I did find that the string "Internal Exception"
>> >>is
>> >> in the aif_core.dll.
>> >>
>> >> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>> >>this
>> >> on their local computers? Only on the Jenkins Windows Slave and
> Windows
>> >> VM? What do they have in common? What version of Windows are they
>> >> running? What kind of graphics cards do they have?
>> >>
>> >> -Alex
>> >>
>> >> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
>> >>
>> >>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>>>
>> >>>> Ah, that thread looked like it was a year old. Did you work around
> it
>> >>>>or
>> >>>> just stop working on it?
>> >>>
>> >>>I just stopped working on it because I hit a dead end. I was clueless
>> >>>as
>> >>>to how to fix it.
>> >>>
>> >>>>
>> >>>> Other than checking the path, I don't have any ideas to try at the
>> >>>>moment.
>> >>>>
>> >>>> On your Azure VM, if you manually launch the compiler from Windows
>> >>>>command
>> >>>> prompt you get this error, right?
>> >>>>
>> >>>
>> >>>I will try it out tonight and let you know.
>> >>>
>> >>>Thanks,
>> >>>Om
>> >>>
>> >>>> -Alex
>> >>>>
>> >>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>> >>>>wrote:
>> >>>>
>> >>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>>> >>
>> >>>> >> We keep hitting this error, but the mail archives do not document
>> >>>>how
>> >>>we
>> >>>> >> fix it. This time, we should write down the answer. Om's hit it,
>> >>>> >>Justin
>> >>>> >> hit it, I think I had it once. The emails seem to indicate that
> it
>> >>>> >>ispath
>> >>>> >> related, but the build.xml does at least check if the pbutil.exe
>> >>>>exists
>> >>>> >> and is passing on that.
>> >>>> >>
>> >>>> >
>> >>>> >In my case, I have not been able to fix it. In fact, if we are
>> >>>>trying
>> >>>>to
>> >>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>> >>>>if
>> >>>>we
>> >>>> >can figure out what is happening.
>> >>>> >We can then apply that fix to the windows1 slave on
> builds.apache.org
>> >>>> >
>> >>>> >Thanks,
>> >>>> >Om
>> >>>> >
>> >>>> >> I'll try to see if I can repro on my windows box tonight.
>> >>>> >>
>> >>>> >> -Alex
>> >>>> >>
>> >>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>> >>>><ma...@systar.com>
>> >>>> >> wrote:
>> >>>> >>
>> >>>> >> >Thanks Erik for the clarification.
>> >>>> >> >
>> >>>> >> >I confirm to you, I had to send the updated swc manually for
>> >>>>testing
>> >>>> >> >because the nightly build was down.
>> >>>> >> >
>> >>>> >> >Sorry, I didn't follow the thread from the beginning, so I
> checked
>> >>>>the
>> >>>> >> >archives, maybe have missed something.
>> >>>> >> >
>> >>>> >> >I can see from the build logs that pixel bender build failed and
>> >>>>it
>> >>>> >>seems
>> >>>> >> >to be a path issue.
>> >>>> >> >If that's correct, this is the path I am using on my local build
>> >>>>in
>> >>>>my
>> >>>> >> >env.properties:
>> >>>> >> >
>> >>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>> >>>>Utilities -
>> >>>> >> >CS5\\Pixel Bender Toolkit 2
>> >>>> >> >
>> >>>> >> >I can see that in the build log, the path is:
>> >>>> >> >
>> >>>> >> >check-pixelbender-home:
>> >>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
> (x86)/Adobe/Adobe
>> >>>> >> >Utilities - CS5/Pixel Bender Toolkit 2
>> >>>> >> >
>> >>>> >> >When I run it on my local env, it gives the following:
>> >>>> >> >
>> >>>> >> >[echo]
>> >>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
> -
>> >>>> >> >CS5\Pixel Bender Toolkit 2
>> >>>> >> >
>> >>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>> >>>> >> >
>> >>>> >> >WDYT?
>> >>>> >> >
>> >>>> >> >Maurice
>> >>>> >> >
>> >>>> >> >-----Message d'origine-----
>> >>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>> >>>> >> >Envoyé : lundi 9 décembre 2013 08:53
>> >>>> >> >À : dev@flex.apache.org
>> >>>> >> >Objet : [Builds/Jenkins] Help and advise needed
>> >>>> >> >
>> >>>> >> >Hi,
>> >>>> >> >
>> >>>> >> >I'm having some difficulty getting the 'regular' builds on
>> >>>>'build@a.o'
>> >>>> >> >working. For those not subscribed to the builds list, the
>> >>>>situation
>> >>>>is
>> >>>> >>as
>> >>>> >> >follows:
>> >>>> >> >
>> >>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>> >>>>one
>> >>>is
>> >>>> >> >sporadically active. I've requested access to the machine, but
> got
>> >>>>the
>> >>>> >> >answer: "nine is enough." A suggestions there was actually only
>> >>>>one,
>> >>>> >>with
>> >>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>> >>>>remove
>> >>>> >>old,
>> >>>> >> >inactive admins and add new, active ones
>> >>>> >> >
>> >>>> >> >- since the windows1 slave is old, full and overworked, it
>> >>>>regularly
>> >>>> >>went
>> >>>> >> >down for days on end. We are one of the few projects that uses
> the
>> >>>> >> >windows slaves, so I ended up being the guy who always complains
>> >>>>the
>> >>>> >> >slave is down...
>> >>>> >> >
>> >>>> >> >- the one active admin is now working on a second slave
>> >>>>(windows2).
>> >>>>In
>> >>>> >> >itself, that is a very good thing. However, in his own words, "he
>> >>>feels
>> >>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>> >>>>but I
>> >>>> >> >know better than to further aggravate my relation with him by
>> >>>objecting
>> >>>> >> >too strongly.
>> >>>> >> >
>> >>>> >> >The point of this elaborate introduction is this: somewhere in
> his
>> >>>> >> >experiments he broke the Windows slaves for our builds. We have
>> >>>>not
>> >>>> >>had a
>> >>>> >> >successful build in a week. Normally, not that big a deal, but
>> >>>>with
>> >>>the
>> >>>> >> >third party IDE people working on FlexJS and the very active
>> >>>>mobile
>> >>>> >> >development both relying on nightly builds, I feel this is not a
>> >>>>time
>> >>>> >>to
>> >>>> >> >NOT have clean, daily builds of all our projects...
>> >>>> >> >
>> >>>> >> >Anything 'negative' I say on the builds list will certainly make
>> >>>things
>> >>>> >> >worse - my NL temperament and lack of finesse often does not sit
>> >>>>well
>> >>>> >> >with US recipients ;-) - so I would ask you to please chime in on
>> >>>>the
>> >>>> >> >builds list and that we together get our builds back to
>> >>>>functioning.
>> >>>> >> >
>> >>>> >> >Thanks!
>> >>>> >> >
>> >>>> >> >EdB
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >--
>> >>>> >> >Ix Multimedia Software
>> >>>> >> >
>> >>>> >> >Jan Luykenstraat 27
>> >>>> >> >3521 VB Utrecht
>> >>>> >> >
>> >>>> >> >T. 06-51952295
>> >>>> >> >I. www.ixsoftware.nl
>> >>>> >>
>> >>>>
>> >>
>> >
>> >
>> >
>> >--
>> >Ix Multimedia Software
>> >
>> >Jan Luykenstraat 27
>> >3521 VB Utrecht
>> >
>> >T. 06-51952295
>> >I. www.ixsoftware.nl
>>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 9, 2013 11:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>
>
> On 12/9/13 11:12 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> >Remember, Gavin (builds@a.o) claim he changed nothing on the slave
> >that's now failing. I'm sure we didn't change anything on the Jenkins
> >job that is now failing. It isn't something in the SDK that's causing
> >this, lot's of people and the Mustella VM are building that regularly.
> >
> >Anyway: I'm not familiar with Pixelbender at all, is there some way we
> >can ask Gavin to test it on the slave that doesn't involve Jenkins?
> >Like a command line that he can simply copy-paste into a shell and
> >give us the results from?
> Yeah, it is a pretty simple compiler. All we do is give it a command that
> is effectively pbutil <input> <output> as in:
> "$PIXELBENDER_HOME\pbutil.exe"
>
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
> r.pbk
>
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
> r.pbj
>
> If you have a windows machine please verify that I didn't type that wrong,
> I'm on my mac right now.
>
> I know everyone claims "nothing changed". But I'm wondering if we can
> compare Om's VM setup against yours and fix Om's setup before we go back
> and bug Gavin. Meanwhile, I'm trying to find the source to the compiler.
Unfortunately I had to kill the VM and recreate a new one. I went through
the whole setup and PB runs like a champ now.
Good news is that I can start working on making this the second slave to
Erik's VM.
I am also planning on creating a public clonable image so that other
committers can start creating their VMsand bring them online as well.
This way, we could continue to reduce our dependence on builds@a.o.
Thanks,
Om
>
> I have a wild guess that the aif dlls have some silly check for graphic
> cards or some other Photoshop or After Effects dependency. Or maybe some
> OpenGL library that comes with newer versions of Windows. If it is a
> graphics card thing then some hardware change or configuration outside the
> slave itself could have caused things to fail. Then everyone would
> technically be right that the nothing changed in the Slave or our code.
>
>
> -Alex
>
> >
> >EdB
> >
> >
> >
> >On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
> >> I tried to reproduce the failure on my machine but couldn't. I tried
> >> different path statements, removing the aif_* dlls, and changing
execute
> >> rights on those dlls. I did find that the string "Internal Exception"
> >>is
> >> in the aif_core.dll.
> >>
> >> Not sure what to do next, but now I'm thinking: maybe nobody has seen
> >>this
> >> on their local computers? Only on the Jenkins Windows Slave and
Windows
> >> VM? What do they have in common? What version of Windows are they
> >> running? What kind of graphics cards do they have?
> >>
> >> -Alex
> >>
> >> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com>
wrote:
> >>
> >>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >>>>
> >>>> Ah, that thread looked like it was a year old. Did you work around
it
> >>>>or
> >>>> just stop working on it?
> >>>
> >>>I just stopped working on it because I hit a dead end. I was clueless
> >>>as
> >>>to how to fix it.
> >>>
> >>>>
> >>>> Other than checking the path, I don't have any ideas to try at the
> >>>>moment.
> >>>>
> >>>> On your Azure VM, if you manually launch the compiler from Windows
> >>>>command
> >>>> prompt you get this error, right?
> >>>>
> >>>
> >>>I will try it out tonight and let you know.
> >>>
> >>>Thanks,
> >>>Om
> >>>
> >>>> -Alex
> >>>>
> >>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
> >>>>wrote:
> >>>>
> >>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >>>> >>
> >>>> >> We keep hitting this error, but the mail archives do not document
> >>>>how
> >>>we
> >>>> >> fix it. This time, we should write down the answer. Om's hit it,
> >>>> >>Justin
> >>>> >> hit it, I think I had it once. The emails seem to indicate that
it
> >>>> >>ispath
> >>>> >> related, but the build.xml does at least check if the pbutil.exe
> >>>>exists
> >>>> >> and is passing on that.
> >>>> >>
> >>>> >
> >>>> >In my case, I have not been able to fix it. In fact, if we are
> >>>>trying
> >>>>to
> >>>> >reproduce the problem, we could use my Mustella VM on Azure and see
> >>>>if
> >>>>we
> >>>> >can figure out what is happening.
> >>>> >We can then apply that fix to the windows1 slave on
builds.apache.org
> >>>> >
> >>>> >Thanks,
> >>>> >Om
> >>>> >
> >>>> >> I'll try to see if I can repro on my windows box tonight.
> >>>> >>
> >>>> >> -Alex
> >>>> >>
> >>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
> >>>><ma...@systar.com>
> >>>> >> wrote:
> >>>> >>
> >>>> >> >Thanks Erik for the clarification.
> >>>> >> >
> >>>> >> >I confirm to you, I had to send the updated swc manually for
> >>>>testing
> >>>> >> >because the nightly build was down.
> >>>> >> >
> >>>> >> >Sorry, I didn't follow the thread from the beginning, so I
checked
> >>>>the
> >>>> >> >archives, maybe have missed something.
> >>>> >> >
> >>>> >> >I can see from the build logs that pixel bender build failed and
> >>>>it
> >>>> >>seems
> >>>> >> >to be a path issue.
> >>>> >> >If that's correct, this is the path I am using on my local build
> >>>>in
> >>>>my
> >>>> >> >env.properties:
> >>>> >> >
> >>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
> >>>>Utilities -
> >>>> >> >CS5\\Pixel Bender Toolkit 2
> >>>> >> >
> >>>> >> >I can see that in the build log, the path is:
> >>>> >> >
> >>>> >> >check-pixelbender-home:
> >>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
(x86)/Adobe/Adobe
> >>>> >> >Utilities - CS5/Pixel Bender Toolkit 2
> >>>> >> >
> >>>> >> >When I run it on my local env, it gives the following:
> >>>> >> >
> >>>> >> >[echo]
> >>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
-
> >>>> >> >CS5\Pixel Bender Toolkit 2
> >>>> >> >
> >>>> >> >So maybe using "\" instead of "/" could fix the issue ?
> >>>> >> >
> >>>> >> >WDYT?
> >>>> >> >
> >>>> >> >Maurice
> >>>> >> >
> >>>> >> >-----Message d'origine-----
> >>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>>> >> >Envoyé : lundi 9 décembre 2013 08:53
> >>>> >> >À : dev@flex.apache.org
> >>>> >> >Objet : [Builds/Jenkins] Help and advise needed
> >>>> >> >
> >>>> >> >Hi,
> >>>> >> >
> >>>> >> >I'm having some difficulty getting the 'regular' builds on
> >>>>'build@a.o'
> >>>> >> >working. For those not subscribed to the builds list, the
> >>>>situation
> >>>>is
> >>>> >>as
> >>>> >> >follows:
> >>>> >> >
> >>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
> >>>>one
> >>>is
> >>>> >> >sporadically active. I've requested access to the machine, but
got
> >>>>the
> >>>> >> >answer: "nine is enough." A suggestions there was actually only
> >>>>one,
> >>>> >>with
> >>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
> >>>>remove
> >>>> >>old,
> >>>> >> >inactive admins and add new, active ones
> >>>> >> >
> >>>> >> >- since the windows1 slave is old, full and overworked, it
> >>>>regularly
> >>>> >>went
> >>>> >> >down for days on end. We are one of the few projects that uses
the
> >>>> >> >windows slaves, so I ended up being the guy who always complains
> >>>>the
> >>>> >> >slave is down...
> >>>> >> >
> >>>> >> >- the one active admin is now working on a second slave
> >>>>(windows2).
> >>>>In
> >>>> >> >itself, that is a very good thing. However, in his own words, "he
> >>>feels
> >>>> >> >entitled to use our builds to experiment." I feel that is wrong,
> >>>>but I
> >>>> >> >know better than to further aggravate my relation with him by
> >>>objecting
> >>>> >> >too strongly.
> >>>> >> >
> >>>> >> >The point of this elaborate introduction is this: somewhere in
his
> >>>> >> >experiments he broke the Windows slaves for our builds. We have
> >>>>not
> >>>> >>had a
> >>>> >> >successful build in a week. Normally, not that big a deal, but
> >>>>with
> >>>the
> >>>> >> >third party IDE people working on FlexJS and the very active
> >>>>mobile
> >>>> >> >development both relying on nightly builds, I feel this is not a
> >>>>time
> >>>> >>to
> >>>> >> >NOT have clean, daily builds of all our projects...
> >>>> >> >
> >>>> >> >Anything 'negative' I say on the builds list will certainly make
> >>>things
> >>>> >> >worse - my NL temperament and lack of finesse often does not sit
> >>>>well
> >>>> >> >with US recipients ;-) - so I would ask you to please chime in on
> >>>>the
> >>>> >> >builds list and that we together get our builds back to
> >>>>functioning.
> >>>> >> >
> >>>> >> >Thanks!
> >>>> >> >
> >>>> >> >EdB
> >>>> >> >
> >>>> >> >
> >>>> >> >
> >>>> >> >--
> >>>> >> >Ix Multimedia Software
> >>>> >> >
> >>>> >> >Jan Luykenstraat 27
> >>>> >> >3521 VB Utrecht
> >>>> >> >
> >>>> >> >T. 06-51952295
> >>>> >> >I. www.ixsoftware.nl
> >>>> >>
> >>>>
> >>
> >
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I. www.ixsoftware.nl
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Be sure to fill out the form as soon as you can (takes a couple of
minutes), because MS take a lot of time processing them.
EdB
On Tue, Dec 10, 2013 at 7:37 PM, Alex Harui <ah...@adobe.com> wrote:
> Maybe over the holiday break I'll try to get my MSDN subscription and VM.
>
> -Alex
>
> On 12/10/13 10:21 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Tue, Dec 10, 2013 at 10:13 AM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 9:48 AM, Erik de Bruin <er...@ixsoftware.nl>
>>>wrote:
>>>
>>>> I think he has the same MSDN as me, which should give him enough
>>>> 'credits' to run a medium sized VM for ever... I currently run the
>>>> Mustella VM as a large instance for about half a month, then switch it
>>>> to medium for the remainder. A bit of a hassle, but worth it to run
>>>> Mustella smoothly, I think. A 'regular' Jenkins server should run
>>>> perfectly fine on a medium instance.
>>>>
>>>> EdB
>>>>
>>>>
>>> Yes, that is correct. All Apache committers get a free MSDN
>>>subscription
>>> [1] which is supposed to be used for the benefit of Apache projects. A
>>> monthly credit for Windows Azure VMs comes with this subscription.
>>>
>>> My goal is to create a clone-able public image which has everything
>>>needed
>>> to run Mustella builds that each committer can instantiate and deploy.
>>>I
>>> want to make this whole process as simple as possible so that we can
>>>get as
>>> many committers' VMs up and running in no time.
>>>
>>> After that we will have one master Jenkins and set up all other VMs as
>>> slaves. This way, we can first distribute VMs to do runs of various
>>>FP/AIR
>>> combinations. And then eventually, break down Mustella tests into
>>>various
>>> sections and have each slave run a subset, in order to reduce the time
>>> taken for each Mustella run.
>>> And we need to dedicate a VM specifically for building the SDK (that
>>>Erik
>>> wanted) so as to reduce our dependence on builds@apache.org.
>>>
>>> I need a volunteer committer to help test out and document this process.
>>> Any takers?
>>>
>>> Thanks,
>>> Om
>>>
>>> [1]
>>>
>>>https://svn.apache.org/repos/private/committers/donated-licenses/msdn-sub
>>>scription.html
>>>
>>
>>
>>After the recent Mustella failures, I remembered that we need a VM for
>>Alex's patch server as well.
>>
>>Thanks,
>>Om
>>
>>
>>
>>>
>>>
>>>>
>>>>
>>>> On Tue, Dec 10, 2013 at 6:14 PM, Alex Harui <ah...@adobe.com> wrote:
>>>> > I don't think we actually know the cause of the problem. I am going
>>>>to
>>>> > continue to spend cycles to try to find out though.
>>>> >
>>>> > It would be nice to have an alternative to builds.a.o. I'm not sure
>>>>if
>>>> it
>>>> > will cost Om money to run a builds server.
>>>> >
>>>> > -Alex
>>>> >
>>>> > On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>>> > wrote:
>>>> >
>>>> >>I understand that.
>>>> >>
>>>> >>Actually, my "understanding" on this issue was that pixel bender
>>>> compiler
>>>> >>required some sort of hardware configuration (OpenGL, etc...) that
>>>>were
>>>> >>not present on the b.a.o. new Windows Jenkins slave node, so that's
>>>>why
>>>> >>the build was failing, and the Apache Infra was reluctant to let us
>>>> >>modify anything, or even access the VM ourselves.
>>>> >>So that's why I was proposing a "software only" solution.
>>>> >>
>>>> >>Now, it seems from what Om is saying that we can set up and use our
>>>>own
>>>> >>Jenkins slave node VM.
>>>> >>
>>>> >>That, of course, is much preferable...
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>> >>Envoyé : mardi 10 décembre 2013 10:44
>>>> >>À : dev@flex.apache.org
>>>> >>Objet : Re: [Builds/Jenkins] Help and advise needed
>>>> >>
>>>> >>Maurice,
>>>> >>
>>>> >>Your help is very much appreciated!
>>>> >>
>>>> >>I put "legal" in quotes, the issue is not really one of the law,
>>>>more of
>>>> >>the rules. An Apache release is supposed to be 'source only', and we
>>>>if
>>>> >>we can produce needed binaries from source, we keep only the source,
>>>>not
>>>> >>the artefacts themselves in the repo.
>>>> >>
>>>> >>
>>>> >>EdB
>>>> >>
>>>> >>
>>>> >>
>>>> >>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >><ma...@systar.com> wrote:
>>>> >>>>In addition to the various "legal" issues with binaries in the
>>>>repo.
>>>> >>> I understand it's not a good idea to have binaries in the repo, so
>>>>I
>>>> >>>won't insist.
>>>> >>> But please can you explain what are the legal issues of having
>>>> binaries
>>>> >>>in the repo? Is this because of Adobe, or ASF rules ?
>>>> >>>
>>>> >>> On a side note, I was just trying to help, with my limited
>>>> >>> understanding and knowledge, and because the email thread was
>>>>titled
>>>> >>> "help and advise needed" ;-)
>>>> >>>
>>>> >>> Regards,
>>>> >>>
>>>> >>> Maurice
>>>> >>>
>>>> >>> -----Message d'origine-----
>>>> >>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>> >>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>> [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>> In addition to the various "legal" issues with binaries in the
>>>>repo,
>>>> >>>we'd be masking the cause of this failure. In order to prevent
>>>>further
>>>> >>>deterioration of the build process, we need to figure out what went
>>>> >>>wrong and fix it.
>>>> >>>
>>>> >>> EdB
>>>> >>>
>>>> >>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>> >>> Took me while to figure out that I hadn't gone insane or if my
>>>> >>> keyboard was broken ;-)
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>><ma...@systar.com> wrote:
>>>> >>>>> someone who does use the pbj's will grab the nightly and
>>>>complain.
>>>> >>>>
>>>> >>>> I don't understand.
>>>> >>>> Why would someone complain if the pbj's are in the nightly?
>>>> >>>>
>>>> >>>> [From the other emai]
>>>> >>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>files
>>>> >>>>>were removed during the initial release audit.
>>>> >>>>>I don't think a workaround can involve checking in the pbj files.
>>>> But
>>>> >>>>>we could borrow them from a prior release package temporarily.
>>>> >>>>
>>>> >>>>>So we could make the compilation conditional on a env parameter,
>>>>and
>>>> >>>>>set that in the Jenkins job accordingly?
>>>> >>>>>Yes but ...
>>>> >>>>
>>>> >>>> Alex, the conversation is getting out synch, so I am not sure
>>>>that I
>>>> >>>>have understood what you said.
>>>> >>>>
>>>> >>>> So can we include the pbj in the repo, and have a parameter to
>>>> >>>>conditionally compile the pbj ?
>>>> >>>> - This parameter would be set by default to do the compilation (so
>>>> >>>> that folks can recompile)
>>>> >>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>> >>>>
>>>> >>>>
>>>> >>>> Maurice
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> --
>>>> >>> Ix Multimedia Software
>>>> >>>
>>>> >>> Jan Luykenstraat 27
>>>> >>> 3521 VB Utrecht
>>>> >>>
>>>> >>> T. 06-51952295
>>>> >>> I. www.ixsoftware.nl
>>>> >>
>>>> >>
>>>> >>
>>>> >>--
>>>> >>Ix Multimedia Software
>>>> >>
>>>> >>Jan Luykenstraat 27
>>>> >>3521 VB Utrecht
>>>> >>
>>>> >>T. 06-51952295
>>>> >>I. www.ixsoftware.nl
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Ix Multimedia Software
>>>>
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>>
>>>
>>>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Maybe over the holiday break I'll try to get my MSDN subscription and VM.
-Alex
On 12/10/13 10:21 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Tue, Dec 10, 2013 at 10:13 AM, OmPrakash Muppirala
><bi...@gmail.com>wrote:
>
>> On Tue, Dec 10, 2013 at 9:48 AM, Erik de Bruin <er...@ixsoftware.nl>
>>wrote:
>>
>>> I think he has the same MSDN as me, which should give him enough
>>> 'credits' to run a medium sized VM for ever... I currently run the
>>> Mustella VM as a large instance for about half a month, then switch it
>>> to medium for the remainder. A bit of a hassle, but worth it to run
>>> Mustella smoothly, I think. A 'regular' Jenkins server should run
>>> perfectly fine on a medium instance.
>>>
>>> EdB
>>>
>>>
>> Yes, that is correct. All Apache committers get a free MSDN
>>subscription
>> [1] which is supposed to be used for the benefit of Apache projects. A
>> monthly credit for Windows Azure VMs comes with this subscription.
>>
>> My goal is to create a clone-able public image which has everything
>>needed
>> to run Mustella builds that each committer can instantiate and deploy.
>>I
>> want to make this whole process as simple as possible so that we can
>>get as
>> many committers' VMs up and running in no time.
>>
>> After that we will have one master Jenkins and set up all other VMs as
>> slaves. This way, we can first distribute VMs to do runs of various
>>FP/AIR
>> combinations. And then eventually, break down Mustella tests into
>>various
>> sections and have each slave run a subset, in order to reduce the time
>> taken for each Mustella run.
>> And we need to dedicate a VM specifically for building the SDK (that
>>Erik
>> wanted) so as to reduce our dependence on builds@apache.org.
>>
>> I need a volunteer committer to help test out and document this process.
>> Any takers?
>>
>> Thanks,
>> Om
>>
>> [1]
>>
>>https://svn.apache.org/repos/private/committers/donated-licenses/msdn-sub
>>scription.html
>>
>
>
>After the recent Mustella failures, I remembered that we need a VM for
>Alex's patch server as well.
>
>Thanks,
>Om
>
>
>
>>
>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 6:14 PM, Alex Harui <ah...@adobe.com> wrote:
>>> > I don't think we actually know the cause of the problem. I am going
>>>to
>>> > continue to spend cycles to try to find out though.
>>> >
>>> > It would be nice to have an alternative to builds.a.o. I'm not sure
>>>if
>>> it
>>> > will cost Om money to run a builds server.
>>> >
>>> > -Alex
>>> >
>>> > On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>> > wrote:
>>> >
>>> >>I understand that.
>>> >>
>>> >>Actually, my "understanding" on this issue was that pixel bender
>>> compiler
>>> >>required some sort of hardware configuration (OpenGL, etc...) that
>>>were
>>> >>not present on the b.a.o. new Windows Jenkins slave node, so that's
>>>why
>>> >>the build was failing, and the Apache Infra was reluctant to let us
>>> >>modify anything, or even access the VM ourselves.
>>> >>So that's why I was proposing a "software only" solution.
>>> >>
>>> >>Now, it seems from what Om is saying that we can set up and use our
>>>own
>>> >>Jenkins slave node VM.
>>> >>
>>> >>That, of course, is much preferable...
>>> >>
>>> >>Maurice
>>> >>
>>> >>-----Message d'origine-----
>>> >>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>>> >>Envoyé : mardi 10 décembre 2013 10:44
>>> >>À : dev@flex.apache.org
>>> >>Objet : Re: [Builds/Jenkins] Help and advise needed
>>> >>
>>> >>Maurice,
>>> >>
>>> >>Your help is very much appreciated!
>>> >>
>>> >>I put "legal" in quotes, the issue is not really one of the law,
>>>more of
>>> >>the rules. An Apache release is supposed to be 'source only', and we
>>>if
>>> >>we can produce needed binaries from source, we keep only the source,
>>>not
>>> >>the artefacts themselves in the repo.
>>> >>
>>> >>
>>> >>EdB
>>> >>
>>> >>
>>> >>
>>> >>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>> >><ma...@systar.com> wrote:
>>> >>>>In addition to the various "legal" issues with binaries in the
>>>repo.
>>> >>> I understand it's not a good idea to have binaries in the repo, so
>>>I
>>> >>>won't insist.
>>> >>> But please can you explain what are the legal issues of having
>>> binaries
>>> >>>in the repo? Is this because of Adobe, or ASF rules ?
>>> >>>
>>> >>> On a side note, I was just trying to help, with my limited
>>> >>> understanding and knowledge, and because the email thread was
>>>titled
>>> >>> "help and advise needed" ;-)
>>> >>>
>>> >>> Regards,
>>> >>>
>>> >>> Maurice
>>> >>>
>>> >>> -----Message d'origine-----
>>> >>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>> >>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> >>> [Builds/Jenkins] Help and advise needed
>>> >>>
>>> >>> In addition to the various "legal" issues with binaries in the
>>>repo,
>>> >>>we'd be masking the cause of this failure. In order to prevent
>>>further
>>> >>>deterioration of the build process, we need to figure out what went
>>> >>>wrong and fix it.
>>> >>>
>>> >>> EdB
>>> >>>
>>> >>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>> >>> Took me while to figure out that I hadn't gone insane or if my
>>> >>> keyboard was broken ;-)
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>> >>><ma...@systar.com> wrote:
>>> >>>>> someone who does use the pbj's will grab the nightly and
>>>complain.
>>> >>>>
>>> >>>> I don't understand.
>>> >>>> Why would someone complain if the pbj's are in the nightly?
>>> >>>>
>>> >>>> [From the other emai]
>>> >>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>files
>>> >>>>>were removed during the initial release audit.
>>> >>>>>I don't think a workaround can involve checking in the pbj files.
>>> But
>>> >>>>>we could borrow them from a prior release package temporarily.
>>> >>>>
>>> >>>>>So we could make the compilation conditional on a env parameter,
>>>and
>>> >>>>>set that in the Jenkins job accordingly?
>>> >>>>>Yes but ...
>>> >>>>
>>> >>>> Alex, the conversation is getting out synch, so I am not sure
>>>that I
>>> >>>>have understood what you said.
>>> >>>>
>>> >>>> So can we include the pbj in the repo, and have a parameter to
>>> >>>>conditionally compile the pbj ?
>>> >>>> - This parameter would be set by default to do the compilation (so
>>> >>>> that folks can recompile)
>>> >>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>> >>>>
>>> >>>>
>>> >>>> Maurice
>>> >>>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Ix Multimedia Software
>>> >>>
>>> >>> Jan Luykenstraat 27
>>> >>> 3521 VB Utrecht
>>> >>>
>>> >>> T. 06-51952295
>>> >>> I. www.ixsoftware.nl
>>> >>
>>> >>
>>> >>
>>> >>--
>>> >>Ix Multimedia Software
>>> >>
>>> >>Jan Luykenstraat 27
>>> >>3521 VB Utrecht
>>> >>
>>> >>T. 06-51952295
>>> >>I. www.ixsoftware.nl
>>> >
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>>
>>
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 10:13 AM, OmPrakash Muppirala
<bi...@gmail.com>wrote:
> On Tue, Dec 10, 2013 at 9:48 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> I think he has the same MSDN as me, which should give him enough
>> 'credits' to run a medium sized VM for ever... I currently run the
>> Mustella VM as a large instance for about half a month, then switch it
>> to medium for the remainder. A bit of a hassle, but worth it to run
>> Mustella smoothly, I think. A 'regular' Jenkins server should run
>> perfectly fine on a medium instance.
>>
>> EdB
>>
>>
> Yes, that is correct. All Apache committers get a free MSDN subscription
> [1] which is supposed to be used for the benefit of Apache projects. A
> monthly credit for Windows Azure VMs comes with this subscription.
>
> My goal is to create a clone-able public image which has everything needed
> to run Mustella builds that each committer can instantiate and deploy. I
> want to make this whole process as simple as possible so that we can get as
> many committers' VMs up and running in no time.
>
> After that we will have one master Jenkins and set up all other VMs as
> slaves. This way, we can first distribute VMs to do runs of various FP/AIR
> combinations. And then eventually, break down Mustella tests into various
> sections and have each slave run a subset, in order to reduce the time
> taken for each Mustella run.
> And we need to dedicate a VM specifically for building the SDK (that Erik
> wanted) so as to reduce our dependence on builds@apache.org.
>
> I need a volunteer committer to help test out and document this process.
> Any takers?
>
> Thanks,
> Om
>
> [1]
> https://svn.apache.org/repos/private/committers/donated-licenses/msdn-subscription.html
>
After the recent Mustella failures, I remembered that we need a VM for
Alex's patch server as well.
Thanks,
Om
>
>
>>
>>
>> On Tue, Dec 10, 2013 at 6:14 PM, Alex Harui <ah...@adobe.com> wrote:
>> > I don't think we actually know the cause of the problem. I am going to
>> > continue to spend cycles to try to find out though.
>> >
>> > It would be nice to have an alternative to builds.a.o. I'm not sure if
>> it
>> > will cost Om money to run a builds server.
>> >
>> > -Alex
>> >
>> > On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>> > wrote:
>> >
>> >>I understand that.
>> >>
>> >>Actually, my "understanding" on this issue was that pixel bender
>> compiler
>> >>required some sort of hardware configuration (OpenGL, etc...) that were
>> >>not present on the b.a.o. new Windows Jenkins slave node, so that's why
>> >>the build was failing, and the Apache Infra was reluctant to let us
>> >>modify anything, or even access the VM ourselves.
>> >>So that's why I was proposing a "software only" solution.
>> >>
>> >>Now, it seems from what Om is saying that we can set up and use our own
>> >>Jenkins slave node VM.
>> >>
>> >>That, of course, is much preferable...
>> >>
>> >>Maurice
>> >>
>> >>-----Message d'origine-----
>> >>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>> >>Envoyé : mardi 10 décembre 2013 10:44
>> >>À : dev@flex.apache.org
>> >>Objet : Re: [Builds/Jenkins] Help and advise needed
>> >>
>> >>Maurice,
>> >>
>> >>Your help is very much appreciated!
>> >>
>> >>I put "legal" in quotes, the issue is not really one of the law, more of
>> >>the rules. An Apache release is supposed to be 'source only', and we if
>> >>we can produce needed binaries from source, we keep only the source, not
>> >>the artefacts themselves in the repo.
>> >>
>> >>
>> >>EdB
>> >>
>> >>
>> >>
>> >>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>> >><ma...@systar.com> wrote:
>> >>>>In addition to the various "legal" issues with binaries in the repo.
>> >>> I understand it's not a good idea to have binaries in the repo, so I
>> >>>won't insist.
>> >>> But please can you explain what are the legal issues of having
>> binaries
>> >>>in the repo? Is this because of Adobe, or ASF rules ?
>> >>>
>> >>> On a side note, I was just trying to help, with my limited
>> >>> understanding and knowledge, and because the email thread was titled
>> >>> "help and advise needed" ;-)
>> >>>
>> >>> Regards,
>> >>>
>> >>> Maurice
>> >>>
>> >>> -----Message d'origine-----
>> >>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>> >>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> >>> [Builds/Jenkins] Help and advise needed
>> >>>
>> >>> In addition to the various "legal" issues with binaries in the repo,
>> >>>we'd be masking the cause of this failure. In order to prevent further
>> >>>deterioration of the build process, we need to figure out what went
>> >>>wrong and fix it.
>> >>>
>> >>> EdB
>> >>>
>> >>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>> >>> Took me while to figure out that I hadn't gone insane or if my
>> >>> keyboard was broken ;-)
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>> >>><ma...@systar.com> wrote:
>> >>>>> someone who does use the pbj's will grab the nightly and complain.
>> >>>>
>> >>>> I don't understand.
>> >>>> Why would someone complain if the pbj's are in the nightly?
>> >>>>
>> >>>> [From the other emai]
>> >>>>>Apache repos aren't supposed to contain compiled code. The pbj files
>> >>>>>were removed during the initial release audit.
>> >>>>>I don't think a workaround can involve checking in the pbj files.
>> But
>> >>>>>we could borrow them from a prior release package temporarily.
>> >>>>
>> >>>>>So we could make the compilation conditional on a env parameter, and
>> >>>>>set that in the Jenkins job accordingly?
>> >>>>>Yes but ...
>> >>>>
>> >>>> Alex, the conversation is getting out synch, so I am not sure that I
>> >>>>have understood what you said.
>> >>>>
>> >>>> So can we include the pbj in the repo, and have a parameter to
>> >>>>conditionally compile the pbj ?
>> >>>> - This parameter would be set by default to do the compilation (so
>> >>>> that folks can recompile)
>> >>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>> >>>>
>> >>>>
>> >>>> Maurice
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Ix Multimedia Software
>> >>>
>> >>> Jan Luykenstraat 27
>> >>> 3521 VB Utrecht
>> >>>
>> >>> T. 06-51952295
>> >>> I. www.ixsoftware.nl
>> >>
>> >>
>> >>
>> >>--
>> >>Ix Multimedia Software
>> >>
>> >>Jan Luykenstraat 27
>> >>3521 VB Utrecht
>> >>
>> >>T. 06-51952295
>> >>I. www.ixsoftware.nl
>> >
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>
>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 9:48 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> I think he has the same MSDN as me, which should give him enough
> 'credits' to run a medium sized VM for ever... I currently run the
> Mustella VM as a large instance for about half a month, then switch it
> to medium for the remainder. A bit of a hassle, but worth it to run
> Mustella smoothly, I think. A 'regular' Jenkins server should run
> perfectly fine on a medium instance.
>
> EdB
>
>
Yes, that is correct. All Apache committers get a free MSDN subscription
[1] which is supposed to be used for the benefit of Apache projects. A
monthly credit for Windows Azure VMs comes with this subscription.
My goal is to create a clone-able public image which has everything needed
to run Mustella builds that each committer can instantiate and deploy. I
want to make this whole process as simple as possible so that we can get as
many committers' VMs up and running in no time.
After that we will have one master Jenkins and set up all other VMs as
slaves. This way, we can first distribute VMs to do runs of various FP/AIR
combinations. And then eventually, break down Mustella tests into various
sections and have each slave run a subset, in order to reduce the time
taken for each Mustella run.
And we need to dedicate a VM specifically for building the SDK (that Erik
wanted) so as to reduce our dependence on builds@apache.org.
I need a volunteer committer to help test out and document this process.
Any takers?
Thanks,
Om
[1]
https://svn.apache.org/repos/private/committers/donated-licenses/msdn-subscription.html
>
>
> On Tue, Dec 10, 2013 at 6:14 PM, Alex Harui <ah...@adobe.com> wrote:
> > I don't think we actually know the cause of the problem. I am going to
> > continue to spend cycles to try to find out though.
> >
> > It would be nice to have an alternative to builds.a.o. I'm not sure if
> it
> > will cost Om money to run a builds server.
> >
> > -Alex
> >
> > On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
> > wrote:
> >
> >>I understand that.
> >>
> >>Actually, my "understanding" on this issue was that pixel bender compiler
> >>required some sort of hardware configuration (OpenGL, etc...) that were
> >>not present on the b.a.o. new Windows Jenkins slave node, so that's why
> >>the build was failing, and the Apache Infra was reluctant to let us
> >>modify anything, or even access the VM ourselves.
> >>So that's why I was proposing a "software only" solution.
> >>
> >>Now, it seems from what Om is saying that we can set up and use our own
> >>Jenkins slave node VM.
> >>
> >>That, of course, is much preferable...
> >>
> >>Maurice
> >>
> >>-----Message d'origine-----
> >>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>Envoyé : mardi 10 décembre 2013 10:44
> >>À : dev@flex.apache.org
> >>Objet : Re: [Builds/Jenkins] Help and advise needed
> >>
> >>Maurice,
> >>
> >>Your help is very much appreciated!
> >>
> >>I put "legal" in quotes, the issue is not really one of the law, more of
> >>the rules. An Apache release is supposed to be 'source only', and we if
> >>we can produce needed binaries from source, we keep only the source, not
> >>the artefacts themselves in the repo.
> >>
> >>
> >>EdB
> >>
> >>
> >>
> >>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >><ma...@systar.com> wrote:
> >>>>In addition to the various "legal" issues with binaries in the repo.
> >>> I understand it's not a good idea to have binaries in the repo, so I
> >>>won't insist.
> >>> But please can you explain what are the legal issues of having binaries
> >>>in the repo? Is this because of Adobe, or ASF rules ?
> >>>
> >>> On a side note, I was just trying to help, with my limited
> >>> understanding and knowledge, and because the email thread was titled
> >>> "help and advise needed" ;-)
> >>>
> >>> Regards,
> >>>
> >>> Maurice
> >>>
> >>> -----Message d'origine-----
> >>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>> [Builds/Jenkins] Help and advise needed
> >>>
> >>> In addition to the various "legal" issues with binaries in the repo,
> >>>we'd be masking the cause of this failure. In order to prevent further
> >>>deterioration of the build process, we need to figure out what went
> >>>wrong and fix it.
> >>>
> >>> EdB
> >>>
> >>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> >>> Took me while to figure out that I hadn't gone insane or if my
> >>> keyboard was broken ;-)
> >>>
> >>>
> >>>
> >>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>><ma...@systar.com> wrote:
> >>>>> someone who does use the pbj's will grab the nightly and complain.
> >>>>
> >>>> I don't understand.
> >>>> Why would someone complain if the pbj's are in the nightly?
> >>>>
> >>>> [From the other emai]
> >>>>>Apache repos aren't supposed to contain compiled code. The pbj files
> >>>>>were removed during the initial release audit.
> >>>>>I don't think a workaround can involve checking in the pbj files. But
> >>>>>we could borrow them from a prior release package temporarily.
> >>>>
> >>>>>So we could make the compilation conditional on a env parameter, and
> >>>>>set that in the Jenkins job accordingly?
> >>>>>Yes but ...
> >>>>
> >>>> Alex, the conversation is getting out synch, so I am not sure that I
> >>>>have understood what you said.
> >>>>
> >>>> So can we include the pbj in the repo, and have a parameter to
> >>>>conditionally compile the pbj ?
> >>>> - This parameter would be set by default to do the compilation (so
> >>>> that folks can recompile)
> >>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>>
> >>>>
> >>>> Maurice
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Ix Multimedia Software
> >>>
> >>> Jan Luykenstraat 27
> >>> 3521 VB Utrecht
> >>>
> >>> T. 06-51952295
> >>> I. www.ixsoftware.nl
> >>
> >>
> >>
> >>--
> >>Ix Multimedia Software
> >>
> >>Jan Luykenstraat 27
> >>3521 VB Utrecht
> >>
> >>T. 06-51952295
> >>I. www.ixsoftware.nl
> >
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I think he has the same MSDN as me, which should give him enough
'credits' to run a medium sized VM for ever... I currently run the
Mustella VM as a large instance for about half a month, then switch it
to medium for the remainder. A bit of a hassle, but worth it to run
Mustella smoothly, I think. A 'regular' Jenkins server should run
perfectly fine on a medium instance.
EdB
On Tue, Dec 10, 2013 at 6:14 PM, Alex Harui <ah...@adobe.com> wrote:
> I don't think we actually know the cause of the problem. I am going to
> continue to spend cycles to try to find out though.
>
> It would be nice to have an alternative to builds.a.o. I'm not sure if it
> will cost Om money to run a builds server.
>
> -Alex
>
> On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
>>I understand that.
>>
>>Actually, my "understanding" on this issue was that pixel bender compiler
>>required some sort of hardware configuration (OpenGL, etc...) that were
>>not present on the b.a.o. new Windows Jenkins slave node, so that's why
>>the build was failing, and the Apache Infra was reluctant to let us
>>modify anything, or even access the VM ourselves.
>>So that's why I was proposing a "software only" solution.
>>
>>Now, it seems from what Om is saying that we can set up and use our own
>>Jenkins slave node VM.
>>
>>That, of course, is much preferable...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>>Envoyé : mardi 10 décembre 2013 10:44
>>À : dev@flex.apache.org
>>Objet : Re: [Builds/Jenkins] Help and advise needed
>>
>>Maurice,
>>
>>Your help is very much appreciated!
>>
>>I put "legal" in quotes, the issue is not really one of the law, more of
>>the rules. An Apache release is supposed to be 'source only', and we if
>>we can produce needed binaries from source, we keep only the source, not
>>the artefacts themselves in the repo.
>>
>>
>>EdB
>>
>>
>>
>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>><ma...@systar.com> wrote:
>>>>In addition to the various "legal" issues with binaries in the repo.
>>> I understand it's not a good idea to have binaries in the repo, so I
>>>won't insist.
>>> But please can you explain what are the legal issues of having binaries
>>>in the repo? Is this because of Adobe, or ASF rules ?
>>>
>>> On a side note, I was just trying to help, with my limited
>>> understanding and knowledge, and because the email thread was titled
>>> "help and advise needed" ;-)
>>>
>>> Regards,
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> In addition to the various "legal" issues with binaries in the repo,
>>>we'd be masking the cause of this failure. In order to prevent further
>>>deterioration of the build process, we need to figure out what went
>>>wrong and fix it.
>>>
>>> EdB
>>>
>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>> Took me while to figure out that I hadn't gone insane or if my
>>> keyboard was broken ;-)
>>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>><ma...@systar.com> wrote:
>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>
>>>> I don't understand.
>>>> Why would someone complain if the pbj's are in the nightly?
>>>>
>>>> [From the other emai]
>>>>>Apache repos aren't supposed to contain compiled code. The pbj files
>>>>>were removed during the initial release audit.
>>>>>I don't think a workaround can involve checking in the pbj files. But
>>>>>we could borrow them from a prior release package temporarily.
>>>>
>>>>>So we could make the compilation conditional on a env parameter, and
>>>>>set that in the Jenkins job accordingly?
>>>>>Yes but ...
>>>>
>>>> Alex, the conversation is getting out synch, so I am not sure that I
>>>>have understood what you said.
>>>>
>>>> So can we include the pbj in the repo, and have a parameter to
>>>>conditionally compile the pbj ?
>>>> - This parameter would be set by default to do the compilation (so
>>>> that folks can recompile)
>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>
>>>>
>>>> Maurice
>>>>
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Thanks for your support and have a good day.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mercredi 11 décembre 2013 00:14
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Om sort of asked already. We'll see how they respond. Thanks for all your help on this.
-Alex
On 12/10/13 2:57 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>One possible fix (I couldn't check it yet ) is to open "Jenkins slave"
>Windows service, and check "Allow to interact with desktop".
>That may solve the problem, but not sure yet...
>
>Can you ask the infra ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 23:54 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Awesome. You are the detective of the day. Thanks for staying with it.
>
>-Alex
>
>On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Got it! Here is what happened:
>>https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Wi
>>n
>>dow
>>s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsser
>>s+v
>>s+ice
>>%28require.NET2.0framework%29
>>
>>I did the same and got the same launch command.
>>
>>So the slave is launched as a service as well, and does not get a window.
>>
>>Maurice
>>
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 23:41
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>Besides, do you know (or can you ask infra) if there are other Apache
>>projects that require a window, and what are their run config?
>>That might help...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 23:39
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>Also, could you ask if jenkins is running on a locked session, or
>>completely out of session.
>>
>>The slave window can only work when in session or with session locked,
>>but not "out of session".
>>While the other methods (including "run as windows service") can also
>>work out of session, but in this case, you need to check that service
>>can interact with the desktop.
>>
>>I still have a few check to do here, to confirm these assumptions.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013
>>23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>advise needed
>>
>>Awesome. I hope you are correct.
>>
>>On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>When you connect to https://builds.apache.org/computer/windows1/
>>>
>>>It says just below the title "Connected through JNLP"
>>>
>>>I have compared with my own installation and there is a notable
>>>difference:
>>>
>>>b.a.o:
>>>
>>>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>>>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>>>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>>>
>>>my Jenkins:
>>>sun.java.command com.sun.javaws.Main
>>>C:\Users\amsellem\AppData\Local\Temp\javaws2
>>>
>>>
>>>According to Jenkins doc, the b.a.o launch method is used for
>>>headless slaves, so that would explain why it does not get a window.
>>>
>>>I am trying to do the same now and let you know.
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>Saw it. Have we asked him if the Flex build is running in a slave
>>>and the slave has a window?
>>>
>>>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>>>Here is Gavin's response a minute ago:
>>>>
>>>>=================
>>>>> Gavin,
>>>>>
>>>>> Can you please copy-paste this line into a command prompt and tell
>>>>>us what the result is:
>>>>>
>>>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>>>
>>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>>> pbk"
>>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>>>
>>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>>> pbj"
>>>>>
>>>>> (mind the wrap)
>>>>>
>>>>> Thanks!
>>>>
>>>>Result is a slight pause, then the prompt returns. No error, no output.
>>>>
>>>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>>>variable.)
>>>>
>>>>Let me know what's next to check , thanks
>>>>
>>>>Gav...
>>>>=================
>>>>
>>>>
>>>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>>>><bi...@gmail.com>wrote:
>>>>
>>>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>>>
>>>>>> Don't know, but if you can prove that the slave can be configured
>>>>>>in a way that it won't run, then we have a more specific question
>>>>>>to ask infra.
>>>>>>
>>>>>> -Alex
>>>>>>
>>>>>
>>>>> Wow, this is like CSI ;-)
>>>>>
>>>>> Here is what we know. Gavin recently installed a new slave
>>>>>(windows2) I am guessing that something was probably changed in
>>>>>the way slaves are run.
>>>>>
>>>>> BTW, here is another piece of information. This is the system
>>>>> info for
>>>>> windows1:
>>>>>
>>>>> https://builds.apache.org/computer/windows1/systemInfo
>>>>>
>>>>> Anything looks out of the ordinary?
>>>>>
>>>>> Thanks,
>>>>> Om
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>>>> <ma...@systar.com>
>>>>>> wrote:
>>>>>>
>>>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>>>> >- Java web start (JNLP)
>>>>>> >- command line from master
>>>>>> >- via SSH on Unix machines
>>>>>> >- as a Windows Service.
>>>>>> >
>>>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>>>window.
>>>>>> >I am going to try "as a Windows Service".
>>>>>> >
>>>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>>>> >
>>>>>> >Maurice
>>>>>> >-----Message d'origine-----
>>>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>>>> >[Builds/Jenkins] Help and advise needed
>>>>>> >
>>>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>>>> >
>>>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>>>> ><ma...@systar.com>
>>>>>> >wrote:
>>>>>> >
>>>>>> >>Now run the same build on a slave node (that gets a windows
>>>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>>>> >>
>>>>>> >>Remote build on windowsSlave1 in workspace
>>>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>>>pixelbender-compile
>>>>>> >>&& exit %%ERRORLEVEL%%"'
>>>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m
>>>>>> >>-XX:MaxPermSize=512m -XX:MaxHeapSize=512m
>>>>>> >>-XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
>>>>>> >>Buildfile:
>>>>>>
>>>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\
>>>>>>>>b
>>>>>>>>u
>>>>>>>>ild
>>>>>>>>.
>>>>>>>>x
>>>>>> >>ml
>>>>>> >>
>>>>>> >>pixelbender-compile:
>>>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >> [exec] Version string: 3.0.0
>>>>>> >> [exec]
>>>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>>>> >> [exec] OpenGL Version 3.0
>>>>>> >> [exec] Has NPOT support: TRUE
>>>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>>>> >> [exec] Completed shader test!
>>>>>> >> [exec] Return code: 7
>>>>>> >> [exec] Result: 7
>>>>>> >>BUILD SUCCESSFUL
>>>>>> >>Total time: 8 seconds
>>>>>> >>Finished: SUCCESS
>>>>>> >>
>>>>>> >>Well, that's a difference.
>>>>>> >>
>>>>>> >>Maurice
>>>>>> >>
>>>>>> >>-----Message d'origine-----
>>>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>>> >>décembre
>>>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>>> >>Help and advise needed
>>>>>> >>
>>>>>> >>Nice. Thanks for sticking with it.
>>>>>> >>
>>>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>>>> >><ma...@systar.com>
>>>>>> >>wrote:
>>>>>> >>
>>>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>>>> >>>64bit
>>>>>>(
>>>>>> >>>Tomcat is running as a Windows Service).
>>>>>> >>>
>>>>>> >>>- Created a simple job, on the "master" node, than starts
>>>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>>>"pixelbender-compile"
>>>>>> >>>target
>>>>>> >>>- Jenkins output of the job:
>>>>>> >>>
>>>>>> >>>pixelbender-compile:
>>>>>> >>> [exec] AIF Internal exception
>>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>>>> >>> [exec] Return code: 1
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>>
>>>>>> >>>So I am getting the same error.
>>>>>> >>>
>>>>>> >>>Om says "master" does not get a window, so this result seems
>>>>>> >>>to be normal.
>>>>>> >>>
>>>>>> >>>I am trying now to create a slave node and run the job on it.
>>>>>> >>>
>>>>>> >>>Maurice
>>>>>> >>>
>>>>>> >>>-----Message d'origine-----
>>>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>>>> >>>
>>>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>>>> >>>
>>>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>>>first...
>>>>>> >>>
>>>>>> >>>Maurice
>>>>>> >>>
>>>>>> >>>-----Message d'origine-----
>>>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part
>>>>>> >>>de OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>>>>> >>>advise needed
>>>>>> >>>
>>>>>> >>>Maurice,
>>>>>> >>>
>>>>>> >>>When you ran it on your machine, was it on Cygwin or from
>>>>>>Jenkins?
>>>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>>>(master)
>>>>>> >>>does not get a window. Only slave executors are configured to
>>>>>> >>>get a window.
>>>>>> >>>Whereas Cygwin does not have such restrictions.
>>>>>> >>>
>>>>>> >>>Thanks,
>>>>>> >>>Om
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui
>>>>>> >>><ah...@adobe.com>
>>>>>>wrote:
>>>>>> >>>
>>>>>> >>>> I have no idea what to do with that information. But thanks
>>>>>> >>>>for trying.
>>>>>> >>>>
>>>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>>>> >>>> <ma...@systar.com>
>>>>>> >>>> wrote:
>>>>>> >>>>
>>>>>> >>>> >So this is the output from the b.a.o box:
>>>>>> >>>> >
>>>>>> >>>> >pixelbender-compile:
>>>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>>>> >>>> > [exec] AIF Internal exception
>>>>>> >>>> > [exec] Return code: 1
>>>>>> >>>> > [exec] Result: 1
>>>>>> >>>> >
>>>>>> >>>> >To be compared to the output on my PC:
>>>>>> >>>> >pixelbender-compile
>>>>>> >>>> >exec
>>>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>>>> >>>> >Vendor string: NVIDIA Corporation
>>>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >>>> >Version string: 3.0.0
>>>>>> >>>> >
>>>>>> >>>> >OpenGL version as determined by Extensionator...
>>>>>> >>>> >OpenGL Version 3.0
>>>>>> >>>> >Has NPOT support: TRUE
>>>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>> >>>> >shader test!
>>>>>> >>>> >Return code: 7
>>>>>> >>>> >Result: 7
>>>>>> >>>> >Exec
>>>>>> >>>> >
>>>>>> >>>> >That does not tell much, except that there seems to be an
>>>>>> >>>> >issue with accessing the GPU.
>>>>>> >>>> >
>>>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>>>> >>>> >more tests
>>>>>> >>>>?
>>>>>> >>>> >
>>>>>> >>>> >Maurice
>>>>>> >>>> >
>>>>>> >>>> >-----Message d'origine----- De : Maurice Amsellem
>>>>>> >>>> >[mailto:maurice.amsellem@systar.com]
>>>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>>>dev@flex.apache.orgObjet :
>>>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>>>> >>>> >
>>>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>>>> >>>> >
>>>>>> >>>> >Can you try on your side, please ?
>>>>>> >>>> >
>>>>>> >>>> >-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >2013
>>>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>>> >>>> >Help
>>>>>>and
>>>>>> >>>> >advise needed
>>>>>> >>>> >
>>>>>> >>>> >Won't that break Mac builds?
>>>>>> >>>> >
>>>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>>>> >>>> ><ma...@systar.com>
>>>>>> >>>> >wrote:
>>>>>> >>>> >
>>>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>>>> >>>> >>
>>>>>> >>>> >><exec
>>>>>> >>>> >>executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>>>> >>>> >>
>>>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>>>> >>>> >>
>>>>>> >>>> >>I am sure the result will be interesting.
>>>>>> >>>> >>
>>>>>> >>>> >>Anyway, it can't hurt ;-)
>>>>>> >>>> >>
>>>>>> >>>> >>Maurice
>>>>>> >>>> >>
>>>>>> >>>> >>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>
>>>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's
>>>>>> >>>> >>latest
>>>>>> >>>>request.
>>>>>> >>>> >>
>>>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>>>> >>>> >>
>>>>>> >>>> >>-Alex
>>>>>> >>>> >>
>>>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>>>> >>>> >><ma...@systar.com>
>>>>>> >>>> >>wrote:
>>>>>> >>>> >>
>>>>>> >>>> >>>Sure, if you can ask him.
>>>>>> >>>> >>>
>>>>>> >>>> >>>Maurice
>>>>>> >>>> >>>
>>>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>
>>>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>>>> >>>> >>>
>>>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>>>> >>>> >>><ma...@systar.com>
>>>>>> >>>> >>>wrote:
>>>>>> >>>> >>>
>>>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>>>> >>>> >>>>version of
>>>>>>OpenGL:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Console output on my laptop is below:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>>>Bender
>>>>>> >>>> >>>>Toolkit
>>>>>> >>>> >>>>2>sniffer_gpu.exe
>>>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >>>> >>>>Version string: 3.0.0
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>>>> >>>> >>>>OpenGL Version 3.0
>>>>>> >>>> >>>>Has NPOT support: TRUE
>>>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE
>>>>>> >>>> >>>>Completed
>>>>>>shader
>>>>>> >>>>test!
>>>>>> >>>> >>>>Return code: 7
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>>>utility
>>>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>WDYT ?
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Maurice
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>>>[Builds/Jenkins]
>>>>>> >>>> >>>>Help and advise needed
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>>>> >>>> >>>>I am going to continue to spend cycles to try to find
>>>>>> >>>> >>>>out
>>>>>>though.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>>>> >>>> >>>>I'm
>>>>>>not
>>>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>-Alex
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>>>> >>>> >>>><ma...@systar.com>
>>>>>> >>>> >>>>wrote:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>>I understand that.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Actually, my "understanding" on this issue was that
>>>>>> >>>> >>>>>pixel bender compiler required some sort of hardware
>>>>>> >>>> >>>>>configuration (OpenGL,
>>>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>>>Jenkins
>>>>>> >>>> >>>>>slave node, so that's why the build was failing, and
>>>>>> >>>> >>>>>the Apache Infra was reluctant to let us modify
>>>>>> >>>> >>>>>anything, or even access the VM ourselves.
>>>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>>>> >>>> >>>>>and
>>>>>>use
>>>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>That, of course, is much preferable...
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Maurice
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Maurice,
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Your help is very much appreciated!
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>>>> >>>> >>>>>the law, more of the rules. An Apache release is
>>>>>> >>>> >>>>>supposed to be 'source only', and we if we can produce
>>>>>> >>>> >>>>>needed binaries from source, we keep only the source,
>>>>>> >>>> >>>>>not the artefacts
>>>>>>themselves in
>>>>>> >>>>the repo.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>EdB
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>>>> >>>> >>>>>>>In addition to the various "legal" issues with
>>>>>> >>>> >>>>>>>binaries in the
>>>>>> >>>>repo.
>>>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>>>> >>>> >>>>>>the repo, so I won't insist.
>>>>>> >>>> >>>>>> But please can you explain what are the legal issues
>>>>>> >>>> >>>>>>of having binaries in the repo? Is this because of
>>>>>> >>>> >>>>>>Adobe, or
>>>>>>ASF
>>>>>> >>>>rules ?
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>>>> >>>> >>>>>> email thread
>>>>>>was
>>>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Regards,
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Maurice
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>>>mardi
>>>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
>>>>>>Re:
>>>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> In addition to the various "legal" issues with
>>>>>> >>>> >>>>>>binaries in the repo, we'd be masking the cause of
>>>>>> >>>> >>>>>>this
>>>>>>failure.
>>>>>> >>>> >>>>>>In
>>>>>>order
>>>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>>>> >>>> >>>>>>we
>>>>>>need
>>>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> EdB
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella
>>>>>> >>>> >>>>>> VM set
>>>>>>to
>>>>>> >>>>FR...
>>>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the
>>>>>> >>>> >>>>>>>> nightly and
>>>>>> >>>>complain.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> I don't understand.
>>>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>>>nightly?
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> [From the other emai]
>>>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>>>The
>>>>>> >>>> >>>>>>>>pbj files were removed during the initial release
>>>>>>audit.
>>>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in
>>>>>> >>>> >>>>>>>>the pbj
>>>>>> >>>>files.
>>>>>> >>>> >>>>>>>>But we could borrow them from a prior release
>>>>>> >>>> >>>>>>>>package
>>>>>> >>>>temporarily.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>>>So we could make the compilation conditional on a
>>>>>> >>>> >>>>>>>>env parameter, and set that in the Jenkins job accordingly?
>>>>>> >>>> >>>>>>>>Yes but ...
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>>>parameter
>>>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>>>pbj's.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> Maurice
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> --
>>>>>> >>>> >>>>>> Ix Multimedia Software
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>>>> >>>> >>>>>> 3521 VB Utrecht
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> T. 06-51952295
>>>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>--
>>>>>> >>>> >>>>>Ix Multimedia Software
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Jan Luykenstraat 27
>>>>>> >>>> >>>>>3521 VB Utrecht
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>T. 06-51952295
>>>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>>>> >>>> >>>>
>>>>>> >>>> >>>
>>>>>> >>>> >>
>>>>>> >>>> >
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>>
>>>>>
>>>
>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Great sleuthing Maurice! Thanks for sticking to it and figuring it out :-)
I have asked Infra a similar question. I will wait for their response and
give them more information.
Om
On Tue, Dec 10, 2013 at 2:57 PM, Maurice Amsellem <
maurice.amsellem@systar.com> wrote:
> One possible fix (I couldn't check it yet ) is to open "Jenkins slave"
> Windows service, and check "Allow to interact with desktop".
> That may solve the problem, but not sure yet...
>
> Can you ask the infra ?
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : mardi 10 décembre 2013 23:54
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Awesome. You are the detective of the day. Thanks for staying with it.
>
> -Alex
>
> On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >Got it! Here is what happened:
> >https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Win
> >dow
> >s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsserv
> >s+ice
> >%28require.NET2.0framework%29
> >
> >I did the same and got the same launch command.
> >
> >So the slave is launched as a service as well, and does not get a window.
> >
> >Maurice
> >
> >
> >-----Message d'origine-----
> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >Envoyé : mardi 10 décembre 2013 23:41
> >À : dev@flex.apache.org
> >Objet : RE: [Builds/Jenkins] Help and advise needed
> >
> >Besides, do you know (or can you ask infra) if there are other Apache
> >projects that require a window, and what are their run config?
> >That might help...
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >Envoyé : mardi 10 décembre 2013 23:39
> >À : dev@flex.apache.org
> >Objet : RE: [Builds/Jenkins] Help and advise needed
> >
> >Also, could you ask if jenkins is running on a locked session, or
> >completely out of session.
> >
> >The slave window can only work when in session or with session locked,
> >but not "out of session".
> >While the other methods (including "run as windows service") can also
> >work out of session, but in this case, you need to check that service
> >can interact with the desktop.
> >
> >I still have a few check to do here, to confirm these assumptions.
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >2013
> >23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >advise needed
> >
> >Awesome. I hope you are correct.
> >
> >On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
> >wrote:
> >
> >>When you connect to https://builds.apache.org/computer/windows1/
> >>
> >>It says just below the title "Connected through JNLP"
> >>
> >>I have compared with my own installation and there is a notable
> >>difference:
> >>
> >>b.a.o:
> >>
> >>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
> >>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
> >>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
> >>
> >>my Jenkins:
> >>sun.java.command com.sun.javaws.Main
> >>C:\Users\amsellem\AppData\Local\Temp\javaws2
> >>
> >>
> >>According to Jenkins doc, the b.a.o launch method is used for headless
> >>slaves, so that would explain why it does not get a window.
> >>
> >>I am trying to do the same now and let you know.
> >>
> >>-----Message d'origine-----
> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>and advise needed
> >>
> >>Saw it. Have we asked him if the Flex build is running in a slave and
> >>the slave has a window?
> >>
> >>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
> >>
> >>>Here is Gavin's response a minute ago:
> >>>
> >>>=================
> >>>> Gavin,
> >>>>
> >>>> Can you please copy-paste this line into a command prompt and tell
> >>>>us what the result is:
> >>>>
> >>>> "%PIXELBENDER_HOME%\pbutil.exe"
> >>>> "F:\hudson\hudson-slave\workspace\flex-
> >>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> >>>> pbk"
> >>>> "F:\hudson\hudson-slave\workspace\flex-
> >>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> >>>> pbj"
> >>>>
> >>>> (mind the wrap)
> >>>>
> >>>> Thanks!
> >>>
> >>>Result is a slight pause, then the prompt returns. No error, no output.
> >>>
> >>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
> >>>variable.)
> >>>
> >>>Let me know what's next to check , thanks
> >>>
> >>>Gav...
> >>>=================
> >>>
> >>>
> >>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
> >>><bi...@gmail.com>wrote:
> >>>
> >>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
> >>>>
> >>>>> Don't know, but if you can prove that the slave can be configured
> >>>>>in a way that it won't run, then we have a more specific question
> >>>>>to ask infra.
> >>>>>
> >>>>> -Alex
> >>>>>
> >>>>
> >>>> Wow, this is like CSI ;-)
> >>>>
> >>>> Here is what we know. Gavin recently installed a new slave
> >>>>(windows2) I am guessing that something was probably changed in the
> >>>>way slaves are run.
> >>>>
> >>>> BTW, here is another piece of information. This is the system info
> >>>> for
> >>>> windows1:
> >>>>
> >>>> https://builds.apache.org/computer/windows1/systemInfo
> >>>>
> >>>> Anything looks out of the ordinary?
> >>>>
> >>>> Thanks,
> >>>> Om
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
> >>>>> <ma...@systar.com>
> >>>>> wrote:
> >>>>>
> >>>>> >According to jenkins gui, there are 4 ways of starting the slave :
> >>>>> >- Java web start (JNLP)
> >>>>> >- command line from master
> >>>>> >- via SSH on Unix machines
> >>>>> >- as a Windows Service.
> >>>>> >
> >>>>> >I am using JNLP, but maybe the other launch methods don't get a
> >>>>>window.
> >>>>> >I am going to try "as a Windows Service".
> >>>>> >
> >>>>> >Is there a way to know how the slave is launched on b.a.o?
> >>>>> >
> >>>>> >Maurice
> >>>>> >-----Message d'origine-----
> >>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
> >>>>> >[Builds/Jenkins] Help and advise needed
> >>>>> >
> >>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
> >>>>> >get a window? Maybe Infra changed some default on builds.a.o.
> >>>>> >
> >>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
> >>>>> ><ma...@systar.com>
> >>>>> >wrote:
> >>>>> >
> >>>>> >>Now run the same build on a slave node (that gets a windows
> >>>>> >>"jenkins slave agent", that is visible on the desktop ):
> >>>>> >>
> >>>>> >>Remote build on windowsSlave1 in workspace
> >>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
> >>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
> >>>>>pixelbender-compile
> >>>>> >>&& exit %%ERRORLEVEL%%"'
> >>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m
> >>>>> >>-XX:MaxPermSize=512m -XX:MaxHeapSize=512m
> >>>>> >>-XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
> >>>>> >>Buildfile:
> >>>>>
> >>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\b
> >>>>>>>u
> >>>>>>>ild
> >>>>>>>.
> >>>>>>>x
> >>>>> >>ml
> >>>>> >>
> >>>>> >>pixelbender-compile:
> >>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
> >>>>> >> [exec] Vendor string: NVIDIA Corporation
> >>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
> >>>>> >> [exec] Version string: 3.0.0
> >>>>> >> [exec]
> >>>>> >> [exec] OpenGL version as determined by Extensionator...
> >>>>> >> [exec] OpenGL Version 3.0
> >>>>> >> [exec] Has NPOT support: TRUE
> >>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
> >>>>> >> [exec] Completed shader test!
> >>>>> >> [exec] Return code: 7
> >>>>> >> [exec] Result: 7
> >>>>> >>BUILD SUCCESSFUL
> >>>>> >>Total time: 8 seconds
> >>>>> >>Finished: SUCCESS
> >>>>> >>
> >>>>> >>Well, that's a difference.
> >>>>> >>
> >>>>> >>Maurice
> >>>>> >>
> >>>>> >>-----Message d'origine-----
> >>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>>> >>décembre
> >>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>>> >>Help and advise needed
> >>>>> >>
> >>>>> >>Nice. Thanks for sticking with it.
> >>>>> >>
> >>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
> >>>>> >><ma...@systar.com>
> >>>>> >>wrote:
> >>>>> >>
> >>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
> >>>>> >>>64bit
> >>>>>(
> >>>>> >>>Tomcat is running as a Windows Service).
> >>>>> >>>
> >>>>> >>>- Created a simple job, on the "master" node, than starts
> >>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
> >>>>>"pixelbender-compile"
> >>>>> >>>target
> >>>>> >>>- Jenkins output of the job:
> >>>>> >>>
> >>>>> >>>pixelbender-compile:
> >>>>> >>> [exec] AIF Internal exception
> >>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
> >>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
> >>>>> >>> [exec] Return code: 1
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>> [exec] ERROR: AIF Internal exception
> >>>>> >>> [exec] Result: 1
> >>>>> >>>
> >>>>> >>>So I am getting the same error.
> >>>>> >>>
> >>>>> >>>Om says "master" does not get a window, so this result seems to
> >>>>> >>>be normal.
> >>>>> >>>
> >>>>> >>>I am trying now to create a slave node and run the job on it.
> >>>>> >>>
> >>>>> >>>Maurice
> >>>>> >>>
> >>>>> >>>-----Message d'origine-----
> >>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
> >>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
> >>>>> >>>
> >>>>> >>>It was from the command line (cmd ant ), so gets a window.
> >>>>> >>>
> >>>>> >>>I am trying now from Jenkins service, but needs to install it
> >>>>>first...
> >>>>> >>>
> >>>>> >>>Maurice
> >>>>> >>>
> >>>>> >>>-----Message d'origine-----
> >>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
> >>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
> >>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >>>>> >>>advise needed
> >>>>> >>>
> >>>>> >>>Maurice,
> >>>>> >>>
> >>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
> >>>>> >>>I think there is a difference. On Jenkins, the main executor
> >>>>>(master)
> >>>>> >>>does not get a window. Only slave executors are configured to
> >>>>> >>>get a window.
> >>>>> >>>Whereas Cygwin does not have such restrictions.
> >>>>> >>>
> >>>>> >>>Thanks,
> >>>>> >>>Om
> >>>>> >>>
> >>>>> >>>
> >>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
> >>>>>wrote:
> >>>>> >>>
> >>>>> >>>> I have no idea what to do with that information. But thanks
> >>>>> >>>>for trying.
> >>>>> >>>>
> >>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
> >>>>> >>>> <ma...@systar.com>
> >>>>> >>>> wrote:
> >>>>> >>>>
> >>>>> >>>> >So this is the output from the b.a.o box:
> >>>>> >>>> >
> >>>>> >>>> >pixelbender-compile:
> >>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> >>>>> >>>> > [exec] AIF Internal exception
> >>>>> >>>> > [exec] Return code: 1
> >>>>> >>>> > [exec] Result: 1
> >>>>> >>>> >
> >>>>> >>>> >To be compared to the output on my PC:
> >>>>> >>>> >pixelbender-compile
> >>>>> >>>> >exec
> >>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
> >>>>> >>>> >Vendor string: NVIDIA Corporation
> >>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
> >>>>> >>>> >Version string: 3.0.0
> >>>>> >>>> >
> >>>>> >>>> >OpenGL version as determined by Extensionator...
> >>>>> >>>> >OpenGL Version 3.0
> >>>>> >>>> >Has NPOT support: TRUE
> >>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
> >>>>> >>>> >shader test!
> >>>>> >>>> >Return code: 7
> >>>>> >>>> >Result: 7
> >>>>> >>>> >Exec
> >>>>> >>>> >
> >>>>> >>>> >That does not tell much, except that there seems to be an
> >>>>> >>>> >issue with accessing the GPU.
> >>>>> >>>> >
> >>>>> >>>> >Shall I un-commit the change now, or do you want to perform
> >>>>> >>>> >more tests
> >>>>> >>>>?
> >>>>> >>>> >
> >>>>> >>>> >Maurice
> >>>>> >>>> >
> >>>>> >>>> >-----Message d'origine-----
> >>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
> >>>>>dev@flex.apache.orgObjet :
> >>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
> >>>>> >>>> >
> >>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
> >>>>> >>>> >
> >>>>> >>>> >Can you try on your side, please ?
> >>>>> >>>> >
> >>>>> >>>> >-----Message d'origine-----
> >>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>>> >>>> >décembre
> >>>>> >>>> >2013
> >>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>>> >>>> >Help
> >>>>>and
> >>>>> >>>> >advise needed
> >>>>> >>>> >
> >>>>> >>>> >Won't that break Mac builds?
> >>>>> >>>> >
> >>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
> >>>>> >>>> ><ma...@systar.com>
> >>>>> >>>> >wrote:
> >>>>> >>>> >
> >>>>> >>>> >>Alex, it's one line to change in the build.xml
> >>>>> >>>> >>
> >>>>> >>>> >><exec
> >>>>> >>>> >>executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>>>> >>>> >>
> >>>>> >>>> >>I will give it a try and we will know in 15 min.
> >>>>> >>>> >>
> >>>>> >>>> >>I am sure the result will be interesting.
> >>>>> >>>> >>
> >>>>> >>>> >>Anyway, it can't hurt ;-)
> >>>>> >>>> >>
> >>>>> >>>> >>Maurice
> >>>>> >>>> >>
> >>>>> >>>> >>-----Message d'origine----- De : Alex Harui
> >>>>> >>>> >>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
> >>>>> >>>> >>[Builds/Jenkins] Help and advise needed
> >>>>> >>>> >>
> >>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's
> >>>>> >>>> >>latest
> >>>>> >>>>request.
> >>>>> >>>> >>
> >>>>> >>>> >>BTW, thanks for finding out about the tool.
> >>>>> >>>> >>
> >>>>> >>>> >>-Alex
> >>>>> >>>> >>
> >>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
> >>>>> >>>> >><ma...@systar.com>
> >>>>> >>>> >>wrote:
> >>>>> >>>> >>
> >>>>> >>>> >>>Sure, if you can ask him.
> >>>>> >>>> >>>
> >>>>> >>>> >>>Maurice
> >>>>> >>>> >>>
> >>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
> >>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
> >>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
> >>>>> >>>> >>>
> >>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
> >>>>> >>>> >>>
> >>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
> >>>>> >>>> >>><ma...@systar.com>
> >>>>> >>>> >>>wrote:
> >>>>> >>>> >>>
> >>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
> >>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
> >>>>> >>>> >>>>version of
> >>>>>OpenGL:
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>Console output on my laptop is below:
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
> >>>>>Bender
> >>>>> >>>> >>>>Toolkit
> >>>>> >>>> >>>>2>sniffer_gpu.exe
> >>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>>>> >>>> >>>>Vendor string: NVIDIA Corporation
> >>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>>>> >>>> >>>>Version string: 3.0.0
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>OpenGL version as determined by Extensionator...
> >>>>> >>>> >>>>OpenGL Version 3.0
> >>>>> >>>> >>>>Has NPOT support: TRUE
> >>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
> >>>>>shader
> >>>>> >>>>test!
> >>>>> >>>> >>>>Return code: 7
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
> >>>>>utility
> >>>>> >>>> >>>>and show the output on the b.a.o vm.
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>WDYT ?
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>Maurice
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
> >>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
> >>>>>[Builds/Jenkins]
> >>>>> >>>> >>>>Help and advise needed
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>I don't think we actually know the cause of the problem.
> >>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
> >>>>>though.
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
> >>>>> >>>> >>>>I'm
> >>>>>not
> >>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>-Alex
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
> >>>>> >>>> >>>><ma...@systar.com>
> >>>>> >>>> >>>>wrote:
> >>>>> >>>> >>>>
> >>>>> >>>> >>>>>I understand that.
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Actually, my "understanding" on this issue was that
> >>>>> >>>> >>>>>pixel bender compiler required some sort of hardware
> >>>>> >>>> >>>>>configuration (OpenGL,
> >>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
> >>>>>Jenkins
> >>>>> >>>> >>>>>slave node, so that's why the build was failing, and
> >>>>> >>>> >>>>>the Apache Infra was reluctant to let us modify
> >>>>> >>>> >>>>>anything, or even access the VM ourselves.
> >>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
> >>>>> >>>> >>>>>and
> >>>>>use
> >>>>> >>>> >>>>>our own Jenkins slave node VM.
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>That, of course, is much preferable...
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Maurice
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
> >>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
> >>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Maurice,
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Your help is very much appreciated!
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
> >>>>> >>>> >>>>>the law, more of the rules. An Apache release is
> >>>>> >>>> >>>>>supposed to be 'source only', and we if we can produce
> >>>>> >>>> >>>>>needed binaries from source, we keep only the source,
> >>>>> >>>> >>>>>not the artefacts
> >>>>>themselves in
> >>>>> >>>>the repo.
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>EdB
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>>>> >>>> >>>>><ma...@systar.com> wrote:
> >>>>> >>>> >>>>>>>In addition to the various "legal" issues with
> >>>>> >>>> >>>>>>>binaries in the
> >>>>> >>>>repo.
> >>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
> >>>>> >>>> >>>>>>the repo, so I won't insist.
> >>>>> >>>> >>>>>> But please can you explain what are the legal issues
> >>>>> >>>> >>>>>>of having binaries in the repo? Is this because of
> >>>>> >>>> >>>>>>Adobe, or
> >>>>>ASF
> >>>>> >>>>rules ?
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
> >>>>> >>>> >>>>>> limited understanding and knowledge, and because the
> >>>>> >>>> >>>>>> email thread
> >>>>>was
> >>>>> >>>> >>>>>> titled "help and advise needed" ;-)
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> Regards,
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> Maurice
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
> >>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
> >>>>>mardi
> >>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
> >>>>>Re:
> >>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> In addition to the various "legal" issues with
> >>>>> >>>> >>>>>>binaries in the repo, we'd be masking the cause of this
> failure.
> >>>>> >>>> >>>>>>In
> >>>>>order
> >>>>> >>>> >>>>>>to prevent further deterioration of the build process,
> >>>>> >>>> >>>>>>we
> >>>>>need
> >>>>> >>>> >>>>>>to figure out what went wrong and fix it.
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> EdB
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
> >>>>> >>>> >>>>>> set
> >>>>>to
> >>>>> >>>>FR...
> >>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
> >>>>> >>>> >>>>>> or if my keyboard was broken ;-)
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>>>> >>>> >>>>>><ma...@systar.com> wrote:
> >>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
> >>>>> >>>> >>>>>>>> and
> >>>>> >>>>complain.
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>> I don't understand.
> >>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
> >>>>>nightly?
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>> [From the other emai]
> >>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
> >>>>>The
> >>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
> >>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in
> >>>>> >>>> >>>>>>>>the pbj
> >>>>> >>>>files.
> >>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
> >>>>> >>>>temporarily.
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
> >>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
> >>>>> >>>> >>>>>>>>Yes but ...
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
> >>>>> >>>> >>>>>>>not sure that I have understood what you said.
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
> >>>>>parameter
> >>>>> >>>> >>>>>>>to conditionally compile the pbj ?
> >>>>> >>>> >>>>>>> - This parameter would be set by default to do the
> >>>>> >>>> >>>>>>>compilation (so that folks can recompile)
> >>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
> >>>>>pbj's.
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>> Maurice
> >>>>> >>>> >>>>>>>
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> --
> >>>>> >>>> >>>>>> Ix Multimedia Software
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> Jan Luykenstraat 27
> >>>>> >>>> >>>>>> 3521 VB Utrecht
> >>>>> >>>> >>>>>>
> >>>>> >>>> >>>>>> T. 06-51952295
> >>>>> >>>> >>>>>> I. www.ixsoftware.nl
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>--
> >>>>> >>>> >>>>>Ix Multimedia Software
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>Jan Luykenstraat 27
> >>>>> >>>> >>>>>3521 VB Utrecht
> >>>>> >>>> >>>>>
> >>>>> >>>> >>>>>T. 06-51952295
> >>>>> >>>> >>>>>I. www.ixsoftware.nl
> >>>>> >>>> >>>>
> >>>>> >>>> >>>
> >>>>> >>>> >>
> >>>>> >>>> >
> >>>>> >>>>
> >>>>> >>>>
> >>>>> >>
> >>>>> >
> >>>>>
> >>>>>
> >>>>
> >>
> >
>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
I tried the proposed fix (check "Allow to interact with desktop" on slave service) but it didn't work.
So I guess it really needs to be started through JNLP in the session, and not as a service.
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:58
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
One possible fix (I couldn't check it yet ) is to open "Jenkins slave" Windows service, and check "Allow to interact with desktop".
That may solve the problem, but not sure yet...
Can you ask the infra ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013 23:54 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. You are the detective of the day. Thanks for staying with it.
-Alex
On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Got it! Here is what happened:
>https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Win
>dow
>s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsserv
>s+ice
>%28require.NET2.0framework%29
>
>I did the same and got the same launch command.
>
>So the slave is launched as a service as well, and does not get a window.
>
>Maurice
>
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:41
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Besides, do you know (or can you ask infra) if there are other Apache
>projects that require a window, and what are their run config?
>That might help...
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:39
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Also, could you ask if jenkins is running on a locked session, or
>completely out of session.
>
>The slave window can only work when in session or with session locked,
>but not "out of session".
>While the other methods (including "run as windows service") can also
>work out of session, but in this case, you need to check that service
>can interact with the desktop.
>
>I still have a few check to do here, to confirm these assumptions.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013
>23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>advise needed
>
>Awesome. I hope you are correct.
>
>On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>When you connect to https://builds.apache.org/computer/windows1/
>>
>>It says just below the title "Connected through JNLP"
>>
>>I have compared with my own installation and there is a notable
>>difference:
>>
>>b.a.o:
>>
>>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>>
>>my Jenkins:
>>sun.java.command com.sun.javaws.Main
>>C:\Users\amsellem\AppData\Local\Temp\javaws2
>>
>>
>>According to Jenkins doc, the b.a.o launch method is used for headless
>>slaves, so that would explain why it does not get a window.
>>
>>I am trying to do the same now and let you know.
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Saw it. Have we asked him if the Flex build is running in a slave and
>>the slave has a window?
>>
>>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>Here is Gavin's response a minute ago:
>>>
>>>=================
>>>> Gavin,
>>>>
>>>> Can you please copy-paste this line into a command prompt and tell
>>>>us what the result is:
>>>>
>>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbk"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbj"
>>>>
>>>> (mind the wrap)
>>>>
>>>> Thanks!
>>>
>>>Result is a slight pause, then the prompt returns. No error, no output.
>>>
>>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>>variable.)
>>>
>>>Let me know what's next to check , thanks
>>>
>>>Gav...
>>>=================
>>>
>>>
>>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>>><bi...@gmail.com>wrote:
>>>
>>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>>
>>>>> Don't know, but if you can prove that the slave can be configured
>>>>>in a way that it won't run, then we have a more specific question
>>>>>to ask infra.
>>>>>
>>>>> -Alex
>>>>>
>>>>
>>>> Wow, this is like CSI ;-)
>>>>
>>>> Here is what we know. Gavin recently installed a new slave
>>>>(windows2) I am guessing that something was probably changed in the
>>>>way slaves are run.
>>>>
>>>> BTW, here is another piece of information. This is the system info
>>>> for
>>>> windows1:
>>>>
>>>> https://builds.apache.org/computer/windows1/systemInfo
>>>>
>>>> Anything looks out of the ordinary?
>>>>
>>>> Thanks,
>>>> Om
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>>> <ma...@systar.com>
>>>>> wrote:
>>>>>
>>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>>> >- Java web start (JNLP)
>>>>> >- command line from master
>>>>> >- via SSH on Unix machines
>>>>> >- as a Windows Service.
>>>>> >
>>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>>window.
>>>>> >I am going to try "as a Windows Service".
>>>>> >
>>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>>> >
>>>>> >Maurice
>>>>> >-----Message d'origine-----
>>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>>> >[Builds/Jenkins] Help and advise needed
>>>>> >
>>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>>> >
>>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>>> ><ma...@systar.com>
>>>>> >wrote:
>>>>> >
>>>>> >>Now run the same build on a slave node (that gets a windows
>>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>>> >>
>>>>> >>Remote build on windowsSlave1 in workspace
>>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>>pixelbender-compile
>>>>> >>&& exit %%ERRORLEVEL%%"'
>>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m
>>>>> >>-XX:MaxPermSize=512m -XX:MaxHeapSize=512m
>>>>> >>-XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
>>>>> >>Buildfile:
>>>>>
>>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\b
>>>>>>>u
>>>>>>>ild
>>>>>>>.
>>>>>>>x
>>>>> >>ml
>>>>> >>
>>>>> >>pixelbender-compile:
>>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>>> >> [exec] Version string: 3.0.0
>>>>> >> [exec]
>>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>>> >> [exec] OpenGL Version 3.0
>>>>> >> [exec] Has NPOT support: TRUE
>>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>>> >> [exec] Completed shader test!
>>>>> >> [exec] Return code: 7
>>>>> >> [exec] Result: 7
>>>>> >>BUILD SUCCESSFUL
>>>>> >>Total time: 8 seconds
>>>>> >>Finished: SUCCESS
>>>>> >>
>>>>> >>Well, that's a difference.
>>>>> >>
>>>>> >>Maurice
>>>>> >>
>>>>> >>-----Message d'origine-----
>>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>décembre
>>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>Help and advise needed
>>>>> >>
>>>>> >>Nice. Thanks for sticking with it.
>>>>> >>
>>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>>> >><ma...@systar.com>
>>>>> >>wrote:
>>>>> >>
>>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>>> >>>64bit
>>>>>(
>>>>> >>>Tomcat is running as a Windows Service).
>>>>> >>>
>>>>> >>>- Created a simple job, on the "master" node, than starts
>>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>>"pixelbender-compile"
>>>>> >>>target
>>>>> >>>- Jenkins output of the job:
>>>>> >>>
>>>>> >>>pixelbender-compile:
>>>>> >>> [exec] AIF Internal exception
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>>> >>> [exec] Return code: 1
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>>
>>>>> >>>So I am getting the same error.
>>>>> >>>
>>>>> >>>Om says "master" does not get a window, so this result seems to
>>>>> >>>be normal.
>>>>> >>>
>>>>> >>>I am trying now to create a slave node and run the job on it.
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>
>>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>>> >>>
>>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>>first...
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>>>> >>>advise needed
>>>>> >>>
>>>>> >>>Maurice,
>>>>> >>>
>>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>>(master)
>>>>> >>>does not get a window. Only slave executors are configured to
>>>>> >>>get a window.
>>>>> >>>Whereas Cygwin does not have such restrictions.
>>>>> >>>
>>>>> >>>Thanks,
>>>>> >>>Om
>>>>> >>>
>>>>> >>>
>>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>>wrote:
>>>>> >>>
>>>>> >>>> I have no idea what to do with that information. But thanks
>>>>> >>>>for trying.
>>>>> >>>>
>>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>>> >>>> <ma...@systar.com>
>>>>> >>>> wrote:
>>>>> >>>>
>>>>> >>>> >So this is the output from the b.a.o box:
>>>>> >>>> >
>>>>> >>>> >pixelbender-compile:
>>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>>> >>>> > [exec] AIF Internal exception
>>>>> >>>> > [exec] Return code: 1
>>>>> >>>> > [exec] Result: 1
>>>>> >>>> >
>>>>> >>>> >To be compared to the output on my PC:
>>>>> >>>> >pixelbender-compile
>>>>> >>>> >exec
>>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>>> >>>> >Vendor string: NVIDIA Corporation
>>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >Version string: 3.0.0
>>>>> >>>> >
>>>>> >>>> >OpenGL version as determined by Extensionator...
>>>>> >>>> >OpenGL Version 3.0
>>>>> >>>> >Has NPOT support: TRUE
>>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>>> >>>> >shader test!
>>>>> >>>> >Return code: 7
>>>>> >>>> >Result: 7
>>>>> >>>> >Exec
>>>>> >>>> >
>>>>> >>>> >That does not tell much, except that there seems to be an
>>>>> >>>> >issue with accessing the GPU.
>>>>> >>>> >
>>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>>> >>>> >more tests
>>>>> >>>>?
>>>>> >>>> >
>>>>> >>>> >Maurice
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>>dev@flex.apache.orgObjet :
>>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>> >
>>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>>> >>>> >
>>>>> >>>> >Can you try on your side, please ?
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>>> >décembre
>>>>> >>>> >2013
>>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>>> >Help
>>>>>and
>>>>> >>>> >advise needed
>>>>> >>>> >
>>>>> >>>> >Won't that break Mac builds?
>>>>> >>>> >
>>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>>> >>>> ><ma...@systar.com>
>>>>> >>>> >wrote:
>>>>> >>>> >
>>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>>> >>>> >>
>>>>> >>>> >><exec
>>>>> >>>> >>executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>>> >>>> >>
>>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>>> >>>> >>
>>>>> >>>> >>I am sure the result will be interesting.
>>>>> >>>> >>
>>>>> >>>> >>Anyway, it can't hurt ;-)
>>>>> >>>> >>
>>>>> >>>> >>Maurice
>>>>> >>>> >>
>>>>> >>>> >>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>
>>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's
>>>>> >>>> >>latest
>>>>> >>>>request.
>>>>> >>>> >>
>>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>>> >>>> >>
>>>>> >>>> >>-Alex
>>>>> >>>> >>
>>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>>> >>>> >><ma...@systar.com>
>>>>> >>>> >>wrote:
>>>>> >>>> >>
>>>>> >>>> >>>Sure, if you can ask him.
>>>>> >>>> >>>
>>>>> >>>> >>>Maurice
>>>>> >>>> >>>
>>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>
>>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>>> >>>> >>>
>>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>>> >>>> >>><ma...@systar.com>
>>>>> >>>> >>>wrote:
>>>>> >>>> >>>
>>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>>> >>>> >>>>version of
>>>>>OpenGL:
>>>>> >>>> >>>>
>>>>> >>>> >>>>Console output on my laptop is below:
>>>>> >>>> >>>>
>>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>>Bender
>>>>> >>>> >>>>Toolkit
>>>>> >>>> >>>>2>sniffer_gpu.exe
>>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >>>>Version string: 3.0.0
>>>>> >>>> >>>>
>>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>>> >>>> >>>>OpenGL Version 3.0
>>>>> >>>> >>>>Has NPOT support: TRUE
>>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>shader
>>>>> >>>>test!
>>>>> >>>> >>>>Return code: 7
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>>utility
>>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>>> >>>> >>>>
>>>>> >>>> >>>>WDYT ?
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maurice
>>>>> >>>> >>>>
>>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>>[Builds/Jenkins]
>>>>> >>>> >>>>Help and advise needed
>>>>> >>>> >>>>
>>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>>though.
>>>>> >>>> >>>>
>>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>>> >>>> >>>>I'm
>>>>>not
>>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>>> >>>> >>>>
>>>>> >>>> >>>>-Alex
>>>>> >>>> >>>>
>>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>>> >>>> >>>><ma...@systar.com>
>>>>> >>>> >>>>wrote:
>>>>> >>>> >>>>
>>>>> >>>> >>>>>I understand that.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Actually, my "understanding" on this issue was that
>>>>> >>>> >>>>>pixel bender compiler required some sort of hardware
>>>>> >>>> >>>>>configuration (OpenGL,
>>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>>Jenkins
>>>>> >>>> >>>>>slave node, so that's why the build was failing, and
>>>>> >>>> >>>>>the Apache Infra was reluctant to let us modify
>>>>> >>>> >>>>>anything, or even access the VM ourselves.
>>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>>> >>>> >>>>>and
>>>>>use
>>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>That, of course, is much preferable...
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice,
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Your help is very much appreciated!
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>>> >>>> >>>>>the law, more of the rules. An Apache release is
>>>>> >>>> >>>>>supposed to be 'source only', and we if we can produce
>>>>> >>>> >>>>>needed binaries from source, we keep only the source,
>>>>> >>>> >>>>>not the artefacts
>>>>>themselves in
>>>>> >>>>the repo.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>EdB
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>In addition to the various "legal" issues with
>>>>> >>>> >>>>>>>binaries in the
>>>>> >>>>repo.
>>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>>> >>>> >>>>>>the repo, so I won't insist.
>>>>> >>>> >>>>>> But please can you explain what are the legal issues
>>>>> >>>> >>>>>>of having binaries in the repo? Is this because of
>>>>> >>>> >>>>>>Adobe, or
>>>>>ASF
>>>>> >>>>rules ?
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>>> >>>> >>>>>> email thread
>>>>>was
>>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Regards,
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Maurice
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>>mardi
>>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
>>>>>Re:
>>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> In addition to the various "legal" issues with
>>>>> >>>> >>>>>>binaries in the repo, we'd be masking the cause of this failure.
>>>>> >>>> >>>>>>In
>>>>>order
>>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>>> >>>> >>>>>>we
>>>>>need
>>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> EdB
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>>> >>>> >>>>>> set
>>>>>to
>>>>> >>>>FR...
>>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>>> >>>> >>>>>>>> and
>>>>> >>>>complain.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> I don't understand.
>>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>>nightly?
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> [From the other emai]
>>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>>The
>>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in
>>>>> >>>> >>>>>>>>the pbj
>>>>> >>>>files.
>>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>>> >>>>temporarily.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>>> >>>> >>>>>>>>Yes but ...
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>>parameter
>>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>>pbj's.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Maurice
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> --
>>>>> >>>> >>>>>> Ix Multimedia Software
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>>> >>>> >>>>>> 3521 VB Utrecht
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> T. 06-51952295
>>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>--
>>>>> >>>> >>>>>Ix Multimedia Software
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Jan Luykenstraat 27
>>>>> >>>> >>>>>3521 VB Utrecht
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>T. 06-51952295
>>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>>> >>>> >>>>
>>>>> >>>> >>>
>>>>> >>>> >>
>>>>> >>>> >
>>>>> >>>>
>>>>> >>>>
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>
>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Om sort of asked already. We'll see how they respond. Thanks for all
your help on this.
-Alex
On 12/10/13 2:57 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>One possible fix (I couldn't check it yet ) is to open "Jenkins slave"
>Windows service, and check "Allow to interact with desktop".
>That may solve the problem, but not sure yet...
>
>Can you ask the infra ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 23:54
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Awesome. You are the detective of the day. Thanks for staying with it.
>
>-Alex
>
>On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Got it! Here is what happened:
>>https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Win
>>dow
>>s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsserv
>>s+ice
>>%28require.NET2.0framework%29
>>
>>I did the same and got the same launch command.
>>
>>So the slave is launched as a service as well, and does not get a window.
>>
>>Maurice
>>
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 23:41
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>Besides, do you know (or can you ask infra) if there are other Apache
>>projects that require a window, and what are their run config?
>>That might help...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 23:39
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>Also, could you ask if jenkins is running on a locked session, or
>>completely out of session.
>>
>>The slave window can only work when in session or with session locked,
>>but not "out of session".
>>While the other methods (including "run as windows service") can also
>>work out of session, but in this case, you need to check that service
>>can interact with the desktop.
>>
>>I still have a few check to do here, to confirm these assumptions.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013
>>23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>advise needed
>>
>>Awesome. I hope you are correct.
>>
>>On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>When you connect to https://builds.apache.org/computer/windows1/
>>>
>>>It says just below the title "Connected through JNLP"
>>>
>>>I have compared with my own installation and there is a notable
>>>difference:
>>>
>>>b.a.o:
>>>
>>>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>>>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>>>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>>>
>>>my Jenkins:
>>>sun.java.command com.sun.javaws.Main
>>>C:\Users\amsellem\AppData\Local\Temp\javaws2
>>>
>>>
>>>According to Jenkins doc, the b.a.o launch method is used for headless
>>>slaves, so that would explain why it does not get a window.
>>>
>>>I am trying to do the same now and let you know.
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>Saw it. Have we asked him if the Flex build is running in a slave and
>>>the slave has a window?
>>>
>>>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>>>Here is Gavin's response a minute ago:
>>>>
>>>>=================
>>>>> Gavin,
>>>>>
>>>>> Can you please copy-paste this line into a command prompt and tell
>>>>>us what the result is:
>>>>>
>>>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>>>
>>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>>> pbk"
>>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>>>
>>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>>> pbj"
>>>>>
>>>>> (mind the wrap)
>>>>>
>>>>> Thanks!
>>>>
>>>>Result is a slight pause, then the prompt returns. No error, no output.
>>>>
>>>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>>>variable.)
>>>>
>>>>Let me know what's next to check , thanks
>>>>
>>>>Gav...
>>>>=================
>>>>
>>>>
>>>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>>>><bi...@gmail.com>wrote:
>>>>
>>>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>>>
>>>>>> Don't know, but if you can prove that the slave can be configured
>>>>>>in a way that it won't run, then we have a more specific question
>>>>>>to ask infra.
>>>>>>
>>>>>> -Alex
>>>>>>
>>>>>
>>>>> Wow, this is like CSI ;-)
>>>>>
>>>>> Here is what we know. Gavin recently installed a new slave
>>>>>(windows2) I am guessing that something was probably changed in the
>>>>>way slaves are run.
>>>>>
>>>>> BTW, here is another piece of information. This is the system info
>>>>> for
>>>>> windows1:
>>>>>
>>>>> https://builds.apache.org/computer/windows1/systemInfo
>>>>>
>>>>> Anything looks out of the ordinary?
>>>>>
>>>>> Thanks,
>>>>> Om
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>>>> <ma...@systar.com>
>>>>>> wrote:
>>>>>>
>>>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>>>> >- Java web start (JNLP)
>>>>>> >- command line from master
>>>>>> >- via SSH on Unix machines
>>>>>> >- as a Windows Service.
>>>>>> >
>>>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>>>window.
>>>>>> >I am going to try "as a Windows Service".
>>>>>> >
>>>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>>>> >
>>>>>> >Maurice
>>>>>> >-----Message d'origine-----
>>>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>>>> >[Builds/Jenkins] Help and advise needed
>>>>>> >
>>>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>>>> >
>>>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>>>> ><ma...@systar.com>
>>>>>> >wrote:
>>>>>> >
>>>>>> >>Now run the same build on a slave node (that gets a windows
>>>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>>>> >>
>>>>>> >>Remote build on windowsSlave1 in workspace
>>>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>>>pixelbender-compile
>>>>>> >>&& exit %%ERRORLEVEL%%"'
>>>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m
>>>>>> >>-XX:MaxPermSize=512m -XX:MaxHeapSize=512m
>>>>>> >>-XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
>>>>>> >>Buildfile:
>>>>>>
>>>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\b
>>>>>>>>u
>>>>>>>>ild
>>>>>>>>.
>>>>>>>>x
>>>>>> >>ml
>>>>>> >>
>>>>>> >>pixelbender-compile:
>>>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >> [exec] Version string: 3.0.0
>>>>>> >> [exec]
>>>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>>>> >> [exec] OpenGL Version 3.0
>>>>>> >> [exec] Has NPOT support: TRUE
>>>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>>>> >> [exec] Completed shader test!
>>>>>> >> [exec] Return code: 7
>>>>>> >> [exec] Result: 7
>>>>>> >>BUILD SUCCESSFUL
>>>>>> >>Total time: 8 seconds
>>>>>> >>Finished: SUCCESS
>>>>>> >>
>>>>>> >>Well, that's a difference.
>>>>>> >>
>>>>>> >>Maurice
>>>>>> >>
>>>>>> >>-----Message d'origine-----
>>>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>>> >>décembre
>>>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>>> >>Help and advise needed
>>>>>> >>
>>>>>> >>Nice. Thanks for sticking with it.
>>>>>> >>
>>>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>>>> >><ma...@systar.com>
>>>>>> >>wrote:
>>>>>> >>
>>>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>>>> >>>64bit
>>>>>>(
>>>>>> >>>Tomcat is running as a Windows Service).
>>>>>> >>>
>>>>>> >>>- Created a simple job, on the "master" node, than starts
>>>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>>>"pixelbender-compile"
>>>>>> >>>target
>>>>>> >>>- Jenkins output of the job:
>>>>>> >>>
>>>>>> >>>pixelbender-compile:
>>>>>> >>> [exec] AIF Internal exception
>>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>>>> >>> [exec] Return code: 1
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>>> >>> [exec] Result: 1
>>>>>> >>>
>>>>>> >>>So I am getting the same error.
>>>>>> >>>
>>>>>> >>>Om says "master" does not get a window, so this result seems to
>>>>>> >>>be normal.
>>>>>> >>>
>>>>>> >>>I am trying now to create a slave node and run the job on it.
>>>>>> >>>
>>>>>> >>>Maurice
>>>>>> >>>
>>>>>> >>>-----Message d'origine-----
>>>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>>>> >>>
>>>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>>>> >>>
>>>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>>>first...
>>>>>> >>>
>>>>>> >>>Maurice
>>>>>> >>>
>>>>>> >>>-----Message d'origine-----
>>>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>>>>> >>>advise needed
>>>>>> >>>
>>>>>> >>>Maurice,
>>>>>> >>>
>>>>>> >>>When you ran it on your machine, was it on Cygwin or from
>>>>>>Jenkins?
>>>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>>>(master)
>>>>>> >>>does not get a window. Only slave executors are configured to
>>>>>> >>>get a window.
>>>>>> >>>Whereas Cygwin does not have such restrictions.
>>>>>> >>>
>>>>>> >>>Thanks,
>>>>>> >>>Om
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>>>wrote:
>>>>>> >>>
>>>>>> >>>> I have no idea what to do with that information. But thanks
>>>>>> >>>>for trying.
>>>>>> >>>>
>>>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>>>> >>>> <ma...@systar.com>
>>>>>> >>>> wrote:
>>>>>> >>>>
>>>>>> >>>> >So this is the output from the b.a.o box:
>>>>>> >>>> >
>>>>>> >>>> >pixelbender-compile:
>>>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>>>> >>>> > [exec] AIF Internal exception
>>>>>> >>>> > [exec] Return code: 1
>>>>>> >>>> > [exec] Result: 1
>>>>>> >>>> >
>>>>>> >>>> >To be compared to the output on my PC:
>>>>>> >>>> >pixelbender-compile
>>>>>> >>>> >exec
>>>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>>>> >>>> >Vendor string: NVIDIA Corporation
>>>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >>>> >Version string: 3.0.0
>>>>>> >>>> >
>>>>>> >>>> >OpenGL version as determined by Extensionator...
>>>>>> >>>> >OpenGL Version 3.0
>>>>>> >>>> >Has NPOT support: TRUE
>>>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>> >>>> >shader test!
>>>>>> >>>> >Return code: 7
>>>>>> >>>> >Result: 7
>>>>>> >>>> >Exec
>>>>>> >>>> >
>>>>>> >>>> >That does not tell much, except that there seems to be an
>>>>>> >>>> >issue with accessing the GPU.
>>>>>> >>>> >
>>>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>>>> >>>> >more tests
>>>>>> >>>>?
>>>>>> >>>> >
>>>>>> >>>> >Maurice
>>>>>> >>>> >
>>>>>> >>>> >-----Message d'origine-----
>>>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>>>dev@flex.apache.orgObjet :
>>>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>>>> >>>> >
>>>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>>>> >>>> >
>>>>>> >>>> >Can you try on your side, please ?
>>>>>> >>>> >
>>>>>> >>>> >-----Message d'origine-----
>>>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>>> >>>> >décembre
>>>>>> >>>> >2013
>>>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>>> >>>> >Help
>>>>>>and
>>>>>> >>>> >advise needed
>>>>>> >>>> >
>>>>>> >>>> >Won't that break Mac builds?
>>>>>> >>>> >
>>>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>>>> >>>> ><ma...@systar.com>
>>>>>> >>>> >wrote:
>>>>>> >>>> >
>>>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>>>> >>>> >>
>>>>>> >>>> >><exec
>>>>>> >>>> >>executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>>>> >>>> >>
>>>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>>>> >>>> >>
>>>>>> >>>> >>I am sure the result will be interesting.
>>>>>> >>>> >>
>>>>>> >>>> >>Anyway, it can't hurt ;-)
>>>>>> >>>> >>
>>>>>> >>>> >>Maurice
>>>>>> >>>> >>
>>>>>> >>>> >>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>
>>>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's
>>>>>> >>>> >>latest
>>>>>> >>>>request.
>>>>>> >>>> >>
>>>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>>>> >>>> >>
>>>>>> >>>> >>-Alex
>>>>>> >>>> >>
>>>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>>>> >>>> >><ma...@systar.com>
>>>>>> >>>> >>wrote:
>>>>>> >>>> >>
>>>>>> >>>> >>>Sure, if you can ask him.
>>>>>> >>>> >>>
>>>>>> >>>> >>>Maurice
>>>>>> >>>> >>>
>>>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>
>>>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>>>> >>>> >>>
>>>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>>>> >>>> >>><ma...@systar.com>
>>>>>> >>>> >>>wrote:
>>>>>> >>>> >>>
>>>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>>>> >>>> >>>>version of
>>>>>>OpenGL:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Console output on my laptop is below:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>>>Bender
>>>>>> >>>> >>>>Toolkit
>>>>>> >>>> >>>>2>sniffer_gpu.exe
>>>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>>> >>>> >>>>Version string: 3.0.0
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>>>> >>>> >>>>OpenGL Version 3.0
>>>>>> >>>> >>>>Has NPOT support: TRUE
>>>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>>shader
>>>>>> >>>>test!
>>>>>> >>>> >>>>Return code: 7
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>>>utility
>>>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>WDYT ?
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>Maurice
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>>>[Builds/Jenkins]
>>>>>> >>>> >>>>Help and advise needed
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>>>though.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>>>> >>>> >>>>I'm
>>>>>>not
>>>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>-Alex
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>>>> >>>> >>>><ma...@systar.com>
>>>>>> >>>> >>>>wrote:
>>>>>> >>>> >>>>
>>>>>> >>>> >>>>>I understand that.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Actually, my "understanding" on this issue was that
>>>>>> >>>> >>>>>pixel bender compiler required some sort of hardware
>>>>>> >>>> >>>>>configuration (OpenGL,
>>>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>>>Jenkins
>>>>>> >>>> >>>>>slave node, so that's why the build was failing, and
>>>>>> >>>> >>>>>the Apache Infra was reluctant to let us modify
>>>>>> >>>> >>>>>anything, or even access the VM ourselves.
>>>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>>>> >>>> >>>>>and
>>>>>>use
>>>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>That, of course, is much preferable...
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Maurice
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Maurice,
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Your help is very much appreciated!
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>>>> >>>> >>>>>the law, more of the rules. An Apache release is
>>>>>> >>>> >>>>>supposed to be 'source only', and we if we can produce
>>>>>> >>>> >>>>>needed binaries from source, we keep only the source,
>>>>>> >>>> >>>>>not the artefacts
>>>>>>themselves in
>>>>>> >>>>the repo.
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>EdB
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>>>> >>>> >>>>>>>In addition to the various "legal" issues with
>>>>>> >>>> >>>>>>>binaries in the
>>>>>> >>>>repo.
>>>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>>>> >>>> >>>>>>the repo, so I won't insist.
>>>>>> >>>> >>>>>> But please can you explain what are the legal issues
>>>>>> >>>> >>>>>>of having binaries in the repo? Is this because of
>>>>>> >>>> >>>>>>Adobe, or
>>>>>>ASF
>>>>>> >>>>rules ?
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>>>> >>>> >>>>>> email thread
>>>>>>was
>>>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Regards,
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Maurice
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>>>mardi
>>>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
>>>>>>Re:
>>>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> In addition to the various "legal" issues with
>>>>>> >>>> >>>>>>binaries in the repo, we'd be masking the cause of this
>>>>>>failure.
>>>>>> >>>> >>>>>>In
>>>>>>order
>>>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>>>> >>>> >>>>>>we
>>>>>>need
>>>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> EdB
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>>>> >>>> >>>>>> set
>>>>>>to
>>>>>> >>>>FR...
>>>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>>>> >>>> >>>>>>>> and
>>>>>> >>>>complain.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> I don't understand.
>>>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>>>nightly?
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> [From the other emai]
>>>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>>>The
>>>>>> >>>> >>>>>>>>pbj files were removed during the initial release
>>>>>>audit.
>>>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in
>>>>>> >>>> >>>>>>>>the pbj
>>>>>> >>>>files.
>>>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>>>> >>>>temporarily.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>>>> >>>> >>>>>>>>Yes but ...
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>>>parameter
>>>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>>>pbj's.
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>> Maurice
>>>>>> >>>> >>>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> --
>>>>>> >>>> >>>>>> Ix Multimedia Software
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>>>> >>>> >>>>>> 3521 VB Utrecht
>>>>>> >>>> >>>>>>
>>>>>> >>>> >>>>>> T. 06-51952295
>>>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>--
>>>>>> >>>> >>>>>Ix Multimedia Software
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>Jan Luykenstraat 27
>>>>>> >>>> >>>>>3521 VB Utrecht
>>>>>> >>>> >>>>>
>>>>>> >>>> >>>>>T. 06-51952295
>>>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>>>> >>>> >>>>
>>>>>> >>>> >>>
>>>>>> >>>> >>
>>>>>> >>>> >
>>>>>> >>>>
>>>>>> >>>>
>>>>>> >>
>>>>>> >
>>>>>>
>>>>>>
>>>>>
>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
One possible fix (I couldn't check it yet ) is to open "Jenkins slave" Windows service, and check "Allow to interact with desktop".
That may solve the problem, but not sure yet...
Can you ask the infra ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 23:54
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. You are the detective of the day. Thanks for staying with it.
-Alex
On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Got it! Here is what happened:
>https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Win
>dow
>s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsserv
>s+ice
>%28require.NET2.0framework%29
>
>I did the same and got the same launch command.
>
>So the slave is launched as a service as well, and does not get a window.
>
>Maurice
>
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:41
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Besides, do you know (or can you ask infra) if there are other Apache
>projects that require a window, and what are their run config?
>That might help...
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:39
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Also, could you ask if jenkins is running on a locked session, or
>completely out of session.
>
>The slave window can only work when in session or with session locked,
>but not "out of session".
>While the other methods (including "run as windows service") can also
>work out of session, but in this case, you need to check that service
>can interact with the desktop.
>
>I still have a few check to do here, to confirm these assumptions.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013
>23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>advise needed
>
>Awesome. I hope you are correct.
>
>On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>When you connect to https://builds.apache.org/computer/windows1/
>>
>>It says just below the title "Connected through JNLP"
>>
>>I have compared with my own installation and there is a notable
>>difference:
>>
>>b.a.o:
>>
>>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>>
>>my Jenkins:
>>sun.java.command com.sun.javaws.Main
>>C:\Users\amsellem\AppData\Local\Temp\javaws2
>>
>>
>>According to Jenkins doc, the b.a.o launch method is used for headless
>>slaves, so that would explain why it does not get a window.
>>
>>I am trying to do the same now and let you know.
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Saw it. Have we asked him if the Flex build is running in a slave and
>>the slave has a window?
>>
>>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>Here is Gavin's response a minute ago:
>>>
>>>=================
>>>> Gavin,
>>>>
>>>> Can you please copy-paste this line into a command prompt and tell
>>>>us what the result is:
>>>>
>>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbk"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbj"
>>>>
>>>> (mind the wrap)
>>>>
>>>> Thanks!
>>>
>>>Result is a slight pause, then the prompt returns. No error, no output.
>>>
>>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>>variable.)
>>>
>>>Let me know what's next to check , thanks
>>>
>>>Gav...
>>>=================
>>>
>>>
>>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>>><bi...@gmail.com>wrote:
>>>
>>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>>
>>>>> Don't know, but if you can prove that the slave can be configured
>>>>>in a way that it won't run, then we have a more specific question
>>>>>to ask infra.
>>>>>
>>>>> -Alex
>>>>>
>>>>
>>>> Wow, this is like CSI ;-)
>>>>
>>>> Here is what we know. Gavin recently installed a new slave
>>>>(windows2) I am guessing that something was probably changed in the
>>>>way slaves are run.
>>>>
>>>> BTW, here is another piece of information. This is the system info
>>>> for
>>>> windows1:
>>>>
>>>> https://builds.apache.org/computer/windows1/systemInfo
>>>>
>>>> Anything looks out of the ordinary?
>>>>
>>>> Thanks,
>>>> Om
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>>> <ma...@systar.com>
>>>>> wrote:
>>>>>
>>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>>> >- Java web start (JNLP)
>>>>> >- command line from master
>>>>> >- via SSH on Unix machines
>>>>> >- as a Windows Service.
>>>>> >
>>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>>window.
>>>>> >I am going to try "as a Windows Service".
>>>>> >
>>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>>> >
>>>>> >Maurice
>>>>> >-----Message d'origine-----
>>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>>> >[Builds/Jenkins] Help and advise needed
>>>>> >
>>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>>> >
>>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>>> ><ma...@systar.com>
>>>>> >wrote:
>>>>> >
>>>>> >>Now run the same build on a slave node (that gets a windows
>>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>>> >>
>>>>> >>Remote build on windowsSlave1 in workspace
>>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>>pixelbender-compile
>>>>> >>&& exit %%ERRORLEVEL%%"'
>>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m
>>>>> >>-XX:MaxPermSize=512m -XX:MaxHeapSize=512m
>>>>> >>-XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
>>>>> >>Buildfile:
>>>>>
>>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\b
>>>>>>>u
>>>>>>>ild
>>>>>>>.
>>>>>>>x
>>>>> >>ml
>>>>> >>
>>>>> >>pixelbender-compile:
>>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>>> >> [exec] Version string: 3.0.0
>>>>> >> [exec]
>>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>>> >> [exec] OpenGL Version 3.0
>>>>> >> [exec] Has NPOT support: TRUE
>>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>>> >> [exec] Completed shader test!
>>>>> >> [exec] Return code: 7
>>>>> >> [exec] Result: 7
>>>>> >>BUILD SUCCESSFUL
>>>>> >>Total time: 8 seconds
>>>>> >>Finished: SUCCESS
>>>>> >>
>>>>> >>Well, that's a difference.
>>>>> >>
>>>>> >>Maurice
>>>>> >>
>>>>> >>-----Message d'origine-----
>>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>décembre
>>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>Help and advise needed
>>>>> >>
>>>>> >>Nice. Thanks for sticking with it.
>>>>> >>
>>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>>> >><ma...@systar.com>
>>>>> >>wrote:
>>>>> >>
>>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>>> >>>64bit
>>>>>(
>>>>> >>>Tomcat is running as a Windows Service).
>>>>> >>>
>>>>> >>>- Created a simple job, on the "master" node, than starts
>>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>>"pixelbender-compile"
>>>>> >>>target
>>>>> >>>- Jenkins output of the job:
>>>>> >>>
>>>>> >>>pixelbender-compile:
>>>>> >>> [exec] AIF Internal exception
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>>> >>> [exec] Return code: 1
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>>
>>>>> >>>So I am getting the same error.
>>>>> >>>
>>>>> >>>Om says "master" does not get a window, so this result seems to
>>>>> >>>be normal.
>>>>> >>>
>>>>> >>>I am trying now to create a slave node and run the job on it.
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>
>>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>>> >>>
>>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>>first...
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>>>> >>>advise needed
>>>>> >>>
>>>>> >>>Maurice,
>>>>> >>>
>>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>>(master)
>>>>> >>>does not get a window. Only slave executors are configured to
>>>>> >>>get a window.
>>>>> >>>Whereas Cygwin does not have such restrictions.
>>>>> >>>
>>>>> >>>Thanks,
>>>>> >>>Om
>>>>> >>>
>>>>> >>>
>>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>>wrote:
>>>>> >>>
>>>>> >>>> I have no idea what to do with that information. But thanks
>>>>> >>>>for trying.
>>>>> >>>>
>>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>>> >>>> <ma...@systar.com>
>>>>> >>>> wrote:
>>>>> >>>>
>>>>> >>>> >So this is the output from the b.a.o box:
>>>>> >>>> >
>>>>> >>>> >pixelbender-compile:
>>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>>> >>>> > [exec] AIF Internal exception
>>>>> >>>> > [exec] Return code: 1
>>>>> >>>> > [exec] Result: 1
>>>>> >>>> >
>>>>> >>>> >To be compared to the output on my PC:
>>>>> >>>> >pixelbender-compile
>>>>> >>>> >exec
>>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>>> >>>> >Vendor string: NVIDIA Corporation
>>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >Version string: 3.0.0
>>>>> >>>> >
>>>>> >>>> >OpenGL version as determined by Extensionator...
>>>>> >>>> >OpenGL Version 3.0
>>>>> >>>> >Has NPOT support: TRUE
>>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>>> >>>> >shader test!
>>>>> >>>> >Return code: 7
>>>>> >>>> >Result: 7
>>>>> >>>> >Exec
>>>>> >>>> >
>>>>> >>>> >That does not tell much, except that there seems to be an
>>>>> >>>> >issue with accessing the GPU.
>>>>> >>>> >
>>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>>> >>>> >more tests
>>>>> >>>>?
>>>>> >>>> >
>>>>> >>>> >Maurice
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>>dev@flex.apache.orgObjet :
>>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>> >
>>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>>> >>>> >
>>>>> >>>> >Can you try on your side, please ?
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>>> >décembre
>>>>> >>>> >2013
>>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>>> >Help
>>>>>and
>>>>> >>>> >advise needed
>>>>> >>>> >
>>>>> >>>> >Won't that break Mac builds?
>>>>> >>>> >
>>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>>> >>>> ><ma...@systar.com>
>>>>> >>>> >wrote:
>>>>> >>>> >
>>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>>> >>>> >>
>>>>> >>>> >><exec
>>>>> >>>> >>executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>>> >>>> >>
>>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>>> >>>> >>
>>>>> >>>> >>I am sure the result will be interesting.
>>>>> >>>> >>
>>>>> >>>> >>Anyway, it can't hurt ;-)
>>>>> >>>> >>
>>>>> >>>> >>Maurice
>>>>> >>>> >>
>>>>> >>>> >>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>
>>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's
>>>>> >>>> >>latest
>>>>> >>>>request.
>>>>> >>>> >>
>>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>>> >>>> >>
>>>>> >>>> >>-Alex
>>>>> >>>> >>
>>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>>> >>>> >><ma...@systar.com>
>>>>> >>>> >>wrote:
>>>>> >>>> >>
>>>>> >>>> >>>Sure, if you can ask him.
>>>>> >>>> >>>
>>>>> >>>> >>>Maurice
>>>>> >>>> >>>
>>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>
>>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>>> >>>> >>>
>>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>>> >>>> >>><ma...@systar.com>
>>>>> >>>> >>>wrote:
>>>>> >>>> >>>
>>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>>> >>>> >>>>version of
>>>>>OpenGL:
>>>>> >>>> >>>>
>>>>> >>>> >>>>Console output on my laptop is below:
>>>>> >>>> >>>>
>>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>>Bender
>>>>> >>>> >>>>Toolkit
>>>>> >>>> >>>>2>sniffer_gpu.exe
>>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >>>>Version string: 3.0.0
>>>>> >>>> >>>>
>>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>>> >>>> >>>>OpenGL Version 3.0
>>>>> >>>> >>>>Has NPOT support: TRUE
>>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>shader
>>>>> >>>>test!
>>>>> >>>> >>>>Return code: 7
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>>utility
>>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>>> >>>> >>>>
>>>>> >>>> >>>>WDYT ?
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maurice
>>>>> >>>> >>>>
>>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>>[Builds/Jenkins]
>>>>> >>>> >>>>Help and advise needed
>>>>> >>>> >>>>
>>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>>though.
>>>>> >>>> >>>>
>>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>>> >>>> >>>>I'm
>>>>>not
>>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>>> >>>> >>>>
>>>>> >>>> >>>>-Alex
>>>>> >>>> >>>>
>>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>>> >>>> >>>><ma...@systar.com>
>>>>> >>>> >>>>wrote:
>>>>> >>>> >>>>
>>>>> >>>> >>>>>I understand that.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Actually, my "understanding" on this issue was that
>>>>> >>>> >>>>>pixel bender compiler required some sort of hardware
>>>>> >>>> >>>>>configuration (OpenGL,
>>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>>Jenkins
>>>>> >>>> >>>>>slave node, so that's why the build was failing, and
>>>>> >>>> >>>>>the Apache Infra was reluctant to let us modify
>>>>> >>>> >>>>>anything, or even access the VM ourselves.
>>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>>> >>>> >>>>>and
>>>>>use
>>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>That, of course, is much preferable...
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice,
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Your help is very much appreciated!
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>>> >>>> >>>>>the law, more of the rules. An Apache release is
>>>>> >>>> >>>>>supposed to be 'source only', and we if we can produce
>>>>> >>>> >>>>>needed binaries from source, we keep only the source,
>>>>> >>>> >>>>>not the artefacts
>>>>>themselves in
>>>>> >>>>the repo.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>EdB
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>In addition to the various "legal" issues with
>>>>> >>>> >>>>>>>binaries in the
>>>>> >>>>repo.
>>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>>> >>>> >>>>>>the repo, so I won't insist.
>>>>> >>>> >>>>>> But please can you explain what are the legal issues
>>>>> >>>> >>>>>>of having binaries in the repo? Is this because of
>>>>> >>>> >>>>>>Adobe, or
>>>>>ASF
>>>>> >>>>rules ?
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>>> >>>> >>>>>> email thread
>>>>>was
>>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Regards,
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Maurice
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>>mardi
>>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
>>>>>Re:
>>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> In addition to the various "legal" issues with
>>>>> >>>> >>>>>>binaries in the repo, we'd be masking the cause of this failure.
>>>>> >>>> >>>>>>In
>>>>>order
>>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>>> >>>> >>>>>>we
>>>>>need
>>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> EdB
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>>> >>>> >>>>>> set
>>>>>to
>>>>> >>>>FR...
>>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>>> >>>> >>>>>>>> and
>>>>> >>>>complain.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> I don't understand.
>>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>>nightly?
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> [From the other emai]
>>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>>The
>>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in
>>>>> >>>> >>>>>>>>the pbj
>>>>> >>>>files.
>>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>>> >>>>temporarily.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>>> >>>> >>>>>>>>Yes but ...
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>>parameter
>>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>>pbj's.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Maurice
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> --
>>>>> >>>> >>>>>> Ix Multimedia Software
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>>> >>>> >>>>>> 3521 VB Utrecht
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> T. 06-51952295
>>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>--
>>>>> >>>> >>>>>Ix Multimedia Software
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Jan Luykenstraat 27
>>>>> >>>> >>>>>3521 VB Utrecht
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>T. 06-51952295
>>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>>> >>>> >>>>
>>>>> >>>> >>>
>>>>> >>>> >>
>>>>> >>>> >
>>>>> >>>>
>>>>> >>>>
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
And proof: here is the output where the slave is installed as a service:
Lancé par une alarme périodique
Construction à distance sur windowsSlave1 in workspace D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile && exit %%ERRORLEVEL%%"'
ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m -XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
Buildfile: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.xml
pixelbender-compile:
[exec] AIF Internal exceptionDevice: 005CB6DC has video RAM(MB): 3844
[exec]
[exec] Device: 005CB6DC has video RAM(MB): 512
[exec] Return code: 1
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
BINGO!!!
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:52
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Got it! Here is what happened:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29
I did the same and got the same launch command.
So the slave is launched as a service as well, and does not get a window.
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:41
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Besides, do you know (or can you ask infra) if there are other Apache projects that require a window, and what are their run config?
That might help...
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:39
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Also, could you ask if jenkins is running on a locked session, or completely out of session.
The slave window can only work when in session or with session locked, but not "out of session".
While the other methods (including "run as windows service") can also work out of session, but in this case, you need to check that service can interact with the desktop.
I still have a few check to do here, to confirm these assumptions.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013 23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. I hope you are correct.
On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>When you connect to https://builds.apache.org/computer/windows1/
>
>It says just below the title "Connected through JNLP"
>
>I have compared with my own installation and there is a notable
>difference:
>
>b.a.o:
>
>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>
>my Jenkins:
>sun.java.command com.sun.javaws.Main
>C:\Users\amsellem\AppData\Local\Temp\javaws2
>
>
>According to Jenkins doc, the b.a.o launch method is used for headless
>slaves, so that would explain why it does not get a window.
>
>I am trying to do the same now and let you know.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>the slave has a window?
>
>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>Here is Gavin's response a minute ago:
>>
>>=================
>>> Gavin,
>>>
>>> Can you please copy-paste this line into a command prompt and tell
>>>us what the result is:
>>>
>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbk"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbj"
>>>
>>> (mind the wrap)
>>>
>>> Thanks!
>>
>>Result is a slight pause, then the prompt returns. No error, no output.
>>
>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>variable.)
>>
>>Let me know what's next to check , thanks
>>
>>Gav...
>>=================
>>
>>
>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> Don't know, but if you can prove that the slave can be configured
>>>>in a way that it won't run, then we have a more specific question
>>>>to ask infra.
>>>>
>>>> -Alex
>>>>
>>>
>>> Wow, this is like CSI ;-)
>>>
>>> Here is what we know. Gavin recently installed a new slave
>>>(windows2) I am guessing that something was probably changed in the
>>>way slaves are run.
>>>
>>> BTW, here is another piece of information. This is the system info
>>> for
>>> windows1:
>>>
>>> https://builds.apache.org/computer/windows1/systemInfo
>>>
>>> Anything looks out of the ordinary?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>
>>>>
>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>> >- Java web start (JNLP)
>>>> >- command line from master
>>>> >- via SSH on Unix machines
>>>> >- as a Windows Service.
>>>> >
>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>window.
>>>> >I am going to try "as a Windows Service".
>>>> >
>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>> >
>>>> >Maurice
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>> >[Builds/Jenkins] Help and advise needed
>>>> >
>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>> >
>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Now run the same build on a slave node (that gets a windows
>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>> >>
>>>> >>Remote build on windowsSlave1 in workspace
>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>pixelbender-compile
>>>> >>&& exit %%ERRORLEVEL%%"'
>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>> >>-Djava.net.preferIPv4Stack=true
>>>> >>Buildfile:
>>>>
>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\bu
>>>>>>ild
>>>>>>.
>>>>>>x
>>>> >>ml
>>>> >>
>>>> >>pixelbender-compile:
>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>> >> [exec] Version string: 3.0.0
>>>> >> [exec]
>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>> >> [exec] OpenGL Version 3.0
>>>> >> [exec] Has NPOT support: TRUE
>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>> >> [exec] Completed shader test!
>>>> >> [exec] Return code: 7
>>>> >> [exec] Result: 7
>>>> >>BUILD SUCCESSFUL
>>>> >>Total time: 8 seconds
>>>> >>Finished: SUCCESS
>>>> >>
>>>> >>Well, that's a difference.
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>Nice. Thanks for sticking with it.
>>>> >>
>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>> >>>64bit
>>>>(
>>>> >>>Tomcat is running as a Windows Service).
>>>> >>>
>>>> >>>- Created a simple job, on the "master" node, than starts
>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>"pixelbender-compile"
>>>> >>>target
>>>> >>>- Jenkins output of the job:
>>>> >>>
>>>> >>>pixelbender-compile:
>>>> >>> [exec] AIF Internal exception
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>> >>> [exec] Return code: 1
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>>
>>>> >>>So I am getting the same error.
>>>> >>>
>>>> >>>Om says "master" does not get a window, so this result seems to
>>>> >>>be normal.
>>>> >>>
>>>> >>>I am trying now to create a slave node and run the job on it.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>> >>>
>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>first...
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>> >>>needed
>>>> >>>
>>>> >>>Maurice,
>>>> >>>
>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>(master)
>>>> >>>does not get a window. Only slave executors are configured to
>>>> >>>get a window.
>>>> >>>Whereas Cygwin does not have such restrictions.
>>>> >>>
>>>> >>>Thanks,
>>>> >>>Om
>>>> >>>
>>>> >>>
>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>wrote:
>>>> >>>
>>>> >>>> I have no idea what to do with that information. But thanks
>>>> >>>>for trying.
>>>> >>>>
>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> >>>> <ma...@systar.com>
>>>> >>>> wrote:
>>>> >>>>
>>>> >>>> >So this is the output from the b.a.o box:
>>>> >>>> >
>>>> >>>> >pixelbender-compile:
>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> >>>> > [exec] AIF Internal exception
>>>> >>>> > [exec] Return code: 1
>>>> >>>> > [exec] Result: 1
>>>> >>>> >
>>>> >>>> >To be compared to the output on my PC:
>>>> >>>> >pixelbender-compile
>>>> >>>> >exec
>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >>>> >Vendor string: NVIDIA Corporation
>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >Version string: 3.0.0
>>>> >>>> >
>>>> >>>> >OpenGL version as determined by Extensionator...
>>>> >>>> >OpenGL Version 3.0
>>>> >>>> >Has NPOT support: TRUE
>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>> >>>> >shader test!
>>>> >>>> >Return code: 7
>>>> >>>> >Result: 7
>>>> >>>> >Exec
>>>> >>>> >
>>>> >>>> >That does not tell much, except that there seems to be an
>>>> >>>> >issue with accessing the GPU.
>>>> >>>> >
>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>> >>>> >more tests
>>>> >>>>?
>>>> >>>> >
>>>> >>>> >Maurice
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>dev@flex.apache.orgObjet :
>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >>>> >
>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >>>> >
>>>> >>>> >Can you try on your side, please ?
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >décembre
>>>> >>>> >2013
>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>> >Help
>>>>and
>>>> >>>> >advise needed
>>>> >>>> >
>>>> >>>> >Won't that break Mac builds?
>>>> >>>> >
>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> >>>> ><ma...@systar.com>
>>>> >>>> >wrote:
>>>> >>>> >
>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>> >>>> >>
>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>>> >>
>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>> >>>> >>
>>>> >>>> >>I am sure the result will be interesting.
>>>> >>>> >>
>>>> >>>> >>Anyway, it can't hurt ;-)
>>>> >>>> >>
>>>> >>>> >>Maurice
>>>> >>>> >>
>>>> >>>> >>-----Message d'origine-----
>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>décembre
>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>
>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>> >>>>request.
>>>> >>>> >>
>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>> >>>> >>
>>>> >>>> >>-Alex
>>>> >>>> >>
>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >>>> >><ma...@systar.com>
>>>> >>>> >>wrote:
>>>> >>>> >>
>>>> >>>> >>>Sure, if you can ask him.
>>>> >>>> >>>
>>>> >>>> >>>Maurice
>>>> >>>> >>>
>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>
>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>> >>>
>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>>> >>><ma...@systar.com>
>>>> >>>> >>>wrote:
>>>> >>>> >>>
>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>> >>>> >>>>version of
>>>>OpenGL:
>>>> >>>> >>>>
>>>> >>>> >>>>Console output on my laptop is below:
>>>> >>>> >>>>
>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>Bender
>>>> >>>> >>>>Toolkit
>>>> >>>> >>>>2>sniffer_gpu.exe
>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >>>>Version string: 3.0.0
>>>> >>>> >>>>
>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>> >>>>OpenGL Version 3.0
>>>> >>>> >>>>Has NPOT support: TRUE
>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>shader
>>>> >>>>test!
>>>> >>>> >>>>Return code: 7
>>>> >>>> >>>>
>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>utility
>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>> >>>> >>>>
>>>> >>>> >>>>WDYT ?
>>>> >>>> >>>>
>>>> >>>> >>>>Maurice
>>>> >>>> >>>>
>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins]
>>>> >>>> >>>>Help and advise needed
>>>> >>>> >>>>
>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>though.
>>>> >>>> >>>>
>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>> >>>> >>>>I'm
>>>>not
>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>> >>>>
>>>> >>>> >>>>-Alex
>>>> >>>> >>>>
>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>> >>>><ma...@systar.com>
>>>> >>>> >>>>wrote:
>>>> >>>> >>>>
>>>> >>>> >>>>>I understand that.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>> >>>> >>>>>configuration (OpenGL,
>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>Jenkins
>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>> >>>> >>>>>even access the VM ourselves.
>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>> >>>> >>>>>and
>>>>use
>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>> >>>> >>>>>
>>>> >>>> >>>>>That, of course, is much preferable...
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice
>>>> >>>> >>>>>
>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice,
>>>> >>>> >>>>>
>>>> >>>> >>>>>Your help is very much appreciated!
>>>> >>>> >>>>>
>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>> >>>> >>>>>artefacts
>>>>themselves in
>>>> >>>>the repo.
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>EdB
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>>in the
>>>> >>>>repo.
>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>> >>>> >>>>>>the repo, so I won't insist.
>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>> >>>> >>>>>>or
>>>>ASF
>>>> >>>>rules ?
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>> >>>> >>>>>> email thread
>>>>was
>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Regards,
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Maurice
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>mardi
>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>> >>>> >>>>>>In
>>>>order
>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>> >>>> >>>>>>we
>>>>need
>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> EdB
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>> >>>> >>>>>> set
>>>>to
>>>> >>>>FR...
>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>> >>>> >>>>>>>> and
>>>> >>>>complain.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> I don't understand.
>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>nightly?
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> [From the other emai]
>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>The
>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>> >>>> >>>>>>>>pbj
>>>> >>>>files.
>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>> >>>>temporarily.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>> >>>>>>>>Yes but ...
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>parameter
>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>pbj's.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Maurice
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> --
>>>> >>>> >>>>>> Ix Multimedia Software
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>> >>>> >>>>>> 3521 VB Utrecht
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> T. 06-51952295
>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>--
>>>> >>>> >>>>>Ix Multimedia Software
>>>> >>>> >>>>>
>>>> >>>> >>>>>Jan Luykenstraat 27
>>>> >>>> >>>>>3521 VB Utrecht
>>>> >>>> >>>>>
>>>> >>>> >>>>>T. 06-51952295
>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>> >>>> >>>>
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >
>>>> >>>>
>>>> >>>>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Awesome. You are the detective of the day. Thanks for staying with it.
-Alex
On 12/10/13 2:52 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Got it! Here is what happened:
>https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Window
>s+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice
>%28require.NET2.0framework%29
>
>I did the same and got the same launch command.
>
>So the slave is launched as a service as well, and does not get a window.
>
>Maurice
>
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:41
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Besides, do you know (or can you ask infra) if there are other Apache
>projects that require a window, and what are their run config?
>That might help...
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 23:39
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Also, could you ask if jenkins is running on a locked session, or
>completely out of session.
>
>The slave window can only work when in session or with session locked,
>but not "out of session".
>While the other methods (including "run as windows service") can also
>work out of session, but in this case, you need to check that service can
>interact with the desktop.
>
>I still have a few check to do here, to confirm these assumptions.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013
>23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>advise needed
>
>Awesome. I hope you are correct.
>
>On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>When you connect to https://builds.apache.org/computer/windows1/
>>
>>It says just below the title "Connected through JNLP"
>>
>>I have compared with my own installation and there is a notable
>>difference:
>>
>>b.a.o:
>>
>>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>>
>>my Jenkins:
>>sun.java.command com.sun.javaws.Main
>>C:\Users\amsellem\AppData\Local\Temp\javaws2
>>
>>
>>According to Jenkins doc, the b.a.o launch method is used for headless
>>slaves, so that would explain why it does not get a window.
>>
>>I am trying to do the same now and let you know.
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Saw it. Have we asked him if the Flex build is running in a slave and
>>the slave has a window?
>>
>>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>Here is Gavin's response a minute ago:
>>>
>>>=================
>>>> Gavin,
>>>>
>>>> Can you please copy-paste this line into a command prompt and tell
>>>>us what the result is:
>>>>
>>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbk"
>>>> "F:\hudson\hudson-slave\workspace\flex-
>>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>>> pbj"
>>>>
>>>> (mind the wrap)
>>>>
>>>> Thanks!
>>>
>>>Result is a slight pause, then the prompt returns. No error, no output.
>>>
>>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>>variable.)
>>>
>>>Let me know what's next to check , thanks
>>>
>>>Gav...
>>>=================
>>>
>>>
>>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>>><bi...@gmail.com>wrote:
>>>
>>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>>
>>>>> Don't know, but if you can prove that the slave can be configured
>>>>>in a way that it won't run, then we have a more specific question
>>>>>to ask infra.
>>>>>
>>>>> -Alex
>>>>>
>>>>
>>>> Wow, this is like CSI ;-)
>>>>
>>>> Here is what we know. Gavin recently installed a new slave
>>>>(windows2) I am guessing that something was probably changed in the
>>>>way slaves are run.
>>>>
>>>> BTW, here is another piece of information. This is the system info
>>>> for
>>>> windows1:
>>>>
>>>> https://builds.apache.org/computer/windows1/systemInfo
>>>>
>>>> Anything looks out of the ordinary?
>>>>
>>>> Thanks,
>>>> Om
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>>> <ma...@systar.com>
>>>>> wrote:
>>>>>
>>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>>> >- Java web start (JNLP)
>>>>> >- command line from master
>>>>> >- via SSH on Unix machines
>>>>> >- as a Windows Service.
>>>>> >
>>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>>window.
>>>>> >I am going to try "as a Windows Service".
>>>>> >
>>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>>> >
>>>>> >Maurice
>>>>> >-----Message d'origine-----
>>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>>> >[Builds/Jenkins] Help and advise needed
>>>>> >
>>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>>> >
>>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>>> ><ma...@systar.com>
>>>>> >wrote:
>>>>> >
>>>>> >>Now run the same build on a slave node (that gets a windows
>>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>>> >>
>>>>> >>Remote build on windowsSlave1 in workspace
>>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>>pixelbender-compile
>>>>> >>&& exit %%ERRORLEVEL%%"'
>>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>>> >>-Djava.net.preferIPv4Stack=true
>>>>> >>Buildfile:
>>>>>
>>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\bu
>>>>>>>ild
>>>>>>>.
>>>>>>>x
>>>>> >>ml
>>>>> >>
>>>>> >>pixelbender-compile:
>>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>>> >> [exec] Version string: 3.0.0
>>>>> >> [exec]
>>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>>> >> [exec] OpenGL Version 3.0
>>>>> >> [exec] Has NPOT support: TRUE
>>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>>> >> [exec] Completed shader test!
>>>>> >> [exec] Return code: 7
>>>>> >> [exec] Result: 7
>>>>> >>BUILD SUCCESSFUL
>>>>> >>Total time: 8 seconds
>>>>> >>Finished: SUCCESS
>>>>> >>
>>>>> >>Well, that's a difference.
>>>>> >>
>>>>> >>Maurice
>>>>> >>
>>>>> >>-----Message d'origine-----
>>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>décembre
>>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>Help and advise needed
>>>>> >>
>>>>> >>Nice. Thanks for sticking with it.
>>>>> >>
>>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>>> >><ma...@systar.com>
>>>>> >>wrote:
>>>>> >>
>>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>>> >>>64bit
>>>>>(
>>>>> >>>Tomcat is running as a Windows Service).
>>>>> >>>
>>>>> >>>- Created a simple job, on the "master" node, than starts
>>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>>"pixelbender-compile"
>>>>> >>>target
>>>>> >>>- Jenkins output of the job:
>>>>> >>>
>>>>> >>>pixelbender-compile:
>>>>> >>> [exec] AIF Internal exception
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>>> >>> [exec] Return code: 1
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>> [exec] ERROR: AIF Internal exception
>>>>> >>> [exec] Result: 1
>>>>> >>>
>>>>> >>>So I am getting the same error.
>>>>> >>>
>>>>> >>>Om says "master" does not get a window, so this result seems to
>>>>> >>>be normal.
>>>>> >>>
>>>>> >>>I am trying now to create a slave node and run the job on it.
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>
>>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>>> >>>
>>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>>first...
>>>>> >>>
>>>>> >>>Maurice
>>>>> >>>
>>>>> >>>-----Message d'origine-----
>>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>>> >>>needed
>>>>> >>>
>>>>> >>>Maurice,
>>>>> >>>
>>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>>(master)
>>>>> >>>does not get a window. Only slave executors are configured to
>>>>> >>>get a window.
>>>>> >>>Whereas Cygwin does not have such restrictions.
>>>>> >>>
>>>>> >>>Thanks,
>>>>> >>>Om
>>>>> >>>
>>>>> >>>
>>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>>wrote:
>>>>> >>>
>>>>> >>>> I have no idea what to do with that information. But thanks
>>>>> >>>>for trying.
>>>>> >>>>
>>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>>> >>>> <ma...@systar.com>
>>>>> >>>> wrote:
>>>>> >>>>
>>>>> >>>> >So this is the output from the b.a.o box:
>>>>> >>>> >
>>>>> >>>> >pixelbender-compile:
>>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>>> >>>> > [exec] AIF Internal exception
>>>>> >>>> > [exec] Return code: 1
>>>>> >>>> > [exec] Result: 1
>>>>> >>>> >
>>>>> >>>> >To be compared to the output on my PC:
>>>>> >>>> >pixelbender-compile
>>>>> >>>> >exec
>>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>>> >>>> >Vendor string: NVIDIA Corporation
>>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >Version string: 3.0.0
>>>>> >>>> >
>>>>> >>>> >OpenGL version as determined by Extensionator...
>>>>> >>>> >OpenGL Version 3.0
>>>>> >>>> >Has NPOT support: TRUE
>>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>>> >>>> >shader test!
>>>>> >>>> >Return code: 7
>>>>> >>>> >Result: 7
>>>>> >>>> >Exec
>>>>> >>>> >
>>>>> >>>> >That does not tell much, except that there seems to be an
>>>>> >>>> >issue with accessing the GPU.
>>>>> >>>> >
>>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>>> >>>> >more tests
>>>>> >>>>?
>>>>> >>>> >
>>>>> >>>> >Maurice
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>>dev@flex.apache.orgObjet :
>>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>>> >>>> >
>>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>>> >>>> >
>>>>> >>>> >Can you try on your side, please ?
>>>>> >>>> >
>>>>> >>>> >-----Message d'origine-----
>>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>>> >décembre
>>>>> >>>> >2013
>>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>>> >>>> >Help
>>>>>and
>>>>> >>>> >advise needed
>>>>> >>>> >
>>>>> >>>> >Won't that break Mac builds?
>>>>> >>>> >
>>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>>> >>>> ><ma...@systar.com>
>>>>> >>>> >wrote:
>>>>> >>>> >
>>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>>> >>>> >>
>>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>>> >>>> >>
>>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>>> >>>> >>
>>>>> >>>> >>I am sure the result will be interesting.
>>>>> >>>> >>
>>>>> >>>> >>Anyway, it can't hurt ;-)
>>>>> >>>> >>
>>>>> >>>> >>Maurice
>>>>> >>>> >>
>>>>> >>>> >>-----Message d'origine-----
>>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>>> >>>> >>décembre
>>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>
>>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>>> >>>>request.
>>>>> >>>> >>
>>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>>> >>>> >>
>>>>> >>>> >>-Alex
>>>>> >>>> >>
>>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>>> >>>> >><ma...@systar.com>
>>>>> >>>> >>wrote:
>>>>> >>>> >>
>>>>> >>>> >>>Sure, if you can ask him.
>>>>> >>>> >>>
>>>>> >>>> >>>Maurice
>>>>> >>>> >>>
>>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>
>>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>>> >>>> >>>
>>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>>> >>>> >>><ma...@systar.com>
>>>>> >>>> >>>wrote:
>>>>> >>>> >>>
>>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>>> >>>> >>>>version of
>>>>>OpenGL:
>>>>> >>>> >>>>
>>>>> >>>> >>>>Console output on my laptop is below:
>>>>> >>>> >>>>
>>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>>Bender
>>>>> >>>> >>>>Toolkit
>>>>> >>>> >>>>2>sniffer_gpu.exe
>>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>> >>>> >>>>Version string: 3.0.0
>>>>> >>>> >>>>
>>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>>> >>>> >>>>OpenGL Version 3.0
>>>>> >>>> >>>>Has NPOT support: TRUE
>>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>>shader
>>>>> >>>>test!
>>>>> >>>> >>>>Return code: 7
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>>utility
>>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>>> >>>> >>>>
>>>>> >>>> >>>>WDYT ?
>>>>> >>>> >>>>
>>>>> >>>> >>>>Maurice
>>>>> >>>> >>>>
>>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>>[Builds/Jenkins]
>>>>> >>>> >>>>Help and advise needed
>>>>> >>>> >>>>
>>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>>though.
>>>>> >>>> >>>>
>>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>>> >>>> >>>>I'm
>>>>>not
>>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>>> >>>> >>>>
>>>>> >>>> >>>>-Alex
>>>>> >>>> >>>>
>>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>>> >>>> >>>><ma...@systar.com>
>>>>> >>>> >>>>wrote:
>>>>> >>>> >>>>
>>>>> >>>> >>>>>I understand that.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>>> >>>> >>>>>configuration (OpenGL,
>>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>>Jenkins
>>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>>> >>>> >>>>>even access the VM ourselves.
>>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>>> >>>> >>>>>and
>>>>>use
>>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>That, of course, is much preferable...
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Maurice,
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Your help is very much appreciated!
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>>> >>>> >>>>>artefacts
>>>>>themselves in
>>>>> >>>>the repo.
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>EdB
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>>> >>>> >>>>>>>in the
>>>>> >>>>repo.
>>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>>> >>>> >>>>>>the repo, so I won't insist.
>>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>>> >>>> >>>>>>or
>>>>>ASF
>>>>> >>>>rules ?
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>>> >>>> >>>>>> email thread
>>>>>was
>>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Regards,
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Maurice
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>>mardi
>>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet :
>>>>>Re:
>>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>>> >>>> >>>>>>In
>>>>>order
>>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>>> >>>> >>>>>>we
>>>>>need
>>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> EdB
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>>> >>>> >>>>>> set
>>>>>to
>>>>> >>>>FR...
>>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>>> >>>> >>>>>>>> and
>>>>> >>>>complain.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> I don't understand.
>>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>>nightly?
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> [From the other emai]
>>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>>The
>>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>>> >>>> >>>>>>>>pbj
>>>>> >>>>files.
>>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>>> >>>>temporarily.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>>> >>>> >>>>>>>>Yes but ...
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>>parameter
>>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>>pbj's.
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>> Maurice
>>>>> >>>> >>>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> --
>>>>> >>>> >>>>>> Ix Multimedia Software
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>>> >>>> >>>>>> 3521 VB Utrecht
>>>>> >>>> >>>>>>
>>>>> >>>> >>>>>> T. 06-51952295
>>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>--
>>>>> >>>> >>>>>Ix Multimedia Software
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>Jan Luykenstraat 27
>>>>> >>>> >>>>>3521 VB Utrecht
>>>>> >>>> >>>>>
>>>>> >>>> >>>>>T. 06-51952295
>>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>>> >>>> >>>>
>>>>> >>>> >>>
>>>>> >>>> >>
>>>>> >>>> >
>>>>> >>>>
>>>>> >>>>
>>>>> >>
>>>>> >
>>>>>
>>>>>
>>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Got it! Here is what happened:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29
I did the same and got the same launch command.
So the slave is launched as a service as well, and does not get a window.
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:41
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Besides, do you know (or can you ask infra) if there are other Apache projects that require a window, and what are their run config?
That might help...
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:39
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Also, could you ask if jenkins is running on a locked session, or completely out of session.
The slave window can only work when in session or with session locked, but not "out of session".
While the other methods (including "run as windows service") can also work out of session, but in this case, you need to check that service can interact with the desktop.
I still have a few check to do here, to confirm these assumptions.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013 23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. I hope you are correct.
On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>When you connect to https://builds.apache.org/computer/windows1/
>
>It says just below the title "Connected through JNLP"
>
>I have compared with my own installation and there is a notable
>difference:
>
>b.a.o:
>
>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>
>my Jenkins:
>sun.java.command com.sun.javaws.Main
>C:\Users\amsellem\AppData\Local\Temp\javaws2
>
>
>According to Jenkins doc, the b.a.o launch method is used for headless
>slaves, so that would explain why it does not get a window.
>
>I am trying to do the same now and let you know.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>the slave has a window?
>
>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>Here is Gavin's response a minute ago:
>>
>>=================
>>> Gavin,
>>>
>>> Can you please copy-paste this line into a command prompt and tell
>>>us what the result is:
>>>
>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbk"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbj"
>>>
>>> (mind the wrap)
>>>
>>> Thanks!
>>
>>Result is a slight pause, then the prompt returns. No error, no output.
>>
>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>variable.)
>>
>>Let me know what's next to check , thanks
>>
>>Gav...
>>=================
>>
>>
>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> Don't know, but if you can prove that the slave can be configured
>>>>in a way that it won't run, then we have a more specific question
>>>>to ask infra.
>>>>
>>>> -Alex
>>>>
>>>
>>> Wow, this is like CSI ;-)
>>>
>>> Here is what we know. Gavin recently installed a new slave
>>>(windows2) I am guessing that something was probably changed in the
>>>way slaves are run.
>>>
>>> BTW, here is another piece of information. This is the system info
>>> for
>>> windows1:
>>>
>>> https://builds.apache.org/computer/windows1/systemInfo
>>>
>>> Anything looks out of the ordinary?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>
>>>>
>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>> >- Java web start (JNLP)
>>>> >- command line from master
>>>> >- via SSH on Unix machines
>>>> >- as a Windows Service.
>>>> >
>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>window.
>>>> >I am going to try "as a Windows Service".
>>>> >
>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>> >
>>>> >Maurice
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>> >[Builds/Jenkins] Help and advise needed
>>>> >
>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>> >
>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Now run the same build on a slave node (that gets a windows
>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>> >>
>>>> >>Remote build on windowsSlave1 in workspace
>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>pixelbender-compile
>>>> >>&& exit %%ERRORLEVEL%%"'
>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>> >>-Djava.net.preferIPv4Stack=true
>>>> >>Buildfile:
>>>>
>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\bu
>>>>>>ild
>>>>>>.
>>>>>>x
>>>> >>ml
>>>> >>
>>>> >>pixelbender-compile:
>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>> >> [exec] Version string: 3.0.0
>>>> >> [exec]
>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>> >> [exec] OpenGL Version 3.0
>>>> >> [exec] Has NPOT support: TRUE
>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>> >> [exec] Completed shader test!
>>>> >> [exec] Return code: 7
>>>> >> [exec] Result: 7
>>>> >>BUILD SUCCESSFUL
>>>> >>Total time: 8 seconds
>>>> >>Finished: SUCCESS
>>>> >>
>>>> >>Well, that's a difference.
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>Nice. Thanks for sticking with it.
>>>> >>
>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>> >>>64bit
>>>>(
>>>> >>>Tomcat is running as a Windows Service).
>>>> >>>
>>>> >>>- Created a simple job, on the "master" node, than starts
>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>"pixelbender-compile"
>>>> >>>target
>>>> >>>- Jenkins output of the job:
>>>> >>>
>>>> >>>pixelbender-compile:
>>>> >>> [exec] AIF Internal exception
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>> >>> [exec] Return code: 1
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>>
>>>> >>>So I am getting the same error.
>>>> >>>
>>>> >>>Om says "master" does not get a window, so this result seems to
>>>> >>>be normal.
>>>> >>>
>>>> >>>I am trying now to create a slave node and run the job on it.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>> >>>
>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>first...
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>> >>>needed
>>>> >>>
>>>> >>>Maurice,
>>>> >>>
>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>(master)
>>>> >>>does not get a window. Only slave executors are configured to
>>>> >>>get a window.
>>>> >>>Whereas Cygwin does not have such restrictions.
>>>> >>>
>>>> >>>Thanks,
>>>> >>>Om
>>>> >>>
>>>> >>>
>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>wrote:
>>>> >>>
>>>> >>>> I have no idea what to do with that information. But thanks
>>>> >>>>for trying.
>>>> >>>>
>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> >>>> <ma...@systar.com>
>>>> >>>> wrote:
>>>> >>>>
>>>> >>>> >So this is the output from the b.a.o box:
>>>> >>>> >
>>>> >>>> >pixelbender-compile:
>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> >>>> > [exec] AIF Internal exception
>>>> >>>> > [exec] Return code: 1
>>>> >>>> > [exec] Result: 1
>>>> >>>> >
>>>> >>>> >To be compared to the output on my PC:
>>>> >>>> >pixelbender-compile
>>>> >>>> >exec
>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >>>> >Vendor string: NVIDIA Corporation
>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >Version string: 3.0.0
>>>> >>>> >
>>>> >>>> >OpenGL version as determined by Extensionator...
>>>> >>>> >OpenGL Version 3.0
>>>> >>>> >Has NPOT support: TRUE
>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>> >>>> >shader test!
>>>> >>>> >Return code: 7
>>>> >>>> >Result: 7
>>>> >>>> >Exec
>>>> >>>> >
>>>> >>>> >That does not tell much, except that there seems to be an
>>>> >>>> >issue with accessing the GPU.
>>>> >>>> >
>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>> >>>> >more tests
>>>> >>>>?
>>>> >>>> >
>>>> >>>> >Maurice
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>dev@flex.apache.orgObjet :
>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >>>> >
>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >>>> >
>>>> >>>> >Can you try on your side, please ?
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >décembre
>>>> >>>> >2013
>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>> >Help
>>>>and
>>>> >>>> >advise needed
>>>> >>>> >
>>>> >>>> >Won't that break Mac builds?
>>>> >>>> >
>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> >>>> ><ma...@systar.com>
>>>> >>>> >wrote:
>>>> >>>> >
>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>> >>>> >>
>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>>> >>
>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>> >>>> >>
>>>> >>>> >>I am sure the result will be interesting.
>>>> >>>> >>
>>>> >>>> >>Anyway, it can't hurt ;-)
>>>> >>>> >>
>>>> >>>> >>Maurice
>>>> >>>> >>
>>>> >>>> >>-----Message d'origine-----
>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>décembre
>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>
>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>> >>>>request.
>>>> >>>> >>
>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>> >>>> >>
>>>> >>>> >>-Alex
>>>> >>>> >>
>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >>>> >><ma...@systar.com>
>>>> >>>> >>wrote:
>>>> >>>> >>
>>>> >>>> >>>Sure, if you can ask him.
>>>> >>>> >>>
>>>> >>>> >>>Maurice
>>>> >>>> >>>
>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>
>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>> >>>
>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>>> >>><ma...@systar.com>
>>>> >>>> >>>wrote:
>>>> >>>> >>>
>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>> >>>> >>>>version of
>>>>OpenGL:
>>>> >>>> >>>>
>>>> >>>> >>>>Console output on my laptop is below:
>>>> >>>> >>>>
>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>Bender
>>>> >>>> >>>>Toolkit
>>>> >>>> >>>>2>sniffer_gpu.exe
>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >>>>Version string: 3.0.0
>>>> >>>> >>>>
>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>> >>>>OpenGL Version 3.0
>>>> >>>> >>>>Has NPOT support: TRUE
>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>shader
>>>> >>>>test!
>>>> >>>> >>>>Return code: 7
>>>> >>>> >>>>
>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>utility
>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>> >>>> >>>>
>>>> >>>> >>>>WDYT ?
>>>> >>>> >>>>
>>>> >>>> >>>>Maurice
>>>> >>>> >>>>
>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins]
>>>> >>>> >>>>Help and advise needed
>>>> >>>> >>>>
>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>though.
>>>> >>>> >>>>
>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>> >>>> >>>>I'm
>>>>not
>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>> >>>>
>>>> >>>> >>>>-Alex
>>>> >>>> >>>>
>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>> >>>><ma...@systar.com>
>>>> >>>> >>>>wrote:
>>>> >>>> >>>>
>>>> >>>> >>>>>I understand that.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>> >>>> >>>>>configuration (OpenGL,
>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>Jenkins
>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>> >>>> >>>>>even access the VM ourselves.
>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>> >>>> >>>>>and
>>>>use
>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>> >>>> >>>>>
>>>> >>>> >>>>>That, of course, is much preferable...
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice
>>>> >>>> >>>>>
>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice,
>>>> >>>> >>>>>
>>>> >>>> >>>>>Your help is very much appreciated!
>>>> >>>> >>>>>
>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>> >>>> >>>>>artefacts
>>>>themselves in
>>>> >>>>the repo.
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>EdB
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>>in the
>>>> >>>>repo.
>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>> >>>> >>>>>>the repo, so I won't insist.
>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>> >>>> >>>>>>or
>>>>ASF
>>>> >>>>rules ?
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>> >>>> >>>>>> email thread
>>>>was
>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Regards,
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Maurice
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>mardi
>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>> >>>> >>>>>>In
>>>>order
>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>> >>>> >>>>>>we
>>>>need
>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> EdB
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>> >>>> >>>>>> set
>>>>to
>>>> >>>>FR...
>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>> >>>> >>>>>>>> and
>>>> >>>>complain.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> I don't understand.
>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>nightly?
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> [From the other emai]
>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>The
>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>> >>>> >>>>>>>>pbj
>>>> >>>>files.
>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>> >>>>temporarily.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>> >>>>>>>>Yes but ...
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>parameter
>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>pbj's.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Maurice
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> --
>>>> >>>> >>>>>> Ix Multimedia Software
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>> >>>> >>>>>> 3521 VB Utrecht
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> T. 06-51952295
>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>--
>>>> >>>> >>>>>Ix Multimedia Software
>>>> >>>> >>>>>
>>>> >>>> >>>>>Jan Luykenstraat 27
>>>> >>>> >>>>>3521 VB Utrecht
>>>> >>>> >>>>>
>>>> >>>> >>>>>T. 06-51952295
>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>> >>>> >>>>
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >
>>>> >>>>
>>>> >>>>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Besides, do you know (or can you ask infra) if there are other Apache projects that require a window, and what are their run config?
That might help...
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 23:39
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Also, could you ask if jenkins is running on a locked session, or completely out of session.
The slave window can only work when in session or with session locked, but not "out of session".
While the other methods (including "run as windows service") can also work out of session, but in this case, you need to check that service can interact with the desktop.
I still have a few check to do here, to confirm these assumptions.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013 23:35 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. I hope you are correct.
On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>When you connect to https://builds.apache.org/computer/windows1/
>
>It says just below the title "Connected through JNLP"
>
>I have compared with my own installation and there is a notable
>difference:
>
>b.a.o:
>
>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>
>my Jenkins:
>sun.java.command com.sun.javaws.Main
>C:\Users\amsellem\AppData\Local\Temp\javaws2
>
>
>According to Jenkins doc, the b.a.o launch method is used for headless
>slaves, so that would explain why it does not get a window.
>
>I am trying to do the same now and let you know.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>the slave has a window?
>
>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>Here is Gavin's response a minute ago:
>>
>>=================
>>> Gavin,
>>>
>>> Can you please copy-paste this line into a command prompt and tell
>>>us what the result is:
>>>
>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbk"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbj"
>>>
>>> (mind the wrap)
>>>
>>> Thanks!
>>
>>Result is a slight pause, then the prompt returns. No error, no output.
>>
>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>variable.)
>>
>>Let me know what's next to check , thanks
>>
>>Gav...
>>=================
>>
>>
>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> Don't know, but if you can prove that the slave can be configured
>>>>in a way that it won't run, then we have a more specific question
>>>>to ask infra.
>>>>
>>>> -Alex
>>>>
>>>
>>> Wow, this is like CSI ;-)
>>>
>>> Here is what we know. Gavin recently installed a new slave
>>>(windows2) I am guessing that something was probably changed in the
>>>way slaves are run.
>>>
>>> BTW, here is another piece of information. This is the system info
>>> for
>>> windows1:
>>>
>>> https://builds.apache.org/computer/windows1/systemInfo
>>>
>>> Anything looks out of the ordinary?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>
>>>>
>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>> >- Java web start (JNLP)
>>>> >- command line from master
>>>> >- via SSH on Unix machines
>>>> >- as a Windows Service.
>>>> >
>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>window.
>>>> >I am going to try "as a Windows Service".
>>>> >
>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>> >
>>>> >Maurice
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>> >[Builds/Jenkins] Help and advise needed
>>>> >
>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>> >
>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Now run the same build on a slave node (that gets a windows
>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>> >>
>>>> >>Remote build on windowsSlave1 in workspace
>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>pixelbender-compile
>>>> >>&& exit %%ERRORLEVEL%%"'
>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>> >>-Djava.net.preferIPv4Stack=true
>>>> >>Buildfile:
>>>>
>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\bu
>>>>>>ild
>>>>>>.
>>>>>>x
>>>> >>ml
>>>> >>
>>>> >>pixelbender-compile:
>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>> >> [exec] Version string: 3.0.0
>>>> >> [exec]
>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>> >> [exec] OpenGL Version 3.0
>>>> >> [exec] Has NPOT support: TRUE
>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>> >> [exec] Completed shader test!
>>>> >> [exec] Return code: 7
>>>> >> [exec] Result: 7
>>>> >>BUILD SUCCESSFUL
>>>> >>Total time: 8 seconds
>>>> >>Finished: SUCCESS
>>>> >>
>>>> >>Well, that's a difference.
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>Nice. Thanks for sticking with it.
>>>> >>
>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>> >>>64bit
>>>>(
>>>> >>>Tomcat is running as a Windows Service).
>>>> >>>
>>>> >>>- Created a simple job, on the "master" node, than starts
>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>"pixelbender-compile"
>>>> >>>target
>>>> >>>- Jenkins output of the job:
>>>> >>>
>>>> >>>pixelbender-compile:
>>>> >>> [exec] AIF Internal exception
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>> >>> [exec] Return code: 1
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>>
>>>> >>>So I am getting the same error.
>>>> >>>
>>>> >>>Om says "master" does not get a window, so this result seems to
>>>> >>>be normal.
>>>> >>>
>>>> >>>I am trying now to create a slave node and run the job on it.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>> >>>
>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>first...
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>> >>>needed
>>>> >>>
>>>> >>>Maurice,
>>>> >>>
>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>(master)
>>>> >>>does not get a window. Only slave executors are configured to
>>>> >>>get a window.
>>>> >>>Whereas Cygwin does not have such restrictions.
>>>> >>>
>>>> >>>Thanks,
>>>> >>>Om
>>>> >>>
>>>> >>>
>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>wrote:
>>>> >>>
>>>> >>>> I have no idea what to do with that information. But thanks
>>>> >>>>for trying.
>>>> >>>>
>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> >>>> <ma...@systar.com>
>>>> >>>> wrote:
>>>> >>>>
>>>> >>>> >So this is the output from the b.a.o box:
>>>> >>>> >
>>>> >>>> >pixelbender-compile:
>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> >>>> > [exec] AIF Internal exception
>>>> >>>> > [exec] Return code: 1
>>>> >>>> > [exec] Result: 1
>>>> >>>> >
>>>> >>>> >To be compared to the output on my PC:
>>>> >>>> >pixelbender-compile
>>>> >>>> >exec
>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >>>> >Vendor string: NVIDIA Corporation
>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >Version string: 3.0.0
>>>> >>>> >
>>>> >>>> >OpenGL version as determined by Extensionator...
>>>> >>>> >OpenGL Version 3.0
>>>> >>>> >Has NPOT support: TRUE
>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>> >>>> >shader test!
>>>> >>>> >Return code: 7
>>>> >>>> >Result: 7
>>>> >>>> >Exec
>>>> >>>> >
>>>> >>>> >That does not tell much, except that there seems to be an
>>>> >>>> >issue with accessing the GPU.
>>>> >>>> >
>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>> >>>> >more tests
>>>> >>>>?
>>>> >>>> >
>>>> >>>> >Maurice
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>dev@flex.apache.orgObjet :
>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >>>> >
>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >>>> >
>>>> >>>> >Can you try on your side, please ?
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >décembre
>>>> >>>> >2013
>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>> >Help
>>>>and
>>>> >>>> >advise needed
>>>> >>>> >
>>>> >>>> >Won't that break Mac builds?
>>>> >>>> >
>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> >>>> ><ma...@systar.com>
>>>> >>>> >wrote:
>>>> >>>> >
>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>> >>>> >>
>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>>> >>
>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>> >>>> >>
>>>> >>>> >>I am sure the result will be interesting.
>>>> >>>> >>
>>>> >>>> >>Anyway, it can't hurt ;-)
>>>> >>>> >>
>>>> >>>> >>Maurice
>>>> >>>> >>
>>>> >>>> >>-----Message d'origine-----
>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>décembre
>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>
>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>> >>>>request.
>>>> >>>> >>
>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>> >>>> >>
>>>> >>>> >>-Alex
>>>> >>>> >>
>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >>>> >><ma...@systar.com>
>>>> >>>> >>wrote:
>>>> >>>> >>
>>>> >>>> >>>Sure, if you can ask him.
>>>> >>>> >>>
>>>> >>>> >>>Maurice
>>>> >>>> >>>
>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>
>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>> >>>
>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>>> >>><ma...@systar.com>
>>>> >>>> >>>wrote:
>>>> >>>> >>>
>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>> >>>> >>>>version of
>>>>OpenGL:
>>>> >>>> >>>>
>>>> >>>> >>>>Console output on my laptop is below:
>>>> >>>> >>>>
>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>Bender
>>>> >>>> >>>>Toolkit
>>>> >>>> >>>>2>sniffer_gpu.exe
>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >>>>Version string: 3.0.0
>>>> >>>> >>>>
>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>> >>>>OpenGL Version 3.0
>>>> >>>> >>>>Has NPOT support: TRUE
>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>shader
>>>> >>>>test!
>>>> >>>> >>>>Return code: 7
>>>> >>>> >>>>
>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>utility
>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>> >>>> >>>>
>>>> >>>> >>>>WDYT ?
>>>> >>>> >>>>
>>>> >>>> >>>>Maurice
>>>> >>>> >>>>
>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins]
>>>> >>>> >>>>Help and advise needed
>>>> >>>> >>>>
>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>though.
>>>> >>>> >>>>
>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>> >>>> >>>>I'm
>>>>not
>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>> >>>>
>>>> >>>> >>>>-Alex
>>>> >>>> >>>>
>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>> >>>><ma...@systar.com>
>>>> >>>> >>>>wrote:
>>>> >>>> >>>>
>>>> >>>> >>>>>I understand that.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>> >>>> >>>>>configuration (OpenGL,
>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>Jenkins
>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>> >>>> >>>>>even access the VM ourselves.
>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>> >>>> >>>>>and
>>>>use
>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>> >>>> >>>>>
>>>> >>>> >>>>>That, of course, is much preferable...
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice
>>>> >>>> >>>>>
>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice,
>>>> >>>> >>>>>
>>>> >>>> >>>>>Your help is very much appreciated!
>>>> >>>> >>>>>
>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>> >>>> >>>>>artefacts
>>>>themselves in
>>>> >>>>the repo.
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>EdB
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>>in the
>>>> >>>>repo.
>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>> >>>> >>>>>>the repo, so I won't insist.
>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>> >>>> >>>>>>or
>>>>ASF
>>>> >>>>rules ?
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>> >>>> >>>>>> email thread
>>>>was
>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Regards,
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Maurice
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>mardi
>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>> >>>> >>>>>>In
>>>>order
>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>> >>>> >>>>>>we
>>>>need
>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> EdB
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>> >>>> >>>>>> set
>>>>to
>>>> >>>>FR...
>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>> >>>> >>>>>>>> and
>>>> >>>>complain.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> I don't understand.
>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>nightly?
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> [From the other emai]
>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>The
>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>> >>>> >>>>>>>>pbj
>>>> >>>>files.
>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>> >>>>temporarily.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>> >>>>>>>>Yes but ...
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>parameter
>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>pbj's.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Maurice
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> --
>>>> >>>> >>>>>> Ix Multimedia Software
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>> >>>> >>>>>> 3521 VB Utrecht
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> T. 06-51952295
>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>--
>>>> >>>> >>>>>Ix Multimedia Software
>>>> >>>> >>>>>
>>>> >>>> >>>>>Jan Luykenstraat 27
>>>> >>>> >>>>>3521 VB Utrecht
>>>> >>>> >>>>>
>>>> >>>> >>>>>T. 06-51952295
>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>> >>>> >>>>
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >
>>>> >>>>
>>>> >>>>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Also, could you ask if jenkins is running on a locked session, or completely out of session.
The slave window can only work when in session or with session locked, but not "out of session".
While the other methods (including "run as windows service") can also work out of session, but in this case, you need to check that service can interact with the desktop.
I still have a few check to do here, to confirm these assumptions.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 23:35
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. I hope you are correct.
On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>When you connect to https://builds.apache.org/computer/windows1/
>
>It says just below the title "Connected through JNLP"
>
>I have compared with my own installation and there is a notable
>difference:
>
>b.a.o:
>
>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>
>my Jenkins:
>sun.java.command com.sun.javaws.Main
>C:\Users\amsellem\AppData\Local\Temp\javaws2
>
>
>According to Jenkins doc, the b.a.o launch method is used for headless
>slaves, so that would explain why it does not get a window.
>
>I am trying to do the same now and let you know.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>the slave has a window?
>
>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>Here is Gavin's response a minute ago:
>>
>>=================
>>> Gavin,
>>>
>>> Can you please copy-paste this line into a command prompt and tell
>>>us what the result is:
>>>
>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbk"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbj"
>>>
>>> (mind the wrap)
>>>
>>> Thanks!
>>
>>Result is a slight pause, then the prompt returns. No error, no output.
>>
>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>variable.)
>>
>>Let me know what's next to check , thanks
>>
>>Gav...
>>=================
>>
>>
>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> Don't know, but if you can prove that the slave can be configured
>>>>in a way that it won't run, then we have a more specific question
>>>>to ask infra.
>>>>
>>>> -Alex
>>>>
>>>
>>> Wow, this is like CSI ;-)
>>>
>>> Here is what we know. Gavin recently installed a new slave
>>>(windows2) I am guessing that something was probably changed in the
>>>way slaves are run.
>>>
>>> BTW, here is another piece of information. This is the system info
>>> for
>>> windows1:
>>>
>>> https://builds.apache.org/computer/windows1/systemInfo
>>>
>>> Anything looks out of the ordinary?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>
>>>>
>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>> >- Java web start (JNLP)
>>>> >- command line from master
>>>> >- via SSH on Unix machines
>>>> >- as a Windows Service.
>>>> >
>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>window.
>>>> >I am going to try "as a Windows Service".
>>>> >
>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>> >
>>>> >Maurice
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>> >[Builds/Jenkins] Help and advise needed
>>>> >
>>>> >InterestingŠ Is there a way to configure a slave so it doesn't
>>>> >get a window? Maybe Infra changed some default on builds.a.o.
>>>> >
>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Now run the same build on a slave node (that gets a windows
>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>> >>
>>>> >>Remote build on windowsSlave1 in workspace
>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>pixelbender-compile
>>>> >>&& exit %%ERRORLEVEL%%"'
>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>> >>-Djava.net.preferIPv4Stack=true
>>>> >>Buildfile:
>>>>
>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\bu
>>>>>>ild
>>>>>>.
>>>>>>x
>>>> >>ml
>>>> >>
>>>> >>pixelbender-compile:
>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>> >> [exec] Version string: 3.0.0
>>>> >> [exec]
>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>> >> [exec] OpenGL Version 3.0
>>>> >> [exec] Has NPOT support: TRUE
>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>> >> [exec] Completed shader test!
>>>> >> [exec] Return code: 7
>>>> >> [exec] Result: 7
>>>> >>BUILD SUCCESSFUL
>>>> >>Total time: 8 seconds
>>>> >>Finished: SUCCESS
>>>> >>
>>>> >>Well, that's a difference.
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>Nice. Thanks for sticking with it.
>>>> >>
>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>> >>>64bit
>>>>(
>>>> >>>Tomcat is running as a Windows Service).
>>>> >>>
>>>> >>>- Created a simple job, on the "master" node, than starts
>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>"pixelbender-compile"
>>>> >>>target
>>>> >>>- Jenkins output of the job:
>>>> >>>
>>>> >>>pixelbender-compile:
>>>> >>> [exec] AIF Internal exception
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>> >>> [exec] Return code: 1
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>>
>>>> >>>So I am getting the same error.
>>>> >>>
>>>> >>>Om says "master" does not get a window, so this result seems to
>>>> >>>be normal.
>>>> >>>
>>>> >>>I am trying now to create a slave node and run the job on it.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>> >>>
>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>first...
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>> >>>needed
>>>> >>>
>>>> >>>Maurice,
>>>> >>>
>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>(master)
>>>> >>>does not get a window. Only slave executors are configured to
>>>> >>>get a window.
>>>> >>>Whereas Cygwin does not have such restrictions.
>>>> >>>
>>>> >>>Thanks,
>>>> >>>Om
>>>> >>>
>>>> >>>
>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>wrote:
>>>> >>>
>>>> >>>> I have no idea what to do with that information. But thanks
>>>> >>>>for trying.
>>>> >>>>
>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> >>>> <ma...@systar.com>
>>>> >>>> wrote:
>>>> >>>>
>>>> >>>> >So this is the output from the b.a.o box:
>>>> >>>> >
>>>> >>>> >pixelbender-compile:
>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> >>>> > [exec] AIF Internal exception
>>>> >>>> > [exec] Return code: 1
>>>> >>>> > [exec] Result: 1
>>>> >>>> >
>>>> >>>> >To be compared to the output on my PC:
>>>> >>>> >pixelbender-compile
>>>> >>>> >exec
>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >>>> >Vendor string: NVIDIA Corporation
>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >Version string: 3.0.0
>>>> >>>> >
>>>> >>>> >OpenGL version as determined by Extensionator...
>>>> >>>> >OpenGL Version 3.0
>>>> >>>> >Has NPOT support: TRUE
>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>> >>>> >shader test!
>>>> >>>> >Return code: 7
>>>> >>>> >Result: 7
>>>> >>>> >Exec
>>>> >>>> >
>>>> >>>> >That does not tell much, except that there seems to be an
>>>> >>>> >issue with accessing the GPU.
>>>> >>>> >
>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>> >>>> >more tests
>>>> >>>>?
>>>> >>>> >
>>>> >>>> >Maurice
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>dev@flex.apache.orgObjet :
>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >>>> >
>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >>>> >
>>>> >>>> >Can you try on your side, please ?
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >décembre
>>>> >>>> >2013
>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>> >Help
>>>>and
>>>> >>>> >advise needed
>>>> >>>> >
>>>> >>>> >Won't that break Mac builds?
>>>> >>>> >
>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> >>>> ><ma...@systar.com>
>>>> >>>> >wrote:
>>>> >>>> >
>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>> >>>> >>
>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>>> >>
>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>> >>>> >>
>>>> >>>> >>I am sure the result will be interesting.
>>>> >>>> >>
>>>> >>>> >>Anyway, it can't hurt ;-)
>>>> >>>> >>
>>>> >>>> >>Maurice
>>>> >>>> >>
>>>> >>>> >>-----Message d'origine-----
>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>décembre
>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>
>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>> >>>>request.
>>>> >>>> >>
>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>> >>>> >>
>>>> >>>> >>-Alex
>>>> >>>> >>
>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >>>> >><ma...@systar.com>
>>>> >>>> >>wrote:
>>>> >>>> >>
>>>> >>>> >>>Sure, if you can ask him.
>>>> >>>> >>>
>>>> >>>> >>>Maurice
>>>> >>>> >>>
>>>> >>>> >>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>
>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>> >>>
>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>>> >>><ma...@systar.com>
>>>> >>>> >>>wrote:
>>>> >>>> >>>
>>>> >>>> >>>>There is a utility in pixel bender toolkit directory
>>>> >>>> >>>>called "sniffer_gpu.exe" that check the presence and
>>>> >>>> >>>>version of
>>>>OpenGL:
>>>> >>>> >>>>
>>>> >>>> >>>>Console output on my laptop is below:
>>>> >>>> >>>>
>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>Bender
>>>> >>>> >>>>Toolkit
>>>> >>>> >>>>2>sniffer_gpu.exe
>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >>>>Version string: 3.0.0
>>>> >>>> >>>>
>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>> >>>>OpenGL Version 3.0
>>>> >>>> >>>>Has NPOT support: TRUE
>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>shader
>>>> >>>>test!
>>>> >>>> >>>>Return code: 7
>>>> >>>> >>>>
>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>utility
>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>> >>>> >>>>
>>>> >>>> >>>>WDYT ?
>>>> >>>> >>>>
>>>> >>>> >>>>Maurice
>>>> >>>> >>>>
>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins]
>>>> >>>> >>>>Help and advise needed
>>>> >>>> >>>>
>>>> >>>> >>>>I don't think we actually know the cause of the problem.
>>>> >>>> >>>>I am going to continue to spend cycles to try to find out
>>>>though.
>>>> >>>> >>>>
>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o.
>>>> >>>> >>>>I'm
>>>>not
>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>> >>>>
>>>> >>>> >>>>-Alex
>>>> >>>> >>>>
>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>> >>>><ma...@systar.com>
>>>> >>>> >>>>wrote:
>>>> >>>> >>>>
>>>> >>>> >>>>>I understand that.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>> >>>> >>>>>configuration (OpenGL,
>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>Jenkins
>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>> >>>> >>>>>even access the VM ourselves.
>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>> >>>> >>>>>and
>>>>use
>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>> >>>> >>>>>
>>>> >>>> >>>>>That, of course, is much preferable...
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice
>>>> >>>> >>>>>
>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice,
>>>> >>>> >>>>>
>>>> >>>> >>>>>Your help is very much appreciated!
>>>> >>>> >>>>>
>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>> >>>> >>>>>artefacts
>>>>themselves in
>>>> >>>>the repo.
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>EdB
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>>in the
>>>> >>>>repo.
>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>> >>>> >>>>>>the repo, so I won't insist.
>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>> >>>> >>>>>>or
>>>>ASF
>>>> >>>>rules ?
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>> >>>> >>>>>> email thread
>>>>was
>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Regards,
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Maurice
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>mardi
>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>> >>>> >>>>>>In
>>>>order
>>>> >>>> >>>>>>to prevent further deterioration of the build process,
>>>> >>>> >>>>>>we
>>>>need
>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> EdB
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>> >>>> >>>>>> set
>>>>to
>>>> >>>>FR...
>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane
>>>> >>>> >>>>>> or if my keyboard was broken ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>> >>>> >>>>>>>> and
>>>> >>>>complain.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> I don't understand.
>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>nightly?
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> [From the other emai]
>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>The
>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>> >>>> >>>>>>>>pbj
>>>> >>>>files.
>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>> >>>>temporarily.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>> >>>>>>>>Yes but ...
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>parameter
>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>pbj's.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Maurice
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> --
>>>> >>>> >>>>>> Ix Multimedia Software
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>> >>>> >>>>>> 3521 VB Utrecht
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> T. 06-51952295
>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>--
>>>> >>>> >>>>>Ix Multimedia Software
>>>> >>>> >>>>>
>>>> >>>> >>>>>Jan Luykenstraat 27
>>>> >>>> >>>>>3521 VB Utrecht
>>>> >>>> >>>>>
>>>> >>>> >>>>>T. 06-51952295
>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>> >>>> >>>>
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >
>>>> >>>>
>>>> >>>>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Awesome. I hope you are correct.
On 12/10/13 2:32 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>When you connect to https://builds.apache.org/computer/windows1/
>
>It says just below the title "Connected through JNLP"
>
>I have compared with my own installation and there is a notable
>difference:
>
>b.a.o:
>
>sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl
>https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret
>2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
>
>my Jenkins:
>sun.java.command com.sun.javaws.Main
>C:\Users\amsellem\AppData\Local\Temp\javaws2
>
>
>According to Jenkins doc, the b.a.o launch method is used for headless
>slaves, so that would explain why it does not get a window.
>
>I am trying to do the same now and let you know.
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 23:22
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>the slave has a window?
>
>On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>Here is Gavin's response a minute ago:
>>
>>=================
>>> Gavin,
>>>
>>> Can you please copy-paste this line into a command prompt and tell us
>>>what the result is:
>>>
>>> "%PIXELBENDER_HOME%\pbutil.exe"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbk"
>>> "F:\hudson\hudson-slave\workspace\flex-
>>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>>> pbj"
>>>
>>> (mind the wrap)
>>>
>>> Thanks!
>>
>>Result is a slight pause, then the prompt returns. No error, no output.
>>
>>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>>variable.)
>>
>>Let me know what's next to check , thanks
>>
>>Gav...
>>=================
>>
>>
>>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
>><bi...@gmail.com>wrote:
>>
>>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> Don't know, but if you can prove that the slave can be configured in
>>>>a way that it won't run, then we have a more specific question to
>>>>ask infra.
>>>>
>>>> -Alex
>>>>
>>>
>>> Wow, this is like CSI ;-)
>>>
>>> Here is what we know. Gavin recently installed a new slave
>>>(windows2) I am guessing that something was probably changed in the
>>>way slaves are run.
>>>
>>> BTW, here is another piece of information. This is the system info
>>> for
>>> windows1:
>>>
>>> https://builds.apache.org/computer/windows1/systemInfo
>>>
>>> Anything looks out of the ordinary?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>
>>>>
>>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>>> >- Java web start (JNLP)
>>>> >- command line from master
>>>> >- via SSH on Unix machines
>>>> >- as a Windows Service.
>>>> >
>>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>>window.
>>>> >I am going to try "as a Windows Service".
>>>> >
>>>> >Is there a way to know how the slave is launched on b.a.o?
>>>> >
>>>> >Maurice
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>>> >[Builds/Jenkins] Help and advise needed
>>>> >
>>>> >InterestingŠ Is there a way to configure a slave so it doesn't get
>>>> >a window? Maybe Infra changed some default on builds.a.o.
>>>> >
>>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Now run the same build on a slave node (that gets a windows
>>>> >>"jenkins slave agent", that is visible on the desktop ):
>>>> >>
>>>> >>Remote build on windowsSlave1 in workspace
>>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>>pixelbender-compile
>>>> >>&& exit %%ERRORLEVEL%%"'
>>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>>> >>-Djava.net.preferIPv4Stack=true
>>>> >>Buildfile:
>>>>
>>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build
>>>>>>.
>>>>>>x
>>>> >>ml
>>>> >>
>>>> >>pixelbender-compile:
>>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>>> >> [exec] Vendor string: NVIDIA Corporation
>>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>>> >> [exec] Version string: 3.0.0
>>>> >> [exec]
>>>> >> [exec] OpenGL version as determined by Extensionator...
>>>> >> [exec] OpenGL Version 3.0
>>>> >> [exec] Has NPOT support: TRUE
>>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>>> >> [exec] Completed shader test!
>>>> >> [exec] Return code: 7
>>>> >> [exec] Result: 7
>>>> >>BUILD SUCCESSFUL
>>>> >>Total time: 8 seconds
>>>> >>Finished: SUCCESS
>>>> >>
>>>> >>Well, that's a difference.
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>Nice. Thanks for sticking with it.
>>>> >>
>>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>>> >>>64bit
>>>>(
>>>> >>>Tomcat is running as a Windows Service).
>>>> >>>
>>>> >>>- Created a simple job, on the "master" node, than starts
>>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>>"pixelbender-compile"
>>>> >>>target
>>>> >>>- Jenkins output of the job:
>>>> >>>
>>>> >>>pixelbender-compile:
>>>> >>> [exec] AIF Internal exception
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>>> >>> [exec] Return code: 1
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>> [exec] ERROR: AIF Internal exception
>>>> >>> [exec] Result: 1
>>>> >>>
>>>> >>>So I am getting the same error.
>>>> >>>
>>>> >>>Om says "master" does not get a window, so this result seems to
>>>> >>>be normal.
>>>> >>>
>>>> >>>I am trying now to create a slave node and run the job on it.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>> >>>
>>>> >>>It was from the command line (cmd ant ), so gets a window.
>>>> >>>
>>>> >>>I am trying now from Jenkins service, but needs to install it
>>>>first...
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>> >>>needed
>>>> >>>
>>>> >>>Maurice,
>>>> >>>
>>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>> >>>I think there is a difference. On Jenkins, the main executor
>>>>(master)
>>>> >>>does not get a window. Only slave executors are configured to
>>>> >>>get a window.
>>>> >>>Whereas Cygwin does not have such restrictions.
>>>> >>>
>>>> >>>Thanks,
>>>> >>>Om
>>>> >>>
>>>> >>>
>>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>>wrote:
>>>> >>>
>>>> >>>> I have no idea what to do with that information. But thanks
>>>> >>>>for trying.
>>>> >>>>
>>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> >>>> <ma...@systar.com>
>>>> >>>> wrote:
>>>> >>>>
>>>> >>>> >So this is the output from the b.a.o box:
>>>> >>>> >
>>>> >>>> >pixelbender-compile:
>>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> >>>> > [exec] AIF Internal exception
>>>> >>>> > [exec] Return code: 1
>>>> >>>> > [exec] Result: 1
>>>> >>>> >
>>>> >>>> >To be compared to the output on my PC:
>>>> >>>> >pixelbender-compile
>>>> >>>> >exec
>>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >>>> >Vendor string: NVIDIA Corporation
>>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >Version string: 3.0.0
>>>> >>>> >
>>>> >>>> >OpenGL version as determined by Extensionator...
>>>> >>>> >OpenGL Version 3.0
>>>> >>>> >Has NPOT support: TRUE
>>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>>> >>>> >shader test!
>>>> >>>> >Return code: 7
>>>> >>>> >Result: 7
>>>> >>>> >Exec
>>>> >>>> >
>>>> >>>> >That does not tell much, except that there seems to be an
>>>> >>>> >issue with accessing the GPU.
>>>> >>>> >
>>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>>> >>>> >more tests
>>>> >>>>?
>>>> >>>> >
>>>> >>>> >Maurice
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>>dev@flex.apache.orgObjet :
>>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >>>> >
>>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >>>> >
>>>> >>>> >Can you try on your side, please ?
>>>> >>>> >
>>>> >>>> >-----Message d'origine-----
>>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >décembre
>>>> >>>> >2013
>>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>> >Help
>>>>and
>>>> >>>> >advise needed
>>>> >>>> >
>>>> >>>> >Won't that break Mac builds?
>>>> >>>> >
>>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> >>>> ><ma...@systar.com>
>>>> >>>> >wrote:
>>>> >>>> >
>>>> >>>> >>Alex, it's one line to change in the build.xml
>>>> >>>> >>
>>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>>> >>
>>>> >>>> >>I will give it a try and we will know in 15 min.
>>>> >>>> >>
>>>> >>>> >>I am sure the result will be interesting.
>>>> >>>> >>
>>>> >>>> >>Anyway, it can't hurt ;-)
>>>> >>>> >>
>>>> >>>> >>Maurice
>>>> >>>> >>
>>>> >>>> >>-----Message d'origine-----
>>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>décembre
>>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>
>>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>> >>>>request.
>>>> >>>> >>
>>>> >>>> >>BTW, thanks for finding out about the tool.
>>>> >>>> >>
>>>> >>>> >>-Alex
>>>> >>>> >>
>>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >>>> >><ma...@systar.com>
>>>> >>>> >>wrote:
>>>> >>>> >>
>>>> >>>> >>>Sure, if you can ask him.
>>>> >>>> >>>
>>>> >>>> >>>Maurice
>>>> >>>> >>>
>>>> >>>> >>>-----Message d'origine-----
>>>> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>> >>>décembre
>>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>
>>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>> >>>
>>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>>> >>><ma...@systar.com>
>>>> >>>> >>>wrote:
>>>> >>>> >>>
>>>> >>>> >>>>There is a utility in pixel bender toolkit directory called
>>>> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of
>>>>OpenGL:
>>>> >>>> >>>>
>>>> >>>> >>>>Console output on my laptop is below:
>>>> >>>> >>>>
>>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>>Bender
>>>> >>>> >>>>Toolkit
>>>> >>>> >>>>2>sniffer_gpu.exe
>>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>> >>>>Version string: 3.0.0
>>>> >>>> >>>>
>>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>> >>>>OpenGL Version 3.0
>>>> >>>> >>>>Has NPOT support: TRUE
>>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>>shader
>>>> >>>>test!
>>>> >>>> >>>>Return code: 7
>>>> >>>> >>>>
>>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>>utility
>>>> >>>> >>>>and show the output on the b.a.o vm.
>>>> >>>> >>>>
>>>> >>>> >>>>WDYT ?
>>>> >>>> >>>>
>>>> >>>> >>>>Maurice
>>>> >>>> >>>>
>>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins]
>>>> >>>> >>>>Help and advise needed
>>>> >>>> >>>>
>>>> >>>> >>>>I don't think we actually know the cause of the problem. I
>>>> >>>> >>>>am going to continue to spend cycles to try to find out
>>>>though.
>>>> >>>> >>>>
>>>> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm
>>>>not
>>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>> >>>>
>>>> >>>> >>>>-Alex
>>>> >>>> >>>>
>>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>> >>>><ma...@systar.com>
>>>> >>>> >>>>wrote:
>>>> >>>> >>>>
>>>> >>>> >>>>>I understand that.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>> >>>>>bender compiler required some sort of hardware
>>>> >>>> >>>>>configuration (OpenGL,
>>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>>Jenkins
>>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>>> >>>> >>>>>even access the VM ourselves.
>>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>> >>>>>
>>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>>> >>>> >>>>>and
>>>>use
>>>> >>>> >>>>>our own Jenkins slave node VM.
>>>> >>>> >>>>>
>>>> >>>> >>>>>That, of course, is much preferable...
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice
>>>> >>>> >>>>>
>>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>
>>>> >>>> >>>>>Maurice,
>>>> >>>> >>>>>
>>>> >>>> >>>>>Your help is very much appreciated!
>>>> >>>> >>>>>
>>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>>> >>>> >>>>>artefacts
>>>>themselves in
>>>> >>>>the repo.
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>EdB
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>> >>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>>in the
>>>> >>>>repo.
>>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>>> >>>> >>>>>>the repo, so I won't insist.
>>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>>> >>>> >>>>>>or
>>>>ASF
>>>> >>>>rules ?
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>>> >>>> >>>>>> email thread
>>>>was
>>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Regards,
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Maurice
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>>mardi
>>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>>> >>>> >>>>>>In
>>>>order
>>>> >>>> >>>>>>to prevent further deterioration of the build process, we
>>>>need
>>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> EdB
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>>> >>>> >>>>>> set
>>>>to
>>>> >>>>FR...
>>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or
>>>> >>>> >>>>>> if my keyboard was broken ;-)
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>>> >>>> >>>>>>>> and
>>>> >>>>complain.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> I don't understand.
>>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>>nightly?
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> [From the other emai]
>>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>>The
>>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>>> >>>> >>>>>>>>pbj
>>>> >>>>files.
>>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>>> >>>>temporarily.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>> >>>>>>>>Yes but ...
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>>> >>>> >>>>>>>not sure that I have understood what you said.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>>parameter
>>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled
>>>>pbj's.
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>> Maurice
>>>> >>>> >>>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> --
>>>> >>>> >>>>>> Ix Multimedia Software
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> Jan Luykenstraat 27
>>>> >>>> >>>>>> 3521 VB Utrecht
>>>> >>>> >>>>>>
>>>> >>>> >>>>>> T. 06-51952295
>>>> >>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>
>>>> >>>> >>>>>--
>>>> >>>> >>>>>Ix Multimedia Software
>>>> >>>> >>>>>
>>>> >>>> >>>>>Jan Luykenstraat 27
>>>> >>>> >>>>>3521 VB Utrecht
>>>> >>>> >>>>>
>>>> >>>> >>>>>T. 06-51952295
>>>> >>>> >>>>>I. www.ixsoftware.nl
>>>> >>>> >>>>
>>>> >>>> >>>
>>>> >>>> >>
>>>> >>>> >
>>>> >>>>
>>>> >>>>
>>>> >>
>>>> >
>>>>
>>>>
>>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
When you connect to https://builds.apache.org/computer/windows1/
It says just below the title "Connected through JNLP"
I have compared with my own installation and there is a notable difference:
b.a.o:
sun.java.command F:\hudson\hudson-slave\slave.jar -jnlpUrl https://builds.apache.org/computer/windows1/slave-agent.jnlp -secret 2ac5728b916b5d3992b88fa28b8ed9ae243a057fde8e08bd16a32cd327264fb1
my Jenkins:
sun.java.command com.sun.javaws.Main C:\Users\amsellem\AppData\Local\Temp\javaws2
According to Jenkins doc, the b.a.o launch method is used for headless slaves, so that would explain why it does not get a window.
I am trying to do the same now and let you know.
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 23:22
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Saw it. Have we asked him if the Flex build is running in a slave and the slave has a window?
On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>Here is Gavin's response a minute ago:
>
>=================
>> Gavin,
>>
>> Can you please copy-paste this line into a command prompt and tell us
>>what the result is:
>>
>> "%PIXELBENDER_HOME%\pbutil.exe"
>> "F:\hudson\hudson-slave\workspace\flex-
>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>> pbk"
>> "F:\hudson\hudson-slave\workspace\flex-
>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>> pbj"
>>
>> (mind the wrap)
>>
>> Thanks!
>
>Result is a slight pause, then the prompt returns. No error, no output.
>
>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>variable.)
>
>Let me know what's next to check , thanks
>
>Gav...
>=================
>
>
>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
><bi...@gmail.com>wrote:
>
>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> Don't know, but if you can prove that the slave can be configured in
>>>a way that it won't run, then we have a more specific question to
>>>ask infra.
>>>
>>> -Alex
>>>
>>
>> Wow, this is like CSI ;-)
>>
>> Here is what we know. Gavin recently installed a new slave
>>(windows2) I am guessing that something was probably changed in the
>>way slaves are run.
>>
>> BTW, here is another piece of information. This is the system info
>> for
>> windows1:
>>
>> https://builds.apache.org/computer/windows1/systemInfo
>>
>> Anything looks out of the ordinary?
>>
>> Thanks,
>> Om
>>
>>
>>
>>
>>>
>>> On 12/10/13 1:55 PM, "Maurice Amsellem"
>>> <ma...@systar.com>
>>> wrote:
>>>
>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>> >- Java web start (JNLP)
>>> >- command line from master
>>> >- via SSH on Unix machines
>>> >- as a Windows Service.
>>> >
>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>window.
>>> >I am going to try "as a Windows Service".
>>> >
>>> >Is there a way to know how the slave is launched on b.a.o?
>>> >
>>> >Maurice
>>> >-----Message d'origine-----
>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >décembre 2013 22:46 À : dev@flex.apache.org Objet : Re:
>>> >[Builds/Jenkins] Help and advise needed
>>> >
>>> >InterestingŠ Is there a way to configure a slave so it doesn't get
>>> >a window? Maybe Infra changed some default on builds.a.o.
>>> >
>>> >On 12/10/13 1:44 PM, "Maurice Amsellem"
>>> ><ma...@systar.com>
>>> >wrote:
>>> >
>>> >>Now run the same build on a slave node (that gets a windows
>>> >>"jenkins slave agent", that is visible on the desktop ):
>>> >>
>>> >>Remote build on windowsSlave1 in workspace
>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>pixelbender-compile
>>> >>&& exit %%ERRORLEVEL%%"'
>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>> >>-Djava.net.preferIPv4Stack=true
>>> >>Buildfile:
>>>
>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.
>>>>>x
>>> >>ml
>>> >>
>>> >>pixelbender-compile:
>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>> >> [exec] Vendor string: NVIDIA Corporation
>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>> >> [exec] Version string: 3.0.0
>>> >> [exec]
>>> >> [exec] OpenGL version as determined by Extensionator...
>>> >> [exec] OpenGL Version 3.0
>>> >> [exec] Has NPOT support: TRUE
>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>> >> [exec] Completed shader test!
>>> >> [exec] Return code: 7
>>> >> [exec] Result: 7
>>> >>BUILD SUCCESSFUL
>>> >>Total time: 8 seconds
>>> >>Finished: SUCCESS
>>> >>
>>> >>Well, that's a difference.
>>> >>
>>> >>Maurice
>>> >>
>>> >>-----Message d'origine-----
>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>décembre
>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>Help and advise needed
>>> >>
>>> >>Nice. Thanks for sticking with it.
>>> >>
>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem"
>>> >><ma...@systar.com>
>>> >>wrote:
>>> >>
>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6
>>> >>>64bit
>>>(
>>> >>>Tomcat is running as a Windows Service).
>>> >>>
>>> >>>- Created a simple job, on the "master" node, than starts
>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>"pixelbender-compile"
>>> >>>target
>>> >>>- Jenkins output of the job:
>>> >>>
>>> >>>pixelbender-compile:
>>> >>> [exec] AIF Internal exception
>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>> >>> [exec] Return code: 1
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>>
>>> >>>So I am getting the same error.
>>> >>>
>>> >>>Om says "master" does not get a window, so this result seems to
>>> >>>be normal.
>>> >>>
>>> >>>I am trying now to create a slave node and run the job on it.
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >>>Envoyé : mardi 10 décembre 2013 22:07 À : dev@flex.apache.org
>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>> >>>
>>> >>>It was from the command line (cmd ant ), so gets a window.
>>> >>>
>>> >>>I am trying now from Jenkins service, but needs to install it
>>>first...
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>> >>>needed
>>> >>>
>>> >>>Maurice,
>>> >>>
>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>> >>>I think there is a difference. On Jenkins, the main executor
>>>(master)
>>> >>>does not get a window. Only slave executors are configured to
>>> >>>get a window.
>>> >>>Whereas Cygwin does not have such restrictions.
>>> >>>
>>> >>>Thanks,
>>> >>>Om
>>> >>>
>>> >>>
>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>wrote:
>>> >>>
>>> >>>> I have no idea what to do with that information. But thanks
>>> >>>>for trying.
>>> >>>>
>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>> >>>> <ma...@systar.com>
>>> >>>> wrote:
>>> >>>>
>>> >>>> >So this is the output from the b.a.o box:
>>> >>>> >
>>> >>>> >pixelbender-compile:
>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>> >>>> > [exec] AIF Internal exception
>>> >>>> > [exec] Return code: 1
>>> >>>> > [exec] Result: 1
>>> >>>> >
>>> >>>> >To be compared to the output on my PC:
>>> >>>> >pixelbender-compile
>>> >>>> >exec
>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>> >>>> >Vendor string: NVIDIA Corporation
>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>> >>>> >Version string: 3.0.0
>>> >>>> >
>>> >>>> >OpenGL version as determined by Extensionator...
>>> >>>> >OpenGL Version 3.0
>>> >>>> >Has NPOT support: TRUE
>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed
>>> >>>> >shader test!
>>> >>>> >Return code: 7
>>> >>>> >Result: 7
>>> >>>> >Exec
>>> >>>> >
>>> >>>> >That does not tell much, except that there seems to be an
>>> >>>> >issue with accessing the GPU.
>>> >>>> >
>>> >>>> >Shall I un-commit the change now, or do you want to perform
>>> >>>> >more tests
>>> >>>>?
>>> >>>> >
>>> >>>> >Maurice
>>> >>>> >
>>> >>>> >-----Message d'origine-----
>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>dev@flex.apache.orgObjet :
>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>> >>>> >
>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>> >>>> >
>>> >>>> >Can you try on your side, please ?
>>> >>>> >
>>> >>>> >-----Message d'origine-----
>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >décembre
>>> >>>> >2013
>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>> >Help
>>>and
>>> >>>> >advise needed
>>> >>>> >
>>> >>>> >Won't that break Mac builds?
>>> >>>> >
>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>> >>>> ><ma...@systar.com>
>>> >>>> >wrote:
>>> >>>> >
>>> >>>> >>Alex, it's one line to change in the build.xml
>>> >>>> >>
>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>> >>>> >>
>>> >>>> >>I will give it a try and we will know in 15 min.
>>> >>>> >>
>>> >>>> >>I am sure the result will be interesting.
>>> >>>> >>
>>> >>>> >>Anyway, it can't hurt ;-)
>>> >>>> >>
>>> >>>> >>Maurice
>>> >>>> >>
>>> >>>> >>-----Message d'origine-----
>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >>décembre
>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>[Builds/Jenkins] Help and advise needed
>>> >>>> >>
>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>> >>>>request.
>>> >>>> >>
>>> >>>> >>BTW, thanks for finding out about the tool.
>>> >>>> >>
>>> >>>> >>-Alex
>>> >>>> >>
>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>> >>>> >><ma...@systar.com>
>>> >>>> >>wrote:
>>> >>>> >>
>>> >>>> >>>Sure, if you can ask him.
>>> >>>> >>>
>>> >>>> >>>Maurice
>>> >>>> >>>
>>> >>>> >>>-----Message d'origine-----
>>> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >>>décembre
>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>>[Builds/Jenkins] Help and advise needed
>>> >>>> >>>
>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>> >>>> >>>
>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>> >>>> >>><ma...@systar.com>
>>> >>>> >>>wrote:
>>> >>>> >>>
>>> >>>> >>>>There is a utility in pixel bender toolkit directory called
>>> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of
>>>OpenGL:
>>> >>>> >>>>
>>> >>>> >>>>Console output on my laptop is below:
>>> >>>> >>>>
>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>Bender
>>> >>>> >>>>Toolkit
>>> >>>> >>>>2>sniffer_gpu.exe
>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>> >>>> >>>>Version string: 3.0.0
>>> >>>> >>>>
>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>> >>>> >>>>OpenGL Version 3.0
>>> >>>> >>>>Has NPOT support: TRUE
>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>shader
>>> >>>>test!
>>> >>>> >>>>Return code: 7
>>> >>>> >>>>
>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>utility
>>> >>>> >>>>and show the output on the b.a.o vm.
>>> >>>> >>>>
>>> >>>> >>>>WDYT ?
>>> >>>> >>>>
>>> >>>> >>>>Maurice
>>> >>>> >>>>
>>> >>>> >>>>-----Message d'origine----- De : Alex Harui
>>> >>>> >>>>[mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>[Builds/Jenkins]
>>> >>>> >>>>Help and advise needed
>>> >>>> >>>>
>>> >>>> >>>>I don't think we actually know the cause of the problem. I
>>> >>>> >>>>am going to continue to spend cycles to try to find out though.
>>> >>>> >>>>
>>> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm
>>>not
>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>> >>>> >>>>
>>> >>>> >>>>-Alex
>>> >>>> >>>>
>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>> >>>> >>>><ma...@systar.com>
>>> >>>> >>>>wrote:
>>> >>>> >>>>
>>> >>>> >>>>>I understand that.
>>> >>>> >>>>>
>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>> >>>> >>>>>bender compiler required some sort of hardware
>>> >>>> >>>>>configuration (OpenGL,
>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>Jenkins
>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or
>>> >>>> >>>>>even access the VM ourselves.
>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>> >>>> >>>>>
>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up
>>> >>>> >>>>>and
>>>use
>>> >>>> >>>>>our own Jenkins slave node VM.
>>> >>>> >>>>>
>>> >>>> >>>>>That, of course, is much preferable...
>>> >>>> >>>>>
>>> >>>> >>>>>Maurice
>>> >>>> >>>>>
>>> >>>> >>>>>-----Message d'origine----- De : Erik de Bruin
>>> >>>> >>>>>[mailto:erik@ixsoftware.nl] Envoyé : mardi
>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>> >>>> >>>>>
>>> >>>> >>>>>Maurice,
>>> >>>> >>>>>
>>> >>>> >>>>>Your help is very much appreciated!
>>> >>>> >>>>>
>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of
>>> >>>> >>>>>the law, more of the rules. An Apache release is supposed
>>> >>>> >>>>>to be 'source only', and we if we can produce needed
>>> >>>> >>>>>binaries from source, we keep only the source, not the
>>> >>>> >>>>>artefacts
>>>themselves in
>>> >>>>the repo.
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>EdB
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>> >>>> >>>>><ma...@systar.com> wrote:
>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries
>>> >>>> >>>>>>>in the
>>> >>>>repo.
>>> >>>> >>>>>> I understand it's not a good idea to have binaries in
>>> >>>> >>>>>>the repo, so I won't insist.
>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe,
>>> >>>> >>>>>>or
>>>ASF
>>> >>>>rules ?
>>> >>>> >>>>>>
>>> >>>> >>>>>> On a side note, I was just trying to help, with my
>>> >>>> >>>>>> limited understanding and knowledge, and because the
>>> >>>> >>>>>> email thread
>>>was
>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>> >>>> >>>>>>
>>> >>>> >>>>>> Regards,
>>> >>>> >>>>>>
>>> >>>> >>>>>> Maurice
>>> >>>> >>>>>>
>>> >>>> >>>>>> -----Message d'origine----- De : Erik de Bruin
>>> >>>> >>>>>> [mailto:erik@ixsoftware.nl] Envoyé :
>>>mardi
>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>> >>>> >>>>>>
>>> >>>> >>>>>> In addition to the various "legal" issues with binaries
>>> >>>> >>>>>>in the repo, we'd be masking the cause of this failure.
>>> >>>> >>>>>>In
>>>order
>>> >>>> >>>>>>to prevent further deterioration of the build process, we
>>>need
>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>> >>>> >>>>>>
>>> >>>> >>>>>> EdB
>>> >>>> >>>>>>
>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM
>>> >>>> >>>>>> set
>>>to
>>> >>>>FR...
>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or
>>> >>>> >>>>>> if my keyboard was broken ;-)
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>> >>>> >>>>>><ma...@systar.com> wrote:
>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly
>>> >>>> >>>>>>>> and
>>> >>>>complain.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> I don't understand.
>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>nightly?
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> [From the other emai]
>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>The
>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the
>>> >>>> >>>>>>>>pbj
>>> >>>>files.
>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>> >>>>temporarily.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>> >>>> >>>>>>>>Yes but ...
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am
>>> >>>> >>>>>>>not sure that I have understood what you said.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>parameter
>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> Maurice
>>> >>>> >>>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>> --
>>> >>>> >>>>>> Ix Multimedia Software
>>> >>>> >>>>>>
>>> >>>> >>>>>> Jan Luykenstraat 27
>>> >>>> >>>>>> 3521 VB Utrecht
>>> >>>> >>>>>>
>>> >>>> >>>>>> T. 06-51952295
>>> >>>> >>>>>> I. www.ixsoftware.nl
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>--
>>> >>>> >>>>>Ix Multimedia Software
>>> >>>> >>>>>
>>> >>>> >>>>>Jan Luykenstraat 27
>>> >>>> >>>>>3521 VB Utrecht
>>> >>>> >>>>>
>>> >>>> >>>>>T. 06-51952295
>>> >>>> >>>>>I. www.ixsoftware.nl
>>> >>>> >>>>
>>> >>>> >>>
>>> >>>> >>
>>> >>>> >
>>> >>>>
>>> >>>>
>>> >>
>>> >
>>>
>>>
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 2:21 PM, Alex Harui <ah...@adobe.com> wrote:
> Saw it. Have we asked him if the Flex build is running in a slave and the
> slave has a window?
>
>
Windows1 is a slave. At least it was. I will check.
> On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >Here is Gavin's response a minute ago:
> >
> >=================
> >> Gavin,
> >>
> >> Can you please copy-paste this line into a command prompt and tell us
> >>what
> >> the result is:
> >>
> >> "%PIXELBENDER_HOME%\pbutil.exe"
> >> "F:\hudson\hudson-slave\workspace\flex-
> >> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> >> pbk"
> >> "F:\hudson\hudson-slave\workspace\flex-
> >> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> >> pbj"
> >>
> >> (mind the wrap)
> >>
> >> Thanks!
> >
> >Result is a slight pause, then the prompt returns. No error, no output.
> >
> >(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
> >variable.)
> >
> >Let me know what's next to check , thanks
> >
> >Gav...
> >=================
> >
> >
> >On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
> ><bi...@gmail.com>wrote:
> >
> >> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
> >>
> >>> Don't know, but if you can prove that the slave can be configured in a
> >>>way
> >>> that it won't run, then we have a more specific question to ask infra.
> >>>
> >>> -Alex
> >>>
> >>
> >> Wow, this is like CSI ;-)
> >>
> >> Here is what we know. Gavin recently installed a new slave (windows2)
> >>I
> >> am guessing that something was probably changed in the way slaves are
> >>run.
> >>
> >> BTW, here is another piece of information. This is the system info for
> >> windows1:
> >>
> >> https://builds.apache.org/computer/windows1/systemInfo
> >>
> >> Anything looks out of the ordinary?
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>
> >>
> >>>
> >>> On 12/10/13 1:55 PM, "Maurice Amsellem" <ma...@systar.com>
> >>> wrote:
> >>>
> >>> >According to jenkins gui, there are 4 ways of starting the slave :
> >>> >- Java web start (JNLP)
> >>> >- command line from master
> >>> >- via SSH on Unix machines
> >>> >- as a Windows Service.
> >>> >
> >>> >I am using JNLP, but maybe the other launch methods don't get a
> >>>window.
> >>> >I am going to try "as a Windows Service".
> >>> >
> >>> >Is there a way to know how the slave is launched on b.a.o?
> >>> >
> >>> >Maurice
> >>> >-----Message d'origine-----
> >>> >De : Alex Harui [mailto:aharui@adobe.com]
> >>> >Envoyé : mardi 10 décembre 2013 22:46
> >>> >À : dev@flex.apache.org
> >>> >Objet : Re: [Builds/Jenkins] Help and advise needed
> >>> >
> >>> >InterestingŠ Is there a way to configure a slave so it doesn't get a
> >>> >window? Maybe Infra changed some default on builds.a.o.
> >>> >
> >>> >On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
> >>> >wrote:
> >>> >
> >>> >>Now run the same build on a slave node (that gets a windows "jenkins
> >>> >>slave agent", that is visible on the desktop ):
> >>> >>
> >>> >>Remote build on windowsSlave1 in workspace
> >>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
> >>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
> >>>pixelbender-compile
> >>> >>&& exit %%ERRORLEVEL%%"'
> >>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
> >>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
> >>> >>-Djava.net.preferIPv4Stack=true
> >>> >>Buildfile:
> >>>
> >>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.
> >>>>>x
> >>> >>ml
> >>> >>
> >>> >>pixelbender-compile:
> >>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
> >>> >> [exec] Vendor string: NVIDIA Corporation
> >>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
> >>> >> [exec] Version string: 3.0.0
> >>> >> [exec]
> >>> >> [exec] OpenGL version as determined by Extensionator...
> >>> >> [exec] OpenGL Version 3.0
> >>> >> [exec] Has NPOT support: TRUE
> >>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
> >>> >> [exec] Completed shader test!
> >>> >> [exec] Return code: 7
> >>> >> [exec] Result: 7
> >>> >>BUILD SUCCESSFUL
> >>> >>Total time: 8 seconds
> >>> >>Finished: SUCCESS
> >>> >>
> >>> >>Well, that's a difference.
> >>> >>
> >>> >>Maurice
> >>> >>
> >>> >>-----Message d'origine-----
> >>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>> >>and advise needed
> >>> >>
> >>> >>Nice. Thanks for sticking with it.
> >>> >>
> >>> >>On 12/10/13 1:21 PM, "Maurice Amsellem" <maurice.amsellem@systar.com
> >
> >>> >>wrote:
> >>> >>
> >>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit
> >>>(
> >>> >>>Tomcat is running as a Windows Service).
> >>> >>>
> >>> >>>- Created a simple job, on the "master" node, than starts
> >>> >>>flex-sdk\frameworks\projects\framework\build.xml
> >>>"pixelbender-compile"
> >>> >>>target
> >>> >>>- Jenkins output of the job:
> >>> >>>
> >>> >>>pixelbender-compile:
> >>> >>> [exec] AIF Internal exception
> >>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
> >>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
> >>> >>> [exec] Return code: 1
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>> [exec] ERROR: AIF Internal exception
> >>> >>> [exec] Result: 1
> >>> >>>
> >>> >>>So I am getting the same error.
> >>> >>>
> >>> >>>Om says "master" does not get a window, so this result seems to be
> >>> >>>normal.
> >>> >>>
> >>> >>>I am trying now to create a slave node and run the job on it.
> >>> >>>
> >>> >>>Maurice
> >>> >>>
> >>> >>>-----Message d'origine-----
> >>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>> >>>Envoyé : mardi 10 décembre 2013 22:07
> >>> >>>À : dev@flex.apache.org
> >>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
> >>> >>>
> >>> >>>It was from the command line (cmd ant ), so gets a window.
> >>> >>>
> >>> >>>I am trying now from Jenkins service, but needs to install it
> >>>first...
> >>> >>>
> >>> >>>Maurice
> >>> >>>
> >>> >>>-----Message d'origine-----
> >>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
> >>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
> >>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
> >>> >>>needed
> >>> >>>
> >>> >>>Maurice,
> >>> >>>
> >>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
> >>> >>>I think there is a difference. On Jenkins, the main executor
> >>>(master)
> >>> >>>does not get a window. Only slave executors are configured to get a
> >>> >>>window.
> >>> >>>Whereas Cygwin does not have such restrictions.
> >>> >>>
> >>> >>>Thanks,
> >>> >>>Om
> >>> >>>
> >>> >>>
> >>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
> >>>wrote:
> >>> >>>
> >>> >>>> I have no idea what to do with that information. But thanks for
> >>> >>>>trying.
> >>> >>>>
> >>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
> >>> >>>> <ma...@systar.com>
> >>> >>>> wrote:
> >>> >>>>
> >>> >>>> >So this is the output from the b.a.o box:
> >>> >>>> >
> >>> >>>> >pixelbender-compile:
> >>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> >>> >>>> > [exec] AIF Internal exception
> >>> >>>> > [exec] Return code: 1
> >>> >>>> > [exec] Result: 1
> >>> >>>> >
> >>> >>>> >To be compared to the output on my PC:
> >>> >>>> >pixelbender-compile
> >>> >>>> >exec
> >>> >>>> >Device: 00633CEC has video RAM(MB): 512
> >>> >>>> >Vendor string: NVIDIA Corporation
> >>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
> >>> >>>> >Version string: 3.0.0
> >>> >>>> >
> >>> >>>> >OpenGL version as determined by Extensionator...
> >>> >>>> >OpenGL Version 3.0
> >>> >>>> >Has NPOT support: TRUE
> >>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
> >>> >>>> >test!
> >>> >>>> >Return code: 7
> >>> >>>> >Result: 7
> >>> >>>> >Exec
> >>> >>>> >
> >>> >>>> >That does not tell much, except that there seems to be an issue
> >>> >>>> >with accessing the GPU.
> >>> >>>> >
> >>> >>>> >Shall I un-commit the change now, or do you want to perform more
> >>> >>>> >tests
> >>> >>>>?
> >>> >>>> >
> >>> >>>> >Maurice
> >>> >>>> >
> >>> >>>> >-----Message d'origine-----
> >>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
> >>>dev@flex.apache.orgObjet :
> >>> >>>> >RE: [Builds/Jenkins] Help and advise needed
> >>> >>>> >
> >>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
> >>> >>>> >
> >>> >>>> >Can you try on your side, please ?
> >>> >>>> >
> >>> >>>> >-----Message d'origine-----
> >>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>> >>>> >décembre
> >>> >>>> >2013
> >>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>>and
> >>> >>>> >advise needed
> >>> >>>> >
> >>> >>>> >Won't that break Mac builds?
> >>> >>>> >
> >>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
> >>> >>>> ><ma...@systar.com>
> >>> >>>> >wrote:
> >>> >>>> >
> >>> >>>> >>Alex, it's one line to change in the build.xml
> >>> >>>> >>
> >>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>> >>>> >>
> >>> >>>> >>I will give it a try and we will know in 15 min.
> >>> >>>> >>
> >>> >>>> >>I am sure the result will be interesting.
> >>> >>>> >>
> >>> >>>> >>Anyway, it can't hurt ;-)
> >>> >>>> >>
> >>> >>>> >>Maurice
> >>> >>>> >>
> >>> >>>> >>-----Message d'origine-----
> >>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>> >>>> >>décembre
> >>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>> >>>> >>Help and advise needed
> >>> >>>> >>
> >>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
> >>> >>>>request.
> >>> >>>> >>
> >>> >>>> >>BTW, thanks for finding out about the tool.
> >>> >>>> >>
> >>> >>>> >>-Alex
> >>> >>>> >>
> >>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
> >>> >>>> >><ma...@systar.com>
> >>> >>>> >>wrote:
> >>> >>>> >>
> >>> >>>> >>>Sure, if you can ask him.
> >>> >>>> >>>
> >>> >>>> >>>Maurice
> >>> >>>> >>>
> >>> >>>> >>>-----Message d'origine-----
> >>> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>> >>>> >>>décembre
> >>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins]
> >>> >>>> >>>Help and advise needed
> >>> >>>> >>>
> >>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
> >>> >>>> >>>
> >>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
> >>> >>>> >>><ma...@systar.com>
> >>> >>>> >>>wrote:
> >>> >>>> >>>
> >>> >>>> >>>>There is a utility in pixel bender toolkit directory called
> >>> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of
> >>>OpenGL:
> >>> >>>> >>>>
> >>> >>>> >>>>Console output on my laptop is below:
> >>> >>>> >>>>
> >>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
> >>>Bender
> >>> >>>> >>>>Toolkit
> >>> >>>> >>>>2>sniffer_gpu.exe
> >>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>> >>>> >>>>Vendor string: NVIDIA Corporation
> >>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>> >>>> >>>>Version string: 3.0.0
> >>> >>>> >>>>
> >>> >>>> >>>>OpenGL version as determined by Extensionator...
> >>> >>>> >>>>OpenGL Version 3.0
> >>> >>>> >>>>Has NPOT support: TRUE
> >>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
> >>>shader
> >>> >>>>test!
> >>> >>>> >>>>Return code: 7
> >>> >>>> >>>>
> >>> >>>> >>>>Maybe we could temporarily modify the build to run this
> >>>utility
> >>> >>>> >>>>and show the output on the b.a.o vm.
> >>> >>>> >>>>
> >>> >>>> >>>>WDYT ?
> >>> >>>> >>>>
> >>> >>>> >>>>Maurice
> >>> >>>> >>>>
> >>> >>>> >>>>-----Message d'origine-----
> >>> >>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>> >>>> >>>>décembre
> >>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
> >>>[Builds/Jenkins]
> >>> >>>> >>>>Help and advise needed
> >>> >>>> >>>>
> >>> >>>> >>>>I don't think we actually know the cause of the problem. I am
> >>> >>>> >>>>going to continue to spend cycles to try to find out though.
> >>> >>>> >>>>
> >>> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm
> >>>not
> >>> >>>> >>>>sure if it will cost Om money to run a builds server.
> >>> >>>> >>>>
> >>> >>>> >>>>-Alex
> >>> >>>> >>>>
> >>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
> >>> >>>> >>>><ma...@systar.com>
> >>> >>>> >>>>wrote:
> >>> >>>> >>>>
> >>> >>>> >>>>>I understand that.
> >>> >>>> >>>>>
> >>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
> >>> >>>> >>>>>bender compiler required some sort of hardware configuration
> >>> >>>> >>>>>(OpenGL,
> >>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
> >>>Jenkins
> >>> >>>> >>>>>slave node, so that's why the build was failing, and the
> >>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
> >>> >>>> >>>>>access the VM ourselves.
> >>> >>>> >>>>>So that's why I was proposing a "software only" solution.
> >>> >>>> >>>>>
> >>> >>>> >>>>>Now, it seems from what Om is saying that we can set up and
> >>>use
> >>> >>>> >>>>>our own Jenkins slave node VM.
> >>> >>>> >>>>>
> >>> >>>> >>>>>That, of course, is much preferable...
> >>> >>>> >>>>>
> >>> >>>> >>>>>Maurice
> >>> >>>> >>>>>
> >>> >>>> >>>>>-----Message d'origine-----
> >>> >>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé :
> mardi
> >>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
> >>> >>>> >>>>>
> >>> >>>> >>>>>Maurice,
> >>> >>>> >>>>>
> >>> >>>> >>>>>Your help is very much appreciated!
> >>> >>>> >>>>>
> >>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of the
> >>> >>>> >>>>>law, more of the rules. An Apache release is supposed to be
> >>> >>>> >>>>>'source only', and we if we can produce needed binaries from
> >>> >>>> >>>>>source, we keep only the source, not the artefacts
> >>>themselves in
> >>> >>>>the repo.
> >>> >>>> >>>>>
> >>> >>>> >>>>>
> >>> >>>> >>>>>EdB
> >>> >>>> >>>>>
> >>> >>>> >>>>>
> >>> >>>> >>>>>
> >>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>> >>>> >>>>><ma...@systar.com> wrote:
> >>> >>>> >>>>>>>In addition to the various "legal" issues with binaries in
> >>> >>>> >>>>>>>the
> >>> >>>>repo.
> >>> >>>> >>>>>> I understand it's not a good idea to have binaries in the
> >>> >>>> >>>>>>repo, so I won't insist.
> >>> >>>> >>>>>> But please can you explain what are the legal issues of
> >>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe, or
> >>>ASF
> >>> >>>>rules ?
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> On a side note, I was just trying to help, with my limited
> >>> >>>> >>>>>> understanding and knowledge, and because the email thread
> >>>was
> >>> >>>> >>>>>> titled "help and advise needed" ;-)
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> Regards,
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> Maurice
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> -----Message d'origine-----
> >>> >>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé :
> >>>mardi
> >>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> In addition to the various "legal" issues with binaries in
> >>> >>>> >>>>>>the repo, we'd be masking the cause of this failure. In
> >>>order
> >>> >>>> >>>>>>to prevent further deterioration of the build process, we
> >>>need
> >>> >>>> >>>>>>to figure out what went wrong and fix it.
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> EdB
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set
> >>>to
> >>> >>>>FR...
> >>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
> >>> >>>> >>>>>> my keyboard was broken ;-)
> >>> >>>> >>>>>>
> >>> >>>> >>>>>>
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>> >>>> >>>>>><ma...@systar.com> wrote:
> >>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
> >>> >>>>complain.
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>> I don't understand.
> >>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
> >>>nightly?
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>> [From the other emai]
> >>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
> >>>The
> >>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
> >>> >>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
> >>> >>>>files.
> >>> >>>> >>>>>>>>But we could borrow them from a prior release package
> >>> >>>>temporarily.
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>>>So we could make the compilation conditional on a env
> >>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
> >>> >>>> >>>>>>>>Yes but ...
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
> >>> >>>> >>>>>>>sure that I have understood what you said.
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
> >>>parameter
> >>> >>>> >>>>>>>to conditionally compile the pbj ?
> >>> >>>> >>>>>>> - This parameter would be set by default to do the
> >>> >>>> >>>>>>>compilation (so that folks can recompile)
> >>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>> Maurice
> >>> >>>> >>>>>>>
> >>> >>>> >>>>>>
> >>> >>>> >>>>>>
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> --
> >>> >>>> >>>>>> Ix Multimedia Software
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> Jan Luykenstraat 27
> >>> >>>> >>>>>> 3521 VB Utrecht
> >>> >>>> >>>>>>
> >>> >>>> >>>>>> T. 06-51952295
> >>> >>>> >>>>>> I. www.ixsoftware.nl
> >>> >>>> >>>>>
> >>> >>>> >>>>>
> >>> >>>> >>>>>
> >>> >>>> >>>>>--
> >>> >>>> >>>>>Ix Multimedia Software
> >>> >>>> >>>>>
> >>> >>>> >>>>>Jan Luykenstraat 27
> >>> >>>> >>>>>3521 VB Utrecht
> >>> >>>> >>>>>
> >>> >>>> >>>>>T. 06-51952295
> >>> >>>> >>>>>I. www.ixsoftware.nl
> >>> >>>> >>>>
> >>> >>>> >>>
> >>> >>>> >>
> >>> >>>> >
> >>> >>>>
> >>> >>>>
> >>> >>
> >>> >
> >>>
> >>>
> >>
>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Saw it. Have we asked him if the Flex build is running in a slave and the
slave has a window?
On 12/10/13 2:17 PM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>Here is Gavin's response a minute ago:
>
>=================
>> Gavin,
>>
>> Can you please copy-paste this line into a command prompt and tell us
>>what
>> the result is:
>>
>> "%PIXELBENDER_HOME%\pbutil.exe"
>> "F:\hudson\hudson-slave\workspace\flex-
>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>> pbk"
>> "F:\hudson\hudson-slave\workspace\flex-
>> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
>> pbj"
>>
>> (mind the wrap)
>>
>> Thanks!
>
>Result is a slight pause, then the prompt returns. No error, no output.
>
>(PixelBender is where its meant to be, PIXELBENDER_HOME is a user
>variable.)
>
>Let me know what's next to check , thanks
>
>Gav...
>=================
>
>
>On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
><bi...@gmail.com>wrote:
>
>> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> Don't know, but if you can prove that the slave can be configured in a
>>>way
>>> that it won't run, then we have a more specific question to ask infra.
>>>
>>> -Alex
>>>
>>
>> Wow, this is like CSI ;-)
>>
>> Here is what we know. Gavin recently installed a new slave (windows2)
>>I
>> am guessing that something was probably changed in the way slaves are
>>run.
>>
>> BTW, here is another piece of information. This is the system info for
>> windows1:
>>
>> https://builds.apache.org/computer/windows1/systemInfo
>>
>> Anything looks out of the ordinary?
>>
>> Thanks,
>> Om
>>
>>
>>
>>
>>>
>>> On 12/10/13 1:55 PM, "Maurice Amsellem" <ma...@systar.com>
>>> wrote:
>>>
>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>> >- Java web start (JNLP)
>>> >- command line from master
>>> >- via SSH on Unix machines
>>> >- as a Windows Service.
>>> >
>>> >I am using JNLP, but maybe the other launch methods don't get a
>>>window.
>>> >I am going to try "as a Windows Service".
>>> >
>>> >Is there a way to know how the slave is launched on b.a.o?
>>> >
>>> >Maurice
>>> >-----Message d'origine-----
>>> >De : Alex Harui [mailto:aharui@adobe.com]
>>> >Envoyé : mardi 10 décembre 2013 22:46
>>> >À : dev@flex.apache.org
>>> >Objet : Re: [Builds/Jenkins] Help and advise needed
>>> >
>>> >InterestingŠ Is there a way to configure a slave so it doesn't get a
>>> >window? Maybe Infra changed some default on builds.a.o.
>>> >
>>> >On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
>>> >wrote:
>>> >
>>> >>Now run the same build on a slave node (that gets a windows "jenkins
>>> >>slave agent", that is visible on the desktop ):
>>> >>
>>> >>Remote build on windowsSlave1 in workspace
>>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml
>>>pixelbender-compile
>>> >>&& exit %%ERRORLEVEL%%"'
>>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>> >>-Djava.net.preferIPv4Stack=true
>>> >>Buildfile:
>>>
>>>>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.
>>>>>x
>>> >>ml
>>> >>
>>> >>pixelbender-compile:
>>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>>> >> [exec] Vendor string: NVIDIA Corporation
>>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>>> >> [exec] Version string: 3.0.0
>>> >> [exec]
>>> >> [exec] OpenGL version as determined by Extensionator...
>>> >> [exec] OpenGL Version 3.0
>>> >> [exec] Has NPOT support: TRUE
>>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>>> >> [exec] Completed shader test!
>>> >> [exec] Return code: 7
>>> >> [exec] Result: 7
>>> >>BUILD SUCCESSFUL
>>> >>Total time: 8 seconds
>>> >>Finished: SUCCESS
>>> >>
>>> >>Well, that's a difference.
>>> >>
>>> >>Maurice
>>> >>
>>> >>-----Message d'origine-----
>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>> >>and advise needed
>>> >>
>>> >>Nice. Thanks for sticking with it.
>>> >>
>>> >>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
>>> >>wrote:
>>> >>
>>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit
>>>(
>>> >>>Tomcat is running as a Windows Service).
>>> >>>
>>> >>>- Created a simple job, on the "master" node, than starts
>>> >>>flex-sdk\frameworks\projects\framework\build.xml
>>>"pixelbender-compile"
>>> >>>target
>>> >>>- Jenkins output of the job:
>>> >>>
>>> >>>pixelbender-compile:
>>> >>> [exec] AIF Internal exception
>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>> >>> [exec] Return code: 1
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>> [exec] ERROR: AIF Internal exception
>>> >>> [exec] Result: 1
>>> >>>
>>> >>>So I am getting the same error.
>>> >>>
>>> >>>Om says "master" does not get a window, so this result seems to be
>>> >>>normal.
>>> >>>
>>> >>>I am trying now to create a slave node and run the job on it.
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >>>Envoyé : mardi 10 décembre 2013 22:07
>>> >>>À : dev@flex.apache.org
>>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>> >>>
>>> >>>It was from the command line (cmd ant ), so gets a window.
>>> >>>
>>> >>>I am trying now from Jenkins service, but needs to install it
>>>first...
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>> >>>needed
>>> >>>
>>> >>>Maurice,
>>> >>>
>>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>> >>>I think there is a difference. On Jenkins, the main executor
>>>(master)
>>> >>>does not get a window. Only slave executors are configured to get a
>>> >>>window.
>>> >>>Whereas Cygwin does not have such restrictions.
>>> >>>
>>> >>>Thanks,
>>> >>>Om
>>> >>>
>>> >>>
>>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com>
>>>wrote:
>>> >>>
>>> >>>> I have no idea what to do with that information. But thanks for
>>> >>>>trying.
>>> >>>>
>>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>> >>>> <ma...@systar.com>
>>> >>>> wrote:
>>> >>>>
>>> >>>> >So this is the output from the b.a.o box:
>>> >>>> >
>>> >>>> >pixelbender-compile:
>>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>> >>>> > [exec] AIF Internal exception
>>> >>>> > [exec] Return code: 1
>>> >>>> > [exec] Result: 1
>>> >>>> >
>>> >>>> >To be compared to the output on my PC:
>>> >>>> >pixelbender-compile
>>> >>>> >exec
>>> >>>> >Device: 00633CEC has video RAM(MB): 512
>>> >>>> >Vendor string: NVIDIA Corporation
>>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>>> >>>> >Version string: 3.0.0
>>> >>>> >
>>> >>>> >OpenGL version as determined by Extensionator...
>>> >>>> >OpenGL Version 3.0
>>> >>>> >Has NPOT support: TRUE
>>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>>> >>>> >test!
>>> >>>> >Return code: 7
>>> >>>> >Result: 7
>>> >>>> >Exec
>>> >>>> >
>>> >>>> >That does not tell much, except that there seems to be an issue
>>> >>>> >with accessing the GPU.
>>> >>>> >
>>> >>>> >Shall I un-commit the change now, or do you want to perform more
>>> >>>> >tests
>>> >>>>?
>>> >>>> >
>>> >>>> >Maurice
>>> >>>> >
>>> >>>> >-----Message d'origine-----
>>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À :
>>>dev@flex.apache.orgObjet :
>>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>>> >>>> >
>>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>> >>>> >
>>> >>>> >Can you try on your side, please ?
>>> >>>> >
>>> >>>> >-----Message d'origine-----
>>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >décembre
>>> >>>> >2013
>>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and
>>> >>>> >advise needed
>>> >>>> >
>>> >>>> >Won't that break Mac builds?
>>> >>>> >
>>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>> >>>> ><ma...@systar.com>
>>> >>>> >wrote:
>>> >>>> >
>>> >>>> >>Alex, it's one line to change in the build.xml
>>> >>>> >>
>>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>> >>>> >>
>>> >>>> >>I will give it a try and we will know in 15 min.
>>> >>>> >>
>>> >>>> >>I am sure the result will be interesting.
>>> >>>> >>
>>> >>>> >>Anyway, it can't hurt ;-)
>>> >>>> >>
>>> >>>> >>Maurice
>>> >>>> >>
>>> >>>> >>-----Message d'origine-----
>>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >>décembre
>>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>> >>Help and advise needed
>>> >>>> >>
>>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>> >>>>request.
>>> >>>> >>
>>> >>>> >>BTW, thanks for finding out about the tool.
>>> >>>> >>
>>> >>>> >>-Alex
>>> >>>> >>
>>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>> >>>> >><ma...@systar.com>
>>> >>>> >>wrote:
>>> >>>> >>
>>> >>>> >>>Sure, if you can ask him.
>>> >>>> >>>
>>> >>>> >>>Maurice
>>> >>>> >>>
>>> >>>> >>>-----Message d'origine-----
>>> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >>>décembre
>>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>> >>>Help and advise needed
>>> >>>> >>>
>>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>>> >>>> >>>
>>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>> >>>> >>><ma...@systar.com>
>>> >>>> >>>wrote:
>>> >>>> >>>
>>> >>>> >>>>There is a utility in pixel bender toolkit directory called
>>> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of
>>>OpenGL:
>>> >>>> >>>>
>>> >>>> >>>>Console output on my laptop is below:
>>> >>>> >>>>
>>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
>>>Bender
>>> >>>> >>>>Toolkit
>>> >>>> >>>>2>sniffer_gpu.exe
>>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>> >>>> >>>>Vendor string: NVIDIA Corporation
>>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>> >>>> >>>>Version string: 3.0.0
>>> >>>> >>>>
>>> >>>> >>>>OpenGL version as determined by Extensionator...
>>> >>>> >>>>OpenGL Version 3.0
>>> >>>> >>>>Has NPOT support: TRUE
>>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed
>>>shader
>>> >>>>test!
>>> >>>> >>>>Return code: 7
>>> >>>> >>>>
>>> >>>> >>>>Maybe we could temporarily modify the build to run this
>>>utility
>>> >>>> >>>>and show the output on the b.a.o vm.
>>> >>>> >>>>
>>> >>>> >>>>WDYT ?
>>> >>>> >>>>
>>> >>>> >>>>Maurice
>>> >>>> >>>>
>>> >>>> >>>>-----Message d'origine-----
>>> >>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>> >>>>décembre
>>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re:
>>>[Builds/Jenkins]
>>> >>>> >>>>Help and advise needed
>>> >>>> >>>>
>>> >>>> >>>>I don't think we actually know the cause of the problem. I am
>>> >>>> >>>>going to continue to spend cycles to try to find out though.
>>> >>>> >>>>
>>> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm
>>>not
>>> >>>> >>>>sure if it will cost Om money to run a builds server.
>>> >>>> >>>>
>>> >>>> >>>>-Alex
>>> >>>> >>>>
>>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>> >>>> >>>><ma...@systar.com>
>>> >>>> >>>>wrote:
>>> >>>> >>>>
>>> >>>> >>>>>I understand that.
>>> >>>> >>>>>
>>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>> >>>> >>>>>bender compiler required some sort of hardware configuration
>>> >>>> >>>>>(OpenGL,
>>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows
>>>Jenkins
>>> >>>> >>>>>slave node, so that's why the build was failing, and the
>>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
>>> >>>> >>>>>access the VM ourselves.
>>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>>> >>>> >>>>>
>>> >>>> >>>>>Now, it seems from what Om is saying that we can set up and
>>>use
>>> >>>> >>>>>our own Jenkins slave node VM.
>>> >>>> >>>>>
>>> >>>> >>>>>That, of course, is much preferable...
>>> >>>> >>>>>
>>> >>>> >>>>>Maurice
>>> >>>> >>>>>
>>> >>>> >>>>>-----Message d'origine-----
>>> >>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>>> >>>> >>>>>
>>> >>>> >>>>>Maurice,
>>> >>>> >>>>>
>>> >>>> >>>>>Your help is very much appreciated!
>>> >>>> >>>>>
>>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of the
>>> >>>> >>>>>law, more of the rules. An Apache release is supposed to be
>>> >>>> >>>>>'source only', and we if we can produce needed binaries from
>>> >>>> >>>>>source, we keep only the source, not the artefacts
>>>themselves in
>>> >>>>the repo.
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>EdB
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>> >>>> >>>>><ma...@systar.com> wrote:
>>> >>>> >>>>>>>In addition to the various "legal" issues with binaries in
>>> >>>> >>>>>>>the
>>> >>>>repo.
>>> >>>> >>>>>> I understand it's not a good idea to have binaries in the
>>> >>>> >>>>>>repo, so I won't insist.
>>> >>>> >>>>>> But please can you explain what are the legal issues of
>>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe, or
>>>ASF
>>> >>>>rules ?
>>> >>>> >>>>>>
>>> >>>> >>>>>> On a side note, I was just trying to help, with my limited
>>> >>>> >>>>>> understanding and knowledge, and because the email thread
>>>was
>>> >>>> >>>>>> titled "help and advise needed" ;-)
>>> >>>> >>>>>>
>>> >>>> >>>>>> Regards,
>>> >>>> >>>>>>
>>> >>>> >>>>>> Maurice
>>> >>>> >>>>>>
>>> >>>> >>>>>> -----Message d'origine-----
>>> >>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé :
>>>mardi
>>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>> >>>> >>>>>>
>>> >>>> >>>>>> In addition to the various "legal" issues with binaries in
>>> >>>> >>>>>>the repo, we'd be masking the cause of this failure. In
>>>order
>>> >>>> >>>>>>to prevent further deterioration of the build process, we
>>>need
>>> >>>> >>>>>>to figure out what went wrong and fix it.
>>> >>>> >>>>>>
>>> >>>> >>>>>> EdB
>>> >>>> >>>>>>
>>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set
>>>to
>>> >>>>FR...
>>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
>>> >>>> >>>>>> my keyboard was broken ;-)
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>> >>>> >>>>>><ma...@systar.com> wrote:
>>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>> >>>>complain.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> I don't understand.
>>> >>>> >>>>>>> Why would someone complain if the pbj's are in the
>>>nightly?
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> [From the other emai]
>>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code.
>>>The
>>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>>> >>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>> >>>>files.
>>> >>>> >>>>>>>>But we could borrow them from a prior release package
>>> >>>>temporarily.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>> >>>> >>>>>>>>Yes but ...
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
>>> >>>> >>>>>>>sure that I have understood what you said.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> So can we include the pbj in the repo, and have a
>>>parameter
>>> >>>> >>>>>>>to conditionally compile the pbj ?
>>> >>>> >>>>>>> - This parameter would be set by default to do the
>>> >>>> >>>>>>>compilation (so that folks can recompile)
>>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>> >>>> >>>>>>>
>>> >>>> >>>>>>>
>>> >>>> >>>>>>> Maurice
>>> >>>> >>>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>>
>>> >>>> >>>>>> --
>>> >>>> >>>>>> Ix Multimedia Software
>>> >>>> >>>>>>
>>> >>>> >>>>>> Jan Luykenstraat 27
>>> >>>> >>>>>> 3521 VB Utrecht
>>> >>>> >>>>>>
>>> >>>> >>>>>> T. 06-51952295
>>> >>>> >>>>>> I. www.ixsoftware.nl
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>
>>> >>>> >>>>>--
>>> >>>> >>>>>Ix Multimedia Software
>>> >>>> >>>>>
>>> >>>> >>>>>Jan Luykenstraat 27
>>> >>>> >>>>>3521 VB Utrecht
>>> >>>> >>>>>
>>> >>>> >>>>>T. 06-51952295
>>> >>>> >>>>>I. www.ixsoftware.nl
>>> >>>> >>>>
>>> >>>> >>>
>>> >>>> >>
>>> >>>> >
>>> >>>>
>>> >>>>
>>> >>
>>> >
>>>
>>>
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Here is Gavin's response a minute ago:
=================
> Gavin,
>
> Can you please copy-paste this line into a command prompt and tell us what
> the result is:
>
> "%PIXELBENDER_HOME%\pbutil.exe"
> "F:\hudson\hudson-slave\workspace\flex-
> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> pbk"
> "F:\hudson\hudson-slave\workspace\flex-
> sdk\frameworks\projects\framework\src\mx\graphics\shaderClasses\Color.
> pbj"
>
> (mind the wrap)
>
> Thanks!
Result is a slight pause, then the prompt returns. No error, no output.
(PixelBender is where its meant to be, PIXELBENDER_HOME is a user variable.)
Let me know what's next to check , thanks
Gav...
=================
On Tue, Dec 10, 2013 at 2:15 PM, OmPrakash Muppirala
<bi...@gmail.com>wrote:
> On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
>
>> Don't know, but if you can prove that the slave can be configured in a way
>> that it won't run, then we have a more specific question to ask infra.
>>
>> -Alex
>>
>
> Wow, this is like CSI ;-)
>
> Here is what we know. Gavin recently installed a new slave (windows2) I
> am guessing that something was probably changed in the way slaves are run.
>
> BTW, here is another piece of information. This is the system info for
> windows1:
>
> https://builds.apache.org/computer/windows1/systemInfo
>
> Anything looks out of the ordinary?
>
> Thanks,
> Om
>
>
>
>
>>
>> On 12/10/13 1:55 PM, "Maurice Amsellem" <ma...@systar.com>
>> wrote:
>>
>> >According to jenkins gui, there are 4 ways of starting the slave :
>> >- Java web start (JNLP)
>> >- command line from master
>> >- via SSH on Unix machines
>> >- as a Windows Service.
>> >
>> >I am using JNLP, but maybe the other launch methods don't get a window.
>> >I am going to try "as a Windows Service".
>> >
>> >Is there a way to know how the slave is launched on b.a.o?
>> >
>> >Maurice
>> >-----Message d'origine-----
>> >De : Alex Harui [mailto:aharui@adobe.com]
>> >Envoyé : mardi 10 décembre 2013 22:46
>> >À : dev@flex.apache.org
>> >Objet : Re: [Builds/Jenkins] Help and advise needed
>> >
>> >InterestingŠ Is there a way to configure a slave so it doesn't get a
>> >window? Maybe Infra changed some default on builds.a.o.
>> >
>> >On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
>> >wrote:
>> >
>> >>Now run the same build on a slave node (that gets a windows "jenkins
>> >>slave agent", that is visible on the desktop ):
>> >>
>> >>Remote build on windowsSlave1 in workspace
>> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile
>> >>&& exit %%ERRORLEVEL%%"'
>> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>> >>-Djava.net.preferIPv4Stack=true
>> >>Buildfile:
>> >>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.x
>> >>ml
>> >>
>> >>pixelbender-compile:
>> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
>> >> [exec] Vendor string: NVIDIA Corporation
>> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
>> >> [exec] Version string: 3.0.0
>> >> [exec]
>> >> [exec] OpenGL version as determined by Extensionator...
>> >> [exec] OpenGL Version 3.0
>> >> [exec] Has NPOT support: TRUE
>> >> [exec] Has Framebuffer Obeject Extension support: TRUE
>> >> [exec] Completed shader test!
>> >> [exec] Return code: 7
>> >> [exec] Result: 7
>> >>BUILD SUCCESSFUL
>> >>Total time: 8 seconds
>> >>Finished: SUCCESS
>> >>
>> >>Well, that's a difference.
>> >>
>> >>Maurice
>> >>
>> >>-----Message d'origine-----
>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>> >>and advise needed
>> >>
>> >>Nice. Thanks for sticking with it.
>> >>
>> >>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
>> >>wrote:
>> >>
>> >>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>> >>>Tomcat is running as a Windows Service).
>> >>>
>> >>>- Created a simple job, on the "master" node, than starts
>> >>>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>> >>>target
>> >>>- Jenkins output of the job:
>> >>>
>> >>>pixelbender-compile:
>> >>> [exec] AIF Internal exception
>> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
>> >>> [exec] Return code: 1
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>> [exec] ERROR: AIF Internal exception
>> >>> [exec] Result: 1
>> >>>
>> >>>So I am getting the same error.
>> >>>
>> >>>Om says "master" does not get a window, so this result seems to be
>> >>>normal.
>> >>>
>> >>>I am trying now to create a slave node and run the job on it.
>> >>>
>> >>>Maurice
>> >>>
>> >>>-----Message d'origine-----
>> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> >>>Envoyé : mardi 10 décembre 2013 22:07
>> >>>À : dev@flex.apache.org
>> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
>> >>>
>> >>>It was from the command line (cmd ant ), so gets a window.
>> >>>
>> >>>I am trying now from Jenkins service, but needs to install it first...
>> >>>
>> >>>Maurice
>> >>>
>> >>>-----Message d'origine-----
>> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>> >>>needed
>> >>>
>> >>>Maurice,
>> >>>
>> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>> >>>I think there is a difference. On Jenkins, the main executor (master)
>> >>>does not get a window. Only slave executors are configured to get a
>> >>>window.
>> >>>Whereas Cygwin does not have such restrictions.
>> >>>
>> >>>Thanks,
>> >>>Om
>> >>>
>> >>>
>> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>> >>>
>> >>>> I have no idea what to do with that information. But thanks for
>> >>>>trying.
>> >>>>
>> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>> >>>> <ma...@systar.com>
>> >>>> wrote:
>> >>>>
>> >>>> >So this is the output from the b.a.o box:
>> >>>> >
>> >>>> >pixelbender-compile:
>> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>> >>>> > [exec] AIF Internal exception
>> >>>> > [exec] Return code: 1
>> >>>> > [exec] Result: 1
>> >>>> >
>> >>>> >To be compared to the output on my PC:
>> >>>> >pixelbender-compile
>> >>>> >exec
>> >>>> >Device: 00633CEC has video RAM(MB): 512
>> >>>> >Vendor string: NVIDIA Corporation
>> >>>> >Renderer string: NVS 4200M/PCI/SSE2
>> >>>> >Version string: 3.0.0
>> >>>> >
>> >>>> >OpenGL version as determined by Extensionator...
>> >>>> >OpenGL Version 3.0
>> >>>> >Has NPOT support: TRUE
>> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>> >>>> >test!
>> >>>> >Return code: 7
>> >>>> >Result: 7
>> >>>> >Exec
>> >>>> >
>> >>>> >That does not tell much, except that there seems to be an issue
>> >>>> >with accessing the GPU.
>> >>>> >
>> >>>> >Shall I un-commit the change now, or do you want to perform more
>> >>>> >tests
>> >>>>?
>> >>>> >
>> >>>> >Maurice
>> >>>> >
>> >>>> >-----Message d'origine-----
>> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.orgObjet :
>> >>>> >RE: [Builds/Jenkins] Help and advise needed
>> >>>> >
>> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
>> >>>> >
>> >>>> >Can you try on your side, please ?
>> >>>> >
>> >>>> >-----Message d'origine-----
>> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>> >décembre
>> >>>> >2013
>> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>> >>>> >advise needed
>> >>>> >
>> >>>> >Won't that break Mac builds?
>> >>>> >
>> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>> >>>> ><ma...@systar.com>
>> >>>> >wrote:
>> >>>> >
>> >>>> >>Alex, it's one line to change in the build.xml
>> >>>> >>
>> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>> >>>> >>
>> >>>> >>I will give it a try and we will know in 15 min.
>> >>>> >>
>> >>>> >>I am sure the result will be interesting.
>> >>>> >>
>> >>>> >>Anyway, it can't hurt ;-)
>> >>>> >>
>> >>>> >>Maurice
>> >>>> >>
>> >>>> >>-----Message d'origine-----
>> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>> >>décembre
>> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>> >>Help and advise needed
>> >>>> >>
>> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>> >>>>request.
>> >>>> >>
>> >>>> >>BTW, thanks for finding out about the tool.
>> >>>> >>
>> >>>> >>-Alex
>> >>>> >>
>> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>> >>>> >><ma...@systar.com>
>> >>>> >>wrote:
>> >>>> >>
>> >>>> >>>Sure, if you can ask him.
>> >>>> >>>
>> >>>> >>>Maurice
>> >>>> >>>
>> >>>> >>>-----Message d'origine-----
>> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>> >>>décembre
>> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>> >>>Help and advise needed
>> >>>> >>>
>> >>>> >>>Might be simpler just to ask Gavin to run the tool?
>> >>>> >>>
>> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>> >>>> >>><ma...@systar.com>
>> >>>> >>>wrote:
>> >>>> >>>
>> >>>> >>>>There is a utility in pixel bender toolkit directory called
>> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>> >>>> >>>>
>> >>>> >>>>Console output on my laptop is below:
>> >>>> >>>>
>> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>> >>>> >>>>Toolkit
>> >>>> >>>>2>sniffer_gpu.exe
>> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>> >>>> >>>>Vendor string: NVIDIA Corporation
>> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>> >>>> >>>>Version string: 3.0.0
>> >>>> >>>>
>> >>>> >>>>OpenGL version as determined by Extensionator...
>> >>>> >>>>OpenGL Version 3.0
>> >>>> >>>>Has NPOT support: TRUE
>> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>> >>>>test!
>> >>>> >>>>Return code: 7
>> >>>> >>>>
>> >>>> >>>>Maybe we could temporarily modify the build to run this utility
>> >>>> >>>>and show the output on the b.a.o vm.
>> >>>> >>>>
>> >>>> >>>>WDYT ?
>> >>>> >>>>
>> >>>> >>>>Maurice
>> >>>> >>>>
>> >>>> >>>>-----Message d'origine-----
>> >>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>> >>>>décembre
>> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>> >>>>Help and advise needed
>> >>>> >>>>
>> >>>> >>>>I don't think we actually know the cause of the problem. I am
>> >>>> >>>>going to continue to spend cycles to try to find out though.
>> >>>> >>>>
>> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>> >>>> >>>>sure if it will cost Om money to run a builds server.
>> >>>> >>>>
>> >>>> >>>>-Alex
>> >>>> >>>>
>> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>> >>>> >>>><ma...@systar.com>
>> >>>> >>>>wrote:
>> >>>> >>>>
>> >>>> >>>>>I understand that.
>> >>>> >>>>>
>> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
>> >>>> >>>>>bender compiler required some sort of hardware configuration
>> >>>> >>>>>(OpenGL,
>> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>> >>>> >>>>>slave node, so that's why the build was failing, and the
>> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
>> >>>> >>>>>access the VM ourselves.
>> >>>> >>>>>So that's why I was proposing a "software only" solution.
>> >>>> >>>>>
>> >>>> >>>>>Now, it seems from what Om is saying that we can set up and use
>> >>>> >>>>>our own Jenkins slave node VM.
>> >>>> >>>>>
>> >>>> >>>>>That, of course, is much preferable...
>> >>>> >>>>>
>> >>>> >>>>>Maurice
>> >>>> >>>>>
>> >>>> >>>>>-----Message d'origine-----
>> >>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>> >>>> >>>>>[Builds/Jenkins] Help and advise needed
>> >>>> >>>>>
>> >>>> >>>>>Maurice,
>> >>>> >>>>>
>> >>>> >>>>>Your help is very much appreciated!
>> >>>> >>>>>
>> >>>> >>>>>I put "legal" in quotes, the issue is not really one of the
>> >>>> >>>>>law, more of the rules. An Apache release is supposed to be
>> >>>> >>>>>'source only', and we if we can produce needed binaries from
>> >>>> >>>>>source, we keep only the source, not the artefacts themselves in
>> >>>>the repo.
>> >>>> >>>>>
>> >>>> >>>>>
>> >>>> >>>>>EdB
>> >>>> >>>>>
>> >>>> >>>>>
>> >>>> >>>>>
>> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>> >>>> >>>>><ma...@systar.com> wrote:
>> >>>> >>>>>>>In addition to the various "legal" issues with binaries in
>> >>>> >>>>>>>the
>> >>>>repo.
>> >>>> >>>>>> I understand it's not a good idea to have binaries in the
>> >>>> >>>>>>repo, so I won't insist.
>> >>>> >>>>>> But please can you explain what are the legal issues of
>> >>>> >>>>>>having binaries in the repo? Is this because of Adobe, or ASF
>> >>>>rules ?
>> >>>> >>>>>>
>> >>>> >>>>>> On a side note, I was just trying to help, with my limited
>> >>>> >>>>>> understanding and knowledge, and because the email thread was
>> >>>> >>>>>> titled "help and advise needed" ;-)
>> >>>> >>>>>>
>> >>>> >>>>>> Regards,
>> >>>> >>>>>>
>> >>>> >>>>>> Maurice
>> >>>> >>>>>>
>> >>>> >>>>>> -----Message d'origine-----
>> >>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
>> >>>> >>>>>>
>> >>>> >>>>>> In addition to the various "legal" issues with binaries in
>> >>>> >>>>>>the repo, we'd be masking the cause of this failure. In order
>> >>>> >>>>>>to prevent further deterioration of the build process, we need
>> >>>> >>>>>>to figure out what went wrong and fix it.
>> >>>> >>>>>>
>> >>>> >>>>>> EdB
>> >>>> >>>>>>
>> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>> >>>>FR...
>> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
>> >>>> >>>>>> my keyboard was broken ;-)
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>> >>>> >>>>>><ma...@systar.com> wrote:
>> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>> >>>>complain.
>> >>>> >>>>>>>
>> >>>> >>>>>>> I don't understand.
>> >>>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>> >>>> >>>>>>>
>> >>>> >>>>>>> [From the other emai]
>> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>> >>>> >>>>>>>>pbj files were removed during the initial release audit.
>> >>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>> >>>>files.
>> >>>> >>>>>>>>But we could borrow them from a prior release package
>> >>>>temporarily.
>> >>>> >>>>>>>
>> >>>> >>>>>>>>So we could make the compilation conditional on a env
>> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>> >>>> >>>>>>>>Yes but ...
>> >>>> >>>>>>>
>> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
>> >>>> >>>>>>>sure that I have understood what you said.
>> >>>> >>>>>>>
>> >>>> >>>>>>> So can we include the pbj in the repo, and have a parameter
>> >>>> >>>>>>>to conditionally compile the pbj ?
>> >>>> >>>>>>> - This parameter would be set by default to do the
>> >>>> >>>>>>>compilation (so that folks can recompile)
>> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>> >>>> >>>>>>>
>> >>>> >>>>>>>
>> >>>> >>>>>>> Maurice
>> >>>> >>>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>>
>> >>>> >>>>>> --
>> >>>> >>>>>> Ix Multimedia Software
>> >>>> >>>>>>
>> >>>> >>>>>> Jan Luykenstraat 27
>> >>>> >>>>>> 3521 VB Utrecht
>> >>>> >>>>>>
>> >>>> >>>>>> T. 06-51952295
>> >>>> >>>>>> I. www.ixsoftware.nl
>> >>>> >>>>>
>> >>>> >>>>>
>> >>>> >>>>>
>> >>>> >>>>>--
>> >>>> >>>>>Ix Multimedia Software
>> >>>> >>>>>
>> >>>> >>>>>Jan Luykenstraat 27
>> >>>> >>>>>3521 VB Utrecht
>> >>>> >>>>>
>> >>>> >>>>>T. 06-51952295
>> >>>> >>>>>I. www.ixsoftware.nl
>> >>>> >>>>
>> >>>> >>>
>> >>>> >>
>> >>>> >
>> >>>>
>> >>>>
>> >>
>> >
>>
>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 1:58 PM, Alex Harui <ah...@adobe.com> wrote:
> Don't know, but if you can prove that the slave can be configured in a way
> that it won't run, then we have a more specific question to ask infra.
>
> -Alex
>
Wow, this is like CSI ;-)
Here is what we know. Gavin recently installed a new slave (windows2) I
am guessing that something was probably changed in the way slaves are run.
BTW, here is another piece of information. This is the system info for
windows1:
https://builds.apache.org/computer/windows1/systemInfo
Anything looks out of the ordinary?
Thanks,
Om
>
> On 12/10/13 1:55 PM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >According to jenkins gui, there are 4 ways of starting the slave :
> >- Java web start (JNLP)
> >- command line from master
> >- via SSH on Unix machines
> >- as a Windows Service.
> >
> >I am using JNLP, but maybe the other launch methods don't get a window.
> >I am going to try "as a Windows Service".
> >
> >Is there a way to know how the slave is launched on b.a.o?
> >
> >Maurice
> >-----Message d'origine-----
> >De : Alex Harui [mailto:aharui@adobe.com]
> >Envoyé : mardi 10 décembre 2013 22:46
> >À : dev@flex.apache.org
> >Objet : Re: [Builds/Jenkins] Help and advise needed
> >
> >InterestingŠ Is there a way to configure a slave so it doesn't get a
> >window? Maybe Infra changed some default on builds.a.o.
> >
> >On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
> >wrote:
> >
> >>Now run the same build on a slave node (that gets a windows "jenkins
> >>slave agent", that is visible on the desktop ):
> >>
> >>Remote build on windowsSlave1 in workspace
> >>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
> >>[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile
> >>&& exit %%ERRORLEVEL%%"'
> >>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
> >>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
> >>-Djava.net.preferIPv4Stack=true
> >>Buildfile:
> >>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.x
> >>ml
> >>
> >>pixelbender-compile:
> >> [exec] Device: 005EC1C4 has video RAM(MB): 512
> >> [exec] Vendor string: NVIDIA Corporation
> >> [exec] Renderer string: NVS 4200M/PCI/SSE2
> >> [exec] Version string: 3.0.0
> >> [exec]
> >> [exec] OpenGL version as determined by Extensionator...
> >> [exec] OpenGL Version 3.0
> >> [exec] Has NPOT support: TRUE
> >> [exec] Has Framebuffer Obeject Extension support: TRUE
> >> [exec] Completed shader test!
> >> [exec] Return code: 7
> >> [exec] Result: 7
> >>BUILD SUCCESSFUL
> >>Total time: 8 seconds
> >>Finished: SUCCESS
> >>
> >>Well, that's a difference.
> >>
> >>Maurice
> >>
> >>-----Message d'origine-----
> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>and advise needed
> >>
> >>Nice. Thanks for sticking with it.
> >>
> >>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
> >>wrote:
> >>
> >>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
> >>>Tomcat is running as a Windows Service).
> >>>
> >>>- Created a simple job, on the "master" node, than starts
> >>>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
> >>>target
> >>>- Jenkins output of the job:
> >>>
> >>>pixelbender-compile:
> >>> [exec] AIF Internal exception
> >>> [exec] Device: 008BB2BC has video RAM(MB): 3844
> >>> [exec] Device: 008BB2BC has video RAM(MB): 512
> >>> [exec] Return code: 1
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>> [exec] ERROR: AIF Internal exception
> >>> [exec] Result: 1
> >>>
> >>>So I am getting the same error.
> >>>
> >>>Om says "master" does not get a window, so this result seems to be
> >>>normal.
> >>>
> >>>I am trying now to create a slave node and run the job on it.
> >>>
> >>>Maurice
> >>>
> >>>-----Message d'origine-----
> >>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>>Envoyé : mardi 10 décembre 2013 22:07
> >>>À : dev@flex.apache.org
> >>>Objet : RE: [Builds/Jenkins] Help and advise needed
> >>>
> >>>It was from the command line (cmd ant ), so gets a window.
> >>>
> >>>I am trying now from Jenkins service, but needs to install it first...
> >>>
> >>>Maurice
> >>>
> >>>-----Message d'origine-----
> >>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
> >>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
> >>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
> >>>needed
> >>>
> >>>Maurice,
> >>>
> >>>When you ran it on your machine, was it on Cygwin or from Jenkins?
> >>>I think there is a difference. On Jenkins, the main executor (master)
> >>>does not get a window. Only slave executors are configured to get a
> >>>window.
> >>>Whereas Cygwin does not have such restrictions.
> >>>
> >>>Thanks,
> >>>Om
> >>>
> >>>
> >>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
> >>>
> >>>> I have no idea what to do with that information. But thanks for
> >>>>trying.
> >>>>
> >>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
> >>>> <ma...@systar.com>
> >>>> wrote:
> >>>>
> >>>> >So this is the output from the b.a.o box:
> >>>> >
> >>>> >pixelbender-compile:
> >>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> >>>> > [exec] AIF Internal exception
> >>>> > [exec] Return code: 1
> >>>> > [exec] Result: 1
> >>>> >
> >>>> >To be compared to the output on my PC:
> >>>> >pixelbender-compile
> >>>> >exec
> >>>> >Device: 00633CEC has video RAM(MB): 512
> >>>> >Vendor string: NVIDIA Corporation
> >>>> >Renderer string: NVS 4200M/PCI/SSE2
> >>>> >Version string: 3.0.0
> >>>> >
> >>>> >OpenGL version as determined by Extensionator...
> >>>> >OpenGL Version 3.0
> >>>> >Has NPOT support: TRUE
> >>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
> >>>> >test!
> >>>> >Return code: 7
> >>>> >Result: 7
> >>>> >Exec
> >>>> >
> >>>> >That does not tell much, except that there seems to be an issue
> >>>> >with accessing the GPU.
> >>>> >
> >>>> >Shall I un-commit the change now, or do you want to perform more
> >>>> >tests
> >>>>?
> >>>> >
> >>>> >Maurice
> >>>> >
> >>>> >-----Message d'origine-----
> >>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >>>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet
> :
> >>>> >RE: [Builds/Jenkins] Help and advise needed
> >>>> >
> >>>> >I don't have a Mac with ApacheFlex SDK for testing.
> >>>> >
> >>>> >Can you try on your side, please ?
> >>>> >
> >>>> >-----Message d'origine-----
> >>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>> >décembre
> >>>> >2013
> >>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >>>> >advise needed
> >>>> >
> >>>> >Won't that break Mac builds?
> >>>> >
> >>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
> >>>> ><ma...@systar.com>
> >>>> >wrote:
> >>>> >
> >>>> >>Alex, it's one line to change in the build.xml
> >>>> >>
> >>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>>> >>
> >>>> >>I will give it a try and we will know in 15 min.
> >>>> >>
> >>>> >>I am sure the result will be interesting.
> >>>> >>
> >>>> >>Anyway, it can't hurt ;-)
> >>>> >>
> >>>> >>Maurice
> >>>> >>
> >>>> >>-----Message d'origine-----
> >>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>> >>décembre
> >>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>> >>Help and advise needed
> >>>> >>
> >>>> >>I think I'll wait to see how Gavin responds to Erik's latest
> >>>>request.
> >>>> >>
> >>>> >>BTW, thanks for finding out about the tool.
> >>>> >>
> >>>> >>-Alex
> >>>> >>
> >>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
> >>>> >><ma...@systar.com>
> >>>> >>wrote:
> >>>> >>
> >>>> >>>Sure, if you can ask him.
> >>>> >>>
> >>>> >>>Maurice
> >>>> >>>
> >>>> >>>-----Message d'origine-----
> >>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>> >>>décembre
> >>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>> >>>Help and advise needed
> >>>> >>>
> >>>> >>>Might be simpler just to ask Gavin to run the tool?
> >>>> >>>
> >>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
> >>>> >>><ma...@systar.com>
> >>>> >>>wrote:
> >>>> >>>
> >>>> >>>>There is a utility in pixel bender toolkit directory called
> >>>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
> >>>> >>>>
> >>>> >>>>Console output on my laptop is below:
> >>>> >>>>
> >>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
> >>>> >>>>Toolkit
> >>>> >>>>2>sniffer_gpu.exe
> >>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>>> >>>>Vendor string: NVIDIA Corporation
> >>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>>> >>>>Version string: 3.0.0
> >>>> >>>>
> >>>> >>>>OpenGL version as determined by Extensionator...
> >>>> >>>>OpenGL Version 3.0
> >>>> >>>>Has NPOT support: TRUE
> >>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
> >>>>test!
> >>>> >>>>Return code: 7
> >>>> >>>>
> >>>> >>>>Maybe we could temporarily modify the build to run this utility
> >>>> >>>>and show the output on the b.a.o vm.
> >>>> >>>>
> >>>> >>>>WDYT ?
> >>>> >>>>
> >>>> >>>>Maurice
> >>>> >>>>
> >>>> >>>>-----Message d'origine-----
> >>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>> >>>>décembre
> >>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>> >>>>Help and advise needed
> >>>> >>>>
> >>>> >>>>I don't think we actually know the cause of the problem. I am
> >>>> >>>>going to continue to spend cycles to try to find out though.
> >>>> >>>>
> >>>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
> >>>> >>>>sure if it will cost Om money to run a builds server.
> >>>> >>>>
> >>>> >>>>-Alex
> >>>> >>>>
> >>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
> >>>> >>>><ma...@systar.com>
> >>>> >>>>wrote:
> >>>> >>>>
> >>>> >>>>>I understand that.
> >>>> >>>>>
> >>>> >>>>>Actually, my "understanding" on this issue was that pixel
> >>>> >>>>>bender compiler required some sort of hardware configuration
> >>>> >>>>>(OpenGL,
> >>>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
> >>>> >>>>>slave node, so that's why the build was failing, and the
> >>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
> >>>> >>>>>access the VM ourselves.
> >>>> >>>>>So that's why I was proposing a "software only" solution.
> >>>> >>>>>
> >>>> >>>>>Now, it seems from what Om is saying that we can set up and use
> >>>> >>>>>our own Jenkins slave node VM.
> >>>> >>>>>
> >>>> >>>>>That, of course, is much preferable...
> >>>> >>>>>
> >>>> >>>>>Maurice
> >>>> >>>>>
> >>>> >>>>>-----Message d'origine-----
> >>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
> >>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>>> >>>>>[Builds/Jenkins] Help and advise needed
> >>>> >>>>>
> >>>> >>>>>Maurice,
> >>>> >>>>>
> >>>> >>>>>Your help is very much appreciated!
> >>>> >>>>>
> >>>> >>>>>I put "legal" in quotes, the issue is not really one of the
> >>>> >>>>>law, more of the rules. An Apache release is supposed to be
> >>>> >>>>>'source only', and we if we can produce needed binaries from
> >>>> >>>>>source, we keep only the source, not the artefacts themselves in
> >>>>the repo.
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>EdB
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>>> >>>>><ma...@systar.com> wrote:
> >>>> >>>>>>>In addition to the various "legal" issues with binaries in
> >>>> >>>>>>>the
> >>>>repo.
> >>>> >>>>>> I understand it's not a good idea to have binaries in the
> >>>> >>>>>>repo, so I won't insist.
> >>>> >>>>>> But please can you explain what are the legal issues of
> >>>> >>>>>>having binaries in the repo? Is this because of Adobe, or ASF
> >>>>rules ?
> >>>> >>>>>>
> >>>> >>>>>> On a side note, I was just trying to help, with my limited
> >>>> >>>>>> understanding and knowledge, and because the email thread was
> >>>> >>>>>> titled "help and advise needed" ;-)
> >>>> >>>>>>
> >>>> >>>>>> Regards,
> >>>> >>>>>>
> >>>> >>>>>> Maurice
> >>>> >>>>>>
> >>>> >>>>>> -----Message d'origine-----
> >>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
> >>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>>> >>>>>> [Builds/Jenkins] Help and advise needed
> >>>> >>>>>>
> >>>> >>>>>> In addition to the various "legal" issues with binaries in
> >>>> >>>>>>the repo, we'd be masking the cause of this failure. In order
> >>>> >>>>>>to prevent further deterioration of the build process, we need
> >>>> >>>>>>to figure out what went wrong and fix it.
> >>>> >>>>>>
> >>>> >>>>>> EdB
> >>>> >>>>>>
> >>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
> >>>>FR...
> >>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
> >>>> >>>>>> my keyboard was broken ;-)
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>>> >>>>>><ma...@systar.com> wrote:
> >>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
> >>>>complain.
> >>>> >>>>>>>
> >>>> >>>>>>> I don't understand.
> >>>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
> >>>> >>>>>>>
> >>>> >>>>>>> [From the other emai]
> >>>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
> >>>> >>>>>>>>pbj files were removed during the initial release audit.
> >>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
> >>>>files.
> >>>> >>>>>>>>But we could borrow them from a prior release package
> >>>>temporarily.
> >>>> >>>>>>>
> >>>> >>>>>>>>So we could make the compilation conditional on a env
> >>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
> >>>> >>>>>>>>Yes but ...
> >>>> >>>>>>>
> >>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
> >>>> >>>>>>>sure that I have understood what you said.
> >>>> >>>>>>>
> >>>> >>>>>>> So can we include the pbj in the repo, and have a parameter
> >>>> >>>>>>>to conditionally compile the pbj ?
> >>>> >>>>>>> - This parameter would be set by default to do the
> >>>> >>>>>>>compilation (so that folks can recompile)
> >>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>> >>>>>>>
> >>>> >>>>>>>
> >>>> >>>>>>> Maurice
> >>>> >>>>>>>
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>>
> >>>> >>>>>> --
> >>>> >>>>>> Ix Multimedia Software
> >>>> >>>>>>
> >>>> >>>>>> Jan Luykenstraat 27
> >>>> >>>>>> 3521 VB Utrecht
> >>>> >>>>>>
> >>>> >>>>>> T. 06-51952295
> >>>> >>>>>> I. www.ixsoftware.nl
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>--
> >>>> >>>>>Ix Multimedia Software
> >>>> >>>>>
> >>>> >>>>>Jan Luykenstraat 27
> >>>> >>>>>3521 VB Utrecht
> >>>> >>>>>
> >>>> >>>>>T. 06-51952295
> >>>> >>>>>I. www.ixsoftware.nl
> >>>> >>>>
> >>>> >>>
> >>>> >>
> >>>> >
> >>>>
> >>>>
> >>
> >
>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
That's what I thought also, so I tried on my own Jenkins but it didn't work :-(
Maurice
-----Message d'origine-----
De : Mark Kessler [mailto:kesslerconsulting@gmail.com]
Envoyé : mercredi 11 décembre 2013 10:48
À : Dev@Flex
Objet : Re: [Builds/Jenkins] Help and advise needed
Could try adding a basic user account and making the service use that instead. User accounts should be able to access the gpu.
-Mark
On Wed, Dec 11, 2013 at 2:45 AM, Maurice Amsellem < maurice.amsellem@systar.com> wrote:
> >To avoid the window
> Thank you for the suggestion, but I don't think the window is an issue.
> It's rather that when running as a service (System or use account),
> Jenkins slave cannot access the gpu / openGL.
>
> Maurice
>
> -----Message d'origine-----
> De : Peter Ginneberge [mailto:p.ginneberge@gmail.com] Envoyé :
> mercredi 11 décembre 2013 04:02 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> To avoid the window, run the service under a different user, e.g.
> "System" instead of a specific user or vice versa.
>
> Peter
>
> On 10/12/2013 22:55, Maurice Amsellem wrote:
> > According to jenkins gui, there are 4 ways of starting the slave :
> > - Java web start (JNLP)
> > - command line from master
> > - via SSH on Unix machines
> > - as a Windows Service.
> >
> > I am using JNLP, but maybe the other launch methods don't get a window.
> > I am going to try "as a Windows Service".
> >
> > Is there a way to know how the slave is launched on b.a.o?
> >
> > Maurice
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Mark Kessler <ke...@gmail.com>.
Could try adding a basic user account and making the service use that
instead. User accounts should be able to access the gpu.
-Mark
On Wed, Dec 11, 2013 at 2:45 AM, Maurice Amsellem <
maurice.amsellem@systar.com> wrote:
> >To avoid the window
> Thank you for the suggestion, but I don't think the window is an issue.
> It's rather that when running as a service (System or use account),
> Jenkins slave cannot access the gpu / openGL.
>
> Maurice
>
> -----Message d'origine-----
> De : Peter Ginneberge [mailto:p.ginneberge@gmail.com]
> Envoyé : mercredi 11 décembre 2013 04:02
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> To avoid the window, run the service under a different user, e.g.
> "System" instead of a specific user or vice versa.
>
> Peter
>
> On 10/12/2013 22:55, Maurice Amsellem wrote:
> > According to jenkins gui, there are 4 ways of starting the slave :
> > - Java web start (JNLP)
> > - command line from master
> > - via SSH on Unix machines
> > - as a Windows Service.
> >
> > I am using JNLP, but maybe the other launch methods don't get a window.
> > I am going to try "as a Windows Service".
> >
> > Is there a way to know how the slave is launched on b.a.o?
> >
> > Maurice
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
>To avoid the window
Thank you for the suggestion, but I don't think the window is an issue.
It's rather that when running as a service (System or use account), Jenkins slave cannot access the gpu / openGL.
Maurice
-----Message d'origine-----
De : Peter Ginneberge [mailto:p.ginneberge@gmail.com]
Envoyé : mercredi 11 décembre 2013 04:02
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
To avoid the window, run the service under a different user, e.g.
"System" instead of a specific user or vice versa.
Peter
On 10/12/2013 22:55, Maurice Amsellem wrote:
> According to jenkins gui, there are 4 ways of starting the slave :
> - Java web start (JNLP)
> - command line from master
> - via SSH on Unix machines
> - as a Windows Service.
>
> I am using JNLP, but maybe the other launch methods don't get a window.
> I am going to try "as a Windows Service".
>
> Is there a way to know how the slave is launched on b.a.o?
>
> Maurice
Re: [Builds/Jenkins] Help and advise needed
Posted by Peter Ginneberge <p....@gmail.com>.
To avoid the window, run the service under a different user, e.g.
"System" instead of a specific user or vice versa.
Peter
On 10/12/2013 22:55, Maurice Amsellem wrote:
> According to jenkins gui, there are 4 ways of starting the slave :
> - Java web start (JNLP)
> - command line from master
> - via SSH on Unix machines
> - as a Windows Service.
>
> I am using JNLP, but maybe the other launch methods don't get a window.
> I am going to try "as a Windows Service".
>
> Is there a way to know how the slave is launched on b.a.o?
>
> Maurice
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Don't know, but if you can prove that the slave can be configured in a way
that it won't run, then we have a more specific question to ask infra.
-Alex
On 12/10/13 1:55 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>According to jenkins gui, there are 4 ways of starting the slave :
>- Java web start (JNLP)
>- command line from master
>- via SSH on Unix machines
>- as a Windows Service.
>
>I am using JNLP, but maybe the other launch methods don't get a window.
>I am going to try "as a Windows Service".
>
>Is there a way to know how the slave is launched on b.a.o?
>
>Maurice
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 22:46
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>InterestingŠ Is there a way to configure a slave so it doesn't get a
>window? Maybe Infra changed some default on builds.a.o.
>
>On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Now run the same build on a slave node (that gets a windows "jenkins
>>slave agent", that is visible on the desktop ):
>>
>>Remote build on windowsSlave1 in workspace
>>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>>[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile
>>&& exit %%ERRORLEVEL%%"'
>>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>>-Djava.net.preferIPv4Stack=true
>>Buildfile:
>>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.x
>>ml
>>
>>pixelbender-compile:
>> [exec] Device: 005EC1C4 has video RAM(MB): 512
>> [exec] Vendor string: NVIDIA Corporation
>> [exec] Renderer string: NVS 4200M/PCI/SSE2
>> [exec] Version string: 3.0.0
>> [exec]
>> [exec] OpenGL version as determined by Extensionator...
>> [exec] OpenGL Version 3.0
>> [exec] Has NPOT support: TRUE
>> [exec] Has Framebuffer Obeject Extension support: TRUE
>> [exec] Completed shader test!
>> [exec] Return code: 7
>> [exec] Result: 7
>>BUILD SUCCESSFUL
>>Total time: 8 seconds
>>Finished: SUCCESS
>>
>>Well, that's a difference.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Nice. Thanks for sticking with it.
>>
>>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>>>Tomcat is running as a Windows Service).
>>>
>>>- Created a simple job, on the "master" node, than starts
>>>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>>>target
>>>- Jenkins output of the job:
>>>
>>>pixelbender-compile:
>>> [exec] AIF Internal exception
>>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>>> [exec] Device: 008BB2BC has video RAM(MB): 512
>>> [exec] Return code: 1
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>> [exec] ERROR: AIF Internal exception
>>> [exec] Result: 1
>>>
>>>So I am getting the same error.
>>>
>>>Om says "master" does not get a window, so this result seems to be
>>>normal.
>>>
>>>I am trying now to create a slave node and run the job on it.
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>Envoyé : mardi 10 décembre 2013 22:07
>>>À : dev@flex.apache.org
>>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>>
>>>It was from the command line (cmd ant ), so gets a window.
>>>
>>>I am trying now from Jenkins service, but needs to install it first...
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>>needed
>>>
>>>Maurice,
>>>
>>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>>I think there is a difference. On Jenkins, the main executor (master)
>>>does not get a window. Only slave executors are configured to get a
>>>window.
>>>Whereas Cygwin does not have such restrictions.
>>>
>>>Thanks,
>>>Om
>>>
>>>
>>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>>>
>>>> I have no idea what to do with that information. But thanks for
>>>>trying.
>>>>
>>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>>> <ma...@systar.com>
>>>> wrote:
>>>>
>>>> >So this is the output from the b.a.o box:
>>>> >
>>>> >pixelbender-compile:
>>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>>> > [exec] AIF Internal exception
>>>> > [exec] Return code: 1
>>>> > [exec] Result: 1
>>>> >
>>>> >To be compared to the output on my PC:
>>>> >pixelbender-compile
>>>> >exec
>>>> >Device: 00633CEC has video RAM(MB): 512
>>>> >Vendor string: NVIDIA Corporation
>>>> >Renderer string: NVS 4200M/PCI/SSE2
>>>> >Version string: 3.0.0
>>>> >
>>>> >OpenGL version as determined by Extensionator...
>>>> >OpenGL Version 3.0
>>>> >Has NPOT support: TRUE
>>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>>>> >test!
>>>> >Return code: 7
>>>> >Result: 7
>>>> >Exec
>>>> >
>>>> >That does not tell much, except that there seems to be an issue
>>>> >with accessing the GPU.
>>>> >
>>>> >Shall I un-commit the change now, or do you want to perform more
>>>> >tests
>>>>?
>>>> >
>>>> >Maurice
>>>> >
>>>> >-----Message d'origine-----
>>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
>>>> >RE: [Builds/Jenkins] Help and advise needed
>>>> >
>>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>>> >
>>>> >Can you try on your side, please ?
>>>> >
>>>> >-----Message d'origine-----
>>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >décembre
>>>> >2013
>>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>>> >advise needed
>>>> >
>>>> >Won't that break Mac builds?
>>>> >
>>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>>> ><ma...@systar.com>
>>>> >wrote:
>>>> >
>>>> >>Alex, it's one line to change in the build.xml
>>>> >>
>>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>>> >>
>>>> >>I will give it a try and we will know in 15 min.
>>>> >>
>>>> >>I am sure the result will be interesting.
>>>> >>
>>>> >>Anyway, it can't hurt ;-)
>>>> >>
>>>> >>Maurice
>>>> >>
>>>> >>-----Message d'origine-----
>>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>décembre
>>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>Help and advise needed
>>>> >>
>>>> >>I think I'll wait to see how Gavin responds to Erik's latest
>>>>request.
>>>> >>
>>>> >>BTW, thanks for finding out about the tool.
>>>> >>
>>>> >>-Alex
>>>> >>
>>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>>> >><ma...@systar.com>
>>>> >>wrote:
>>>> >>
>>>> >>>Sure, if you can ask him.
>>>> >>>
>>>> >>>Maurice
>>>> >>>
>>>> >>>-----Message d'origine-----
>>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>décembre
>>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>Help and advise needed
>>>> >>>
>>>> >>>Might be simpler just to ask Gavin to run the tool?
>>>> >>>
>>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>>> >>><ma...@systar.com>
>>>> >>>wrote:
>>>> >>>
>>>> >>>>There is a utility in pixel bender toolkit directory called
>>>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>>> >>>>
>>>> >>>>Console output on my laptop is below:
>>>> >>>>
>>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>>> >>>>Toolkit
>>>> >>>>2>sniffer_gpu.exe
>>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>>> >>>>Vendor string: NVIDIA Corporation
>>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>>> >>>>Version string: 3.0.0
>>>> >>>>
>>>> >>>>OpenGL version as determined by Extensionator...
>>>> >>>>OpenGL Version 3.0
>>>> >>>>Has NPOT support: TRUE
>>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>>>>test!
>>>> >>>>Return code: 7
>>>> >>>>
>>>> >>>>Maybe we could temporarily modify the build to run this utility
>>>> >>>>and show the output on the b.a.o vm.
>>>> >>>>
>>>> >>>>WDYT ?
>>>> >>>>
>>>> >>>>Maurice
>>>> >>>>
>>>> >>>>-----Message d'origine-----
>>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>>> >>>>décembre
>>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>>> >>>>Help and advise needed
>>>> >>>>
>>>> >>>>I don't think we actually know the cause of the problem. I am
>>>> >>>>going to continue to spend cycles to try to find out though.
>>>> >>>>
>>>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>>>> >>>>sure if it will cost Om money to run a builds server.
>>>> >>>>
>>>> >>>>-Alex
>>>> >>>>
>>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>>> >>>><ma...@systar.com>
>>>> >>>>wrote:
>>>> >>>>
>>>> >>>>>I understand that.
>>>> >>>>>
>>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>>> >>>>>bender compiler required some sort of hardware configuration
>>>> >>>>>(OpenGL,
>>>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>>> >>>>>slave node, so that's why the build was failing, and the
>>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
>>>> >>>>>access the VM ourselves.
>>>> >>>>>So that's why I was proposing a "software only" solution.
>>>> >>>>>
>>>> >>>>>Now, it seems from what Om is saying that we can set up and use
>>>> >>>>>our own Jenkins slave node VM.
>>>> >>>>>
>>>> >>>>>That, of course, is much preferable...
>>>> >>>>>
>>>> >>>>>Maurice
>>>> >>>>>
>>>> >>>>>-----Message d'origine-----
>>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>> >>>>>[Builds/Jenkins] Help and advise needed
>>>> >>>>>
>>>> >>>>>Maurice,
>>>> >>>>>
>>>> >>>>>Your help is very much appreciated!
>>>> >>>>>
>>>> >>>>>I put "legal" in quotes, the issue is not really one of the
>>>> >>>>>law, more of the rules. An Apache release is supposed to be
>>>> >>>>>'source only', and we if we can produce needed binaries from
>>>> >>>>>source, we keep only the source, not the artefacts themselves in
>>>>the repo.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>EdB
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>> >>>>><ma...@systar.com> wrote:
>>>> >>>>>>>In addition to the various "legal" issues with binaries in
>>>> >>>>>>>the
>>>>repo.
>>>> >>>>>> I understand it's not a good idea to have binaries in the
>>>> >>>>>>repo, so I won't insist.
>>>> >>>>>> But please can you explain what are the legal issues of
>>>> >>>>>>having binaries in the repo? Is this because of Adobe, or ASF
>>>>rules ?
>>>> >>>>>>
>>>> >>>>>> On a side note, I was just trying to help, with my limited
>>>> >>>>>> understanding and knowledge, and because the email thread was
>>>> >>>>>> titled "help and advise needed" ;-)
>>>> >>>>>>
>>>> >>>>>> Regards,
>>>> >>>>>>
>>>> >>>>>> Maurice
>>>> >>>>>>
>>>> >>>>>> -----Message d'origine-----
>>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>>> >>>>>>
>>>> >>>>>> In addition to the various "legal" issues with binaries in
>>>> >>>>>>the repo, we'd be masking the cause of this failure. In order
>>>> >>>>>>to prevent further deterioration of the build process, we need
>>>> >>>>>>to figure out what went wrong and fix it.
>>>> >>>>>>
>>>> >>>>>> EdB
>>>> >>>>>>
>>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>>>>FR...
>>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
>>>> >>>>>> my keyboard was broken ;-)
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>> >>>>>><ma...@systar.com> wrote:
>>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>>>complain.
>>>> >>>>>>>
>>>> >>>>>>> I don't understand.
>>>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>>>> >>>>>>>
>>>> >>>>>>> [From the other emai]
>>>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>>>> >>>>>>>>pbj files were removed during the initial release audit.
>>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>>>files.
>>>> >>>>>>>>But we could borrow them from a prior release package
>>>>temporarily.
>>>> >>>>>>>
>>>> >>>>>>>>So we could make the compilation conditional on a env
>>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>>> >>>>>>>>Yes but ...
>>>> >>>>>>>
>>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
>>>> >>>>>>>sure that I have understood what you said.
>>>> >>>>>>>
>>>> >>>>>>> So can we include the pbj in the repo, and have a parameter
>>>> >>>>>>>to conditionally compile the pbj ?
>>>> >>>>>>> - This parameter would be set by default to do the
>>>> >>>>>>>compilation (so that folks can recompile)
>>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>> >>>>>>>
>>>> >>>>>>>
>>>> >>>>>>> Maurice
>>>> >>>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> --
>>>> >>>>>> Ix Multimedia Software
>>>> >>>>>>
>>>> >>>>>> Jan Luykenstraat 27
>>>> >>>>>> 3521 VB Utrecht
>>>> >>>>>>
>>>> >>>>>> T. 06-51952295
>>>> >>>>>> I. www.ixsoftware.nl
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>--
>>>> >>>>>Ix Multimedia Software
>>>> >>>>>
>>>> >>>>>Jan Luykenstraat 27
>>>> >>>>>3521 VB Utrecht
>>>> >>>>>
>>>> >>>>>T. 06-51952295
>>>> >>>>>I. www.ixsoftware.nl
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
According to jenkins gui, there are 4 ways of starting the slave :
- Java web start (JNLP)
- command line from master
- via SSH on Unix machines
- as a Windows Service.
I am using JNLP, but maybe the other launch methods don't get a window.
I am going to try "as a Windows Service".
Is there a way to know how the slave is launched on b.a.o?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 22:46
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
InterestingŠ Is there a way to configure a slave so it doesn't get a window? Maybe Infra changed some default on builds.a.o.
On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Now run the same build on a slave node (that gets a windows "jenkins
>slave agent", that is visible on the desktop ):
>
>Remote build on windowsSlave1 in workspace
>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile
>&& exit %%ERRORLEVEL%%"'
>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>-Djava.net.preferIPv4Stack=true
>Buildfile:
>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.x
>ml
>
>pixelbender-compile:
> [exec] Device: 005EC1C4 has video RAM(MB): 512
> [exec] Vendor string: NVIDIA Corporation
> [exec] Renderer string: NVS 4200M/PCI/SSE2
> [exec] Version string: 3.0.0
> [exec]
> [exec] OpenGL version as determined by Extensionator...
> [exec] OpenGL Version 3.0
> [exec] Has NPOT support: TRUE
> [exec] Has Framebuffer Obeject Extension support: TRUE
> [exec] Completed shader test!
> [exec] Return code: 7
> [exec] Result: 7
>BUILD SUCCESSFUL
>Total time: 8 seconds
>Finished: SUCCESS
>
>Well, that's a difference.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 22:40 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Nice. Thanks for sticking with it.
>
>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>>Tomcat is running as a Windows Service).
>>
>>- Created a simple job, on the "master" node, than starts
>>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>>target
>>- Jenkins output of the job:
>>
>>pixelbender-compile:
>> [exec] AIF Internal exception
>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>> [exec] Device: 008BB2BC has video RAM(MB): 512
>> [exec] Return code: 1
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>>
>>So I am getting the same error.
>>
>>Om says "master" does not get a window, so this result seems to be
>>normal.
>>
>>I am trying now to create a slave node and run the job on it.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 22:07
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>It was from the command line (cmd ant ), so gets a window.
>>
>>I am trying now from Jenkins service, but needs to install it first...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise
>>needed
>>
>>Maurice,
>>
>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>I think there is a difference. On Jenkins, the main executor (master)
>>does not get a window. Only slave executors are configured to get a
>>window.
>>Whereas Cygwin does not have such restrictions.
>>
>>Thanks,
>>Om
>>
>>
>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> I have no idea what to do with that information. But thanks for
>>>trying.
>>>
>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>> <ma...@systar.com>
>>> wrote:
>>>
>>> >So this is the output from the b.a.o box:
>>> >
>>> >pixelbender-compile:
>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>> > [exec] AIF Internal exception
>>> > [exec] Return code: 1
>>> > [exec] Result: 1
>>> >
>>> >To be compared to the output on my PC:
>>> >pixelbender-compile
>>> >exec
>>> >Device: 00633CEC has video RAM(MB): 512
>>> >Vendor string: NVIDIA Corporation
>>> >Renderer string: NVS 4200M/PCI/SSE2
>>> >Version string: 3.0.0
>>> >
>>> >OpenGL version as determined by Extensionator...
>>> >OpenGL Version 3.0
>>> >Has NPOT support: TRUE
>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>>> >test!
>>> >Return code: 7
>>> >Result: 7
>>> >Exec
>>> >
>>> >That does not tell much, except that there seems to be an issue
>>> >with accessing the GPU.
>>> >
>>> >Shall I un-commit the change now, or do you want to perform more
>>> >tests
>>>?
>>> >
>>> >Maurice
>>> >
>>> >-----Message d'origine-----
>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
>>> >RE: [Builds/Jenkins] Help and advise needed
>>> >
>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>> >
>>> >Can you try on your side, please ?
>>> >
>>> >-----Message d'origine-----
>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >décembre
>>> >2013
>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>> >advise needed
>>> >
>>> >Won't that break Mac builds?
>>> >
>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>> ><ma...@systar.com>
>>> >wrote:
>>> >
>>> >>Alex, it's one line to change in the build.xml
>>> >>
>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>> >>
>>> >>I will give it a try and we will know in 15 min.
>>> >>
>>> >>I am sure the result will be interesting.
>>> >>
>>> >>Anyway, it can't hurt ;-)
>>> >>
>>> >>Maurice
>>> >>
>>> >>-----Message d'origine-----
>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>décembre
>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>Help and advise needed
>>> >>
>>> >>I think I'll wait to see how Gavin responds to Erik's latest request.
>>> >>
>>> >>BTW, thanks for finding out about the tool.
>>> >>
>>> >>-Alex
>>> >>
>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>> >><ma...@systar.com>
>>> >>wrote:
>>> >>
>>> >>>Sure, if you can ask him.
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>décembre
>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>Help and advise needed
>>> >>>
>>> >>>Might be simpler just to ask Gavin to run the tool?
>>> >>>
>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>> >>><ma...@systar.com>
>>> >>>wrote:
>>> >>>
>>> >>>>There is a utility in pixel bender toolkit directory called
>>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>> >>>>
>>> >>>>Console output on my laptop is below:
>>> >>>>
>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>> >>>>Toolkit
>>> >>>>2>sniffer_gpu.exe
>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>> >>>>Vendor string: NVIDIA Corporation
>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>> >>>>Version string: 3.0.0
>>> >>>>
>>> >>>>OpenGL version as determined by Extensionator...
>>> >>>>OpenGL Version 3.0
>>> >>>>Has NPOT support: TRUE
>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>>>test!
>>> >>>>Return code: 7
>>> >>>>
>>> >>>>Maybe we could temporarily modify the build to run this utility
>>> >>>>and show the output on the b.a.o vm.
>>> >>>>
>>> >>>>WDYT ?
>>> >>>>
>>> >>>>Maurice
>>> >>>>
>>> >>>>-----Message d'origine-----
>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>>décembre
>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>>Help and advise needed
>>> >>>>
>>> >>>>I don't think we actually know the cause of the problem. I am
>>> >>>>going to continue to spend cycles to try to find out though.
>>> >>>>
>>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>>> >>>>sure if it will cost Om money to run a builds server.
>>> >>>>
>>> >>>>-Alex
>>> >>>>
>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>> >>>><ma...@systar.com>
>>> >>>>wrote:
>>> >>>>
>>> >>>>>I understand that.
>>> >>>>>
>>> >>>>>Actually, my "understanding" on this issue was that pixel
>>> >>>>>bender compiler required some sort of hardware configuration
>>> >>>>>(OpenGL,
>>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>> >>>>>slave node, so that's why the build was failing, and the
>>> >>>>>Apache Infra was reluctant to let us modify anything, or even
>>> >>>>>access the VM ourselves.
>>> >>>>>So that's why I was proposing a "software only" solution.
>>> >>>>>
>>> >>>>>Now, it seems from what Om is saying that we can set up and use
>>> >>>>>our own Jenkins slave node VM.
>>> >>>>>
>>> >>>>>That, of course, is much preferable...
>>> >>>>>
>>> >>>>>Maurice
>>> >>>>>
>>> >>>>>-----Message d'origine-----
>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>> >>>>>10 décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>> >>>>>[Builds/Jenkins] Help and advise needed
>>> >>>>>
>>> >>>>>Maurice,
>>> >>>>>
>>> >>>>>Your help is very much appreciated!
>>> >>>>>
>>> >>>>>I put "legal" in quotes, the issue is not really one of the
>>> >>>>>law, more of the rules. An Apache release is supposed to be
>>> >>>>>'source only', and we if we can produce needed binaries from
>>> >>>>>source, we keep only the source, not the artefacts themselves in the repo.
>>> >>>>>
>>> >>>>>
>>> >>>>>EdB
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>> >>>>><ma...@systar.com> wrote:
>>> >>>>>>>In addition to the various "legal" issues with binaries in
>>> >>>>>>>the
>>>repo.
>>> >>>>>> I understand it's not a good idea to have binaries in the
>>> >>>>>>repo, so I won't insist.
>>> >>>>>> But please can you explain what are the legal issues of
>>> >>>>>>having binaries in the repo? Is this because of Adobe, or ASF rules ?
>>> >>>>>>
>>> >>>>>> On a side note, I was just trying to help, with my limited
>>> >>>>>> understanding and knowledge, and because the email thread was
>>> >>>>>> titled "help and advise needed" ;-)
>>> >>>>>>
>>> >>>>>> Regards,
>>> >>>>>>
>>> >>>>>> Maurice
>>> >>>>>>
>>> >>>>>> -----Message d'origine-----
>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>> >>>>>>
>>> >>>>>> In addition to the various "legal" issues with binaries in
>>> >>>>>>the repo, we'd be masking the cause of this failure. In order
>>> >>>>>>to prevent further deterioration of the build process, we need
>>> >>>>>>to figure out what went wrong and fix it.
>>> >>>>>>
>>> >>>>>> EdB
>>> >>>>>>
>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>>>FR...
>>> >>>>>> Took me while to figure out that I hadn't gone insane or if
>>> >>>>>> my keyboard was broken ;-)
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>> >>>>>><ma...@systar.com> wrote:
>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>>complain.
>>> >>>>>>>
>>> >>>>>>> I don't understand.
>>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>>> >>>>>>>
>>> >>>>>>> [From the other emai]
>>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>>> >>>>>>>>pbj files were removed during the initial release audit.
>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>>files.
>>> >>>>>>>>But we could borrow them from a prior release package
>>>temporarily.
>>> >>>>>>>
>>> >>>>>>>>So we could make the compilation conditional on a env
>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>> >>>>>>>>Yes but ...
>>> >>>>>>>
>>> >>>>>>> Alex, the conversation is getting out synch, so I am not
>>> >>>>>>>sure that I have understood what you said.
>>> >>>>>>>
>>> >>>>>>> So can we include the pbj in the repo, and have a parameter
>>> >>>>>>>to conditionally compile the pbj ?
>>> >>>>>>> - This parameter would be set by default to do the
>>> >>>>>>>compilation (so that folks can recompile)
>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Maurice
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> --
>>> >>>>>> Ix Multimedia Software
>>> >>>>>>
>>> >>>>>> Jan Luykenstraat 27
>>> >>>>>> 3521 VB Utrecht
>>> >>>>>>
>>> >>>>>> T. 06-51952295
>>> >>>>>> I. www.ixsoftware.nl
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>>--
>>> >>>>>Ix Multimedia Software
>>> >>>>>
>>> >>>>>Jan Luykenstraat 27
>>> >>>>>3521 VB Utrecht
>>> >>>>>
>>> >>>>>T. 06-51952295
>>> >>>>>I. www.ixsoftware.nl
>>> >>>>
>>> >>>
>>> >>
>>> >
>>>
>>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
InterestingŠ Is there a way to configure a slave so it doesn't get a
window? Maybe Infra changed some default on builds.a.o.
On 12/10/13 1:44 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Now run the same build on a slave node (that gets a windows "jenkins
>slave agent", that is visible on the desktop ):
>
>Remote build on windowsSlave1 in workspace
>D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
>[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile &&
>exit %%ERRORLEVEL%%"'
>ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m
>-XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled
>-Djava.net.preferIPv4Stack=true
>Buildfile:
>D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.xml
>
>pixelbender-compile:
> [exec] Device: 005EC1C4 has video RAM(MB): 512
> [exec] Vendor string: NVIDIA Corporation
> [exec] Renderer string: NVS 4200M/PCI/SSE2
> [exec] Version string: 3.0.0
> [exec]
> [exec] OpenGL version as determined by Extensionator...
> [exec] OpenGL Version 3.0
> [exec] Has NPOT support: TRUE
> [exec] Has Framebuffer Obeject Extension support: TRUE
> [exec] Completed shader test!
> [exec] Return code: 7
> [exec] Result: 7
>BUILD SUCCESSFUL
>Total time: 8 seconds
>Finished: SUCCESS
>
>Well, that's a difference.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 22:40
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Nice. Thanks for sticking with it.
>
>On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>>Tomcat is running as a Windows Service).
>>
>>- Created a simple job, on the "master" node, than starts
>>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>>target
>>- Jenkins output of the job:
>>
>>pixelbender-compile:
>> [exec] AIF Internal exception
>> [exec] Device: 008BB2BC has video RAM(MB): 3844
>> [exec] Device: 008BB2BC has video RAM(MB): 512
>> [exec] Return code: 1
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>>
>>So I am getting the same error.
>>
>>Om says "master" does not get a window, so this result seems to be
>>normal.
>>
>>I am trying now to create a slave node and run the job on it.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>Envoyé : mardi 10 décembre 2013 22:07
>>À : dev@flex.apache.org
>>Objet : RE: [Builds/Jenkins] Help and advise needed
>>
>>It was from the command line (cmd ant ), so gets a window.
>>
>>I am trying now from Jenkins service, but needs to install it first...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
>>
>>Maurice,
>>
>>When you ran it on your machine, was it on Cygwin or from Jenkins?
>>I think there is a difference. On Jenkins, the main executor (master)
>>does not get a window. Only slave executors are configured to get a
>>window.
>>Whereas Cygwin does not have such restrictions.
>>
>>Thanks,
>>Om
>>
>>
>>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>>
>>> I have no idea what to do with that information. But thanks for
>>>trying.
>>>
>>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>>> <ma...@systar.com>
>>> wrote:
>>>
>>> >So this is the output from the b.a.o box:
>>> >
>>> >pixelbender-compile:
>>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>>> > [exec] AIF Internal exception
>>> > [exec] Return code: 1
>>> > [exec] Result: 1
>>> >
>>> >To be compared to the output on my PC:
>>> >pixelbender-compile
>>> >exec
>>> >Device: 00633CEC has video RAM(MB): 512
>>> >Vendor string: NVIDIA Corporation
>>> >Renderer string: NVS 4200M/PCI/SSE2
>>> >Version string: 3.0.0
>>> >
>>> >OpenGL version as determined by Extensionator...
>>> >OpenGL Version 3.0
>>> >Has NPOT support: TRUE
>>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>>> >test!
>>> >Return code: 7
>>> >Result: 7
>>> >Exec
>>> >
>>> >That does not tell much, except that there seems to be an issue with
>>> >accessing the GPU.
>>> >
>>> >Shall I un-commit the change now, or do you want to perform more
>>> >tests
>>>?
>>> >
>>> >Maurice
>>> >
>>> >-----Message d'origine-----
>>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
>>> >RE: [Builds/Jenkins] Help and advise needed
>>> >
>>> >I don't have a Mac with ApacheFlex SDK for testing.
>>> >
>>> >Can you try on your side, please ?
>>> >
>>> >-----Message d'origine-----
>>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>> >2013
>>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>>> >advise needed
>>> >
>>> >Won't that break Mac builds?
>>> >
>>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>>> ><ma...@systar.com>
>>> >wrote:
>>> >
>>> >>Alex, it's one line to change in the build.xml
>>> >>
>>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>> >>
>>> >>I will give it a try and we will know in 15 min.
>>> >>
>>> >>I am sure the result will be interesting.
>>> >>
>>> >>Anyway, it can't hurt ;-)
>>> >>
>>> >>Maurice
>>> >>
>>> >>-----Message d'origine-----
>>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>décembre
>>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>Help and advise needed
>>> >>
>>> >>I think I'll wait to see how Gavin responds to Erik's latest request.
>>> >>
>>> >>BTW, thanks for finding out about the tool.
>>> >>
>>> >>-Alex
>>> >>
>>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>>> >><ma...@systar.com>
>>> >>wrote:
>>> >>
>>> >>>Sure, if you can ask him.
>>> >>>
>>> >>>Maurice
>>> >>>
>>> >>>-----Message d'origine-----
>>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>décembre
>>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>Help and advise needed
>>> >>>
>>> >>>Might be simpler just to ask Gavin to run the tool?
>>> >>>
>>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>>> >>><ma...@systar.com>
>>> >>>wrote:
>>> >>>
>>> >>>>There is a utility in pixel bender toolkit directory called
>>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>> >>>>
>>> >>>>Console output on my laptop is below:
>>> >>>>
>>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>> >>>>Toolkit
>>> >>>>2>sniffer_gpu.exe
>>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>>> >>>>Vendor string: NVIDIA Corporation
>>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>>> >>>>Version string: 3.0.0
>>> >>>>
>>> >>>>OpenGL version as determined by Extensionator...
>>> >>>>OpenGL Version 3.0
>>> >>>>Has NPOT support: TRUE
>>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>>>test!
>>> >>>>Return code: 7
>>> >>>>
>>> >>>>Maybe we could temporarily modify the build to run this utility
>>> >>>>and show the output on the b.a.o vm.
>>> >>>>
>>> >>>>WDYT ?
>>> >>>>
>>> >>>>Maurice
>>> >>>>
>>> >>>>-----Message d'origine-----
>>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>>> >>>>décembre
>>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>>> >>>>Help and advise needed
>>> >>>>
>>> >>>>I don't think we actually know the cause of the problem. I am
>>> >>>>going to continue to spend cycles to try to find out though.
>>> >>>>
>>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>>> >>>>sure if it will cost Om money to run a builds server.
>>> >>>>
>>> >>>>-Alex
>>> >>>>
>>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>>> >>>><ma...@systar.com>
>>> >>>>wrote:
>>> >>>>
>>> >>>>>I understand that.
>>> >>>>>
>>> >>>>>Actually, my "understanding" on this issue was that pixel bender
>>> >>>>>compiler required some sort of hardware configuration (OpenGL,
>>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>> >>>>>slave node, so that's why the build was failing, and the Apache
>>> >>>>>Infra was reluctant to let us modify anything, or even access
>>> >>>>>the VM ourselves.
>>> >>>>>So that's why I was proposing a "software only" solution.
>>> >>>>>
>>> >>>>>Now, it seems from what Om is saying that we can set up and use
>>> >>>>>our own Jenkins slave node VM.
>>> >>>>>
>>> >>>>>That, of course, is much preferable...
>>> >>>>>
>>> >>>>>Maurice
>>> >>>>>
>>> >>>>>-----Message d'origine-----
>>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>> >>>>>[Builds/Jenkins] Help and advise needed
>>> >>>>>
>>> >>>>>Maurice,
>>> >>>>>
>>> >>>>>Your help is very much appreciated!
>>> >>>>>
>>> >>>>>I put "legal" in quotes, the issue is not really one of the law,
>>> >>>>>more of the rules. An Apache release is supposed to be 'source
>>> >>>>>only', and we if we can produce needed binaries from source, we
>>> >>>>>keep only the source, not the artefacts themselves in the repo.
>>> >>>>>
>>> >>>>>
>>> >>>>>EdB
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>> >>>>><ma...@systar.com> wrote:
>>> >>>>>>>In addition to the various "legal" issues with binaries in the
>>>repo.
>>> >>>>>> I understand it's not a good idea to have binaries in the
>>> >>>>>>repo, so I won't insist.
>>> >>>>>> But please can you explain what are the legal issues of having
>>> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>> >>>>>>
>>> >>>>>> On a side note, I was just trying to help, with my limited
>>> >>>>>> understanding and knowledge, and because the email thread was
>>> >>>>>> titled "help and advise needed" ;-)
>>> >>>>>>
>>> >>>>>> Regards,
>>> >>>>>>
>>> >>>>>> Maurice
>>> >>>>>>
>>> >>>>>> -----Message d'origine-----
>>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> >>>>>> [Builds/Jenkins] Help and advise needed
>>> >>>>>>
>>> >>>>>> In addition to the various "legal" issues with binaries in the
>>> >>>>>>repo, we'd be masking the cause of this failure. In order to
>>> >>>>>>prevent further deterioration of the build process, we need to
>>> >>>>>>figure out what went wrong and fix it.
>>> >>>>>>
>>> >>>>>> EdB
>>> >>>>>>
>>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>>>FR...
>>> >>>>>> Took me while to figure out that I hadn't gone insane or if my
>>> >>>>>> keyboard was broken ;-)
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>> >>>>>><ma...@systar.com> wrote:
>>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>>complain.
>>> >>>>>>>
>>> >>>>>>> I don't understand.
>>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>>> >>>>>>>
>>> >>>>>>> [From the other emai]
>>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>>> >>>>>>>>pbj files were removed during the initial release audit.
>>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>>files.
>>> >>>>>>>>But we could borrow them from a prior release package
>>>temporarily.
>>> >>>>>>>
>>> >>>>>>>>So we could make the compilation conditional on a env
>>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>>> >>>>>>>>Yes but ...
>>> >>>>>>>
>>> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
>>> >>>>>>>that I have understood what you said.
>>> >>>>>>>
>>> >>>>>>> So can we include the pbj in the repo, and have a parameter
>>> >>>>>>>to conditionally compile the pbj ?
>>> >>>>>>> - This parameter would be set by default to do the
>>> >>>>>>>compilation (so that folks can recompile)
>>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>> >>>>>>>
>>> >>>>>>>
>>> >>>>>>> Maurice
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> --
>>> >>>>>> Ix Multimedia Software
>>> >>>>>>
>>> >>>>>> Jan Luykenstraat 27
>>> >>>>>> 3521 VB Utrecht
>>> >>>>>>
>>> >>>>>> T. 06-51952295
>>> >>>>>> I. www.ixsoftware.nl
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>>--
>>> >>>>>Ix Multimedia Software
>>> >>>>>
>>> >>>>>Jan Luykenstraat 27
>>> >>>>>3521 VB Utrecht
>>> >>>>>
>>> >>>>>T. 06-51952295
>>> >>>>>I. www.ixsoftware.nl
>>> >>>>
>>> >>>
>>> >>
>>> >
>>>
>>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Now run the same build on a slave node (that gets a windows "jenkins slave agent", that is visible on the desktop ):
Remote build on windowsSlave1 in workspace D:\Jenkins\node1\workspace\workspace\Test_pixel_bender
[framework] $ cmd.exe /C '"ant.bat -file build.xml pixelbender-compile && exit %%ERRORLEVEL%%"'
ANT_OPTS=-Xms256m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=512m -XX:MaxHeapSize=512m -XX:+CMSClassUnloadingEnabled -Djava.net.preferIPv4Stack=true
Buildfile: D:\ApacheFlex\git_source\flex-sdk\frameworks\projects\framework\build.xml
pixelbender-compile:
[exec] Device: 005EC1C4 has video RAM(MB): 512
[exec] Vendor string: NVIDIA Corporation
[exec] Renderer string: NVS 4200M/PCI/SSE2
[exec] Version string: 3.0.0
[exec]
[exec] OpenGL version as determined by Extensionator...
[exec] OpenGL Version 3.0
[exec] Has NPOT support: TRUE
[exec] Has Framebuffer Obeject Extension support: TRUE
[exec] Completed shader test!
[exec] Return code: 7
[exec] Result: 7
BUILD SUCCESSFUL
Total time: 8 seconds
Finished: SUCCESS
Well, that's a difference.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 22:40
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Nice. Thanks for sticking with it.
On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>Tomcat is running as a Windows Service).
>
>- Created a simple job, on the "master" node, than starts
>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>target
>- Jenkins output of the job:
>
>pixelbender-compile:
> [exec] AIF Internal exception
> [exec] Device: 008BB2BC has video RAM(MB): 3844
> [exec] Device: 008BB2BC has video RAM(MB): 512
> [exec] Return code: 1
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
>
>So I am getting the same error.
>
>Om says "master" does not get a window, so this result seems to be normal.
>
>I am trying now to create a slave node and run the job on it.
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 22:07
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>It was from the command line (cmd ant ), so gets a window.
>
>I am trying now from Jenkins service, but needs to install it first...
>
>Maurice
>
>-----Message d'origine-----
>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de
>OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À :
>dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Maurice,
>
>When you ran it on your machine, was it on Cygwin or from Jenkins?
>I think there is a difference. On Jenkins, the main executor (master)
>does not get a window. Only slave executors are configured to get a
>window.
>Whereas Cygwin does not have such restrictions.
>
>Thanks,
>Om
>
>
>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>
>> I have no idea what to do with that information. But thanks for trying.
>>
>> On 12/10/13 11:44 AM, "Maurice Amsellem"
>> <ma...@systar.com>
>> wrote:
>>
>> >So this is the output from the b.a.o box:
>> >
>> >pixelbender-compile:
>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>> > [exec] AIF Internal exception
>> > [exec] Return code: 1
>> > [exec] Result: 1
>> >
>> >To be compared to the output on my PC:
>> >pixelbender-compile
>> >exec
>> >Device: 00633CEC has video RAM(MB): 512
>> >Vendor string: NVIDIA Corporation
>> >Renderer string: NVS 4200M/PCI/SSE2
>> >Version string: 3.0.0
>> >
>> >OpenGL version as determined by Extensionator...
>> >OpenGL Version 3.0
>> >Has NPOT support: TRUE
>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>> >test!
>> >Return code: 7
>> >Result: 7
>> >Exec
>> >
>> >That does not tell much, except that there seems to be an issue with
>> >accessing the GPU.
>> >
>> >Shall I un-commit the change now, or do you want to perform more
>> >tests
>>?
>> >
>> >Maurice
>> >
>> >-----Message d'origine-----
>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
>> >RE: [Builds/Jenkins] Help and advise needed
>> >
>> >I don't have a Mac with ApacheFlex SDK for testing.
>> >
>> >Can you try on your side, please ?
>> >
>> >-----Message d'origine-----
>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>> >2013
>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>> >advise needed
>> >
>> >Won't that break Mac builds?
>> >
>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>> ><ma...@systar.com>
>> >wrote:
>> >
>> >>Alex, it's one line to change in the build.xml
>> >>
>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>> >>
>> >>I will give it a try and we will know in 15 min.
>> >>
>> >>I am sure the result will be interesting.
>> >>
>> >>Anyway, it can't hurt ;-)
>> >>
>> >>Maurice
>> >>
>> >>-----Message d'origine-----
>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>décembre
>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>Help and advise needed
>> >>
>> >>I think I'll wait to see how Gavin responds to Erik's latest request.
>> >>
>> >>BTW, thanks for finding out about the tool.
>> >>
>> >>-Alex
>> >>
>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>> >><ma...@systar.com>
>> >>wrote:
>> >>
>> >>>Sure, if you can ask him.
>> >>>
>> >>>Maurice
>> >>>
>> >>>-----Message d'origine-----
>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>décembre
>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>Help and advise needed
>> >>>
>> >>>Might be simpler just to ask Gavin to run the tool?
>> >>>
>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>> >>><ma...@systar.com>
>> >>>wrote:
>> >>>
>> >>>>There is a utility in pixel bender toolkit directory called
>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>> >>>>
>> >>>>Console output on my laptop is below:
>> >>>>
>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>> >>>>Toolkit
>> >>>>2>sniffer_gpu.exe
>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>> >>>>Vendor string: NVIDIA Corporation
>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>> >>>>Version string: 3.0.0
>> >>>>
>> >>>>OpenGL version as determined by Extensionator...
>> >>>>OpenGL Version 3.0
>> >>>>Has NPOT support: TRUE
>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>>test!
>> >>>>Return code: 7
>> >>>>
>> >>>>Maybe we could temporarily modify the build to run this utility
>> >>>>and show the output on the b.a.o vm.
>> >>>>
>> >>>>WDYT ?
>> >>>>
>> >>>>Maurice
>> >>>>
>> >>>>-----Message d'origine-----
>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>>décembre
>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>>Help and advise needed
>> >>>>
>> >>>>I don't think we actually know the cause of the problem. I am
>> >>>>going to continue to spend cycles to try to find out though.
>> >>>>
>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>> >>>>sure if it will cost Om money to run a builds server.
>> >>>>
>> >>>>-Alex
>> >>>>
>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>> >>>><ma...@systar.com>
>> >>>>wrote:
>> >>>>
>> >>>>>I understand that.
>> >>>>>
>> >>>>>Actually, my "understanding" on this issue was that pixel bender
>> >>>>>compiler required some sort of hardware configuration (OpenGL,
>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>> >>>>>slave node, so that's why the build was failing, and the Apache
>> >>>>>Infra was reluctant to let us modify anything, or even access
>> >>>>>the VM ourselves.
>> >>>>>So that's why I was proposing a "software only" solution.
>> >>>>>
>> >>>>>Now, it seems from what Om is saying that we can set up and use
>> >>>>>our own Jenkins slave node VM.
>> >>>>>
>> >>>>>That, of course, is much preferable...
>> >>>>>
>> >>>>>Maurice
>> >>>>>
>> >>>>>-----Message d'origine-----
>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>> >>>>>[Builds/Jenkins] Help and advise needed
>> >>>>>
>> >>>>>Maurice,
>> >>>>>
>> >>>>>Your help is very much appreciated!
>> >>>>>
>> >>>>>I put "legal" in quotes, the issue is not really one of the law,
>> >>>>>more of the rules. An Apache release is supposed to be 'source
>> >>>>>only', and we if we can produce needed binaries from source, we
>> >>>>>keep only the source, not the artefacts themselves in the repo.
>> >>>>>
>> >>>>>
>> >>>>>EdB
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>> >>>>><ma...@systar.com> wrote:
>> >>>>>>>In addition to the various "legal" issues with binaries in the
>>repo.
>> >>>>>> I understand it's not a good idea to have binaries in the
>> >>>>>>repo, so I won't insist.
>> >>>>>> But please can you explain what are the legal issues of having
>> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>> >>>>>>
>> >>>>>> On a side note, I was just trying to help, with my limited
>> >>>>>> understanding and knowledge, and because the email thread was
>> >>>>>> titled "help and advise needed" ;-)
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>>
>> >>>>>> Maurice
>> >>>>>>
>> >>>>>> -----Message d'origine-----
>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> >>>>>> [Builds/Jenkins] Help and advise needed
>> >>>>>>
>> >>>>>> In addition to the various "legal" issues with binaries in the
>> >>>>>>repo, we'd be masking the cause of this failure. In order to
>> >>>>>>prevent further deterioration of the build process, we need to
>> >>>>>>figure out what went wrong and fix it.
>> >>>>>>
>> >>>>>> EdB
>> >>>>>>
>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>>FR...
>> >>>>>> Took me while to figure out that I hadn't gone insane or if my
>> >>>>>> keyboard was broken ;-)
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>> >>>>>><ma...@systar.com> wrote:
>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>complain.
>> >>>>>>>
>> >>>>>>> I don't understand.
>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>> >>>>>>>
>> >>>>>>> [From the other emai]
>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>> >>>>>>>>pbj files were removed during the initial release audit.
>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>files.
>> >>>>>>>>But we could borrow them from a prior release package
>>temporarily.
>> >>>>>>>
>> >>>>>>>>So we could make the compilation conditional on a env
>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>> >>>>>>>>Yes but ...
>> >>>>>>>
>> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
>> >>>>>>>that I have understood what you said.
>> >>>>>>>
>> >>>>>>> So can we include the pbj in the repo, and have a parameter
>> >>>>>>>to conditionally compile the pbj ?
>> >>>>>>> - This parameter would be set by default to do the
>> >>>>>>>compilation (so that folks can recompile)
>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Maurice
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Ix Multimedia Software
>> >>>>>>
>> >>>>>> Jan Luykenstraat 27
>> >>>>>> 3521 VB Utrecht
>> >>>>>>
>> >>>>>> T. 06-51952295
>> >>>>>> I. www.ixsoftware.nl
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>--
>> >>>>>Ix Multimedia Software
>> >>>>>
>> >>>>>Jan Luykenstraat 27
>> >>>>>3521 VB Utrecht
>> >>>>>
>> >>>>>T. 06-51952295
>> >>>>>I. www.ixsoftware.nl
>> >>>>
>> >>>
>> >>
>> >
>>
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Nice. Thanks for sticking with it.
On 12/10/13 1:21 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>So I just installed Jenkins on my PC, running inside Tomcat 6 64bit (
>Tomcat is running as a Windows Service).
>
>- Created a simple job, on the "master" node, than starts
>flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile"
>target
>- Jenkins output of the job:
>
>pixelbender-compile:
> [exec] AIF Internal exception
> [exec] Device: 008BB2BC has video RAM(MB): 3844
> [exec] Device: 008BB2BC has video RAM(MB): 512
> [exec] Return code: 1
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
>
>So I am getting the same error.
>
>Om says "master" does not get a window, so this result seems to be normal.
>
>I am trying now to create a slave node and run the job on it.
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 22:07
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>It was from the command line (cmd ant ), so gets a window.
>
>I am trying now from Jenkins service, but needs to install it first...
>
>Maurice
>
>-----Message d'origine-----
>De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash
>Muppirala Envoyé : mardi 10 décembre 2013 20:49 À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Maurice,
>
>When you ran it on your machine, was it on Cygwin or from Jenkins?
>I think there is a difference. On Jenkins, the main executor (master)
>does not get a window. Only slave executors are configured to get a
>window.
>Whereas Cygwin does not have such restrictions.
>
>Thanks,
>Om
>
>
>On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
>
>> I have no idea what to do with that information. But thanks for trying.
>>
>> On 12/10/13 11:44 AM, "Maurice Amsellem" <ma...@systar.com>
>> wrote:
>>
>> >So this is the output from the b.a.o box:
>> >
>> >pixelbender-compile:
>> > [exec] Device: 004C5F24 has video RAM(MB): 3736
>> > [exec] AIF Internal exception
>> > [exec] Return code: 1
>> > [exec] Result: 1
>> >
>> >To be compared to the output on my PC:
>> >pixelbender-compile
>> >exec
>> >Device: 00633CEC has video RAM(MB): 512
>> >Vendor string: NVIDIA Corporation
>> >Renderer string: NVS 4200M/PCI/SSE2
>> >Version string: 3.0.0
>> >
>> >OpenGL version as determined by Extensionator...
>> >OpenGL Version 3.0
>> >Has NPOT support: TRUE
>> >Has Framebuffer Obeject Extension support: TRUE Completed shader
>> >test!
>> >Return code: 7
>> >Result: 7
>> >Exec
>> >
>> >That does not tell much, except that there seems to be an issue with
>> >accessing the GPU.
>> >
>> >Shall I un-commit the change now, or do you want to perform more tests
>>?
>> >
>> >Maurice
>> >
>> >-----Message d'origine-----
>> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
>> >RE: [Builds/Jenkins] Help and advise needed
>> >
>> >I don't have a Mac with ApacheFlex SDK for testing.
>> >
>> >Can you try on your side, please ?
>> >
>> >-----Message d'origine-----
>> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>> >2013
>> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>> >advise needed
>> >
>> >Won't that break Mac builds?
>> >
>> >On 12/10/13 11:32 AM, "Maurice Amsellem"
>> ><ma...@systar.com>
>> >wrote:
>> >
>> >>Alex, it's one line to change in the build.xml
>> >>
>> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>> >>
>> >>I will give it a try and we will know in 15 min.
>> >>
>> >>I am sure the result will be interesting.
>> >>
>> >>Anyway, it can't hurt ;-)
>> >>
>> >>Maurice
>> >>
>> >>-----Message d'origine-----
>> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>> >>and advise needed
>> >>
>> >>I think I'll wait to see how Gavin responds to Erik's latest request.
>> >>
>> >>BTW, thanks for finding out about the tool.
>> >>
>> >>-Alex
>> >>
>> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
>> >><ma...@systar.com>
>> >>wrote:
>> >>
>> >>>Sure, if you can ask him.
>> >>>
>> >>>Maurice
>> >>>
>> >>>-----Message d'origine-----
>> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>décembre
>> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>Help and advise needed
>> >>>
>> >>>Might be simpler just to ask Gavin to run the tool?
>> >>>
>> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
>> >>><ma...@systar.com>
>> >>>wrote:
>> >>>
>> >>>>There is a utility in pixel bender toolkit directory called
>> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>> >>>>
>> >>>>Console output on my laptop is below:
>> >>>>
>> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>> >>>>Toolkit
>> >>>>2>sniffer_gpu.exe
>> >>>>Device: 0058A9F4 has video RAM(MB): 512
>> >>>>Vendor string: NVIDIA Corporation
>> >>>>Renderer string: NVS 4200M/PCI/SSE2
>> >>>>Version string: 3.0.0
>> >>>>
>> >>>>OpenGL version as determined by Extensionator...
>> >>>>OpenGL Version 3.0
>> >>>>Has NPOT support: TRUE
>> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader
>>test!
>> >>>>Return code: 7
>> >>>>
>> >>>>Maybe we could temporarily modify the build to run this utility
>> >>>>and show the output on the b.a.o vm.
>> >>>>
>> >>>>WDYT ?
>> >>>>
>> >>>>Maurice
>> >>>>
>> >>>>-----Message d'origine-----
>> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
>> >>>>décembre
>> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
>> >>>>Help and advise needed
>> >>>>
>> >>>>I don't think we actually know the cause of the problem. I am
>> >>>>going to continue to spend cycles to try to find out though.
>> >>>>
>> >>>>It would be nice to have an alternative to builds.a.o. I'm not
>> >>>>sure if it will cost Om money to run a builds server.
>> >>>>
>> >>>>-Alex
>> >>>>
>> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
>> >>>><ma...@systar.com>
>> >>>>wrote:
>> >>>>
>> >>>>>I understand that.
>> >>>>>
>> >>>>>Actually, my "understanding" on this issue was that pixel bender
>> >>>>>compiler required some sort of hardware configuration (OpenGL,
>> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>> >>>>>slave node, so that's why the build was failing, and the Apache
>> >>>>>Infra was reluctant to let us modify anything, or even access the
>> >>>>>VM ourselves.
>> >>>>>So that's why I was proposing a "software only" solution.
>> >>>>>
>> >>>>>Now, it seems from what Om is saying that we can set up and use
>> >>>>>our own Jenkins slave node VM.
>> >>>>>
>> >>>>>That, of course, is much preferable...
>> >>>>>
>> >>>>>Maurice
>> >>>>>
>> >>>>>-----Message d'origine-----
>> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>> >>>>>[Builds/Jenkins] Help and advise needed
>> >>>>>
>> >>>>>Maurice,
>> >>>>>
>> >>>>>Your help is very much appreciated!
>> >>>>>
>> >>>>>I put "legal" in quotes, the issue is not really one of the law,
>> >>>>>more of the rules. An Apache release is supposed to be 'source
>> >>>>>only', and we if we can produce needed binaries from source, we
>> >>>>>keep only the source, not the artefacts themselves in the repo.
>> >>>>>
>> >>>>>
>> >>>>>EdB
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>> >>>>><ma...@systar.com> wrote:
>> >>>>>>>In addition to the various "legal" issues with binaries in the
>>repo.
>> >>>>>> I understand it's not a good idea to have binaries in the repo,
>> >>>>>>so I won't insist.
>> >>>>>> But please can you explain what are the legal issues of having
>> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>> >>>>>>
>> >>>>>> On a side note, I was just trying to help, with my limited
>> >>>>>> understanding and knowledge, and because the email thread was
>> >>>>>> titled "help and advise needed" ;-)
>> >>>>>>
>> >>>>>> Regards,
>> >>>>>>
>> >>>>>> Maurice
>> >>>>>>
>> >>>>>> -----Message d'origine-----
>> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
>> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> >>>>>> [Builds/Jenkins] Help and advise needed
>> >>>>>>
>> >>>>>> In addition to the various "legal" issues with binaries in the
>> >>>>>>repo, we'd be masking the cause of this failure. In order to
>> >>>>>>prevent further deterioration of the build process, we need to
>> >>>>>>figure out what went wrong and fix it.
>> >>>>>>
>> >>>>>> EdB
>> >>>>>>
>> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to
>>FR...
>> >>>>>> Took me while to figure out that I hadn't gone insane or if my
>> >>>>>> keyboard was broken ;-)
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>> >>>>>><ma...@systar.com> wrote:
>> >>>>>>>> someone who does use the pbj's will grab the nightly and
>>complain.
>> >>>>>>>
>> >>>>>>> I don't understand.
>> >>>>>>> Why would someone complain if the pbj's are in the nightly?
>> >>>>>>>
>> >>>>>>> [From the other emai]
>> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
>> >>>>>>>>pbj files were removed during the initial release audit.
>> >>>>>>>>I don't think a workaround can involve checking in the pbj
>>files.
>> >>>>>>>>But we could borrow them from a prior release package
>>temporarily.
>> >>>>>>>
>> >>>>>>>>So we could make the compilation conditional on a env
>> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
>> >>>>>>>>Yes but ...
>> >>>>>>>
>> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
>> >>>>>>>that I have understood what you said.
>> >>>>>>>
>> >>>>>>> So can we include the pbj in the repo, and have a parameter to
>> >>>>>>>conditionally compile the pbj ?
>> >>>>>>> - This parameter would be set by default to do the compilation
>> >>>>>>>(so that folks can recompile)
>> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> Maurice
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Ix Multimedia Software
>> >>>>>>
>> >>>>>> Jan Luykenstraat 27
>> >>>>>> 3521 VB Utrecht
>> >>>>>>
>> >>>>>> T. 06-51952295
>> >>>>>> I. www.ixsoftware.nl
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>>--
>> >>>>>Ix Multimedia Software
>> >>>>>
>> >>>>>Jan Luykenstraat 27
>> >>>>>3521 VB Utrecht
>> >>>>>
>> >>>>>T. 06-51952295
>> >>>>>I. www.ixsoftware.nl
>> >>>>
>> >>>
>> >>
>> >
>>
>>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
So I just installed Jenkins on my PC, running inside Tomcat 6 64bit ( Tomcat is running as a Windows Service).
- Created a simple job, on the "master" node, than starts flex-sdk\frameworks\projects\framework\build.xml "pixelbender-compile" target
- Jenkins output of the job:
pixelbender-compile:
[exec] AIF Internal exception
[exec] Device: 008BB2BC has video RAM(MB): 3844
[exec] Device: 008BB2BC has video RAM(MB): 512
[exec] Return code: 1
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
So I am getting the same error.
Om says "master" does not get a window, so this result seems to be normal.
I am trying now to create a slave node and run the job on it.
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 22:07
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
It was from the command line (cmd ant ), so gets a window.
I am trying now from Jenkins service, but needs to install it first...
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala Envoyé : mardi 10 décembre 2013 20:49 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Maurice,
When you ran it on your machine, was it on Cygwin or from Jenkins?
I think there is a difference. On Jenkins, the main executor (master) does not get a window. Only slave executors are configured to get a window.
Whereas Cygwin does not have such restrictions.
Thanks,
Om
On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
> I have no idea what to do with that information. But thanks for trying.
>
> On 12/10/13 11:44 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >So this is the output from the b.a.o box:
> >
> >pixelbender-compile:
> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> > [exec] AIF Internal exception
> > [exec] Return code: 1
> > [exec] Result: 1
> >
> >To be compared to the output on my PC:
> >pixelbender-compile
> >exec
> >Device: 00633CEC has video RAM(MB): 512
> >Vendor string: NVIDIA Corporation
> >Renderer string: NVS 4200M/PCI/SSE2
> >Version string: 3.0.0
> >
> >OpenGL version as determined by Extensionator...
> >OpenGL Version 3.0
> >Has NPOT support: TRUE
> >Has Framebuffer Obeject Extension support: TRUE Completed shader
> >test!
> >Return code: 7
> >Result: 7
> >Exec
> >
> >That does not tell much, except that there seems to be an issue with
> >accessing the GPU.
> >
> >Shall I un-commit the change now, or do you want to perform more tests ?
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
> >RE: [Builds/Jenkins] Help and advise needed
> >
> >I don't have a Mac with ApacheFlex SDK for testing.
> >
> >Can you try on your side, please ?
> >
> >-----Message d'origine-----
> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >2013
> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >advise needed
> >
> >Won't that break Mac builds?
> >
> >On 12/10/13 11:32 AM, "Maurice Amsellem"
> ><ma...@systar.com>
> >wrote:
> >
> >>Alex, it's one line to change in the build.xml
> >>
> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>
> >>I will give it a try and we will know in 15 min.
> >>
> >>I am sure the result will be interesting.
> >>
> >>Anyway, it can't hurt ;-)
> >>
> >>Maurice
> >>
> >>-----Message d'origine-----
> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>and advise needed
> >>
> >>I think I'll wait to see how Gavin responds to Erik's latest request.
> >>
> >>BTW, thanks for finding out about the tool.
> >>
> >>-Alex
> >>
> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
> >><ma...@systar.com>
> >>wrote:
> >>
> >>>Sure, if you can ask him.
> >>>
> >>>Maurice
> >>>
> >>>-----Message d'origine-----
> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>décembre
> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>Help and advise needed
> >>>
> >>>Might be simpler just to ask Gavin to run the tool?
> >>>
> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
> >>><ma...@systar.com>
> >>>wrote:
> >>>
> >>>>There is a utility in pixel bender toolkit directory called
> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
> >>>>
> >>>>Console output on my laptop is below:
> >>>>
> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
> >>>>Toolkit
> >>>>2>sniffer_gpu.exe
> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>>>Vendor string: NVIDIA Corporation
> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>>>Version string: 3.0.0
> >>>>
> >>>>OpenGL version as determined by Extensionator...
> >>>>OpenGL Version 3.0
> >>>>Has NPOT support: TRUE
> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
> >>>>Return code: 7
> >>>>
> >>>>Maybe we could temporarily modify the build to run this utility
> >>>>and show the output on the b.a.o vm.
> >>>>
> >>>>WDYT ?
> >>>>
> >>>>Maurice
> >>>>
> >>>>-----Message d'origine-----
> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>>décembre
> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>>Help and advise needed
> >>>>
> >>>>I don't think we actually know the cause of the problem. I am
> >>>>going to continue to spend cycles to try to find out though.
> >>>>
> >>>>It would be nice to have an alternative to builds.a.o. I'm not
> >>>>sure if it will cost Om money to run a builds server.
> >>>>
> >>>>-Alex
> >>>>
> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
> >>>><ma...@systar.com>
> >>>>wrote:
> >>>>
> >>>>>I understand that.
> >>>>>
> >>>>>Actually, my "understanding" on this issue was that pixel bender
> >>>>>compiler required some sort of hardware configuration (OpenGL,
> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
> >>>>>slave node, so that's why the build was failing, and the Apache
> >>>>>Infra was reluctant to let us modify anything, or even access the
> >>>>>VM ourselves.
> >>>>>So that's why I was proposing a "software only" solution.
> >>>>>
> >>>>>Now, it seems from what Om is saying that we can set up and use
> >>>>>our own Jenkins slave node VM.
> >>>>>
> >>>>>That, of course, is much preferable...
> >>>>>
> >>>>>Maurice
> >>>>>
> >>>>>-----Message d'origine-----
> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>>>>[Builds/Jenkins] Help and advise needed
> >>>>>
> >>>>>Maurice,
> >>>>>
> >>>>>Your help is very much appreciated!
> >>>>>
> >>>>>I put "legal" in quotes, the issue is not really one of the law,
> >>>>>more of the rules. An Apache release is supposed to be 'source
> >>>>>only', and we if we can produce needed binaries from source, we
> >>>>>keep only the source, not the artefacts themselves in the repo.
> >>>>>
> >>>>>
> >>>>>EdB
> >>>>>
> >>>>>
> >>>>>
> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>>>><ma...@systar.com> wrote:
> >>>>>>>In addition to the various "legal" issues with binaries in the repo.
> >>>>>> I understand it's not a good idea to have binaries in the repo,
> >>>>>>so I won't insist.
> >>>>>> But please can you explain what are the legal issues of having
> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
> >>>>>>
> >>>>>> On a side note, I was just trying to help, with my limited
> >>>>>> understanding and knowledge, and because the email thread was
> >>>>>> titled "help and advise needed" ;-)
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Maurice
> >>>>>>
> >>>>>> -----Message d'origine-----
> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>>>>> [Builds/Jenkins] Help and advise needed
> >>>>>>
> >>>>>> In addition to the various "legal" issues with binaries in the
> >>>>>>repo, we'd be masking the cause of this failure. In order to
> >>>>>>prevent further deterioration of the build process, we need to
> >>>>>>figure out what went wrong and fix it.
> >>>>>>
> >>>>>> EdB
> >>>>>>
> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> >>>>>> Took me while to figure out that I hadn't gone insane or if my
> >>>>>> keyboard was broken ;-)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>>>>><ma...@systar.com> wrote:
> >>>>>>>> someone who does use the pbj's will grab the nightly and complain.
> >>>>>>>
> >>>>>>> I don't understand.
> >>>>>>> Why would someone complain if the pbj's are in the nightly?
> >>>>>>>
> >>>>>>> [From the other emai]
> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
> >>>>>>>>pbj files were removed during the initial release audit.
> >>>>>>>>I don't think a workaround can involve checking in the pbj files.
> >>>>>>>>But we could borrow them from a prior release package temporarily.
> >>>>>>>
> >>>>>>>>So we could make the compilation conditional on a env
> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
> >>>>>>>>Yes but ...
> >>>>>>>
> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
> >>>>>>>that I have understood what you said.
> >>>>>>>
> >>>>>>> So can we include the pbj in the repo, and have a parameter to
> >>>>>>>conditionally compile the pbj ?
> >>>>>>> - This parameter would be set by default to do the compilation
> >>>>>>>(so that folks can recompile)
> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>>>>>
> >>>>>>>
> >>>>>>> Maurice
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Ix Multimedia Software
> >>>>>>
> >>>>>> Jan Luykenstraat 27
> >>>>>> 3521 VB Utrecht
> >>>>>>
> >>>>>> T. 06-51952295
> >>>>>> I. www.ixsoftware.nl
> >>>>>
> >>>>>
> >>>>>
> >>>>>--
> >>>>>Ix Multimedia Software
> >>>>>
> >>>>>Jan Luykenstraat 27
> >>>>>3521 VB Utrecht
> >>>>>
> >>>>>T. 06-51952295
> >>>>>I. www.ixsoftware.nl
> >>>>
> >>>
> >>
> >
>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
It was from the command line (cmd ant ), so gets a window.
I am trying now from Jenkins service, but needs to install it first...
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : mardi 10 décembre 2013 20:49
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Maurice,
When you ran it on your machine, was it on Cygwin or from Jenkins?
I think there is a difference. On Jenkins, the main executor (master) does not get a window. Only slave executors are configured to get a window.
Whereas Cygwin does not have such restrictions.
Thanks,
Om
On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
> I have no idea what to do with that information. But thanks for trying.
>
> On 12/10/13 11:44 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >So this is the output from the b.a.o box:
> >
> >pixelbender-compile:
> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> > [exec] AIF Internal exception
> > [exec] Return code: 1
> > [exec] Result: 1
> >
> >To be compared to the output on my PC:
> >pixelbender-compile
> >exec
> >Device: 00633CEC has video RAM(MB): 512
> >Vendor string: NVIDIA Corporation
> >Renderer string: NVS 4200M/PCI/SSE2
> >Version string: 3.0.0
> >
> >OpenGL version as determined by Extensionator...
> >OpenGL Version 3.0
> >Has NPOT support: TRUE
> >Has Framebuffer Obeject Extension support: TRUE Completed shader
> >test!
> >Return code: 7
> >Result: 7
> >Exec
> >
> >That does not tell much, except that there seems to be an issue with
> >accessing the GPU.
> >
> >Shall I un-commit the change now, or do you want to perform more tests ?
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >Envoyé : mardi 10 décembre 2013 20:37 À : dev@flex.apache.org Objet :
> >RE: [Builds/Jenkins] Help and advise needed
> >
> >I don't have a Mac with ApacheFlex SDK for testing.
> >
> >Can you try on your side, please ?
> >
> >-----Message d'origine-----
> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >2013
> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >advise needed
> >
> >Won't that break Mac builds?
> >
> >On 12/10/13 11:32 AM, "Maurice Amsellem"
> ><ma...@systar.com>
> >wrote:
> >
> >>Alex, it's one line to change in the build.xml
> >>
> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>
> >>I will give it a try and we will know in 15 min.
> >>
> >>I am sure the result will be interesting.
> >>
> >>Anyway, it can't hurt ;-)
> >>
> >>Maurice
> >>
> >>-----Message d'origine-----
> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>and advise needed
> >>
> >>I think I'll wait to see how Gavin responds to Erik's latest request.
> >>
> >>BTW, thanks for finding out about the tool.
> >>
> >>-Alex
> >>
> >>On 12/10/13 11:27 AM, "Maurice Amsellem"
> >><ma...@systar.com>
> >>wrote:
> >>
> >>>Sure, if you can ask him.
> >>>
> >>>Maurice
> >>>
> >>>-----Message d'origine-----
> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>décembre
> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>Help and advise needed
> >>>
> >>>Might be simpler just to ask Gavin to run the tool?
> >>>
> >>>On 12/10/13 11:12 AM, "Maurice Amsellem"
> >>><ma...@systar.com>
> >>>wrote:
> >>>
> >>>>There is a utility in pixel bender toolkit directory called
> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
> >>>>
> >>>>Console output on my laptop is below:
> >>>>
> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
> >>>>Toolkit
> >>>>2>sniffer_gpu.exe
> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>>>Vendor string: NVIDIA Corporation
> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>>>Version string: 3.0.0
> >>>>
> >>>>OpenGL version as determined by Extensionator...
> >>>>OpenGL Version 3.0
> >>>>Has NPOT support: TRUE
> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
> >>>>Return code: 7
> >>>>
> >>>>Maybe we could temporarily modify the build to run this utility
> >>>>and show the output on the b.a.o vm.
> >>>>
> >>>>WDYT ?
> >>>>
> >>>>Maurice
> >>>>
> >>>>-----Message d'origine-----
> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10
> >>>>décembre
> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins]
> >>>>Help and advise needed
> >>>>
> >>>>I don't think we actually know the cause of the problem. I am
> >>>>going to continue to spend cycles to try to find out though.
> >>>>
> >>>>It would be nice to have an alternative to builds.a.o. I'm not
> >>>>sure if it will cost Om money to run a builds server.
> >>>>
> >>>>-Alex
> >>>>
> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem"
> >>>><ma...@systar.com>
> >>>>wrote:
> >>>>
> >>>>>I understand that.
> >>>>>
> >>>>>Actually, my "understanding" on this issue was that pixel bender
> >>>>>compiler required some sort of hardware configuration (OpenGL,
> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
> >>>>>slave node, so that's why the build was failing, and the Apache
> >>>>>Infra was reluctant to let us modify anything, or even access the
> >>>>>VM ourselves.
> >>>>>So that's why I was proposing a "software only" solution.
> >>>>>
> >>>>>Now, it seems from what Om is saying that we can set up and use
> >>>>>our own Jenkins slave node VM.
> >>>>>
> >>>>>That, of course, is much preferable...
> >>>>>
> >>>>>Maurice
> >>>>>
> >>>>>-----Message d'origine-----
> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>>>>[Builds/Jenkins] Help and advise needed
> >>>>>
> >>>>>Maurice,
> >>>>>
> >>>>>Your help is very much appreciated!
> >>>>>
> >>>>>I put "legal" in quotes, the issue is not really one of the law,
> >>>>>more of the rules. An Apache release is supposed to be 'source
> >>>>>only', and we if we can produce needed binaries from source, we
> >>>>>keep only the source, not the artefacts themselves in the repo.
> >>>>>
> >>>>>
> >>>>>EdB
> >>>>>
> >>>>>
> >>>>>
> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>>>><ma...@systar.com> wrote:
> >>>>>>>In addition to the various "legal" issues with binaries in the repo.
> >>>>>> I understand it's not a good idea to have binaries in the repo,
> >>>>>>so I won't insist.
> >>>>>> But please can you explain what are the legal issues of having
> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
> >>>>>>
> >>>>>> On a side note, I was just trying to help, with my limited
> >>>>>> understanding and knowledge, and because the email thread was
> >>>>>> titled "help and advise needed" ;-)
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Maurice
> >>>>>>
> >>>>>> -----Message d'origine-----
> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi
> >>>>>> 10 décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>>>>> [Builds/Jenkins] Help and advise needed
> >>>>>>
> >>>>>> In addition to the various "legal" issues with binaries in the
> >>>>>>repo, we'd be masking the cause of this failure. In order to
> >>>>>>prevent further deterioration of the build process, we need to
> >>>>>>figure out what went wrong and fix it.
> >>>>>>
> >>>>>> EdB
> >>>>>>
> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> >>>>>> Took me while to figure out that I hadn't gone insane or if my
> >>>>>> keyboard was broken ;-)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>>>>><ma...@systar.com> wrote:
> >>>>>>>> someone who does use the pbj's will grab the nightly and complain.
> >>>>>>>
> >>>>>>> I don't understand.
> >>>>>>> Why would someone complain if the pbj's are in the nightly?
> >>>>>>>
> >>>>>>> [From the other emai]
> >>>>>>>>Apache repos aren't supposed to contain compiled code. The
> >>>>>>>>pbj files were removed during the initial release audit.
> >>>>>>>>I don't think a workaround can involve checking in the pbj files.
> >>>>>>>>But we could borrow them from a prior release package temporarily.
> >>>>>>>
> >>>>>>>>So we could make the compilation conditional on a env
> >>>>>>>>parameter, and set that in the Jenkins job accordingly?
> >>>>>>>>Yes but ...
> >>>>>>>
> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
> >>>>>>>that I have understood what you said.
> >>>>>>>
> >>>>>>> So can we include the pbj in the repo, and have a parameter to
> >>>>>>>conditionally compile the pbj ?
> >>>>>>> - This parameter would be set by default to do the compilation
> >>>>>>>(so that folks can recompile)
> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>>>>>
> >>>>>>>
> >>>>>>> Maurice
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Ix Multimedia Software
> >>>>>>
> >>>>>> Jan Luykenstraat 27
> >>>>>> 3521 VB Utrecht
> >>>>>>
> >>>>>> T. 06-51952295
> >>>>>> I. www.ixsoftware.nl
> >>>>>
> >>>>>
> >>>>>
> >>>>>--
> >>>>>Ix Multimedia Software
> >>>>>
> >>>>>Jan Luykenstraat 27
> >>>>>3521 VB Utrecht
> >>>>>
> >>>>>T. 06-51952295
> >>>>>I. www.ixsoftware.nl
> >>>>
> >>>
> >>
> >
>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Maurice,
When you ran it on your machine, was it on Cygwin or from Jenkins?
I think there is a difference. On Jenkins, the main executor (master) does
not get a window. Only slave executors are configured to get a window.
Whereas Cygwin does not have such restrictions.
Thanks,
Om
On Tue, Dec 10, 2013 at 11:46 AM, Alex Harui <ah...@adobe.com> wrote:
> I have no idea what to do with that information. But thanks for trying.
>
> On 12/10/13 11:44 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >So this is the output from the b.a.o box:
> >
> >pixelbender-compile:
> > [exec] Device: 004C5F24 has video RAM(MB): 3736
> > [exec] AIF Internal exception
> > [exec] Return code: 1
> > [exec] Result: 1
> >
> >To be compared to the output on my PC:
> >pixelbender-compile
> >exec
> >Device: 00633CEC has video RAM(MB): 512
> >Vendor string: NVIDIA Corporation
> >Renderer string: NVS 4200M/PCI/SSE2
> >Version string: 3.0.0
> >
> >OpenGL version as determined by Extensionator...
> >OpenGL Version 3.0
> >Has NPOT support: TRUE
> >Has Framebuffer Obeject Extension support: TRUE
> >Completed shader test!
> >Return code: 7
> >Result: 7
> >Exec
> >
> >That does not tell much, except that there seems to be an issue with
> >accessing the GPU.
> >
> >Shall I un-commit the change now, or do you want to perform more tests ?
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> >Envoyé : mardi 10 décembre 2013 20:37
> >À : dev@flex.apache.org
> >Objet : RE: [Builds/Jenkins] Help and advise needed
> >
> >I don't have a Mac with ApacheFlex SDK for testing.
> >
> >Can you try on your side, please ?
> >
> >-----Message d'origine-----
> >De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013
> >20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
> >advise needed
> >
> >Won't that break Mac builds?
> >
> >On 12/10/13 11:32 AM, "Maurice Amsellem" <ma...@systar.com>
> >wrote:
> >
> >>Alex, it's one line to change in the build.xml
> >>
> >><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
> >>
> >>I will give it a try and we will know in 15 min.
> >>
> >>I am sure the result will be interesting.
> >>
> >>Anyway, it can't hurt ;-)
> >>
> >>Maurice
> >>
> >>-----Message d'origine-----
> >>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>and advise needed
> >>
> >>I think I'll wait to see how Gavin responds to Erik's latest request.
> >>
> >>BTW, thanks for finding out about the tool.
> >>
> >>-Alex
> >>
> >>On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
> >>wrote:
> >>
> >>>Sure, if you can ask him.
> >>>
> >>>Maurice
> >>>
> >>>-----Message d'origine-----
> >>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>>and advise needed
> >>>
> >>>Might be simpler just to ask Gavin to run the tool?
> >>>
> >>>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
> >>>wrote:
> >>>
> >>>>There is a utility in pixel bender toolkit directory called
> >>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
> >>>>
> >>>>Console output on my laptop is below:
> >>>>
> >>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
> >>>>Toolkit
> >>>>2>sniffer_gpu.exe
> >>>>Device: 0058A9F4 has video RAM(MB): 512
> >>>>Vendor string: NVIDIA Corporation
> >>>>Renderer string: NVS 4200M/PCI/SSE2
> >>>>Version string: 3.0.0
> >>>>
> >>>>OpenGL version as determined by Extensionator...
> >>>>OpenGL Version 3.0
> >>>>Has NPOT support: TRUE
> >>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
> >>>>Return code: 7
> >>>>
> >>>>Maybe we could temporarily modify the build to run this utility and
> >>>>show the output on the b.a.o vm.
> >>>>
> >>>>WDYT ?
> >>>>
> >>>>Maurice
> >>>>
> >>>>-----Message d'origine-----
> >>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
> >>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
> >>>>and advise needed
> >>>>
> >>>>I don't think we actually know the cause of the problem. I am going
> >>>>to continue to spend cycles to try to find out though.
> >>>>
> >>>>It would be nice to have an alternative to builds.a.o. I'm not sure
> >>>>if it will cost Om money to run a builds server.
> >>>>
> >>>>-Alex
> >>>>
> >>>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
> >>>>wrote:
> >>>>
> >>>>>I understand that.
> >>>>>
> >>>>>Actually, my "understanding" on this issue was that pixel bender
> >>>>>compiler required some sort of hardware configuration (OpenGL,
> >>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
> >>>>>slave node, so that's why the build was failing, and the Apache
> >>>>>Infra was reluctant to let us modify anything, or even access the VM
> >>>>>ourselves.
> >>>>>So that's why I was proposing a "software only" solution.
> >>>>>
> >>>>>Now, it seems from what Om is saying that we can set up and use our
> >>>>>own Jenkins slave node VM.
> >>>>>
> >>>>>That, of course, is much preferable...
> >>>>>
> >>>>>Maurice
> >>>>>
> >>>>>-----Message d'origine-----
> >>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >>>>>[Builds/Jenkins] Help and advise needed
> >>>>>
> >>>>>Maurice,
> >>>>>
> >>>>>Your help is very much appreciated!
> >>>>>
> >>>>>I put "legal" in quotes, the issue is not really one of the law,
> >>>>>more of the rules. An Apache release is supposed to be 'source
> >>>>>only', and we if we can produce needed binaries from source, we keep
> >>>>>only the source, not the artefacts themselves in the repo.
> >>>>>
> >>>>>
> >>>>>EdB
> >>>>>
> >>>>>
> >>>>>
> >>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> >>>>><ma...@systar.com> wrote:
> >>>>>>>In addition to the various "legal" issues with binaries in the repo.
> >>>>>> I understand it's not a good idea to have binaries in the repo, so
> >>>>>>I won't insist.
> >>>>>> But please can you explain what are the legal issues of having
> >>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
> >>>>>>
> >>>>>> On a side note, I was just trying to help, with my limited
> >>>>>> understanding and knowledge, and because the email thread was
> >>>>>> titled "help and advise needed" ;-)
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Maurice
> >>>>>>
> >>>>>> -----Message d'origine-----
> >>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >>>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >>>>>> [Builds/Jenkins] Help and advise needed
> >>>>>>
> >>>>>> In addition to the various "legal" issues with binaries in the
> >>>>>>repo, we'd be masking the cause of this failure. In order to
> >>>>>>prevent further deterioration of the build process, we need to
> >>>>>>figure out what went wrong and fix it.
> >>>>>>
> >>>>>> EdB
> >>>>>>
> >>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> >>>>>> Took me while to figure out that I hadn't gone insane or if my
> >>>>>> keyboard was broken ;-)
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >>>>>><ma...@systar.com> wrote:
> >>>>>>>> someone who does use the pbj's will grab the nightly and complain.
> >>>>>>>
> >>>>>>> I don't understand.
> >>>>>>> Why would someone complain if the pbj's are in the nightly?
> >>>>>>>
> >>>>>>> [From the other emai]
> >>>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
> >>>>>>>>files were removed during the initial release audit.
> >>>>>>>>I don't think a workaround can involve checking in the pbj files.
> >>>>>>>>But we could borrow them from a prior release package temporarily.
> >>>>>>>
> >>>>>>>>So we could make the compilation conditional on a env parameter,
> >>>>>>>>and set that in the Jenkins job accordingly?
> >>>>>>>>Yes but ...
> >>>>>>>
> >>>>>>> Alex, the conversation is getting out synch, so I am not sure
> >>>>>>>that I have understood what you said.
> >>>>>>>
> >>>>>>> So can we include the pbj in the repo, and have a parameter to
> >>>>>>>conditionally compile the pbj ?
> >>>>>>> - This parameter would be set by default to do the compilation
> >>>>>>>(so that folks can recompile)
> >>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>>>>>
> >>>>>>>
> >>>>>>> Maurice
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Ix Multimedia Software
> >>>>>>
> >>>>>> Jan Luykenstraat 27
> >>>>>> 3521 VB Utrecht
> >>>>>>
> >>>>>> T. 06-51952295
> >>>>>> I. www.ixsoftware.nl
> >>>>>
> >>>>>
> >>>>>
> >>>>>--
> >>>>>Ix Multimedia Software
> >>>>>
> >>>>>Jan Luykenstraat 27
> >>>>>3521 VB Utrecht
> >>>>>
> >>>>>T. 06-51952295
> >>>>>I. www.ixsoftware.nl
> >>>>
> >>>
> >>
> >
>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
I have no idea what to do with that information. But thanks for trying.
On 12/10/13 11:44 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>So this is the output from the b.a.o box:
>
>pixelbender-compile:
> [exec] Device: 004C5F24 has video RAM(MB): 3736
> [exec] AIF Internal exception
> [exec] Return code: 1
> [exec] Result: 1
>
>To be compared to the output on my PC:
>pixelbender-compile
>exec
>Device: 00633CEC has video RAM(MB): 512
>Vendor string: NVIDIA Corporation
>Renderer string: NVS 4200M/PCI/SSE2
>Version string: 3.0.0
>
>OpenGL version as determined by Extensionator...
>OpenGL Version 3.0
>Has NPOT support: TRUE
>Has Framebuffer Obeject Extension support: TRUE
>Completed shader test!
>Return code: 7
>Result: 7
>Exec
>
>That does not tell much, except that there seems to be an issue with
>accessing the GPU.
>
>Shall I un-commit the change now, or do you want to perform more tests ?
>
>Maurice
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 20:37
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>I don't have a Mac with ApacheFlex SDK for testing.
>
>Can you try on your side, please ?
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013
>20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>advise needed
>
>Won't that break Mac builds?
>
>On 12/10/13 11:32 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Alex, it's one line to change in the build.xml
>>
>><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>>
>>I will give it a try and we will know in 15 min.
>>
>>I am sure the result will be interesting.
>>
>>Anyway, it can't hurt ;-)
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>I think I'll wait to see how Gavin responds to Erik's latest request.
>>
>>BTW, thanks for finding out about the tool.
>>
>>-Alex
>>
>>On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>Sure, if you can ask him.
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>Might be simpler just to ask Gavin to run the tool?
>>>
>>>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>>>wrote:
>>>
>>>>There is a utility in pixel bender toolkit directory called
>>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>>>
>>>>Console output on my laptop is below:
>>>>
>>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>>>Toolkit
>>>>2>sniffer_gpu.exe
>>>>Device: 0058A9F4 has video RAM(MB): 512
>>>>Vendor string: NVIDIA Corporation
>>>>Renderer string: NVS 4200M/PCI/SSE2
>>>>Version string: 3.0.0
>>>>
>>>>OpenGL version as determined by Extensionator...
>>>>OpenGL Version 3.0
>>>>Has NPOT support: TRUE
>>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>>>Return code: 7
>>>>
>>>>Maybe we could temporarily modify the build to run this utility and
>>>>show the output on the b.a.o vm.
>>>>
>>>>WDYT ?
>>>>
>>>>Maurice
>>>>
>>>>-----Message d'origine-----
>>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>>and advise needed
>>>>
>>>>I don't think we actually know the cause of the problem. I am going
>>>>to continue to spend cycles to try to find out though.
>>>>
>>>>It would be nice to have an alternative to builds.a.o. I'm not sure
>>>>if it will cost Om money to run a builds server.
>>>>
>>>>-Alex
>>>>
>>>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>>>wrote:
>>>>
>>>>>I understand that.
>>>>>
>>>>>Actually, my "understanding" on this issue was that pixel bender
>>>>>compiler required some sort of hardware configuration (OpenGL,
>>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>>>>slave node, so that's why the build was failing, and the Apache
>>>>>Infra was reluctant to let us modify anything, or even access the VM
>>>>>ourselves.
>>>>>So that's why I was proposing a "software only" solution.
>>>>>
>>>>>Now, it seems from what Om is saying that we can set up and use our
>>>>>own Jenkins slave node VM.
>>>>>
>>>>>That, of course, is much preferable...
>>>>>
>>>>>Maurice
>>>>>
>>>>>-----Message d'origine-----
>>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>>[Builds/Jenkins] Help and advise needed
>>>>>
>>>>>Maurice,
>>>>>
>>>>>Your help is very much appreciated!
>>>>>
>>>>>I put "legal" in quotes, the issue is not really one of the law,
>>>>>more of the rules. An Apache release is supposed to be 'source
>>>>>only', and we if we can produce needed binaries from source, we keep
>>>>>only the source, not the artefacts themselves in the repo.
>>>>>
>>>>>
>>>>>EdB
>>>>>
>>>>>
>>>>>
>>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>>><ma...@systar.com> wrote:
>>>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>>>> I understand it's not a good idea to have binaries in the repo, so
>>>>>>I won't insist.
>>>>>> But please can you explain what are the legal issues of having
>>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>>>
>>>>>> On a side note, I was just trying to help, with my limited
>>>>>> understanding and knowledge, and because the email thread was
>>>>>> titled "help and advise needed" ;-)
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Maurice
>>>>>>
>>>>>> -----Message d'origine-----
>>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>>>> [Builds/Jenkins] Help and advise needed
>>>>>>
>>>>>> In addition to the various "legal" issues with binaries in the
>>>>>>repo, we'd be masking the cause of this failure. In order to
>>>>>>prevent further deterioration of the build process, we need to
>>>>>>figure out what went wrong and fix it.
>>>>>>
>>>>>> EdB
>>>>>>
>>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>>>> Took me while to figure out that I hadn't gone insane or if my
>>>>>> keyboard was broken ;-)
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>>><ma...@systar.com> wrote:
>>>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>>>
>>>>>>> I don't understand.
>>>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>>>
>>>>>>> [From the other emai]
>>>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>>>files were removed during the initial release audit.
>>>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>>>
>>>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>>>and set that in the Jenkins job accordingly?
>>>>>>>>Yes but ...
>>>>>>>
>>>>>>> Alex, the conversation is getting out synch, so I am not sure
>>>>>>>that I have understood what you said.
>>>>>>>
>>>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>>>conditionally compile the pbj ?
>>>>>>> - This parameter would be set by default to do the compilation
>>>>>>>(so that folks can recompile)
>>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>>>
>>>>>>>
>>>>>>> Maurice
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ix Multimedia Software
>>>>>>
>>>>>> Jan Luykenstraat 27
>>>>>> 3521 VB Utrecht
>>>>>>
>>>>>> T. 06-51952295
>>>>>> I. www.ixsoftware.nl
>>>>>
>>>>>
>>>>>
>>>>>--
>>>>>Ix Multimedia Software
>>>>>
>>>>>Jan Luykenstraat 27
>>>>>3521 VB Utrecht
>>>>>
>>>>>T. 06-51952295
>>>>>I. www.ixsoftware.nl
>>>>
>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
So this is the output from the b.a.o box:
pixelbender-compile:
[exec] Device: 004C5F24 has video RAM(MB): 3736
[exec] AIF Internal exception
[exec] Return code: 1
[exec] Result: 1
To be compared to the output on my PC:
pixelbender-compile
exec
Device: 00633CEC has video RAM(MB): 512
Vendor string: NVIDIA Corporation
Renderer string: NVS 4200M/PCI/SSE2
Version string: 3.0.0
OpenGL version as determined by Extensionator...
OpenGL Version 3.0
Has NPOT support: TRUE
Has Framebuffer Obeject Extension support: TRUE
Completed shader test!
Return code: 7
Result: 7
Exec
That does not tell much, except that there seems to be an issue with accessing the GPU.
Shall I un-commit the change now, or do you want to perform more tests ?
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 20:37
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
I don't have a Mac with ApacheFlex SDK for testing.
Can you try on your side, please ?
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre 2013 20:34 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Won't that break Mac builds?
On 12/10/13 11:32 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Alex, it's one line to change in the build.xml
>
><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>
>I will give it a try and we will know in 15 min.
>
>I am sure the result will be interesting.
>
>Anyway, it can't hurt ;-)
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>I think I'll wait to see how Gavin responds to Erik's latest request.
>
>BTW, thanks for finding out about the tool.
>
>-Alex
>
>On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Sure, if you can ask him.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Might be simpler just to ask Gavin to run the tool?
>>
>>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>There is a utility in pixel bender toolkit directory called
>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>>
>>>Console output on my laptop is below:
>>>
>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>>Toolkit
>>>2>sniffer_gpu.exe
>>>Device: 0058A9F4 has video RAM(MB): 512
>>>Vendor string: NVIDIA Corporation
>>>Renderer string: NVS 4200M/PCI/SSE2
>>>Version string: 3.0.0
>>>
>>>OpenGL version as determined by Extensionator...
>>>OpenGL Version 3.0
>>>Has NPOT support: TRUE
>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>>Return code: 7
>>>
>>>Maybe we could temporarily modify the build to run this utility and
>>>show the output on the b.a.o vm.
>>>
>>>WDYT ?
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>I don't think we actually know the cause of the problem. I am going
>>>to continue to spend cycles to try to find out though.
>>>
>>>It would be nice to have an alternative to builds.a.o. I'm not sure
>>>if it will cost Om money to run a builds server.
>>>
>>>-Alex
>>>
>>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>>wrote:
>>>
>>>>I understand that.
>>>>
>>>>Actually, my "understanding" on this issue was that pixel bender
>>>>compiler required some sort of hardware configuration (OpenGL,
>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>>>slave node, so that's why the build was failing, and the Apache
>>>>Infra was reluctant to let us modify anything, or even access the VM ourselves.
>>>>So that's why I was proposing a "software only" solution.
>>>>
>>>>Now, it seems from what Om is saying that we can set up and use our
>>>>own Jenkins slave node VM.
>>>>
>>>>That, of course, is much preferable...
>>>>
>>>>Maurice
>>>>
>>>>-----Message d'origine-----
>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins] Help and advise needed
>>>>
>>>>Maurice,
>>>>
>>>>Your help is very much appreciated!
>>>>
>>>>I put "legal" in quotes, the issue is not really one of the law,
>>>>more of the rules. An Apache release is supposed to be 'source
>>>>only', and we if we can produce needed binaries from source, we keep
>>>>only the source, not the artefacts themselves in the repo.
>>>>
>>>>
>>>>EdB
>>>>
>>>>
>>>>
>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>><ma...@systar.com> wrote:
>>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>>> I understand it's not a good idea to have binaries in the repo, so
>>>>>I won't insist.
>>>>> But please can you explain what are the legal issues of having
>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>>
>>>>> On a side note, I was just trying to help, with my limited
>>>>> understanding and knowledge, and because the email thread was
>>>>> titled "help and advise needed" ;-)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Maurice
>>>>>
>>>>> -----Message d'origine-----
>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>>> [Builds/Jenkins] Help and advise needed
>>>>>
>>>>> In addition to the various "legal" issues with binaries in the
>>>>>repo, we'd be masking the cause of this failure. In order to
>>>>>prevent further deterioration of the build process, we need to
>>>>>figure out what went wrong and fix it.
>>>>>
>>>>> EdB
>>>>>
>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>>> Took me while to figure out that I hadn't gone insane or if my
>>>>> keyboard was broken ;-)
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>><ma...@systar.com> wrote:
>>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>>
>>>>>> I don't understand.
>>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>>
>>>>>> [From the other emai]
>>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>>files were removed during the initial release audit.
>>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>>
>>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>>and set that in the Jenkins job accordingly?
>>>>>>>Yes but ...
>>>>>>
>>>>>> Alex, the conversation is getting out synch, so I am not sure
>>>>>>that I have understood what you said.
>>>>>>
>>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>>conditionally compile the pbj ?
>>>>>> - This parameter would be set by default to do the compilation
>>>>>>(so that folks can recompile)
>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>>
>>>>>>
>>>>>> Maurice
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ix Multimedia Software
>>>>>
>>>>> Jan Luykenstraat 27
>>>>> 3521 VB Utrecht
>>>>>
>>>>> T. 06-51952295
>>>>> I. www.ixsoftware.nl
>>>>
>>>>
>>>>
>>>>--
>>>>Ix Multimedia Software
>>>>
>>>>Jan Luykenstraat 27
>>>>3521 VB Utrecht
>>>>
>>>>T. 06-51952295
>>>>I. www.ixsoftware.nl
>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
I don't have a Mac with ApacheFlex SDK for testing.
Can you try on your side, please ?
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 20:34
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Won't that break Mac builds?
On 12/10/13 11:32 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Alex, it's one line to change in the build.xml
>
><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>
>I will give it a try and we will know in 15 min.
>
>I am sure the result will be interesting.
>
>Anyway, it can't hurt ;-)
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 20:29 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>I think I'll wait to see how Gavin responds to Erik's latest request.
>
>BTW, thanks for finding out about the tool.
>
>-Alex
>
>On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Sure, if you can ask him.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Might be simpler just to ask Gavin to run the tool?
>>
>>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>There is a utility in pixel bender toolkit directory called
>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>>
>>>Console output on my laptop is below:
>>>
>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>>Toolkit
>>>2>sniffer_gpu.exe
>>>Device: 0058A9F4 has video RAM(MB): 512
>>>Vendor string: NVIDIA Corporation
>>>Renderer string: NVS 4200M/PCI/SSE2
>>>Version string: 3.0.0
>>>
>>>OpenGL version as determined by Extensionator...
>>>OpenGL Version 3.0
>>>Has NPOT support: TRUE
>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>>Return code: 7
>>>
>>>Maybe we could temporarily modify the build to run this utility and
>>>show the output on the b.a.o vm.
>>>
>>>WDYT ?
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>I don't think we actually know the cause of the problem. I am going
>>>to continue to spend cycles to try to find out though.
>>>
>>>It would be nice to have an alternative to builds.a.o. I'm not sure
>>>if it will cost Om money to run a builds server.
>>>
>>>-Alex
>>>
>>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>>wrote:
>>>
>>>>I understand that.
>>>>
>>>>Actually, my "understanding" on this issue was that pixel bender
>>>>compiler required some sort of hardware configuration (OpenGL,
>>>>etc...) that were not present on the b.a.o. new Windows Jenkins
>>>>slave node, so that's why the build was failing, and the Apache
>>>>Infra was reluctant to let us modify anything, or even access the VM ourselves.
>>>>So that's why I was proposing a "software only" solution.
>>>>
>>>>Now, it seems from what Om is saying that we can set up and use our
>>>>own Jenkins slave node VM.
>>>>
>>>>That, of course, is much preferable...
>>>>
>>>>Maurice
>>>>
>>>>-----Message d'origine-----
>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins] Help and advise needed
>>>>
>>>>Maurice,
>>>>
>>>>Your help is very much appreciated!
>>>>
>>>>I put "legal" in quotes, the issue is not really one of the law,
>>>>more of the rules. An Apache release is supposed to be 'source
>>>>only', and we if we can produce needed binaries from source, we keep
>>>>only the source, not the artefacts themselves in the repo.
>>>>
>>>>
>>>>EdB
>>>>
>>>>
>>>>
>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>><ma...@systar.com> wrote:
>>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>>> I understand it's not a good idea to have binaries in the repo, so
>>>>>I won't insist.
>>>>> But please can you explain what are the legal issues of having
>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>>
>>>>> On a side note, I was just trying to help, with my limited
>>>>> understanding and knowledge, and because the email thread was
>>>>> titled "help and advise needed" ;-)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Maurice
>>>>>
>>>>> -----Message d'origine-----
>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>>> [Builds/Jenkins] Help and advise needed
>>>>>
>>>>> In addition to the various "legal" issues with binaries in the
>>>>>repo, we'd be masking the cause of this failure. In order to
>>>>>prevent further deterioration of the build process, we need to
>>>>>figure out what went wrong and fix it.
>>>>>
>>>>> EdB
>>>>>
>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>>> Took me while to figure out that I hadn't gone insane or if my
>>>>> keyboard was broken ;-)
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>><ma...@systar.com> wrote:
>>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>>
>>>>>> I don't understand.
>>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>>
>>>>>> [From the other emai]
>>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>>files were removed during the initial release audit.
>>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>>
>>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>>and set that in the Jenkins job accordingly?
>>>>>>>Yes but ...
>>>>>>
>>>>>> Alex, the conversation is getting out synch, so I am not sure
>>>>>>that I have understood what you said.
>>>>>>
>>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>>conditionally compile the pbj ?
>>>>>> - This parameter would be set by default to do the compilation
>>>>>>(so that folks can recompile)
>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>>
>>>>>>
>>>>>> Maurice
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ix Multimedia Software
>>>>>
>>>>> Jan Luykenstraat 27
>>>>> 3521 VB Utrecht
>>>>>
>>>>> T. 06-51952295
>>>>> I. www.ixsoftware.nl
>>>>
>>>>
>>>>
>>>>--
>>>>Ix Multimedia Software
>>>>
>>>>Jan Luykenstraat 27
>>>>3521 VB Utrecht
>>>>
>>>>T. 06-51952295
>>>>I. www.ixsoftware.nl
>>>
>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Won't that break Mac builds?
On 12/10/13 11:32 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Alex, it's one line to change in the build.xml
>
><exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
>
>I will give it a try and we will know in 15 min.
>
>I am sure the result will be interesting.
>
>Anyway, it can't hurt ;-)
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 20:29
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>I think I'll wait to see how Gavin responds to Erik's latest request.
>
>BTW, thanks for finding out about the tool.
>
>-Alex
>
>On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Sure, if you can ask him.
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>Might be simpler just to ask Gavin to run the tool?
>>
>>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>There is a utility in pixel bender toolkit directory called
>>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>>
>>>Console output on my laptop is below:
>>>
>>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>>Toolkit
>>>2>sniffer_gpu.exe
>>>Device: 0058A9F4 has video RAM(MB): 512
>>>Vendor string: NVIDIA Corporation
>>>Renderer string: NVS 4200M/PCI/SSE2
>>>Version string: 3.0.0
>>>
>>>OpenGL version as determined by Extensionator...
>>>OpenGL Version 3.0
>>>Has NPOT support: TRUE
>>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>>Return code: 7
>>>
>>>Maybe we could temporarily modify the build to run this utility and
>>>show the output on the b.a.o vm.
>>>
>>>WDYT ?
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>>and advise needed
>>>
>>>I don't think we actually know the cause of the problem. I am going
>>>to continue to spend cycles to try to find out though.
>>>
>>>It would be nice to have an alternative to builds.a.o. I'm not sure
>>>if it will cost Om money to run a builds server.
>>>
>>>-Alex
>>>
>>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>>wrote:
>>>
>>>>I understand that.
>>>>
>>>>Actually, my "understanding" on this issue was that pixel bender
>>>>compiler required some sort of hardware configuration (OpenGL,
>>>>etc...) that were not present on the b.a.o. new Windows Jenkins slave
>>>>node, so that's why the build was failing, and the Apache Infra was
>>>>reluctant to let us modify anything, or even access the VM ourselves.
>>>>So that's why I was proposing a "software only" solution.
>>>>
>>>>Now, it seems from what Om is saying that we can set up and use our
>>>>own Jenkins slave node VM.
>>>>
>>>>That, of course, is much preferable...
>>>>
>>>>Maurice
>>>>
>>>>-----Message d'origine-----
>>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>>[Builds/Jenkins] Help and advise needed
>>>>
>>>>Maurice,
>>>>
>>>>Your help is very much appreciated!
>>>>
>>>>I put "legal" in quotes, the issue is not really one of the law, more
>>>>of the rules. An Apache release is supposed to be 'source only', and
>>>>we if we can produce needed binaries from source, we keep only the
>>>>source, not the artefacts themselves in the repo.
>>>>
>>>>
>>>>EdB
>>>>
>>>>
>>>>
>>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>>><ma...@systar.com> wrote:
>>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>>> I understand it's not a good idea to have binaries in the repo, so
>>>>>I won't insist.
>>>>> But please can you explain what are the legal issues of having
>>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>>
>>>>> On a side note, I was just trying to help, with my limited
>>>>> understanding and knowledge, and because the email thread was
>>>>> titled "help and advise needed" ;-)
>>>>>
>>>>> Regards,
>>>>>
>>>>> Maurice
>>>>>
>>>>> -----Message d'origine-----
>>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>>> [Builds/Jenkins] Help and advise needed
>>>>>
>>>>> In addition to the various "legal" issues with binaries in the
>>>>>repo, we'd be masking the cause of this failure. In order to prevent
>>>>>further deterioration of the build process, we need to figure out
>>>>>what went wrong and fix it.
>>>>>
>>>>> EdB
>>>>>
>>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>>> Took me while to figure out that I hadn't gone insane or if my
>>>>> keyboard was broken ;-)
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>>><ma...@systar.com> wrote:
>>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>>
>>>>>> I don't understand.
>>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>>
>>>>>> [From the other emai]
>>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>>files were removed during the initial release audit.
>>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>>
>>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>>and set that in the Jenkins job accordingly?
>>>>>>>Yes but ...
>>>>>>
>>>>>> Alex, the conversation is getting out synch, so I am not sure that
>>>>>>I have understood what you said.
>>>>>>
>>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>>conditionally compile the pbj ?
>>>>>> - This parameter would be set by default to do the compilation (so
>>>>>>that folks can recompile)
>>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>>
>>>>>>
>>>>>> Maurice
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ix Multimedia Software
>>>>>
>>>>> Jan Luykenstraat 27
>>>>> 3521 VB Utrecht
>>>>>
>>>>> T. 06-51952295
>>>>> I. www.ixsoftware.nl
>>>>
>>>>
>>>>
>>>>--
>>>>Ix Multimedia Software
>>>>
>>>>Jan Luykenstraat 27
>>>>3521 VB Utrecht
>>>>
>>>>T. 06-51952295
>>>>I. www.ixsoftware.nl
>>>
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Alex, it's one line to change in the build.xml
<exec executable="${env.PIXELBENDER_HOME}/sniffer_gpu.exe"/>
I will give it a try and we will know in 15 min.
I am sure the result will be interesting.
Anyway, it can't hurt ;-)
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 20:29
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
I think I'll wait to see how Gavin responds to Erik's latest request.
BTW, thanks for finding out about the tool.
-Alex
On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Sure, if you can ask him.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 20:26 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Might be simpler just to ask Gavin to run the tool?
>
>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>There is a utility in pixel bender toolkit directory called
>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>
>>Console output on my laptop is below:
>>
>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender
>>Toolkit
>>2>sniffer_gpu.exe
>>Device: 0058A9F4 has video RAM(MB): 512
>>Vendor string: NVIDIA Corporation
>>Renderer string: NVS 4200M/PCI/SSE2
>>Version string: 3.0.0
>>
>>OpenGL version as determined by Extensionator...
>>OpenGL Version 3.0
>>Has NPOT support: TRUE
>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>Return code: 7
>>
>>Maybe we could temporarily modify the build to run this utility and
>>show the output on the b.a.o vm.
>>
>>WDYT ?
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>I don't think we actually know the cause of the problem. I am going
>>to continue to spend cycles to try to find out though.
>>
>>It would be nice to have an alternative to builds.a.o. I'm not sure
>>if it will cost Om money to run a builds server.
>>
>>-Alex
>>
>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>I understand that.
>>>
>>>Actually, my "understanding" on this issue was that pixel bender
>>>compiler required some sort of hardware configuration (OpenGL,
>>>etc...) that were not present on the b.a.o. new Windows Jenkins slave
>>>node, so that's why the build was failing, and the Apache Infra was
>>>reluctant to let us modify anything, or even access the VM ourselves.
>>>So that's why I was proposing a "software only" solution.
>>>
>>>Now, it seems from what Om is saying that we can set up and use our
>>>own Jenkins slave node VM.
>>>
>>>That, of course, is much preferable...
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>[Builds/Jenkins] Help and advise needed
>>>
>>>Maurice,
>>>
>>>Your help is very much appreciated!
>>>
>>>I put "legal" in quotes, the issue is not really one of the law, more
>>>of the rules. An Apache release is supposed to be 'source only', and
>>>we if we can produce needed binaries from source, we keep only the
>>>source, not the artefacts themselves in the repo.
>>>
>>>
>>>EdB
>>>
>>>
>>>
>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>><ma...@systar.com> wrote:
>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>> I understand it's not a good idea to have binaries in the repo, so
>>>>I won't insist.
>>>> But please can you explain what are the legal issues of having
>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>
>>>> On a side note, I was just trying to help, with my limited
>>>> understanding and knowledge, and because the email thread was
>>>> titled "help and advise needed" ;-)
>>>>
>>>> Regards,
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> In addition to the various "legal" issues with binaries in the
>>>>repo, we'd be masking the cause of this failure. In order to prevent
>>>>further deterioration of the build process, we need to figure out
>>>>what went wrong and fix it.
>>>>
>>>> EdB
>>>>
>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>> Took me while to figure out that I hadn't gone insane or if my
>>>> keyboard was broken ;-)
>>>>
>>>>
>>>>
>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>><ma...@systar.com> wrote:
>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>
>>>>> I don't understand.
>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>
>>>>> [From the other emai]
>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>files were removed during the initial release audit.
>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>
>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>and set that in the Jenkins job accordingly?
>>>>>>Yes but ...
>>>>>
>>>>> Alex, the conversation is getting out synch, so I am not sure that
>>>>>I have understood what you said.
>>>>>
>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>conditionally compile the pbj ?
>>>>> - This parameter would be set by default to do the compilation (so
>>>>>that folks can recompile)
>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>
>>>>>
>>>>> Maurice
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ix Multimedia Software
>>>>
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>
>>>
>>>
>>>--
>>>Ix Multimedia Software
>>>
>>>Jan Luykenstraat 27
>>>3521 VB Utrecht
>>>
>>>T. 06-51952295
>>>I. www.ixsoftware.nl
>>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
I think I'll wait to see how Gavin responds to Erik's latest request.
BTW, thanks for finding out about the tool.
-Alex
On 12/10/13 11:27 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Sure, if you can ask him.
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 20:26
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Might be simpler just to ask Gavin to run the tool?
>
>On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>There is a utility in pixel bender toolkit directory called
>>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>>
>>Console output on my laptop is below:
>>
>>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit
>>2>sniffer_gpu.exe
>>Device: 0058A9F4 has video RAM(MB): 512
>>Vendor string: NVIDIA Corporation
>>Renderer string: NVS 4200M/PCI/SSE2
>>Version string: 3.0.0
>>
>>OpenGL version as determined by Extensionator...
>>OpenGL Version 3.0
>>Has NPOT support: TRUE
>>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>>Return code: 7
>>
>>Maybe we could temporarily modify the build to run this utility and
>>show the output on the b.a.o vm.
>>
>>WDYT ?
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>>and advise needed
>>
>>I don't think we actually know the cause of the problem. I am going to
>>continue to spend cycles to try to find out though.
>>
>>It would be nice to have an alternative to builds.a.o. I'm not sure if
>>it will cost Om money to run a builds server.
>>
>>-Alex
>>
>>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>>wrote:
>>
>>>I understand that.
>>>
>>>Actually, my "understanding" on this issue was that pixel bender
>>>compiler required some sort of hardware configuration (OpenGL, etc...)
>>>that were not present on the b.a.o. new Windows Jenkins slave node, so
>>>that's why the build was failing, and the Apache Infra was reluctant
>>>to let us modify anything, or even access the VM ourselves.
>>>So that's why I was proposing a "software only" solution.
>>>
>>>Now, it seems from what Om is saying that we can set up and use our
>>>own Jenkins slave node VM.
>>>
>>>That, of course, is much preferable...
>>>
>>>Maurice
>>>
>>>-----Message d'origine-----
>>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>>[Builds/Jenkins] Help and advise needed
>>>
>>>Maurice,
>>>
>>>Your help is very much appreciated!
>>>
>>>I put "legal" in quotes, the issue is not really one of the law, more
>>>of the rules. An Apache release is supposed to be 'source only', and
>>>we if we can produce needed binaries from source, we keep only the
>>>source, not the artefacts themselves in the repo.
>>>
>>>
>>>EdB
>>>
>>>
>>>
>>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>>><ma...@systar.com> wrote:
>>>>>In addition to the various "legal" issues with binaries in the repo.
>>>> I understand it's not a good idea to have binaries in the repo, so I
>>>>won't insist.
>>>> But please can you explain what are the legal issues of having
>>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>>
>>>> On a side note, I was just trying to help, with my limited
>>>> understanding and knowledge, and because the email thread was titled
>>>> "help and advise needed" ;-)
>>>>
>>>> Regards,
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> In addition to the various "legal" issues with binaries in the repo,
>>>>we'd be masking the cause of this failure. In order to prevent
>>>>further deterioration of the build process, we need to figure out
>>>>what went wrong and fix it.
>>>>
>>>> EdB
>>>>
>>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>>> Took me while to figure out that I hadn't gone insane or if my
>>>> keyboard was broken ;-)
>>>>
>>>>
>>>>
>>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>>><ma...@systar.com> wrote:
>>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>>
>>>>> I don't understand.
>>>>> Why would someone complain if the pbj's are in the nightly?
>>>>>
>>>>> [From the other emai]
>>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>>files were removed during the initial release audit.
>>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>>But we could borrow them from a prior release package temporarily.
>>>>>
>>>>>>So we could make the compilation conditional on a env parameter,
>>>>>>and set that in the Jenkins job accordingly?
>>>>>>Yes but ...
>>>>>
>>>>> Alex, the conversation is getting out synch, so I am not sure that
>>>>>I have understood what you said.
>>>>>
>>>>> So can we include the pbj in the repo, and have a parameter to
>>>>>conditionally compile the pbj ?
>>>>> - This parameter would be set by default to do the compilation (so
>>>>>that folks can recompile)
>>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>>
>>>>>
>>>>> Maurice
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ix Multimedia Software
>>>>
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>
>>>
>>>
>>>--
>>>Ix Multimedia Software
>>>
>>>Jan Luykenstraat 27
>>>3521 VB Utrecht
>>>
>>>T. 06-51952295
>>>I. www.ixsoftware.nl
>>
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Sure, if you can ask him.
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 20:26
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Might be simpler just to ask Gavin to run the tool?
On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>There is a utility in pixel bender toolkit directory called
>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>
>Console output on my laptop is below:
>
>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit
>2>sniffer_gpu.exe
>Device: 0058A9F4 has video RAM(MB): 512
>Vendor string: NVIDIA Corporation
>Renderer string: NVS 4200M/PCI/SSE2
>Version string: 3.0.0
>
>OpenGL version as determined by Extensionator...
>OpenGL Version 3.0
>Has NPOT support: TRUE
>Has Framebuffer Obeject Extension support: TRUE Completed shader test!
>Return code: 7
>
>Maybe we could temporarily modify the build to run this utility and
>show the output on the b.a.o vm.
>
>WDYT ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com] Envoyé : mardi 10 décembre
>2013 18:15 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>I don't think we actually know the cause of the problem. I am going to
>continue to spend cycles to try to find out though.
>
>It would be nice to have an alternative to builds.a.o. I'm not sure if
>it will cost Om money to run a builds server.
>
>-Alex
>
>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>I understand that.
>>
>>Actually, my "understanding" on this issue was that pixel bender
>>compiler required some sort of hardware configuration (OpenGL, etc...)
>>that were not present on the b.a.o. new Windows Jenkins slave node, so
>>that's why the build was failing, and the Apache Infra was reluctant
>>to let us modify anything, or even access the VM ourselves.
>>So that's why I was proposing a "software only" solution.
>>
>>Now, it seems from what Om is saying that we can set up and use our
>>own Jenkins slave node VM.
>>
>>That, of course, is much preferable...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>[Builds/Jenkins] Help and advise needed
>>
>>Maurice,
>>
>>Your help is very much appreciated!
>>
>>I put "legal" in quotes, the issue is not really one of the law, more
>>of the rules. An Apache release is supposed to be 'source only', and
>>we if we can produce needed binaries from source, we keep only the
>>source, not the artefacts themselves in the repo.
>>
>>
>>EdB
>>
>>
>>
>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>><ma...@systar.com> wrote:
>>>>In addition to the various "legal" issues with binaries in the repo.
>>> I understand it's not a good idea to have binaries in the repo, so I
>>>won't insist.
>>> But please can you explain what are the legal issues of having
>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>
>>> On a side note, I was just trying to help, with my limited
>>> understanding and knowledge, and because the email thread was titled
>>> "help and advise needed" ;-)
>>>
>>> Regards,
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> In addition to the various "legal" issues with binaries in the repo,
>>>we'd be masking the cause of this failure. In order to prevent
>>>further deterioration of the build process, we need to figure out
>>>what went wrong and fix it.
>>>
>>> EdB
>>>
>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>> Took me while to figure out that I hadn't gone insane or if my
>>> keyboard was broken ;-)
>>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>><ma...@systar.com> wrote:
>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>
>>>> I don't understand.
>>>> Why would someone complain if the pbj's are in the nightly?
>>>>
>>>> [From the other emai]
>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>files were removed during the initial release audit.
>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>But we could borrow them from a prior release package temporarily.
>>>>
>>>>>So we could make the compilation conditional on a env parameter,
>>>>>and set that in the Jenkins job accordingly?
>>>>>Yes but ...
>>>>
>>>> Alex, the conversation is getting out synch, so I am not sure that
>>>>I have understood what you said.
>>>>
>>>> So can we include the pbj in the repo, and have a parameter to
>>>>conditionally compile the pbj ?
>>>> - This parameter would be set by default to do the compilation (so
>>>>that folks can recompile)
>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>
>>>>
>>>> Maurice
>>>>
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Sean Thayne <se...@skyseek.com>.
I'd really suggest you guys move to Bamboo. It connects to Jira for user
access control. You can easily set admin rights for specific users. It's
remote agents are way better than jenkin slaves.
I use it for compiling ANEs, Air apps and SWFs. Super easy to setup.
Another great benefit is you can easily have it create/test separate
branches.
Like Jira it's free for open source projects. And their main team of
developers are super responsive and always looking for and open to new
ideas/changes.
~Sean
<http://www.skyseek.com>
class *Sean_Thayne*
extends Developer {
public $skype = "sthayne23";
public $gTalk = "sean@skyseek.com";
public $url = "www.skyseek.com";
}
On Tue, Dec 10, 2013 at 12:12 PM, Maurice Amsellem <
maurice.amsellem@systar.com> wrote:
> There is a utility in pixel bender toolkit directory called
> "sniffer_gpu.exe" that check the presence and version of OpenGL:
>
> Console output on my laptop is below:
>
> C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit
> 2>sniffer_gpu.exe
> Device: 0058A9F4 has video RAM(MB): 512
> Vendor string: NVIDIA Corporation
> Renderer string: NVS 4200M/PCI/SSE2
> Version string: 3.0.0
>
> OpenGL version as determined by Extensionator...
> OpenGL Version 3.0
> Has NPOT support: TRUE
> Has Framebuffer Obeject Extension support: TRUE
> Completed shader test!
> Return code: 7
>
> Maybe we could temporarily modify the build to run this utility and show
> the output on the b.a.o vm.
>
> WDYT ?
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : mardi 10 décembre 2013 18:15
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> I don't think we actually know the cause of the problem. I am going to
> continue to spend cycles to try to find out though.
>
> It would be nice to have an alternative to builds.a.o. I'm not sure if it
> will cost Om money to run a builds server.
>
> -Alex
>
> On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >I understand that.
> >
> >Actually, my "understanding" on this issue was that pixel bender
> >compiler required some sort of hardware configuration (OpenGL, etc...)
> >that were not present on the b.a.o. new Windows Jenkins slave node, so
> >that's why the build was failing, and the Apache Infra was reluctant
> >to let us modify anything, or even access the VM ourselves.
> >So that's why I was proposing a "software only" solution.
> >
> >Now, it seems from what Om is saying that we can set up and use our own
> >Jenkins slave node VM.
> >
> >That, of course, is much preferable...
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
> >[Builds/Jenkins] Help and advise needed
> >
> >Maurice,
> >
> >Your help is very much appreciated!
> >
> >I put "legal" in quotes, the issue is not really one of the law, more
> >of the rules. An Apache release is supposed to be 'source only', and we
> >if we can produce needed binaries from source, we keep only the source,
> >not the artefacts themselves in the repo.
> >
> >
> >EdB
> >
> >
> >
> >On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
> ><ma...@systar.com> wrote:
> >>>In addition to the various "legal" issues with binaries in the repo.
> >> I understand it's not a good idea to have binaries in the repo, so I
> >>won't insist.
> >> But please can you explain what are the legal issues of having
> >>binaries in the repo? Is this because of Adobe, or ASF rules ?
> >>
> >> On a side note, I was just trying to help, with my limited
> >> understanding and knowledge, and because the email thread was titled
> >> "help and advise needed" ;-)
> >>
> >> Regards,
> >>
> >> Maurice
> >>
> >> -----Message d'origine-----
> >> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> >> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> >> [Builds/Jenkins] Help and advise needed
> >>
> >> In addition to the various "legal" issues with binaries in the repo,
> >>we'd be masking the cause of this failure. In order to prevent further
> >>deterioration of the build process, we need to figure out what went
> >>wrong and fix it.
> >>
> >> EdB
> >>
> >> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> >> Took me while to figure out that I hadn't gone insane or if my
> >> keyboard was broken ;-)
> >>
> >>
> >>
> >> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> >><ma...@systar.com> wrote:
> >>>> someone who does use the pbj's will grab the nightly and complain.
> >>>
> >>> I don't understand.
> >>> Why would someone complain if the pbj's are in the nightly?
> >>>
> >>> [From the other emai]
> >>>>Apache repos aren't supposed to contain compiled code. The pbj
> >>>>files were removed during the initial release audit.
> >>>>I don't think a workaround can involve checking in the pbj files.
> >>>>But we could borrow them from a prior release package temporarily.
> >>>
> >>>>So we could make the compilation conditional on a env parameter,
> >>>>and set that in the Jenkins job accordingly?
> >>>>Yes but ...
> >>>
> >>> Alex, the conversation is getting out synch, so I am not sure that I
> >>>have understood what you said.
> >>>
> >>> So can we include the pbj in the repo, and have a parameter to
> >>>conditionally compile the pbj ?
> >>> - This parameter would be set by default to do the compilation (so
> >>>that folks can recompile)
> >>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >>>
> >>>
> >>> Maurice
> >>>
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl
> >
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I. www.ixsoftware.nl
>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Might be simpler just to ask Gavin to run the tool?
On 12/10/13 11:12 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>There is a utility in pixel bender toolkit directory called
>"sniffer_gpu.exe" that check the presence and version of OpenGL:
>
>Console output on my laptop is below:
>
>C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit
>2>sniffer_gpu.exe
>Device: 0058A9F4 has video RAM(MB): 512
>Vendor string: NVIDIA Corporation
>Renderer string: NVS 4200M/PCI/SSE2
>Version string: 3.0.0
>
>OpenGL version as determined by Extensionator...
>OpenGL Version 3.0
>Has NPOT support: TRUE
>Has Framebuffer Obeject Extension support: TRUE
>Completed shader test!
>Return code: 7
>
>Maybe we could temporarily modify the build to run this utility and show
>the output on the b.a.o vm.
>
>WDYT ?
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 18:15
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>I don't think we actually know the cause of the problem. I am going to
>continue to spend cycles to try to find out though.
>
>It would be nice to have an alternative to builds.a.o. I'm not sure if
>it will cost Om money to run a builds server.
>
>-Alex
>
>On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>I understand that.
>>
>>Actually, my "understanding" on this issue was that pixel bender
>>compiler required some sort of hardware configuration (OpenGL, etc...)
>>that were not present on the b.a.o. new Windows Jenkins slave node, so
>>that's why the build was failing, and the Apache Infra was reluctant
>>to let us modify anything, or even access the VM ourselves.
>>So that's why I was proposing a "software only" solution.
>>
>>Now, it seems from what Om is saying that we can set up and use our own
>>Jenkins slave node VM.
>>
>>That, of course, is much preferable...
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>>[Builds/Jenkins] Help and advise needed
>>
>>Maurice,
>>
>>Your help is very much appreciated!
>>
>>I put "legal" in quotes, the issue is not really one of the law, more
>>of the rules. An Apache release is supposed to be 'source only', and we
>>if we can produce needed binaries from source, we keep only the source,
>>not the artefacts themselves in the repo.
>>
>>
>>EdB
>>
>>
>>
>>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
>><ma...@systar.com> wrote:
>>>>In addition to the various "legal" issues with binaries in the repo.
>>> I understand it's not a good idea to have binaries in the repo, so I
>>>won't insist.
>>> But please can you explain what are the legal issues of having
>>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>>
>>> On a side note, I was just trying to help, with my limited
>>> understanding and knowledge, and because the email thread was titled
>>> "help and advise needed" ;-)
>>>
>>> Regards,
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> In addition to the various "legal" issues with binaries in the repo,
>>>we'd be masking the cause of this failure. In order to prevent further
>>>deterioration of the build process, we need to figure out what went
>>>wrong and fix it.
>>>
>>> EdB
>>>
>>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>>> Took me while to figure out that I hadn't gone insane or if my
>>> keyboard was broken ;-)
>>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>>><ma...@systar.com> wrote:
>>>>> someone who does use the pbj's will grab the nightly and complain.
>>>>
>>>> I don't understand.
>>>> Why would someone complain if the pbj's are in the nightly?
>>>>
>>>> [From the other emai]
>>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>>files were removed during the initial release audit.
>>>>>I don't think a workaround can involve checking in the pbj files.
>>>>>But we could borrow them from a prior release package temporarily.
>>>>
>>>>>So we could make the compilation conditional on a env parameter,
>>>>>and set that in the Jenkins job accordingly?
>>>>>Yes but ...
>>>>
>>>> Alex, the conversation is getting out synch, so I am not sure that I
>>>>have understood what you said.
>>>>
>>>> So can we include the pbj in the repo, and have a parameter to
>>>>conditionally compile the pbj ?
>>>> - This parameter would be set by default to do the compilation (so
>>>>that folks can recompile)
>>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>>
>>>>
>>>> Maurice
>>>>
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
There is a utility in pixel bender toolkit directory called "sniffer_gpu.exe" that check the presence and version of OpenGL:
Console output on my laptop is below:
C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2>sniffer_gpu.exe
Device: 0058A9F4 has video RAM(MB): 512
Vendor string: NVIDIA Corporation
Renderer string: NVS 4200M/PCI/SSE2
Version string: 3.0.0
OpenGL version as determined by Extensionator...
OpenGL Version 3.0
Has NPOT support: TRUE
Has Framebuffer Obeject Extension support: TRUE
Completed shader test!
Return code: 7
Maybe we could temporarily modify the build to run this utility and show the output on the b.a.o vm.
WDYT ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 18:15
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
I don't think we actually know the cause of the problem. I am going to continue to spend cycles to try to find out though.
It would be nice to have an alternative to builds.a.o. I'm not sure if it will cost Om money to run a builds server.
-Alex
On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>I understand that.
>
>Actually, my "understanding" on this issue was that pixel bender
>compiler required some sort of hardware configuration (OpenGL, etc...)
>that were not present on the b.a.o. new Windows Jenkins slave node, so
>that's why the build was failing, and the Apache Infra was reluctant
>to let us modify anything, or even access the VM ourselves.
>So that's why I was proposing a "software only" solution.
>
>Now, it seems from what Om is saying that we can set up and use our own
>Jenkins slave node VM.
>
>That, of course, is much preferable...
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>décembre 2013 10:44 À : dev@flex.apache.org Objet : Re:
>[Builds/Jenkins] Help and advise needed
>
>Maurice,
>
>Your help is very much appreciated!
>
>I put "legal" in quotes, the issue is not really one of the law, more
>of the rules. An Apache release is supposed to be 'source only', and we
>if we can produce needed binaries from source, we keep only the source,
>not the artefacts themselves in the repo.
>
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
><ma...@systar.com> wrote:
>>>In addition to the various "legal" issues with binaries in the repo.
>> I understand it's not a good idea to have binaries in the repo, so I
>>won't insist.
>> But please can you explain what are the legal issues of having
>>binaries in the repo? Is this because of Adobe, or ASF rules ?
>>
>> On a side note, I was just trying to help, with my limited
>> understanding and knowledge, and because the email thread was titled
>> "help and advise needed" ;-)
>>
>> Regards,
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> In addition to the various "legal" issues with binaries in the repo,
>>we'd be masking the cause of this failure. In order to prevent further
>>deterioration of the build process, we need to figure out what went
>>wrong and fix it.
>>
>> EdB
>>
>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>> Took me while to figure out that I hadn't gone insane or if my
>> keyboard was broken ;-)
>>
>>
>>
>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>><ma...@systar.com> wrote:
>>>> someone who does use the pbj's will grab the nightly and complain.
>>>
>>> I don't understand.
>>> Why would someone complain if the pbj's are in the nightly?
>>>
>>> [From the other emai]
>>>>Apache repos aren't supposed to contain compiled code. The pbj
>>>>files were removed during the initial release audit.
>>>>I don't think a workaround can involve checking in the pbj files.
>>>>But we could borrow them from a prior release package temporarily.
>>>
>>>>So we could make the compilation conditional on a env parameter,
>>>>and set that in the Jenkins job accordingly?
>>>>Yes but ...
>>>
>>> Alex, the conversation is getting out synch, so I am not sure that I
>>>have understood what you said.
>>>
>>> So can we include the pbj in the repo, and have a parameter to
>>>conditionally compile the pbj ?
>>> - This parameter would be set by default to do the compilation (so
>>>that folks can recompile)
>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>
>>>
>>> Maurice
>>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
I don't think we actually know the cause of the problem. I am going to
continue to spend cycles to try to find out though.
It would be nice to have an alternative to builds.a.o. I'm not sure if it
will cost Om money to run a builds server.
-Alex
On 12/10/13 2:01 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>I understand that.
>
>Actually, my "understanding" on this issue was that pixel bender compiler
>required some sort of hardware configuration (OpenGL, etc...) that were
>not present on the b.a.o. new Windows Jenkins slave node, so that's why
>the build was failing, and the Apache Infra was reluctant to let us
>modify anything, or even access the VM ourselves.
>So that's why I was proposing a "software only" solution.
>
>Now, it seems from what Om is saying that we can set up and use our own
>Jenkins slave node VM.
>
>That, of course, is much preferable...
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>Envoyé : mardi 10 décembre 2013 10:44
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Maurice,
>
>Your help is very much appreciated!
>
>I put "legal" in quotes, the issue is not really one of the law, more of
>the rules. An Apache release is supposed to be 'source only', and we if
>we can produce needed binaries from source, we keep only the source, not
>the artefacts themselves in the repo.
>
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
><ma...@systar.com> wrote:
>>>In addition to the various "legal" issues with binaries in the repo.
>> I understand it's not a good idea to have binaries in the repo, so I
>>won't insist.
>> But please can you explain what are the legal issues of having binaries
>>in the repo? Is this because of Adobe, or ASF rules ?
>>
>> On a side note, I was just trying to help, with my limited
>> understanding and knowledge, and because the email thread was titled
>> "help and advise needed" ;-)
>>
>> Regards,
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> In addition to the various "legal" issues with binaries in the repo,
>>we'd be masking the cause of this failure. In order to prevent further
>>deterioration of the build process, we need to figure out what went
>>wrong and fix it.
>>
>> EdB
>>
>> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
>> Took me while to figure out that I hadn't gone insane or if my
>> keyboard was broken ;-)
>>
>>
>>
>> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
>><ma...@systar.com> wrote:
>>>> someone who does use the pbj's will grab the nightly and complain.
>>>
>>> I don't understand.
>>> Why would someone complain if the pbj's are in the nightly?
>>>
>>> [From the other emai]
>>>>Apache repos aren't supposed to contain compiled code. The pbj files
>>>>were removed during the initial release audit.
>>>>I don't think a workaround can involve checking in the pbj files. But
>>>>we could borrow them from a prior release package temporarily.
>>>
>>>>So we could make the compilation conditional on a env parameter, and
>>>>set that in the Jenkins job accordingly?
>>>>Yes but ...
>>>
>>> Alex, the conversation is getting out synch, so I am not sure that I
>>>have understood what you said.
>>>
>>> So can we include the pbj in the repo, and have a parameter to
>>>conditionally compile the pbj ?
>>> - This parameter would be set by default to do the compilation (so
>>> that folks can recompile)
>>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>>
>>>
>>> Maurice
>>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
I understand that.
Actually, my "understanding" on this issue was that pixel bender compiler required some sort of hardware configuration (OpenGL, etc...) that were not present on the b.a.o. new Windows Jenkins slave node, so that's why the build was failing, and the Apache Infra was reluctant to let us modify anything, or even access the VM ourselves.
So that's why I was proposing a "software only" solution.
Now, it seems from what Om is saying that we can set up and use our own Jenkins slave node VM.
That, of course, is much preferable...
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : mardi 10 décembre 2013 10:44
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Maurice,
Your help is very much appreciated!
I put "legal" in quotes, the issue is not really one of the law, more of the rules. An Apache release is supposed to be 'source only', and we if we can produce needed binaries from source, we keep only the source, not the artefacts themselves in the repo.
EdB
On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>In addition to the various "legal" issues with binaries in the repo.
> I understand it's not a good idea to have binaries in the repo, so I won't insist.
> But please can you explain what are the legal issues of having binaries in the repo? Is this because of Adobe, or ASF rules ?
>
> On a side note, I was just trying to help, with my limited
> understanding and knowledge, and because the email thread was titled
> "help and advise needed" ;-)
>
> Regards,
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
> décembre 2013 09:12 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> In addition to the various "legal" issues with binaries in the repo, we'd be masking the cause of this failure. In order to prevent further deterioration of the build process, we need to figure out what went wrong and fix it.
>
> EdB
>
> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> Took me while to figure out that I hadn't gone insane or if my
> keyboard was broken ;-)
>
>
>
> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> someone who does use the pbj's will grab the nightly and complain.
>>
>> I don't understand.
>> Why would someone complain if the pbj's are in the nightly?
>>
>> [From the other emai]
>>>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit.
>>>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily.
>>
>>>So we could make the compilation conditional on a env parameter, and
>>>set that in the Jenkins job accordingly?
>>>Yes but ...
>>
>> Alex, the conversation is getting out synch, so I am not sure that I have understood what you said.
>>
>> So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ?
>> - This parameter would be set by default to do the compilation (so
>> that folks can recompile)
>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>
>>
>> Maurice
>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Maurice,
Your help is very much appreciated!
I put "legal" in quotes, the issue is not really one of the law, more
of the rules. An Apache release is supposed to be 'source only', and
we if we can produce needed binaries from source, we keep only the
source, not the artefacts themselves in the repo.
EdB
On Tue, Dec 10, 2013 at 10:34 AM, Maurice Amsellem
<ma...@systar.com> wrote:
>>In addition to the various "legal" issues with binaries in the repo.
> I understand it's not a good idea to have binaries in the repo, so I won't insist.
> But please can you explain what are the legal issues of having binaries in the repo? Is this because of Adobe, or ASF rules ?
>
> On a side note, I was just trying to help, with my limited understanding and knowledge, and because the email thread was titled "help and advise needed" ;-)
>
> Regards,
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> Envoyé : mardi 10 décembre 2013 09:12
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> In addition to the various "legal" issues with binaries in the repo, we'd be masking the cause of this failure. In order to prevent further deterioration of the build process, we need to figure out what went wrong and fix it.
>
> EdB
>
> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> Took me while to figure out that I hadn't gone insane or if my keyboard was broken ;-)
>
>
>
> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> someone who does use the pbj's will grab the nightly and complain.
>>
>> I don't understand.
>> Why would someone complain if the pbj's are in the nightly?
>>
>> [From the other emai]
>>>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit.
>>>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily.
>>
>>>So we could make the compilation conditional on a env parameter, and
>>>set that in the Jenkins job accordingly?
>>>Yes but ...
>>
>> Alex, the conversation is getting out synch, so I am not sure that I have understood what you said.
>>
>> So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ?
>> - This parameter would be set by default to do the compilation (so
>> that folks can recompile)
>> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>>
>>
>> Maurice
>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
>In addition to the various "legal" issues with binaries in the repo.
I understand it's not a good idea to have binaries in the repo, so I won't insist.
But please can you explain what are the legal issues of having binaries in the repo? Is this because of Adobe, or ASF rules ?
On a side note, I was just trying to help, with my limited understanding and knowledge, and because the email thread was titled "help and advise needed" ;-)
Regards,
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : mardi 10 décembre 2013 09:12
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
In addition to the various "legal" issues with binaries in the repo, we'd be masking the cause of this failure. In order to prevent further deterioration of the build process, we need to figure out what went wrong and fix it.
EdB
PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
Took me while to figure out that I hadn't gone insane or if my keyboard was broken ;-)
On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> someone who does use the pbj's will grab the nightly and complain.
>
> I don't understand.
> Why would someone complain if the pbj's are in the nightly?
>
> [From the other emai]
>>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit.
>>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily.
>
>>So we could make the compilation conditional on a env parameter, and
>>set that in the Jenkins job accordingly?
>>Yes but ...
>
> Alex, the conversation is getting out synch, so I am not sure that I have understood what you said.
>
> So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ?
> - This parameter would be set by default to do the compilation (so
> that folks can recompile)
> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>
>
> Maurice
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
I am really sorry for that.
Maurice
-----Message d'origine-----
De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash Muppirala
Envoyé : mardi 10 décembre 2013 09:27
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
On Dec 10, 2013 12:13 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> In addition to the various "legal" issues with binaries in the repo,
> we'd be masking the cause of this failure. In order to prevent further
> deterioration of the build process, we need to figure out what went
> wrong and fix it.
>
> EdB
>
> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> Took me while to figure out that I hadn't gone insane or if my
> keyboard was broken ;-)
Oh, that's what it was. I spent a whole session copy pasting commands from my computer on to the VM :-)
>
>
>
> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> <ma...@systar.com> wrote:
> >> someone who does use the pbj's will grab the nightly and complain.
> >
> > I don't understand.
> > Why would someone complain if the pbj's are in the nightly?
> >
> > [From the other emai]
> >>Apache repos aren't supposed to contain compiled code. The pbj
> >>files
were removed during the initial release audit.
> >>I don't think a workaround can involve checking in the pbj files.
> >>But
we could borrow them from a prior release package temporarily.
> >
> >>So we could make the compilation conditional on a env parameter,
> >>and set that in the Jenkins job accordingly?
> >>Yes but ...
> >
> > Alex, the conversation is getting out synch, so I am not sure that I
have understood what you said.
> >
> > So can we include the pbj in the repo, and have a parameter to
conditionally compile the pbj ?
> > - This parameter would be set by default to do the compilation (so
> > that
folks can recompile)
> > - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >
> >
> > Maurice
> >
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 10, 2013 12:13 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> In addition to the various "legal" issues with binaries in the repo,
> we'd be masking the cause of this failure. In order to prevent further
> deterioration of the build process, we need to figure out what went
> wrong and fix it.
>
> EdB
>
> PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> Took me while to figure out that I hadn't gone insane or if my
> keyboard was broken ;-)
Oh, that's what it was. I spent a whole session copy pasting commands from
my computer on to the VM :-)
>
>
>
> On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
> <ma...@systar.com> wrote:
> >> someone who does use the pbj's will grab the nightly and complain.
> >
> > I don't understand.
> > Why would someone complain if the pbj's are in the nightly?
> >
> > [From the other emai]
> >>Apache repos aren't supposed to contain compiled code. The pbj files
were removed during the initial release audit.
> >>I don't think a workaround can involve checking in the pbj files. But
we could borrow them from a prior release package temporarily.
> >
> >>So we could make the compilation conditional on a env parameter, and
> >>set that in the Jenkins job accordingly?
> >>Yes but ...
> >
> > Alex, the conversation is getting out synch, so I am not sure that I
have understood what you said.
> >
> > So can we include the pbj in the repo, and have a parameter to
conditionally compile the pbj ?
> > - This parameter would be set by default to do the compilation (so that
folks can recompile)
> > - and turned off on the b.a.o vm, with pre-compiled pbj's.
> >
> >
> > Maurice
> >
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
In addition to the various "legal" issues with binaries in the repo,
we'd be masking the cause of this failure. In order to prevent further
deterioration of the build process, we need to figure out what went
wrong and fix it.
EdB
PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
Took me while to figure out that I hadn't gone insane or if my
keyboard was broken ;-)
On Tue, Dec 10, 2013 at 9:04 AM, Maurice Amsellem
<ma...@systar.com> wrote:
>> someone who does use the pbj's will grab the nightly and complain.
>
> I don't understand.
> Why would someone complain if the pbj's are in the nightly?
>
> [From the other emai]
>>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit.
>>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily.
>
>>So we could make the compilation conditional on a env parameter, and
>>set that in the Jenkins job accordingly?
>>Yes but ...
>
> Alex, the conversation is getting out synch, so I am not sure that I have understood what you said.
>
> So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ?
> - This parameter would be set by default to do the compilation (so that folks can recompile)
> - and turned off on the b.a.o vm, with pre-compiled pbj's.
>
>
> Maurice
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
> someone who does use the pbj's will grab the nightly and complain.
I don't understand.
Why would someone complain if the pbj's are in the nightly?
[From the other emai]
>Apache repos aren't supposed to contain compiled code. The pbj files were removed during the initial release audit.
>I don't think a workaround can involve checking in the pbj files. But we could borrow them from a prior release package temporarily.
>So we could make the compilation conditional on a env parameter, and
>set that in the Jenkins job accordingly?
>Yes but ...
Alex, the conversation is getting out synch, so I am not sure that I have understood what you said.
So can we include the pbj in the repo, and have a parameter to conditionally compile the pbj ?
- This parameter would be set by default to do the compilation (so that folks can recompile)
- and turned off on the b.a.o vm, with pre-compiled pbj's.
Maurice
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
On 12/9/13 11:40 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>So we could make the compilation conditional on a env parameter, and set
>that in the Jenkins job accordingly?
Yes, but keep in mind that there is always a chance that someone who does
use the pbj's will grab the nightly and complain.
>
>
>Note: the current build has already a condition "unless=isLinux". Does
>this mean Pixel Bender will not compile on Linux machines ?
That's correct, we don't have a way to build the pbj files on Linux.
>
><target name="pixelbender-compile" unless="isLinux">
>
>Maurice
>
>-----Message d'origine-----
>De : Alex Harui [mailto:aharui@adobe.com]
>Envoyé : mardi 10 décembre 2013 08:33
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>We could take the pixel bender compilation out of the jenkins builds, but
>not our release package. It must contain the source and instructions for
>building it, and the binary package must contain that compiled source so
>folks don't have to compile it.
>
>The compiled pbj's should not be in the repo. Hopefully they were
>removed.
>
>-Alex
>
>On 12/9/13 11:26 PM, "Maurice Amsellem" <ma...@systar.com>
>wrote:
>
>>Simple yet radical proposition:
>>
>>The pbk shaders didn't evolve much, and the compiled pbj are already
>>committed to the repo (although git history says they have been removed).
>>So couldn't we simply comment/strip "pixelbender-compile" from the build
>>?
>>If it ever happens to change, we could then recompile the pbj and
>>recommit.
>>
>>What do you think ?
>>
>>Maurice
>>
>>-----Message d'origine-----
>>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>>décembre 2013 08:12 À : dev@flex.apache.org Objet : Re:
>>[Builds/Jenkins] Help and advise needed
>>
>>Remember, Gavin (builds@a.o) claim he changed nothing on the slave
>>that's now failing. I'm sure we didn't change anything on the Jenkins
>>job that is now failing. It isn't something in the SDK that's causing
>>this, lot's of people and the Mustella VM are building that regularly.
>>
>>Anyway: I'm not familiar with Pixelbender at all, is there some way we
>>can ask Gavin to test it on the slave that doesn't involve Jenkins?
>>Like a command line that he can simply copy-paste into a shell and give
>>us the results from?
>>
>>EdB
>>
>>
>>
>>On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>>> I tried to reproduce the failure on my machine but couldn't. I tried
>>> different path statements, removing the aif_* dlls, and changing
>>> execute rights on those dlls. I did find that the string "Internal
>>> Exception" is in the aif_core.dll.
>>>
>>> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>>> this on their local computers? Only on the Jenkins Windows Slave and
>>> Windows VM? What do they have in common? What version of Windows
>>> are they running? What kind of graphics cards do they have?
>>>
>>> -Alex
>>>
>>> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>wrote:
>>>
>>>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>>
>>>>> Ah, that thread looked like it was a year old. Did you work around
>>>>>it or just stop working on it?
>>>>
>>>>I just stopped working on it because I hit a dead end. I was
>>>>clueless as to how to fix it.
>>>>
>>>>>
>>>>> Other than checking the path, I don't have any ideas to try at the
>>>>>moment.
>>>>>
>>>>> On your Azure VM, if you manually launch the compiler from Windows
>>>>>command prompt you get this error, right?
>>>>>
>>>>
>>>>I will try it out tonight and let you know.
>>>>
>>>>Thanks,
>>>>Om
>>>>
>>>>> -Alex
>>>>>
>>>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>>wrote:
>>>>>
>>>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>> >>
>>>>> >> We keep hitting this error, but the mail archives do not
>>>>> >> document how
>>>>we
>>>>> >> fix it. This time, we should write down the answer. Om's hit
>>>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>>>> >>indicate that it ispath related, but the build.xml does at least
>>>>> >>check if the pbutil.exe
>>>>>exists
>>>>> >> and is passing on that.
>>>>> >>
>>>>> >
>>>>> >In my case, I have not been able to fix it. In fact, if we are
>>>>> >trying
>>>>>to
>>>>> >reproduce the problem, we could use my Mustella VM on Azure and
>>>>> >see if
>>>>>we
>>>>> >can figure out what is happening.
>>>>> >We can then apply that fix to the windows1 slave on
>>>>> >builds.apache.org
>>>>> >
>>>>> >Thanks,
>>>>> >Om
>>>>> >
>>>>> >> I'll try to see if I can repro on my windows box tonight.
>>>>> >>
>>>>> >> -Alex
>>>>> >>
>>>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>>>> >> <ma...@systar.com>
>>>>> >> wrote:
>>>>> >>
>>>>> >> >Thanks Erik for the clarification.
>>>>> >> >
>>>>> >> >I confirm to you, I had to send the updated swc manually for
>>>>> >> >testing because the nightly build was down.
>>>>> >> >
>>>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>>>> >> >checked
>>>>>the
>>>>> >> >archives, maybe have missed something.
>>>>> >> >
>>>>> >> >I can see from the build logs that pixel bender build failed
>>>>> >> >and it
>>>>> >>seems
>>>>> >> >to be a path issue.
>>>>> >> >If that's correct, this is the path I am using on my local
>>>>> >> >build in
>>>>>my
>>>>> >> >env.properties:
>>>>> >> >
>>>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>>>Utilities -
>>>>> >> >CS5\\Pixel Bender Toolkit 2
>>>>> >> >
>>>>> >> >I can see that in the build log, the path is:
>>>>> >> >
>>>>> >> >check-pixelbender-home:
>>>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>>>> >> >
>>>>> >> >When I run it on my local env, it gives the following:
>>>>> >> >
>>>>> >> >[echo]
>>>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
>>>>> >> >Utilities
>>>>> >> >- CS5\Pixel Bender Toolkit 2
>>>>> >> >
>>>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>>>> >> >
>>>>> >> >WDYT?
>>>>> >> >
>>>>> >> >Maurice
>>>>> >> >
>>>>> >> >-----Message d'origine-----
>>>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>>>> >> >[Builds/Jenkins] Help and advise needed
>>>>> >> >
>>>>> >> >Hi,
>>>>> >> >
>>>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>>>'build@a.o'
>>>>> >> >working. For those not subscribed to the builds list, the
>>>>> >> >situation
>>>>>is
>>>>> >>as
>>>>> >> >follows:
>>>>> >> >
>>>>> >> >- there are supposedly 9 admins for the windows1 slave, but
>>>>> >> >only one
>>>>is
>>>>> >> >sporadically active. I've requested access to the machine, but
>>>>> >> >got
>>>>>the
>>>>> >> >answer: "nine is enough." A suggestions there was actually only
>>>>> >> >one,
>>>>> >>with
>>>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>>>> >> >remove
>>>>> >>old,
>>>>> >> >inactive admins and add new, active ones
>>>>> >> >
>>>>> >> >- since the windows1 slave is old, full and overworked, it
>>>>> >> >regularly
>>>>> >>went
>>>>> >> >down for days on end. We are one of the few projects that uses
>>>>> >> >the windows slaves, so I ended up being the guy who always
>>>>> >> >complains the slave is down...
>>>>> >> >
>>>>> >> >- the one active admin is now working on a second slave
>>>>>(windows2).
>>>>>In
>>>>> >> >itself, that is a very good thing. However, in his own words,
>>>>> >> >"he
>>>>feels
>>>>> >> >entitled to use our builds to experiment." I feel that is
>>>>> >> >wrong,
>>>>>but I
>>>>> >> >know better than to further aggravate my relation with him by
>>>>objecting
>>>>> >> >too strongly.
>>>>> >> >
>>>>> >> >The point of this elaborate introduction is this: somewhere in
>>>>> >> >his experiments he broke the Windows slaves for our builds. We
>>>>> >> >have not
>>>>> >>had a
>>>>> >> >successful build in a week. Normally, not that big a deal, but
>>>>> >> >with
>>>>the
>>>>> >> >third party IDE people working on FlexJS and the very active
>>>>> >> >mobile development both relying on nightly builds, I feel this
>>>>> >> >is not a
>>>>>time
>>>>> >>to
>>>>> >> >NOT have clean, daily builds of all our projects...
>>>>> >> >
>>>>> >> >Anything 'negative' I say on the builds list will certainly
>>>>> >> >make
>>>>things
>>>>> >> >worse - my NL temperament and lack of finesse often does not
>>>>> >> >sit
>>>>>well
>>>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>>>> >> >on
>>>>>the
>>>>> >> >builds list and that we together get our builds back to
>>>>>functioning.
>>>>> >> >
>>>>> >> >Thanks!
>>>>> >> >
>>>>> >> >EdB
>>>>> >> >
>>>>> >> >
>>>>> >> >
>>>>> >> >--
>>>>> >> >Ix Multimedia Software
>>>>> >> >
>>>>> >> >Jan Luykenstraat 27
>>>>> >> >3521 VB Utrecht
>>>>> >> >
>>>>> >> >T. 06-51952295
>>>>> >> >I. www.ixsoftware.nl
>>>>> >>
>>>>>
>>>
>>
>>
>>
>>--
>>Ix Multimedia Software
>>
>>Jan Luykenstraat 27
>>3521 VB Utrecht
>>
>>T. 06-51952295
>>I. www.ixsoftware.nl
>
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
So we could make the compilation conditional on a env parameter, and set that in the Jenkins job accordingly?
Note: the current build has already a condition "unless=isLinux". Does this mean Pixel Bender will not compile on Linux machines ?
<target name="pixelbender-compile" unless="isLinux">
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 10 décembre 2013 08:33
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
We could take the pixel bender compilation out of the jenkins builds, but not our release package. It must contain the source and instructions for building it, and the binary package must contain that compiled source so folks don't have to compile it.
The compiled pbj's should not be in the repo. Hopefully they were removed.
-Alex
On 12/9/13 11:26 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Simple yet radical proposition:
>
>The pbk shaders didn't evolve much, and the compiled pbj are already
>committed to the repo (although git history says they have been removed).
>So couldn't we simply comment/strip "pixelbender-compile" from the build ?
>If it ever happens to change, we could then recompile the pbj and
>recommit.
>
>What do you think ?
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10
>décembre 2013 08:12 À : dev@flex.apache.org Objet : Re:
>[Builds/Jenkins] Help and advise needed
>
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave
>that's now failing. I'm sure we didn't change anything on the Jenkins
>job that is now failing. It isn't something in the SDK that's causing
>this, lot's of people and the Mustella VM are building that regularly.
>
>Anyway: I'm not familiar with Pixelbender at all, is there some way we
>can ask Gavin to test it on the slave that doesn't involve Jenkins?
>Like a command line that he can simply copy-paste into a shell and give
>us the results from?
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>> I tried to reproduce the failure on my machine but couldn't. I tried
>> different path statements, removing the aif_* dlls, and changing
>> execute rights on those dlls. I did find that the string "Internal
>> Exception" is in the aif_core.dll.
>>
>> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>> this on their local computers? Only on the Jenkins Windows Slave and
>> Windows VM? What do they have in common? What version of Windows
>> are they running? What kind of graphics cards do they have?
>>
>> -Alex
>>
>> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>
>>>> Ah, that thread looked like it was a year old. Did you work around
>>>>it or just stop working on it?
>>>
>>>I just stopped working on it because I hit a dead end. I was
>>>clueless as to how to fix it.
>>>
>>>>
>>>> Other than checking the path, I don't have any ideas to try at the
>>>>moment.
>>>>
>>>> On your Azure VM, if you manually launch the compiler from Windows
>>>>command prompt you get this error, right?
>>>>
>>>
>>>I will try it out tonight and let you know.
>>>
>>>Thanks,
>>>Om
>>>
>>>> -Alex
>>>>
>>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>wrote:
>>>>
>>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>> >>
>>>> >> We keep hitting this error, but the mail archives do not
>>>> >> document how
>>>we
>>>> >> fix it. This time, we should write down the answer. Om's hit
>>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>>> >>indicate that it ispath related, but the build.xml does at least
>>>> >>check if the pbutil.exe
>>>>exists
>>>> >> and is passing on that.
>>>> >>
>>>> >
>>>> >In my case, I have not been able to fix it. In fact, if we are
>>>> >trying
>>>>to
>>>> >reproduce the problem, we could use my Mustella VM on Azure and
>>>> >see if
>>>>we
>>>> >can figure out what is happening.
>>>> >We can then apply that fix to the windows1 slave on
>>>> >builds.apache.org
>>>> >
>>>> >Thanks,
>>>> >Om
>>>> >
>>>> >> I'll try to see if I can repro on my windows box tonight.
>>>> >>
>>>> >> -Alex
>>>> >>
>>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>>> >> <ma...@systar.com>
>>>> >> wrote:
>>>> >>
>>>> >> >Thanks Erik for the clarification.
>>>> >> >
>>>> >> >I confirm to you, I had to send the updated swc manually for
>>>> >> >testing because the nightly build was down.
>>>> >> >
>>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>>> >> >checked
>>>>the
>>>> >> >archives, maybe have missed something.
>>>> >> >
>>>> >> >I can see from the build logs that pixel bender build failed
>>>> >> >and it
>>>> >>seems
>>>> >> >to be a path issue.
>>>> >> >If that's correct, this is the path I am using on my local
>>>> >> >build in
>>>>my
>>>> >> >env.properties:
>>>> >> >
>>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>>Utilities -
>>>> >> >CS5\\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >I can see that in the build log, the path is:
>>>> >> >
>>>> >> >check-pixelbender-home:
>>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >When I run it on my local env, it gives the following:
>>>> >> >
>>>> >> >[echo]
>>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe
>>>> >> >Utilities
>>>> >> >- CS5\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>>> >> >
>>>> >> >WDYT?
>>>> >> >
>>>> >> >Maurice
>>>> >> >
>>>> >> >-----Message d'origine-----
>>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>>> >> >[Builds/Jenkins] Help and advise needed
>>>> >> >
>>>> >> >Hi,
>>>> >> >
>>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>>'build@a.o'
>>>> >> >working. For those not subscribed to the builds list, the
>>>> >> >situation
>>>>is
>>>> >>as
>>>> >> >follows:
>>>> >> >
>>>> >> >- there are supposedly 9 admins for the windows1 slave, but
>>>> >> >only one
>>>is
>>>> >> >sporadically active. I've requested access to the machine, but
>>>> >> >got
>>>>the
>>>> >> >answer: "nine is enough." A suggestions there was actually only
>>>> >> >one,
>>>> >>with
>>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>>> >> >remove
>>>> >>old,
>>>> >> >inactive admins and add new, active ones
>>>> >> >
>>>> >> >- since the windows1 slave is old, full and overworked, it
>>>> >> >regularly
>>>> >>went
>>>> >> >down for days on end. We are one of the few projects that uses
>>>> >> >the windows slaves, so I ended up being the guy who always
>>>> >> >complains the slave is down...
>>>> >> >
>>>> >> >- the one active admin is now working on a second slave
>>>>(windows2).
>>>>In
>>>> >> >itself, that is a very good thing. However, in his own words,
>>>> >> >"he
>>>feels
>>>> >> >entitled to use our builds to experiment." I feel that is
>>>> >> >wrong,
>>>>but I
>>>> >> >know better than to further aggravate my relation with him by
>>>objecting
>>>> >> >too strongly.
>>>> >> >
>>>> >> >The point of this elaborate introduction is this: somewhere in
>>>> >> >his experiments he broke the Windows slaves for our builds. We
>>>> >> >have not
>>>> >>had a
>>>> >> >successful build in a week. Normally, not that big a deal, but
>>>> >> >with
>>>the
>>>> >> >third party IDE people working on FlexJS and the very active
>>>> >> >mobile development both relying on nightly builds, I feel this
>>>> >> >is not a
>>>>time
>>>> >>to
>>>> >> >NOT have clean, daily builds of all our projects...
>>>> >> >
>>>> >> >Anything 'negative' I say on the builds list will certainly
>>>> >> >make
>>>things
>>>> >> >worse - my NL temperament and lack of finesse often does not
>>>> >> >sit
>>>>well
>>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>>> >> >on
>>>>the
>>>> >> >builds list and that we together get our builds back to
>>>>functioning.
>>>> >> >
>>>> >> >Thanks!
>>>> >> >
>>>> >> >EdB
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >--
>>>> >> >Ix Multimedia Software
>>>> >> >
>>>> >> >Jan Luykenstraat 27
>>>> >> >3521 VB Utrecht
>>>> >> >
>>>> >> >T. 06-51952295
>>>> >> >I. www.ixsoftware.nl
>>>> >>
>>>>
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Apache repos aren't supposed to contain compiled code. The pbj files were
removed during the initial release audit.
I don't think a workaround can involve checking in the pbj files. But we
could borrow them from a prior release package temporarily.
-Alex
On 12/9/13 11:35 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Actually, *.pbj are ignored by git, so the files aren't there, although
>they were in the past (cf. git log).
>But the idea is the same.
>
>-----Message d'origine-----
>De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
>Envoyé : mardi 10 décembre 2013 08:27
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Simple yet radical proposition:
>
>The pbk shaders didn't evolve much, and the compiled pbj are already
>committed to the repo (although git history says they have been removed).
>So couldn't we simply comment/strip "pixelbender-compile" from the build ?
>If it ever happens to change, we could then recompile the pbj and
>recommit.
>
>What do you think ?
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10 décembre
>2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and
>advise needed
>
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's
>now failing. I'm sure we didn't change anything on the Jenkins job that
>is now failing. It isn't something in the SDK that's causing this, lot's
>of people and the Mustella VM are building that regularly.
>
>Anyway: I'm not familiar with Pixelbender at all, is there some way we
>can ask Gavin to test it on the slave that doesn't involve Jenkins?
>Like a command line that he can simply copy-paste into a shell and give
>us the results from?
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>> I tried to reproduce the failure on my machine but couldn't. I tried
>> different path statements, removing the aif_* dlls, and changing
>> execute rights on those dlls. I did find that the string "Internal
>> Exception" is in the aif_core.dll.
>>
>> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>> this on their local computers? Only on the Jenkins Windows Slave and
>> Windows VM? What do they have in common? What version of Windows are
>> they running? What kind of graphics cards do they have?
>>
>> -Alex
>>
>> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>
>>>> Ah, that thread looked like it was a year old. Did you work around
>>>>it or just stop working on it?
>>>
>>>I just stopped working on it because I hit a dead end. I was clueless
>>>as to how to fix it.
>>>
>>>>
>>>> Other than checking the path, I don't have any ideas to try at the
>>>>moment.
>>>>
>>>> On your Azure VM, if you manually launch the compiler from Windows
>>>>command prompt you get this error, right?
>>>>
>>>
>>>I will try it out tonight and let you know.
>>>
>>>Thanks,
>>>Om
>>>
>>>> -Alex
>>>>
>>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>wrote:
>>>>
>>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>> >>
>>>> >> We keep hitting this error, but the mail archives do not document
>>>> >> how
>>>we
>>>> >> fix it. This time, we should write down the answer. Om's hit
>>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>>> >>indicate that it ispath related, but the build.xml does at least
>>>> >>check if the pbutil.exe
>>>>exists
>>>> >> and is passing on that.
>>>> >>
>>>> >
>>>> >In my case, I have not been able to fix it. In fact, if we are
>>>> >trying
>>>>to
>>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>>>> >if
>>>>we
>>>> >can figure out what is happening.
>>>> >We can then apply that fix to the windows1 slave on
>>>> >builds.apache.org
>>>> >
>>>> >Thanks,
>>>> >Om
>>>> >
>>>> >> I'll try to see if I can repro on my windows box tonight.
>>>> >>
>>>> >> -Alex
>>>> >>
>>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>>> >> <ma...@systar.com>
>>>> >> wrote:
>>>> >>
>>>> >> >Thanks Erik for the clarification.
>>>> >> >
>>>> >> >I confirm to you, I had to send the updated swc manually for
>>>> >> >testing because the nightly build was down.
>>>> >> >
>>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>>> >> >checked
>>>>the
>>>> >> >archives, maybe have missed something.
>>>> >> >
>>>> >> >I can see from the build logs that pixel bender build failed and
>>>> >> >it
>>>> >>seems
>>>> >> >to be a path issue.
>>>> >> >If that's correct, this is the path I am using on my local build
>>>> >> >in
>>>>my
>>>> >> >env.properties:
>>>> >> >
>>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>>Utilities -
>>>> >> >CS5\\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >I can see that in the build log, the path is:
>>>> >> >
>>>> >> >check-pixelbender-home:
>>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >When I run it on my local env, it gives the following:
>>>> >> >
>>>> >> >[echo]
>>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
>>>> >> >- CS5\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>>> >> >
>>>> >> >WDYT?
>>>> >> >
>>>> >> >Maurice
>>>> >> >
>>>> >> >-----Message d'origine-----
>>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>>> >> >[Builds/Jenkins] Help and advise needed
>>>> >> >
>>>> >> >Hi,
>>>> >> >
>>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>>'build@a.o'
>>>> >> >working. For those not subscribed to the builds list, the
>>>> >> >situation
>>>>is
>>>> >>as
>>>> >> >follows:
>>>> >> >
>>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>>>> >> >one
>>>is
>>>> >> >sporadically active. I've requested access to the machine, but
>>>> >> >got
>>>>the
>>>> >> >answer: "nine is enough." A suggestions there was actually only
>>>> >> >one,
>>>> >>with
>>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>>> >> >remove
>>>> >>old,
>>>> >> >inactive admins and add new, active ones
>>>> >> >
>>>> >> >- since the windows1 slave is old, full and overworked, it
>>>> >> >regularly
>>>> >>went
>>>> >> >down for days on end. We are one of the few projects that uses
>>>> >> >the windows slaves, so I ended up being the guy who always
>>>> >> >complains the slave is down...
>>>> >> >
>>>> >> >- the one active admin is now working on a second slave
>>>>(windows2).
>>>>In
>>>> >> >itself, that is a very good thing. However, in his own words,
>>>> >> >"he
>>>feels
>>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>>but I
>>>> >> >know better than to further aggravate my relation with him by
>>>objecting
>>>> >> >too strongly.
>>>> >> >
>>>> >> >The point of this elaborate introduction is this: somewhere in
>>>> >> >his experiments he broke the Windows slaves for our builds. We
>>>> >> >have not
>>>> >>had a
>>>> >> >successful build in a week. Normally, not that big a deal, but
>>>> >> >with
>>>the
>>>> >> >third party IDE people working on FlexJS and the very active
>>>> >> >mobile development both relying on nightly builds, I feel this
>>>> >> >is not a
>>>>time
>>>> >>to
>>>> >> >NOT have clean, daily builds of all our projects...
>>>> >> >
>>>> >> >Anything 'negative' I say on the builds list will certainly make
>>>things
>>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>>well
>>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>>> >> >on
>>>>the
>>>> >> >builds list and that we together get our builds back to
>>>>functioning.
>>>> >> >
>>>> >> >Thanks!
>>>> >> >
>>>> >> >EdB
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >--
>>>> >> >Ix Multimedia Software
>>>> >> >
>>>> >> >Jan Luykenstraat 27
>>>> >> >3521 VB Utrecht
>>>> >> >
>>>> >> >T. 06-51952295
>>>> >> >I. www.ixsoftware.nl
>>>> >>
>>>>
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Actually, *.pbj are ignored by git, so the files aren't there, although they were in the past (cf. git log).
But the idea is the same.
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : mardi 10 décembre 2013 08:27
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Simple yet radical proposition:
The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed).
So couldn't we simply comment/strip "pixelbender-compile" from the build ?
If it ever happens to change, we could then recompile the pbj and recommit.
What do you think ?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : mardi 10 décembre 2013 08:12 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly.
Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins?
Like a command line that he can simply copy-paste into a shell and give us the results from?
EdB
On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
> I tried to reproduce the failure on my machine but couldn't. I tried
> different path statements, removing the aif_* dlls, and changing
> execute rights on those dlls. I did find that the string "Internal
> Exception" is in the aif_core.dll.
>
> Not sure what to do next, but now I'm thinking: maybe nobody has seen
> this on their local computers? Only on the Jenkins Windows Slave and
> Windows VM? What do they have in common? What version of Windows are
> they running? What kind of graphics cards do they have?
>
> -Alex
>
> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>> Ah, that thread looked like it was a year old. Did you work around
>>>it or just stop working on it?
>>
>>I just stopped working on it because I hit a dead end. I was clueless
>>as to how to fix it.
>>
>>>
>>> Other than checking the path, I don't have any ideas to try at the
>>>moment.
>>>
>>> On your Azure VM, if you manually launch the compiler from Windows
>>>command prompt you get this error, right?
>>>
>>
>>I will try it out tonight and let you know.
>>
>>Thanks,
>>Om
>>
>>> -Alex
>>>
>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>> >>
>>> >> We keep hitting this error, but the mail archives do not document
>>> >> how
>>we
>>> >> fix it. This time, we should write down the answer. Om's hit
>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>> >>indicate that it ispath related, but the build.xml does at least
>>> >>check if the pbutil.exe
>>>exists
>>> >> and is passing on that.
>>> >>
>>> >
>>> >In my case, I have not been able to fix it. In fact, if we are
>>> >trying
>>>to
>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>>> >if
>>>we
>>> >can figure out what is happening.
>>> >We can then apply that fix to the windows1 slave on
>>> >builds.apache.org
>>> >
>>> >Thanks,
>>> >Om
>>> >
>>> >> I'll try to see if I can repro on my windows box tonight.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>> >> <ma...@systar.com>
>>> >> wrote:
>>> >>
>>> >> >Thanks Erik for the clarification.
>>> >> >
>>> >> >I confirm to you, I had to send the updated swc manually for
>>> >> >testing because the nightly build was down.
>>> >> >
>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>> >> >checked
>>>the
>>> >> >archives, maybe have missed something.
>>> >> >
>>> >> >I can see from the build logs that pixel bender build failed and
>>> >> >it
>>> >>seems
>>> >> >to be a path issue.
>>> >> >If that's correct, this is the path I am using on my local build
>>> >> >in
>>>my
>>> >> >env.properties:
>>> >> >
>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>Utilities -
>>> >> >CS5\\Pixel Bender Toolkit 2
>>> >> >
>>> >> >I can see that in the build log, the path is:
>>> >> >
>>> >> >check-pixelbender-home:
>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>> >> >
>>> >> >When I run it on my local env, it gives the following:
>>> >> >
>>> >> >[echo]
>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
>>> >> >- CS5\Pixel Bender Toolkit 2
>>> >> >
>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>> >> >
>>> >> >WDYT?
>>> >> >
>>> >> >Maurice
>>> >> >
>>> >> >-----Message d'origine-----
>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>> >> >[Builds/Jenkins] Help and advise needed
>>> >> >
>>> >> >Hi,
>>> >> >
>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>'build@a.o'
>>> >> >working. For those not subscribed to the builds list, the
>>> >> >situation
>>>is
>>> >>as
>>> >> >follows:
>>> >> >
>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>>> >> >one
>>is
>>> >> >sporadically active. I've requested access to the machine, but
>>> >> >got
>>>the
>>> >> >answer: "nine is enough." A suggestions there was actually only
>>> >> >one,
>>> >>with
>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>> >> >remove
>>> >>old,
>>> >> >inactive admins and add new, active ones
>>> >> >
>>> >> >- since the windows1 slave is old, full and overworked, it
>>> >> >regularly
>>> >>went
>>> >> >down for days on end. We are one of the few projects that uses
>>> >> >the windows slaves, so I ended up being the guy who always
>>> >> >complains the slave is down...
>>> >> >
>>> >> >- the one active admin is now working on a second slave (windows2).
>>>In
>>> >> >itself, that is a very good thing. However, in his own words,
>>> >> >"he
>>feels
>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>but I
>>> >> >know better than to further aggravate my relation with him by
>>objecting
>>> >> >too strongly.
>>> >> >
>>> >> >The point of this elaborate introduction is this: somewhere in
>>> >> >his experiments he broke the Windows slaves for our builds. We
>>> >> >have not
>>> >>had a
>>> >> >successful build in a week. Normally, not that big a deal, but
>>> >> >with
>>the
>>> >> >third party IDE people working on FlexJS and the very active
>>> >> >mobile development both relying on nightly builds, I feel this
>>> >> >is not a
>>>time
>>> >>to
>>> >> >NOT have clean, daily builds of all our projects...
>>> >> >
>>> >> >Anything 'negative' I say on the builds list will certainly make
>>things
>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>well
>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>> >> >on
>>>the
>>> >> >builds list and that we together get our builds back to functioning.
>>> >> >
>>> >> >Thanks!
>>> >> >
>>> >> >EdB
>>> >> >
>>> >> >
>>> >> >
>>> >> >--
>>> >> >Ix Multimedia Software
>>> >> >
>>> >> >Jan Luykenstraat 27
>>> >> >3521 VB Utrecht
>>> >> >
>>> >> >T. 06-51952295
>>> >> >I. www.ixsoftware.nl
>>> >>
>>>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
We could take the pixel bender compilation out of the jenkins builds, but
not our release package. It must contain the source and instructions for
building it, and the binary package must contain that compiled source so
folks don't have to compile it.
The compiled pbj's should not be in the repo. Hopefully they were removed.
-Alex
On 12/9/13 11:26 PM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Simple yet radical proposition:
>
>The pbk shaders didn't evolve much, and the compiled pbj are already
>committed to the repo (although git history says they have been removed).
>So couldn't we simply comment/strip "pixelbender-compile" from the build ?
>If it ever happens to change, we could then recompile the pbj and
>recommit.
>
>What do you think ?
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>Envoyé : mardi 10 décembre 2013 08:12
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's
>now failing. I'm sure we didn't change anything on the Jenkins job that
>is now failing. It isn't something in the SDK that's causing this, lot's
>of people and the Mustella VM are building that regularly.
>
>Anyway: I'm not familiar with Pixelbender at all, is there some way we
>can ask Gavin to test it on the slave that doesn't involve Jenkins?
>Like a command line that he can simply copy-paste into a shell and give
>us the results from?
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>> I tried to reproduce the failure on my machine but couldn't. I tried
>> different path statements, removing the aif_* dlls, and changing
>> execute rights on those dlls. I did find that the string "Internal
>> Exception" is in the aif_core.dll.
>>
>> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>> this on their local computers? Only on the Jenkins Windows Slave and
>> Windows VM? What do they have in common? What version of Windows are
>> they running? What kind of graphics cards do they have?
>>
>> -Alex
>>
>> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>
>>>> Ah, that thread looked like it was a year old. Did you work around
>>>>it or just stop working on it?
>>>
>>>I just stopped working on it because I hit a dead end. I was clueless
>>>as to how to fix it.
>>>
>>>>
>>>> Other than checking the path, I don't have any ideas to try at the
>>>>moment.
>>>>
>>>> On your Azure VM, if you manually launch the compiler from Windows
>>>>command prompt you get this error, right?
>>>>
>>>
>>>I will try it out tonight and let you know.
>>>
>>>Thanks,
>>>Om
>>>
>>>> -Alex
>>>>
>>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>wrote:
>>>>
>>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>> >>
>>>> >> We keep hitting this error, but the mail archives do not document
>>>> >> how
>>>we
>>>> >> fix it. This time, we should write down the answer. Om's hit
>>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>>> >>indicate that it ispath related, but the build.xml does at least
>>>> >>check if the pbutil.exe
>>>>exists
>>>> >> and is passing on that.
>>>> >>
>>>> >
>>>> >In my case, I have not been able to fix it. In fact, if we are
>>>> >trying
>>>>to
>>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>>>> >if
>>>>we
>>>> >can figure out what is happening.
>>>> >We can then apply that fix to the windows1 slave on
>>>> >builds.apache.org
>>>> >
>>>> >Thanks,
>>>> >Om
>>>> >
>>>> >> I'll try to see if I can repro on my windows box tonight.
>>>> >>
>>>> >> -Alex
>>>> >>
>>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>>> >> <ma...@systar.com>
>>>> >> wrote:
>>>> >>
>>>> >> >Thanks Erik for the clarification.
>>>> >> >
>>>> >> >I confirm to you, I had to send the updated swc manually for
>>>> >> >testing because the nightly build was down.
>>>> >> >
>>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>>> >> >checked
>>>>the
>>>> >> >archives, maybe have missed something.
>>>> >> >
>>>> >> >I can see from the build logs that pixel bender build failed and
>>>> >> >it
>>>> >>seems
>>>> >> >to be a path issue.
>>>> >> >If that's correct, this is the path I am using on my local build
>>>> >> >in
>>>>my
>>>> >> >env.properties:
>>>> >> >
>>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>>Utilities -
>>>> >> >CS5\\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >I can see that in the build log, the path is:
>>>> >> >
>>>> >> >check-pixelbender-home:
>>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >When I run it on my local env, it gives the following:
>>>> >> >
>>>> >> >[echo]
>>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
>>>> >> >- CS5\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>>> >> >
>>>> >> >WDYT?
>>>> >> >
>>>> >> >Maurice
>>>> >> >
>>>> >> >-----Message d'origine-----
>>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>>> >> >[Builds/Jenkins] Help and advise needed
>>>> >> >
>>>> >> >Hi,
>>>> >> >
>>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>>'build@a.o'
>>>> >> >working. For those not subscribed to the builds list, the
>>>> >> >situation
>>>>is
>>>> >>as
>>>> >> >follows:
>>>> >> >
>>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>>>> >> >one
>>>is
>>>> >> >sporadically active. I've requested access to the machine, but
>>>> >> >got
>>>>the
>>>> >> >answer: "nine is enough." A suggestions there was actually only
>>>> >> >one,
>>>> >>with
>>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>>> >> >remove
>>>> >>old,
>>>> >> >inactive admins and add new, active ones
>>>> >> >
>>>> >> >- since the windows1 slave is old, full and overworked, it
>>>> >> >regularly
>>>> >>went
>>>> >> >down for days on end. We are one of the few projects that uses
>>>> >> >the windows slaves, so I ended up being the guy who always
>>>> >> >complains the slave is down...
>>>> >> >
>>>> >> >- the one active admin is now working on a second slave
>>>>(windows2).
>>>>In
>>>> >> >itself, that is a very good thing. However, in his own words,
>>>> >> >"he
>>>feels
>>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>>but I
>>>> >> >know better than to further aggravate my relation with him by
>>>objecting
>>>> >> >too strongly.
>>>> >> >
>>>> >> >The point of this elaborate introduction is this: somewhere in
>>>> >> >his experiments he broke the Windows slaves for our builds. We
>>>> >> >have not
>>>> >>had a
>>>> >> >successful build in a week. Normally, not that big a deal, but
>>>> >> >with
>>>the
>>>> >> >third party IDE people working on FlexJS and the very active
>>>> >> >mobile development both relying on nightly builds, I feel this
>>>> >> >is not a
>>>>time
>>>> >>to
>>>> >> >NOT have clean, daily builds of all our projects...
>>>> >> >
>>>> >> >Anything 'negative' I say on the builds list will certainly make
>>>things
>>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>>well
>>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>>> >> >on
>>>>the
>>>> >> >builds list and that we together get our builds back to
>>>>functioning.
>>>> >> >
>>>> >> >Thanks!
>>>> >> >
>>>> >> >EdB
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >--
>>>> >> >Ix Multimedia Software
>>>> >> >
>>>> >> >Jan Luykenstraat 27
>>>> >> >3521 VB Utrecht
>>>> >> >
>>>> >> >T. 06-51952295
>>>> >> >I. www.ixsoftware.nl
>>>> >>
>>>>
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Simple yet radical proposition:
The pbk shaders didn't evolve much, and the compiled pbj are already committed to the repo (although git history says they have been removed).
So couldn't we simply comment/strip "pixelbender-compile" from the build ?
If it ever happens to change, we could then recompile the pbj and recommit.
What do you think ?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : mardi 10 décembre 2013 08:12
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's now failing. I'm sure we didn't change anything on the Jenkins job that is now failing. It isn't something in the SDK that's causing this, lot's of people and the Mustella VM are building that regularly.
Anyway: I'm not familiar with Pixelbender at all, is there some way we can ask Gavin to test it on the slave that doesn't involve Jenkins?
Like a command line that he can simply copy-paste into a shell and give us the results from?
EdB
On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
> I tried to reproduce the failure on my machine but couldn't. I tried
> different path statements, removing the aif_* dlls, and changing
> execute rights on those dlls. I did find that the string "Internal
> Exception" is in the aif_core.dll.
>
> Not sure what to do next, but now I'm thinking: maybe nobody has seen
> this on their local computers? Only on the Jenkins Windows Slave and
> Windows VM? What do they have in common? What version of Windows are
> they running? What kind of graphics cards do they have?
>
> -Alex
>
> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>> Ah, that thread looked like it was a year old. Did you work around
>>>it or just stop working on it?
>>
>>I just stopped working on it because I hit a dead end. I was clueless
>>as to how to fix it.
>>
>>>
>>> Other than checking the path, I don't have any ideas to try at the
>>>moment.
>>>
>>> On your Azure VM, if you manually launch the compiler from Windows
>>>command prompt you get this error, right?
>>>
>>
>>I will try it out tonight and let you know.
>>
>>Thanks,
>>Om
>>
>>> -Alex
>>>
>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>> >>
>>> >> We keep hitting this error, but the mail archives do not document
>>> >> how
>>we
>>> >> fix it. This time, we should write down the answer. Om's hit
>>> >>it, Justin hit it, I think I had it once. The emails seem to
>>> >>indicate that it ispath related, but the build.xml does at least
>>> >>check if the pbutil.exe
>>>exists
>>> >> and is passing on that.
>>> >>
>>> >
>>> >In my case, I have not been able to fix it. In fact, if we are
>>> >trying
>>>to
>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>>> >if
>>>we
>>> >can figure out what is happening.
>>> >We can then apply that fix to the windows1 slave on
>>> >builds.apache.org
>>> >
>>> >Thanks,
>>> >Om
>>> >
>>> >> I'll try to see if I can repro on my windows box tonight.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>> >> <ma...@systar.com>
>>> >> wrote:
>>> >>
>>> >> >Thanks Erik for the clarification.
>>> >> >
>>> >> >I confirm to you, I had to send the updated swc manually for
>>> >> >testing because the nightly build was down.
>>> >> >
>>> >> >Sorry, I didn't follow the thread from the beginning, so I
>>> >> >checked
>>>the
>>> >> >archives, maybe have missed something.
>>> >> >
>>> >> >I can see from the build logs that pixel bender build failed and
>>> >> >it
>>> >>seems
>>> >> >to be a path issue.
>>> >> >If that's correct, this is the path I am using on my local build
>>> >> >in
>>>my
>>> >> >env.properties:
>>> >> >
>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>Utilities -
>>> >> >CS5\\Pixel Bender Toolkit 2
>>> >> >
>>> >> >I can see that in the build log, the path is:
>>> >> >
>>> >> >check-pixelbender-home:
>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files
>>> >> >(x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
>>> >> >
>>> >> >When I run it on my local env, it gives the following:
>>> >> >
>>> >> >[echo]
>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities
>>> >> >- CS5\Pixel Bender Toolkit 2
>>> >> >
>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>> >> >
>>> >> >WDYT?
>>> >> >
>>> >> >Maurice
>>> >> >
>>> >> >-----Message d'origine-----
>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> >> >décembre 2013 08:53 À : dev@flex.apache.org Objet :
>>> >> >[Builds/Jenkins] Help and advise needed
>>> >> >
>>> >> >Hi,
>>> >> >
>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>'build@a.o'
>>> >> >working. For those not subscribed to the builds list, the
>>> >> >situation
>>>is
>>> >>as
>>> >> >follows:
>>> >> >
>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>>> >> >one
>>is
>>> >> >sporadically active. I've requested access to the machine, but
>>> >> >got
>>>the
>>> >> >answer: "nine is enough." A suggestions there was actually only
>>> >> >one,
>>> >>with
>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>> >> >remove
>>> >>old,
>>> >> >inactive admins and add new, active ones
>>> >> >
>>> >> >- since the windows1 slave is old, full and overworked, it
>>> >> >regularly
>>> >>went
>>> >> >down for days on end. We are one of the few projects that uses
>>> >> >the windows slaves, so I ended up being the guy who always
>>> >> >complains the slave is down...
>>> >> >
>>> >> >- the one active admin is now working on a second slave (windows2).
>>>In
>>> >> >itself, that is a very good thing. However, in his own words,
>>> >> >"he
>>feels
>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>but I
>>> >> >know better than to further aggravate my relation with him by
>>objecting
>>> >> >too strongly.
>>> >> >
>>> >> >The point of this elaborate introduction is this: somewhere in
>>> >> >his experiments he broke the Windows slaves for our builds. We
>>> >> >have not
>>> >>had a
>>> >> >successful build in a week. Normally, not that big a deal, but
>>> >> >with
>>the
>>> >> >third party IDE people working on FlexJS and the very active
>>> >> >mobile development both relying on nightly builds, I feel this
>>> >> >is not a
>>>time
>>> >>to
>>> >> >NOT have clean, daily builds of all our projects...
>>> >> >
>>> >> >Anything 'negative' I say on the builds list will certainly make
>>things
>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>well
>>> >> >with US recipients ;-) - so I would ask you to please chime in
>>> >> >on
>>>the
>>> >> >builds list and that we together get our builds back to functioning.
>>> >> >
>>> >> >Thanks!
>>> >> >
>>> >> >EdB
>>> >> >
>>> >> >
>>> >> >
>>> >> >--
>>> >> >Ix Multimedia Software
>>> >> >
>>> >> >Jan Luykenstraat 27
>>> >> >3521 VB Utrecht
>>> >> >
>>> >> >T. 06-51952295
>>> >> >I. www.ixsoftware.nl
>>> >>
>>>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
On 12/9/13 11:12 PM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave
>that's now failing. I'm sure we didn't change anything on the Jenkins
>job that is now failing. It isn't something in the SDK that's causing
>this, lot's of people and the Mustella VM are building that regularly.
>
>Anyway: I'm not familiar with Pixelbender at all, is there some way we
>can ask Gavin to test it on the slave that doesn't involve Jenkins?
>Like a command line that he can simply copy-paste into a shell and
>give us the results from?
Yeah, it is a pretty simple compiler. All we do is give it a command that
is effectively pbutil <input> <output> as in:
"$PIXELBENDER_HOME\pbutil.exe"
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
r.pbk
$FLEX_HOME\frameworks\projects\framework\src\mx\graphics\shaderClasses\Colo
r.pbj
If you have a windows machine please verify that I didn't type that wrong,
I'm on my mac right now.
I know everyone claims "nothing changed". But I'm wondering if we can
compare Om's VM setup against yours and fix Om's setup before we go back
and bug Gavin. Meanwhile, I'm trying to find the source to the compiler.
I have a wild guess that the aif dlls have some silly check for graphic
cards or some other Photoshop or After Effects dependency. Or maybe some
OpenGL library that comes with newer versions of Windows. If it is a
graphics card thing then some hardware change or configuration outside the
slave itself could have caused things to fail. Then everyone would
technically be right that the nothing changed in the Slave or our code.
-Alex
>
>EdB
>
>
>
>On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
>> I tried to reproduce the failure on my machine but couldn't. I tried
>> different path statements, removing the aif_* dlls, and changing execute
>> rights on those dlls. I did find that the string "Internal Exception"
>>is
>> in the aif_core.dll.
>>
>> Not sure what to do next, but now I'm thinking: maybe nobody has seen
>>this
>> on their local computers? Only on the Jenkins Windows Slave and Windows
>> VM? What do they have in common? What version of Windows are they
>> running? What kind of graphics cards do they have?
>>
>> -Alex
>>
>> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>>
>>>> Ah, that thread looked like it was a year old. Did you work around it
>>>>or
>>>> just stop working on it?
>>>
>>>I just stopped working on it because I hit a dead end. I was clueless
>>>as
>>>to how to fix it.
>>>
>>>>
>>>> Other than checking the path, I don't have any ideas to try at the
>>>>moment.
>>>>
>>>> On your Azure VM, if you manually launch the compiler from Windows
>>>>command
>>>> prompt you get this error, right?
>>>>
>>>
>>>I will try it out tonight and let you know.
>>>
>>>Thanks,
>>>Om
>>>
>>>> -Alex
>>>>
>>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>>wrote:
>>>>
>>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>> >>
>>>> >> We keep hitting this error, but the mail archives do not document
>>>>how
>>>we
>>>> >> fix it. This time, we should write down the answer. Om's hit it,
>>>> >>Justin
>>>> >> hit it, I think I had it once. The emails seem to indicate that it
>>>> >>ispath
>>>> >> related, but the build.xml does at least check if the pbutil.exe
>>>>exists
>>>> >> and is passing on that.
>>>> >>
>>>> >
>>>> >In my case, I have not been able to fix it. In fact, if we are
>>>>trying
>>>>to
>>>> >reproduce the problem, we could use my Mustella VM on Azure and see
>>>>if
>>>>we
>>>> >can figure out what is happening.
>>>> >We can then apply that fix to the windows1 slave on builds.apache.org
>>>> >
>>>> >Thanks,
>>>> >Om
>>>> >
>>>> >> I'll try to see if I can repro on my windows box tonight.
>>>> >>
>>>> >> -Alex
>>>> >>
>>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem"
>>>><ma...@systar.com>
>>>> >> wrote:
>>>> >>
>>>> >> >Thanks Erik for the clarification.
>>>> >> >
>>>> >> >I confirm to you, I had to send the updated swc manually for
>>>>testing
>>>> >> >because the nightly build was down.
>>>> >> >
>>>> >> >Sorry, I didn't follow the thread from the beginning, so I checked
>>>>the
>>>> >> >archives, maybe have missed something.
>>>> >> >
>>>> >> >I can see from the build logs that pixel bender build failed and
>>>>it
>>>> >>seems
>>>> >> >to be a path issue.
>>>> >> >If that's correct, this is the path I am using on my local build
>>>>in
>>>>my
>>>> >> >env.properties:
>>>> >> >
>>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>>Utilities -
>>>> >> >CS5\\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >I can see that in the build log, the path is:
>>>> >> >
>>>> >> >check-pixelbender-home:
>>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
>>>> >> >Utilities - CS5/Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >When I run it on my local env, it gives the following:
>>>> >> >
>>>> >> >[echo]
>>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>>>> >> >CS5\Pixel Bender Toolkit 2
>>>> >> >
>>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>>> >> >
>>>> >> >WDYT?
>>>> >> >
>>>> >> >Maurice
>>>> >> >
>>>> >> >-----Message d'origine-----
>>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>> >> >Envoyé : lundi 9 décembre 2013 08:53
>>>> >> >À : dev@flex.apache.org
>>>> >> >Objet : [Builds/Jenkins] Help and advise needed
>>>> >> >
>>>> >> >Hi,
>>>> >> >
>>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>>'build@a.o'
>>>> >> >working. For those not subscribed to the builds list, the
>>>>situation
>>>>is
>>>> >>as
>>>> >> >follows:
>>>> >> >
>>>> >> >- there are supposedly 9 admins for the windows1 slave, but only
>>>>one
>>>is
>>>> >> >sporadically active. I've requested access to the machine, but got
>>>>the
>>>> >> >answer: "nine is enough." A suggestions there was actually only
>>>>one,
>>>> >>with
>>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to
>>>>remove
>>>> >>old,
>>>> >> >inactive admins and add new, active ones
>>>> >> >
>>>> >> >- since the windows1 slave is old, full and overworked, it
>>>>regularly
>>>> >>went
>>>> >> >down for days on end. We are one of the few projects that uses the
>>>> >> >windows slaves, so I ended up being the guy who always complains
>>>>the
>>>> >> >slave is down...
>>>> >> >
>>>> >> >- the one active admin is now working on a second slave
>>>>(windows2).
>>>>In
>>>> >> >itself, that is a very good thing. However, in his own words, "he
>>>feels
>>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>>but I
>>>> >> >know better than to further aggravate my relation with him by
>>>objecting
>>>> >> >too strongly.
>>>> >> >
>>>> >> >The point of this elaborate introduction is this: somewhere in his
>>>> >> >experiments he broke the Windows slaves for our builds. We have
>>>>not
>>>> >>had a
>>>> >> >successful build in a week. Normally, not that big a deal, but
>>>>with
>>>the
>>>> >> >third party IDE people working on FlexJS and the very active
>>>>mobile
>>>> >> >development both relying on nightly builds, I feel this is not a
>>>>time
>>>> >>to
>>>> >> >NOT have clean, daily builds of all our projects...
>>>> >> >
>>>> >> >Anything 'negative' I say on the builds list will certainly make
>>>things
>>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>>well
>>>> >> >with US recipients ;-) - so I would ask you to please chime in on
>>>>the
>>>> >> >builds list and that we together get our builds back to
>>>>functioning.
>>>> >> >
>>>> >> >Thanks!
>>>> >> >
>>>> >> >EdB
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >> >--
>>>> >> >Ix Multimedia Software
>>>> >> >
>>>> >> >Jan Luykenstraat 27
>>>> >> >3521 VB Utrecht
>>>> >> >
>>>> >> >T. 06-51952295
>>>> >> >I. www.ixsoftware.nl
>>>> >>
>>>>
>>
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Remember, Gavin (builds@a.o) claim he changed nothing on the slave
that's now failing. I'm sure we didn't change anything on the Jenkins
job that is now failing. It isn't something in the SDK that's causing
this, lot's of people and the Mustella VM are building that regularly.
Anyway: I'm not familiar with Pixelbender at all, is there some way we
can ask Gavin to test it on the slave that doesn't involve Jenkins?
Like a command line that he can simply copy-paste into a shell and
give us the results from?
EdB
On Tue, Dec 10, 2013 at 8:06 AM, Alex Harui <ah...@adobe.com> wrote:
> I tried to reproduce the failure on my machine but couldn't. I tried
> different path statements, removing the aif_* dlls, and changing execute
> rights on those dlls. I did find that the string "Internal Exception" is
> in the aif_core.dll.
>
> Not sure what to do next, but now I'm thinking: maybe nobody has seen this
> on their local computers? Only on the Jenkins Windows Slave and Windows
> VM? What do they have in common? What version of Windows are they
> running? What kind of graphics cards do they have?
>
> -Alex
>
> On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>> Ah, that thread looked like it was a year old. Did you work around it
>>>or
>>> just stop working on it?
>>
>>I just stopped working on it because I hit a dead end. I was clueless as
>>to how to fix it.
>>
>>>
>>> Other than checking the path, I don't have any ideas to try at the
>>>moment.
>>>
>>> On your Azure VM, if you manually launch the compiler from Windows
>>>command
>>> prompt you get this error, right?
>>>
>>
>>I will try it out tonight and let you know.
>>
>>Thanks,
>>Om
>>
>>> -Alex
>>>
>>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>>
>>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>> >>
>>> >> We keep hitting this error, but the mail archives do not document how
>>we
>>> >> fix it. This time, we should write down the answer. Om's hit it,
>>> >>Justin
>>> >> hit it, I think I had it once. The emails seem to indicate that it
>>> >>ispath
>>> >> related, but the build.xml does at least check if the pbutil.exe
>>>exists
>>> >> and is passing on that.
>>> >>
>>> >
>>> >In my case, I have not been able to fix it. In fact, if we are trying
>>>to
>>> >reproduce the problem, we could use my Mustella VM on Azure and see if
>>>we
>>> >can figure out what is happening.
>>> >We can then apply that fix to the windows1 slave on builds.apache.org
>>> >
>>> >Thanks,
>>> >Om
>>> >
>>> >> I'll try to see if I can repro on my windows box tonight.
>>> >>
>>> >> -Alex
>>> >>
>>> >> On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
>>> >> wrote:
>>> >>
>>> >> >Thanks Erik for the clarification.
>>> >> >
>>> >> >I confirm to you, I had to send the updated swc manually for testing
>>> >> >because the nightly build was down.
>>> >> >
>>> >> >Sorry, I didn't follow the thread from the beginning, so I checked
>>>the
>>> >> >archives, maybe have missed something.
>>> >> >
>>> >> >I can see from the build logs that pixel bender build failed and it
>>> >>seems
>>> >> >to be a path issue.
>>> >> >If that's correct, this is the path I am using on my local build in
>>>my
>>> >> >env.properties:
>>> >> >
>>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>>Utilities -
>>> >> >CS5\\Pixel Bender Toolkit 2
>>> >> >
>>> >> >I can see that in the build log, the path is:
>>> >> >
>>> >> >check-pixelbender-home:
>>> >> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
>>> >> >Utilities - CS5/Pixel Bender Toolkit 2
>>> >> >
>>> >> >When I run it on my local env, it gives the following:
>>> >> >
>>> >> >[echo]
>>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>>> >> >CS5\Pixel Bender Toolkit 2
>>> >> >
>>> >> >So maybe using "\" instead of "/" could fix the issue ?
>>> >> >
>>> >> >WDYT?
>>> >> >
>>> >> >Maurice
>>> >> >
>>> >> >-----Message d'origine-----
>>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>>> >> >Envoyé : lundi 9 décembre 2013 08:53
>>> >> >À : dev@flex.apache.org
>>> >> >Objet : [Builds/Jenkins] Help and advise needed
>>> >> >
>>> >> >Hi,
>>> >> >
>>> >> >I'm having some difficulty getting the 'regular' builds on
>>>'build@a.o'
>>> >> >working. For those not subscribed to the builds list, the situation
>>>is
>>> >>as
>>> >> >follows:
>>> >> >
>>> >> >- there are supposedly 9 admins for the windows1 slave, but only one
>>is
>>> >> >sporadically active. I've requested access to the machine, but got
>>>the
>>> >> >answer: "nine is enough." A suggestions there was actually only one,
>>> >>with
>>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to remove
>>> >>old,
>>> >> >inactive admins and add new, active ones
>>> >> >
>>> >> >- since the windows1 slave is old, full and overworked, it regularly
>>> >>went
>>> >> >down for days on end. We are one of the few projects that uses the
>>> >> >windows slaves, so I ended up being the guy who always complains the
>>> >> >slave is down...
>>> >> >
>>> >> >- the one active admin is now working on a second slave (windows2).
>>>In
>>> >> >itself, that is a very good thing. However, in his own words, "he
>>feels
>>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>>but I
>>> >> >know better than to further aggravate my relation with him by
>>objecting
>>> >> >too strongly.
>>> >> >
>>> >> >The point of this elaborate introduction is this: somewhere in his
>>> >> >experiments he broke the Windows slaves for our builds. We have not
>>> >>had a
>>> >> >successful build in a week. Normally, not that big a deal, but with
>>the
>>> >> >third party IDE people working on FlexJS and the very active mobile
>>> >> >development both relying on nightly builds, I feel this is not a
>>>time
>>> >>to
>>> >> >NOT have clean, daily builds of all our projects...
>>> >> >
>>> >> >Anything 'negative' I say on the builds list will certainly make
>>things
>>> >> >worse - my NL temperament and lack of finesse often does not sit
>>>well
>>> >> >with US recipients ;-) - so I would ask you to please chime in on
>>>the
>>> >> >builds list and that we together get our builds back to functioning.
>>> >> >
>>> >> >Thanks!
>>> >> >
>>> >> >EdB
>>> >> >
>>> >> >
>>> >> >
>>> >> >--
>>> >> >Ix Multimedia Software
>>> >> >
>>> >> >Jan Luykenstraat 27
>>> >> >3521 VB Utrecht
>>> >> >
>>> >> >T. 06-51952295
>>> >> >I. www.ixsoftware.nl
>>> >>
>>>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
I tried to reproduce the failure on my machine but couldn't. I tried
different path statements, removing the aif_* dlls, and changing execute
rights on those dlls. I did find that the string "Internal Exception" is
in the aif_core.dll.
Not sure what to do next, but now I'm thinking: maybe nobody has seen this
on their local computers? Only on the Jenkins Windows Slave and Windows
VM? What do they have in common? What version of Windows are they
running? What kind of graphics cards do they have?
-Alex
On 12/9/13 11:38 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> Ah, that thread looked like it was a year old. Did you work around it
>>or
>> just stop working on it?
>
>I just stopped working on it because I hit a dead end. I was clueless as
>to how to fix it.
>
>>
>> Other than checking the path, I don't have any ideas to try at the
>>moment.
>>
>> On your Azure VM, if you manually launch the compiler from Windows
>>command
>> prompt you get this error, right?
>>
>
>I will try it out tonight and let you know.
>
>Thanks,
>Om
>
>> -Alex
>>
>> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>>
>> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>
>> >> We keep hitting this error, but the mail archives do not document how
>we
>> >> fix it. This time, we should write down the answer. Om's hit it,
>> >>Justin
>> >> hit it, I think I had it once. The emails seem to indicate that it
>> >>ispath
>> >> related, but the build.xml does at least check if the pbutil.exe
>>exists
>> >> and is passing on that.
>> >>
>> >
>> >In my case, I have not been able to fix it. In fact, if we are trying
>>to
>> >reproduce the problem, we could use my Mustella VM on Azure and see if
>>we
>> >can figure out what is happening.
>> >We can then apply that fix to the windows1 slave on builds.apache.org
>> >
>> >Thanks,
>> >Om
>> >
>> >> I'll try to see if I can repro on my windows box tonight.
>> >>
>> >> -Alex
>> >>
>> >> On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
>> >> wrote:
>> >>
>> >> >Thanks Erik for the clarification.
>> >> >
>> >> >I confirm to you, I had to send the updated swc manually for testing
>> >> >because the nightly build was down.
>> >> >
>> >> >Sorry, I didn't follow the thread from the beginning, so I checked
>>the
>> >> >archives, maybe have missed something.
>> >> >
>> >> >I can see from the build logs that pixel bender build failed and it
>> >>seems
>> >> >to be a path issue.
>> >> >If that's correct, this is the path I am using on my local build in
>>my
>> >> >env.properties:
>> >> >
>> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe
>>Utilities -
>> >> >CS5\\Pixel Bender Toolkit 2
>> >> >
>> >> >I can see that in the build log, the path is:
>> >> >
>> >> >check-pixelbender-home:
>> >> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
>> >> >Utilities - CS5/Pixel Bender Toolkit 2
>> >> >
>> >> >When I run it on my local env, it gives the following:
>> >> >
>> >> >[echo]
>> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>> >> >CS5\Pixel Bender Toolkit 2
>> >> >
>> >> >So maybe using "\" instead of "/" could fix the issue ?
>> >> >
>> >> >WDYT?
>> >> >
>> >> >Maurice
>> >> >
>> >> >-----Message d'origine-----
>> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>> >> >Envoyé : lundi 9 décembre 2013 08:53
>> >> >À : dev@flex.apache.org
>> >> >Objet : [Builds/Jenkins] Help and advise needed
>> >> >
>> >> >Hi,
>> >> >
>> >> >I'm having some difficulty getting the 'regular' builds on
>>'build@a.o'
>> >> >working. For those not subscribed to the builds list, the situation
>>is
>> >>as
>> >> >follows:
>> >> >
>> >> >- there are supposedly 9 admins for the windows1 slave, but only one
>is
>> >> >sporadically active. I've requested access to the machine, but got
>>the
>> >> >answer: "nine is enough." A suggestions there was actually only one,
>> >>with
>> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to remove
>> >>old,
>> >> >inactive admins and add new, active ones
>> >> >
>> >> >- since the windows1 slave is old, full and overworked, it regularly
>> >>went
>> >> >down for days on end. We are one of the few projects that uses the
>> >> >windows slaves, so I ended up being the guy who always complains the
>> >> >slave is down...
>> >> >
>> >> >- the one active admin is now working on a second slave (windows2).
>>In
>> >> >itself, that is a very good thing. However, in his own words, "he
>feels
>> >> >entitled to use our builds to experiment." I feel that is wrong,
>>but I
>> >> >know better than to further aggravate my relation with him by
>objecting
>> >> >too strongly.
>> >> >
>> >> >The point of this elaborate introduction is this: somewhere in his
>> >> >experiments he broke the Windows slaves for our builds. We have not
>> >>had a
>> >> >successful build in a week. Normally, not that big a deal, but with
>the
>> >> >third party IDE people working on FlexJS and the very active mobile
>> >> >development both relying on nightly builds, I feel this is not a
>>time
>> >>to
>> >> >NOT have clean, daily builds of all our projects...
>> >> >
>> >> >Anything 'negative' I say on the builds list will certainly make
>things
>> >> >worse - my NL temperament and lack of finesse often does not sit
>>well
>> >> >with US recipients ;-) - so I would ask you to please chime in on
>>the
>> >> >builds list and that we together get our builds back to functioning.
>> >> >
>> >> >Thanks!
>> >> >
>> >> >EdB
>> >> >
>> >> >
>> >> >
>> >> >--
>> >> >Ix Multimedia Software
>> >> >
>> >> >Jan Luykenstraat 27
>> >> >3521 VB Utrecht
>> >> >
>> >> >T. 06-51952295
>> >> >I. www.ixsoftware.nl
>> >>
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 9, 2013 10:56 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> Ah, that thread looked like it was a year old. Did you work around it or
> just stop working on it?
I just stopped working on it because I hit a dead end. I was clueless as
to how to fix it.
>
> Other than checking the path, I don't have any ideas to try at the moment.
>
> On your Azure VM, if you manually launch the compiler from Windows command
> prompt you get this error, right?
>
I will try it out tonight and let you know.
Thanks,
Om
> -Alex
>
> On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
> >On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >> We keep hitting this error, but the mail archives do not document how
we
> >> fix it. This time, we should write down the answer. Om's hit it,
> >>Justin
> >> hit it, I think I had it once. The emails seem to indicate that it
> >>ispath
> >> related, but the build.xml does at least check if the pbutil.exe exists
> >> and is passing on that.
> >>
> >
> >In my case, I have not been able to fix it. In fact, if we are trying to
> >reproduce the problem, we could use my Mustella VM on Azure and see if we
> >can figure out what is happening.
> >We can then apply that fix to the windows1 slave on builds.apache.org
> >
> >Thanks,
> >Om
> >
> >> I'll try to see if I can repro on my windows box tonight.
> >>
> >> -Alex
> >>
> >> On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
> >> wrote:
> >>
> >> >Thanks Erik for the clarification.
> >> >
> >> >I confirm to you, I had to send the updated swc manually for testing
> >> >because the nightly build was down.
> >> >
> >> >Sorry, I didn't follow the thread from the beginning, so I checked the
> >> >archives, maybe have missed something.
> >> >
> >> >I can see from the build logs that pixel bender build failed and it
> >>seems
> >> >to be a path issue.
> >> >If that's correct, this is the path I am using on my local build in my
> >> >env.properties:
> >> >
> >> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities -
> >> >CS5\\Pixel Bender Toolkit 2
> >> >
> >> >I can see that in the build log, the path is:
> >> >
> >> >check-pixelbender-home:
> >> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
> >> >Utilities - CS5/Pixel Bender Toolkit 2
> >> >
> >> >When I run it on my local env, it gives the following:
> >> >
> >> >[echo]
> >> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
> >> >CS5\Pixel Bender Toolkit 2
> >> >
> >> >So maybe using "\" instead of "/" could fix the issue ?
> >> >
> >> >WDYT?
> >> >
> >> >Maurice
> >> >
> >> >-----Message d'origine-----
> >> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> >> >Envoyé : lundi 9 décembre 2013 08:53
> >> >À : dev@flex.apache.org
> >> >Objet : [Builds/Jenkins] Help and advise needed
> >> >
> >> >Hi,
> >> >
> >> >I'm having some difficulty getting the 'regular' builds on 'build@a.o'
> >> >working. For those not subscribed to the builds list, the situation is
> >>as
> >> >follows:
> >> >
> >> >- there are supposedly 9 admins for the windows1 slave, but only one
is
> >> >sporadically active. I've requested access to the machine, but got the
> >> >answer: "nine is enough." A suggestions there was actually only one,
> >>with
> >> >8 ghosts fell on deaf ears. Apparently, it makes no sense to remove
> >>old,
> >> >inactive admins and add new, active ones
> >> >
> >> >- since the windows1 slave is old, full and overworked, it regularly
> >>went
> >> >down for days on end. We are one of the few projects that uses the
> >> >windows slaves, so I ended up being the guy who always complains the
> >> >slave is down...
> >> >
> >> >- the one active admin is now working on a second slave (windows2). In
> >> >itself, that is a very good thing. However, in his own words, "he
feels
> >> >entitled to use our builds to experiment." I feel that is wrong, but I
> >> >know better than to further aggravate my relation with him by
objecting
> >> >too strongly.
> >> >
> >> >The point of this elaborate introduction is this: somewhere in his
> >> >experiments he broke the Windows slaves for our builds. We have not
> >>had a
> >> >successful build in a week. Normally, not that big a deal, but with
the
> >> >third party IDE people working on FlexJS and the very active mobile
> >> >development both relying on nightly builds, I feel this is not a time
> >>to
> >> >NOT have clean, daily builds of all our projects...
> >> >
> >> >Anything 'negative' I say on the builds list will certainly make
things
> >> >worse - my NL temperament and lack of finesse often does not sit well
> >> >with US recipients ;-) - so I would ask you to please chime in on the
> >> >builds list and that we together get our builds back to functioning.
> >> >
> >> >Thanks!
> >> >
> >> >EdB
> >> >
> >> >
> >> >
> >> >--
> >> >Ix Multimedia Software
> >> >
> >> >Jan Luykenstraat 27
> >> >3521 VB Utrecht
> >> >
> >> >T. 06-51952295
> >> >I. www.ixsoftware.nl
> >>
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
Ah, that thread looked like it was a year old. Did you work around it or
just stop working on it?
Other than checking the path, I don't have any ideas to try at the moment.
On your Azure VM, if you manually launch the compiler from Windows command
prompt you get this error, right?
-Alex
On 12/9/13 10:48 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> We keep hitting this error, but the mail archives do not document how we
>> fix it. This time, we should write down the answer. Om's hit it,
>>Justin
>> hit it, I think I had it once. The emails seem to indicate that it
>>ispath
>> related, but the build.xml does at least check if the pbutil.exe exists
>> and is passing on that.
>>
>
>In my case, I have not been able to fix it. In fact, if we are trying to
>reproduce the problem, we could use my Mustella VM on Azure and see if we
>can figure out what is happening.
>We can then apply that fix to the windows1 slave on builds.apache.org
>
>Thanks,
>Om
>
>> I'll try to see if I can repro on my windows box tonight.
>>
>> -Alex
>>
>> On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
>> wrote:
>>
>> >Thanks Erik for the clarification.
>> >
>> >I confirm to you, I had to send the updated swc manually for testing
>> >because the nightly build was down.
>> >
>> >Sorry, I didn't follow the thread from the beginning, so I checked the
>> >archives, maybe have missed something.
>> >
>> >I can see from the build logs that pixel bender build failed and it
>>seems
>> >to be a path issue.
>> >If that's correct, this is the path I am using on my local build in my
>> >env.properties:
>> >
>> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities -
>> >CS5\\Pixel Bender Toolkit 2
>> >
>> >I can see that in the build log, the path is:
>> >
>> >check-pixelbender-home:
>> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
>> >Utilities - CS5/Pixel Bender Toolkit 2
>> >
>> >When I run it on my local env, it gives the following:
>> >
>> >[echo]
>> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>> >CS5\Pixel Bender Toolkit 2
>> >
>> >So maybe using "\" instead of "/" could fix the issue ?
>> >
>> >WDYT?
>> >
>> >Maurice
>> >
>> >-----Message d'origine-----
>> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>> >Envoyé : lundi 9 décembre 2013 08:53
>> >À : dev@flex.apache.org
>> >Objet : [Builds/Jenkins] Help and advise needed
>> >
>> >Hi,
>> >
>> >I'm having some difficulty getting the 'regular' builds on 'build@a.o'
>> >working. For those not subscribed to the builds list, the situation is
>>as
>> >follows:
>> >
>> >- there are supposedly 9 admins for the windows1 slave, but only one is
>> >sporadically active. I've requested access to the machine, but got the
>> >answer: "nine is enough." A suggestions there was actually only one,
>>with
>> >8 ghosts fell on deaf ears. Apparently, it makes no sense to remove
>>old,
>> >inactive admins and add new, active ones
>> >
>> >- since the windows1 slave is old, full and overworked, it regularly
>>went
>> >down for days on end. We are one of the few projects that uses the
>> >windows slaves, so I ended up being the guy who always complains the
>> >slave is down...
>> >
>> >- the one active admin is now working on a second slave (windows2). In
>> >itself, that is a very good thing. However, in his own words, "he feels
>> >entitled to use our builds to experiment." I feel that is wrong, but I
>> >know better than to further aggravate my relation with him by objecting
>> >too strongly.
>> >
>> >The point of this elaborate introduction is this: somewhere in his
>> >experiments he broke the Windows slaves for our builds. We have not
>>had a
>> >successful build in a week. Normally, not that big a deal, but with the
>> >third party IDE people working on FlexJS and the very active mobile
>> >development both relying on nightly builds, I feel this is not a time
>>to
>> >NOT have clean, daily builds of all our projects...
>> >
>> >Anything 'negative' I say on the builds list will certainly make things
>> >worse - my NL temperament and lack of finesse often does not sit well
>> >with US recipients ;-) - so I would ask you to please chime in on the
>> >builds list and that we together get our builds back to functioning.
>> >
>> >Thanks!
>> >
>> >EdB
>> >
>> >
>> >
>> >--
>> >Ix Multimedia Software
>> >
>> >Jan Luykenstraat 27
>> >3521 VB Utrecht
>> >
>> >T. 06-51952295
>> >I. www.ixsoftware.nl
>>
Re: [Builds/Jenkins] Help and advise needed
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 9, 2013 10:35 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> We keep hitting this error, but the mail archives do not document how we
> fix it. This time, we should write down the answer. Om's hit it, Justin
> hit it, I think I had it once. The emails seem to indicate that it ispath
> related, but the build.xml does at least check if the pbutil.exe exists
> and is passing on that.
>
In my case, I have not been able to fix it. In fact, if we are trying to
reproduce the problem, we could use my Mustella VM on Azure and see if we
can figure out what is happening.
We can then apply that fix to the windows1 slave on builds.apache.org
Thanks,
Om
> I'll try to see if I can repro on my windows box tonight.
>
> -Alex
>
> On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >Thanks Erik for the clarification.
> >
> >I confirm to you, I had to send the updated swc manually for testing
> >because the nightly build was down.
> >
> >Sorry, I didn't follow the thread from the beginning, so I checked the
> >archives, maybe have missed something.
> >
> >I can see from the build logs that pixel bender build failed and it seems
> >to be a path issue.
> >If that's correct, this is the path I am using on my local build in my
> >env.properties:
> >
> >env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities -
> >CS5\\Pixel Bender Toolkit 2
> >
> >I can see that in the build log, the path is:
> >
> >check-pixelbender-home:
> > [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
> >Utilities - CS5/Pixel Bender Toolkit 2
> >
> >When I run it on my local env, it gives the following:
> >
> >[echo]
> >PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
> >CS5\Pixel Bender Toolkit 2
> >
> >So maybe using "\" instead of "/" could fix the issue ?
> >
> >WDYT?
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> >Envoyé : lundi 9 décembre 2013 08:53
> >À : dev@flex.apache.org
> >Objet : [Builds/Jenkins] Help and advise needed
> >
> >Hi,
> >
> >I'm having some difficulty getting the 'regular' builds on 'build@a.o'
> >working. For those not subscribed to the builds list, the situation is as
> >follows:
> >
> >- there are supposedly 9 admins for the windows1 slave, but only one is
> >sporadically active. I've requested access to the machine, but got the
> >answer: "nine is enough." A suggestions there was actually only one, with
> >8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old,
> >inactive admins and add new, active ones
> >
> >- since the windows1 slave is old, full and overworked, it regularly went
> >down for days on end. We are one of the few projects that uses the
> >windows slaves, so I ended up being the guy who always complains the
> >slave is down...
> >
> >- the one active admin is now working on a second slave (windows2). In
> >itself, that is a very good thing. However, in his own words, "he feels
> >entitled to use our builds to experiment." I feel that is wrong, but I
> >know better than to further aggravate my relation with him by objecting
> >too strongly.
> >
> >The point of this elaborate introduction is this: somewhere in his
> >experiments he broke the Windows slaves for our builds. We have not had a
> >successful build in a week. Normally, not that big a deal, but with the
> >third party IDE people working on FlexJS and the very active mobile
> >development both relying on nightly builds, I feel this is not a time to
> >NOT have clean, daily builds of all our projects...
> >
> >Anything 'negative' I say on the builds list will certainly make things
> >worse - my NL temperament and lack of finesse often does not sit well
> >with US recipients ;-) - so I would ask you to please chime in on the
> >builds list and that we together get our builds back to functioning.
> >
> >Thanks!
> >
> >EdB
> >
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I. www.ixsoftware.nl
>
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Exactly.
Usually CI is just for checking. But until the Installer can create a
working FlexJS SDK, the people wanting to play with it, like the nice
folks from FDK, mostly have to rely on the nightly builds. The
certainly can build an SDK themselves, but I don't think they need to
waste their time having to do that over and over again. If we want to
maintain our momentum, this seems very important to me. Living without
the flex-sdk builds for a while isn't all that bad in itself, as the
Mustella VM catches most of what they do and much more...
EdB
On Mon, Dec 9, 2013 at 10:30 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds
>> in place, so any contributors/third parties can get the Flex and
>> FlexJS SDKs and have the latest and greatest.
>
> For development and testing purposes only of course :-) If it's not an officially voted on release then that's all it can be used for.
>
> Have a working CI system that run after you check something in IMO is priority no 1 and the nightly build is just a nice little bonus that make life easier for a few folk. It's not actually required as anyone can build the software (with a little bit of effort) from the repo.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds
> in place, so any contributors/third parties can get the Flex and
> FlexJS SDKs and have the latest and greatest.
For development and testing purposes only of course :-) If it's not an officially voted on release then that's all it can be used for.
Have a working CI system that run after you check something in IMO is priority no 1 and the nightly build is just a nice little bonus that make life easier for a few folk. It's not actually required as anyone can build the software (with a little bit of effort) from the repo.
Thanks,
Justin
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
BTW, the test with unchecking "Interact with desktop" didn't give any result (didn't fail).
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : lundi 9 décembre 2013 12:12
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
A session log-off was apparently enough.
Ouf !
Maurice
-----Message d'origine-----
De : Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
Envoyé : lundi 9 décembre 2013 12:08
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Sounds like a good idea to restart the instance. Then run his start scripts.
-Mark
-----Original Message-----
From: Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Sent: Monday, December 09, 2013 5:59 AM
To: dev@flex.apache.org
Subject: RE: [Builds/Jenkins] Help and advise needed
I back back everything (mainly checked "Interact with desktop", then restarted the jenkins service and launched WindowsSlave through jnlp.
But it now fails to connection to master, ( retries 10 times, then aborts).
Note: I did "Prepare for shutdown" before stopping the service, but apparently , it didn't stop properly.
Maybe there are some ports still used or some ghosts processes still running.
What should I do now ? restart the VM?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem <ma...@systar.com> wrote:
> I have set up the sample pixelbender job on mustella VM.
> Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
>
> Can this be done without risk of the service not restarting properly?
> Will the slave agent be restarted automatically? Or does it need to be launched manually?
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> I am just going to run some builds, and change some variables.
> Everything reversible.
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:23 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> 1) On this thread:
>>
>> https://twitter.com/bigosmallm/status/308466759130816512
>>
>> Kevin answering to Om says:
>>
>> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>>
>> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>>
>> 2) what about experimenting on "our" mustella vm?
>> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
>> Of course, that would temporarily break the mustella tests...
>>
>>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Ok, never mind.
>>>
>>> So what else could it be?
>>>
>>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>>> Hi,
>>>>
>>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>>> So there is a possibility that they were not set the same in the new machine.
>>>>
>>>> Makes sense ?
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> Hi,
>>>>
>>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
A session log-off was apparently enough.
Ouf !
Maurice
-----Message d'origine-----
De : Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
Envoyé : lundi 9 décembre 2013 12:08
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Sounds like a good idea to restart the instance. Then run his start scripts.
-Mark
-----Original Message-----
From: Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Sent: Monday, December 09, 2013 5:59 AM
To: dev@flex.apache.org
Subject: RE: [Builds/Jenkins] Help and advise needed
I back back everything (mainly checked "Interact with desktop", then restarted the jenkins service and launched WindowsSlave through jnlp.
But it now fails to connection to master, ( retries 10 times, then aborts).
Note: I did "Prepare for shutdown" before stopping the service, but apparently , it didn't stop properly.
Maybe there are some ports still used or some ghosts processes still running.
What should I do now ? restart the VM?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 11:13 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem <ma...@systar.com> wrote:
> I have set up the sample pixelbender job on mustella VM.
> Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
>
> Can this be done without risk of the service not restarting properly?
> Will the slave agent be restarted automatically? Or does it need to be launched manually?
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> I am just going to run some builds, and change some variables.
> Everything reversible.
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:23 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> 1) On this thread:
>>
>> https://twitter.com/bigosmallm/status/308466759130816512
>>
>> Kevin answering to Om says:
>>
>> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>>
>> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>>
>> 2) what about experimenting on "our" mustella vm?
>> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
>> Of course, that would temporarily break the mustella tests...
>>
>>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Ok, never mind.
>>>
>>> So what else could it be?
>>>
>>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>>> Hi,
>>>>
>>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>>> So there is a possibility that they were not set the same in the new machine.
>>>>
>>>> Makes sense ?
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> Hi,
>>>>
>>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Sounds like a good idea to restart the instance. Then run his start scripts.
-Mark
-----Original Message-----
From: Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Sent: Monday, December 09, 2013 5:59 AM
To: dev@flex.apache.org
Subject: RE: [Builds/Jenkins] Help and advise needed
I back back everything (mainly checked "Interact with desktop", then restarted the jenkins service and launched WindowsSlave through jnlp.
But it now fails to connection to master, ( retries 10 times, then aborts).
Note: I did "Prepare for shutdown" before stopping the service, but apparently , it didn't stop properly.
Maybe there are some ports still used or some ghosts processes still running.
What should I do now ? restart the VM?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 11:13
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem <ma...@systar.com> wrote:
> I have set up the sample pixelbender job on mustella VM.
> Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
>
> Can this be done without risk of the service not restarting properly?
> Will the slave agent be restarted automatically? Or does it need to be launched manually?
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> I am just going to run some builds, and change some variables.
> Everything reversible.
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:23 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> 1) On this thread:
>>
>> https://twitter.com/bigosmallm/status/308466759130816512
>>
>> Kevin answering to Om says:
>>
>> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>>
>> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>>
>> 2) what about experimenting on "our" mustella vm?
>> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
>> Of course, that would temporarily break the mustella tests...
>>
>>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Ok, never mind.
>>>
>>> So what else could it be?
>>>
>>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>>> Hi,
>>>>
>>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>>> So there is a possibility that they were not set the same in the new machine.
>>>>
>>>> Makes sense ?
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> Hi,
>>>>
>>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
I back back everything (mainly checked "Interact with desktop", then restarted the jenkins service and launched WindowsSlave through jnlp.
But it now fails to connection to master, ( retries 10 times, then aborts).
Note: I did "Prepare for shutdown" before stopping the service, but apparently , it didn't stop properly.
Maybe there are some ports still used or some ghosts processes still running.
What should I do now ? restart the VM?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 11:13
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem <ma...@systar.com> wrote:
> I have set up the sample pixelbender job on mustella VM.
> Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
>
> Can this be done without risk of the service not restarting properly?
> Will the slave agent be restarted automatically? Or does it need to be launched manually?
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> I am just going to run some builds, and change some variables.
> Everything reversible.
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:23 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> 1) On this thread:
>>
>> https://twitter.com/bigosmallm/status/308466759130816512
>>
>> Kevin answering to Om says:
>>
>> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>>
>> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>>
>> 2) what about experimenting on "our" mustella vm?
>> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
>> Of course, that would temporarily break the mustella tests...
>>
>>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Ok, never mind.
>>>
>>> So what else could it be?
>>>
>>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>>> Hi,
>>>>
>>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>>> So there is a possibility that they were not set the same in the new machine.
>>>>
>>>> Makes sense ?
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> Hi,
>>>>
>>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
The slave agents should load automatically upon restart... If not,
there are shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem
<ma...@systar.com> wrote:
> I have set up the sample pixelbender job on mustella VM.
> Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
>
> Can this be done without risk of the service not restarting properly?
> Will the slave agent be restarted automatically? Or does it need to be launched manually?
>
> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> I am just going to run some builds, and change some variables.
> Everything reversible.
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
>
> I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
>
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> 1) On this thread:
>>
>> https://twitter.com/bigosmallm/status/308466759130816512
>>
>> Kevin answering to Om says:
>>
>> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>>
>> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>>
>> 2) what about experimenting on "our" mustella vm?
>> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
>> Of course, that would temporarily break the mustella tests...
>>
>>
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Ok, never mind.
>>>
>>> So what else could it be?
>>>
>>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>>> Hi,
>>>>
>>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>>> So there is a possibility that they were not set the same in the new machine.
>>>>
>>>> Makes sense ?
>>>>
>>>> Maurice
>>>>
>>>> -----Message d'origine-----
>>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>>> [Builds/Jenkins] Help and advise needed
>>>>
>>>> Hi,
>>>>
>>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>>
>>>> Thanks,
>>>> Justin
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
I have set up the sample pixelbender job on mustella VM.
Now, I need to remove the "Interact with desktop" option in Jenkins windows service and restart it.
Can this be done without risk of the service not restarting properly?
Will the slave agent be restarted automatically? Or does it need to be launched manually?
Maurice
-----Message d'origine-----
De : Maurice Amsellem [mailto:maurice.amsellem@systar.com]
Envoyé : lundi 9 décembre 2013 10:30
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
I am just going to run some builds, and change some variables.
Everything reversible.
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9 décembre 2013 10:23 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help and advise needed
I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
EdB
On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
> 1) On this thread:
>
> https://twitter.com/bigosmallm/status/308466759130816512
>
> Kevin answering to Om says:
>
> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>
> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>
> 2) what about experimenting on "our" mustella vm?
> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
> Of course, that would temporarily break the mustella tests...
>
>
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> Ok, never mind.
>>
>> So what else could it be?
>>
>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Hi,
>>>
>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>> So there is a possibility that they were not set the same in the new machine.
>>>
>>> Makes sense ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Hi,
>>>
>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
>I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
I am just going to run some builds, and change some variables.
Everything reversible.
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 10:23
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
I don't mind experiments on the Mustella VM, but remember we don't have a proper backup in place.
Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in place, so any contributors/third parties can get the Flex and FlexJS SDKs and have the latest and greatest.
EdB
On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem <ma...@systar.com> wrote:
> 1) On this thread:
>
> https://twitter.com/bigosmallm/status/308466759130816512
>
> Kevin answering to Om says:
>
> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>
> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>
> 2) what about experimenting on "our" mustella vm?
> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
> Of course, that would temporarily break the mustella tests...
>
>
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 10:01 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> Ok, never mind.
>>
>> So what else could it be?
>>
>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Hi,
>>>
>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>> So there is a possibility that they were not set the same in the new machine.
>>>
>>> Makes sense ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi
>>> 9 décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Hi,
>>>
>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I don't mind experiments on the Mustella VM, but remember we don't
have a proper backup in place.
Our nr. 1 priority now, IMHO, must be to have reliable nightly builds
in place, so any contributors/third parties can get the Flex and
FlexJS SDKs and have the latest and greatest.
EdB
On Mon, Dec 9, 2013 at 10:13 AM, Maurice Amsellem
<ma...@systar.com> wrote:
> 1) On this thread:
>
> https://twitter.com/bigosmallm/status/308466759130816512
>
> Kevin answering to Om says:
>
> " [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
>
> So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
>
> 2) what about experimenting on "our" mustella vm?
> We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
> Of course, that would temporarily break the mustella tests...
>
>
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> Envoyé : lundi 9 décembre 2013 10:01
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> Ok, never mind.
>>
>> So what else could it be?
>>
>> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
>> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>>> Hi,
>>>
>>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>>> So there is a possibility that they were not set the same in the new machine.
>>>
>>> Makes sense ?
>>>
>>> Maurice
>>>
>>> -----Message d'origine-----
>>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi 9
>>> décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>>> [Builds/Jenkins] Help and advise needed
>>>
>>> Hi,
>>>
>>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
1) On this thread:
https://twitter.com/bigosmallm/status/308466759130816512
Kevin answering to Om says:
" [pbutil] needs a window, I think, it is failing to initialize OpenGL. If you launch it in a visible command window it may work".
So could it be something like Jenkins service permissions ? Is the service running as "Local system", and "Interact with desktop" checked ? or is it running on a dedicated account?
2) what about experimenting on "our" mustella vm?
We could install pixel bender, and try the "pixel bender compile" with different settings, see if we can reproduce the "AIF error".
Of course, that would temporarily break the mustella tests...
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 10:01
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Om told me earlier he had the same error when setting up his local system, but it went away when the machine was properly set up and he couldn't reproduce it after that. This made me think that the root cause might be with the machine setup and not with the Jenkins config.
EdB
On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem <ma...@systar.com> wrote:
> Ok, never mind.
>
> So what else could it be?
>
> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl] Envoyé : lundi 9
> décembre 2013 09:52 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> Hi,
>>
>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>> So there is a possibility that they were not set the same in the new machine.
>>
>> Makes sense ?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi 9
>> décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Hi,
>>
>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>
>> Thanks,
>> Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Om told me earlier he had the same error when setting up his local
system, but it went away when the machine was properly set up and he
couldn't reproduce it after that. This made me think that the root
cause might be with the machine setup and not with the Jenkins config.
EdB
On Mon, Dec 9, 2013 at 9:55 AM, Maurice Amsellem
<ma...@systar.com> wrote:
> Ok, never mind.
>
> So what else could it be?
>
> Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
>
> Maurice
>
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> Envoyé : lundi 9 décembre 2013 09:52
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
>> Hi,
>>
>> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
>> So there is a possibility that they were not set the same in the new machine.
>>
>> Makes sense ?
>>
>> Maurice
>>
>> -----Message d'origine-----
>> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi 9
>> décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
>> [Builds/Jenkins] Help and advise needed
>>
>> Hi,
>>
>> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>>
>> Thanks,
>> Justin
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Ok, never mind.
So what else could it be?
Does someone know how to reproduce the "AIF Internal exception" in pixel-bender compiler ?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 09:52
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
EdB
On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <ma...@systar.com> wrote:
> Hi,
>
> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
> So there is a possibility that they were not set the same in the new machine.
>
> Makes sense ?
>
> Maurice
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:justin@classsoftware.com] Envoyé : lundi 9
> décembre 2013 09:43 À : dev@flex.apache.org Objet : Re:
> [Builds/Jenkins] Help and advise needed
>
> Hi,
>
> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Nope, that's not it. When the last work was done on the new machine,
the builds also stopped working on the ORIGINAL, supposedly untouched,
machine.
EdB
On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem
<ma...@systar.com> wrote:
> Hi,
>
> I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
> So there is a possibility that they were not set the same in the new machine.
>
> Makes sense ?
>
> Maurice
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:justin@classsoftware.com]
> Envoyé : lundi 9 décembre 2013 09:43
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Hi,
>
> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Hi,
I have checked the jenskins workspace, there is no env.properties in the root folder, which means all the env variables are set through system properties.
So there is a possibility that they were not set the same in the new machine.
Makes sense ?
Maurice
-----Message d'origine-----
De : Justin Mclean [mailto:justin@classsoftware.com]
Envoyé : lundi 9 décembre 2013 09:43
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Hi,
I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
Thanks,
Justin
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Yes, my thoughts exactly. Two things: we cannot change or even check
the settings of the machines themselves, we only have access through
the Jenkins web interface. And the most worrying thing: the builds
also don't work anymore on the original (windows1) machine.
EdB
On Mon, Dec 9, 2013 at 9:43 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
> I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I already did... twice.
EdB
On Mon, Dec 9, 2013 at 9:49 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
> Just checked and here's the config:
> AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
> FLASHPLAYER_DEBUGGER=C\:/Program\ Files\ (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
> PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\ Bender\ Toolkit\ 2
>
> This matches the original config:
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\ Bender\ Toolkit\ 2
>
> So my guess is it hasn't been installed, I'll ask the question on builds@.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Just checked and here's the config:
AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
FLASHPLAYER_DEBUGGER=C\:/Program\ Files\ (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\ Bender\ Toolkit\ 2
This matches the original config:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\ Bender\ Toolkit\ 2
So my guess is it hasn't been installed, I'll ask the question on builds@.
Thanks,
Justin
Re: [Builds/Jenkins] Help and advise needed
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
I'd think it would be unlikely that the Pixel Bender path would of changed as I would assume the Jenkins job was just copied over from the original windows machine. A good first set would be to check the setup on both (if we can) and set that the environment variable are the same on both and then ask if pixel bender has been installed on the second machine in the same location.
Thanks,
Justin
AW: [Builds/Jenkins] Help and advise needed
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi,
what exactly is the current Problem? As far as I understood, the stability of the build-server seems to be a Problem.
I had similar Problems when Setting up the Flexmojos CI Server. After doing all sorts of Amazon EC2, MS Azure VM stuff, I did a fallback to a central CI Server and multiple Agents installed on normal Desktop PCs. So eventually this could be an Option for us. Setting up Jenkins Agents on our own machines, but having the central CI Server, so a build is done as soon as any Agent is available. This way we don't have to rely on the Apache Windows Agent being available.
As far as I know another incubating Project (NPanday - .Net Maven Plugin) has to rely on this machine too and they are having Major Problems with it.
Mabe private Agents could be a solution. For Flexmojos it certainly helped.
Chris
________________________________________
Von: Maurice Amsellem <ma...@systar.com>
Gesendet: Montag, 9. Dezember 2013 09:16
An: dev@flex.apache.org
Betreff: RE: [Builds/Jenkins] Help and advise needed
Thanks Erik for the clarification.
I confirm to you, I had to send the updated swc manually for testing because the nightly build was down.
Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something.
I can see from the build logs that pixel bender build failed and it seems to be a path issue.
If that's correct, this is the path I am using on my local build in my env.properties:
env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2
I can see that in the build log, the path is:
check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
When I run it on my local env, it gives the following:
[echo]
PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2
So maybe using "\" instead of "/" could fix the issue ?
WDYT?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 08:53
À : dev@flex.apache.org
Objet : [Builds/Jenkins] Help and advise needed
Hi,
I'm having some difficulty getting the 'regular' builds on 'build@a.o'
working. For those not subscribed to the builds list, the situation is as follows:
- there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: "nine is enough." A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones
- since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down...
- the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, "he feels entitled to use our builds to experiment." I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly.
The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects...
Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning.
Thanks!
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [Builds/Jenkins] Help and advise needed
Posted by Alex Harui <ah...@adobe.com>.
We keep hitting this error, but the mail archives do not document how we
fix it. This time, we should write down the answer. Om's hit it, Justin
hit it, I think I had it once. The emails seem to indicate that it ispath
related, but the build.xml does at least check if the pbutil.exe exists
and is passing on that.
I'll try to see if I can repro on my windows box tonight.
-Alex
On 12/9/13 12:16 AM, "Maurice Amsellem" <ma...@systar.com>
wrote:
>Thanks Erik for the clarification.
>
>I confirm to you, I had to send the updated swc manually for testing
>because the nightly build was down.
>
>Sorry, I didn't follow the thread from the beginning, so I checked the
>archives, maybe have missed something.
>
>I can see from the build logs that pixel bender build failed and it seems
>to be a path issue.
>If that's correct, this is the path I am using on my local build in my
>env.properties:
>
>env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities -
>CS5\\Pixel Bender Toolkit 2
>
>I can see that in the build log, the path is:
>
>check-pixelbender-home:
> [echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe
>Utilities - CS5/Pixel Bender Toolkit 2
>
>When I run it on my local env, it gives the following:
>
>[echo]
>PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities -
>CS5\Pixel Bender Toolkit 2
>
>So maybe using "\" instead of "/" could fix the issue ?
>
>WDYT?
>
>Maurice
>
>-----Message d'origine-----
>De : Erik de Bruin [mailto:erik@ixsoftware.nl]
>Envoyé : lundi 9 décembre 2013 08:53
>À : dev@flex.apache.org
>Objet : [Builds/Jenkins] Help and advise needed
>
>Hi,
>
>I'm having some difficulty getting the 'regular' builds on 'build@a.o'
>working. For those not subscribed to the builds list, the situation is as
>follows:
>
>- there are supposedly 9 admins for the windows1 slave, but only one is
>sporadically active. I've requested access to the machine, but got the
>answer: "nine is enough." A suggestions there was actually only one, with
>8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old,
>inactive admins and add new, active ones
>
>- since the windows1 slave is old, full and overworked, it regularly went
>down for days on end. We are one of the few projects that uses the
>windows slaves, so I ended up being the guy who always complains the
>slave is down...
>
>- the one active admin is now working on a second slave (windows2). In
>itself, that is a very good thing. However, in his own words, "he feels
>entitled to use our builds to experiment." I feel that is wrong, but I
>know better than to further aggravate my relation with him by objecting
>too strongly.
>
>The point of this elaborate introduction is this: somewhere in his
>experiments he broke the Windows slaves for our builds. We have not had a
>successful build in a week. Normally, not that big a deal, but with the
>third party IDE people working on FlexJS and the very active mobile
>development both relying on nightly builds, I feel this is not a time to
>NOT have clean, daily builds of all our projects...
>
>Anything 'negative' I say on the builds list will certainly make things
>worse - my NL temperament and lack of finesse often does not sit well
>with US recipients ;-) - so I would ask you to please chime in on the
>builds list and that we together get our builds back to functioning.
>
>Thanks!
>
>EdB
>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
RE: [Builds/Jenkins] Help and advise needed
Posted by Maurice Amsellem <ma...@systar.com>.
Thanks Erik for the clarification.
I confirm to you, I had to send the updated swc manually for testing because the nightly build was down.
Sorry, I didn't follow the thread from the beginning, so I checked the archives, maybe have missed something.
I can see from the build logs that pixel bender build failed and it seems to be a path issue.
If that's correct, this is the path I am using on my local build in my env.properties:
env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities - CS5\\Pixel Bender Toolkit 2
I can see that in the build log, the path is:
check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel Bender Toolkit 2
When I run it on my local env, it gives the following:
[echo]
PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel Bender Toolkit 2
So maybe using "\" instead of "/" could fix the issue ?
WDYT?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 08:53
À : dev@flex.apache.org
Objet : [Builds/Jenkins] Help and advise needed
Hi,
I'm having some difficulty getting the 'regular' builds on 'build@a.o'
working. For those not subscribed to the builds list, the situation is as follows:
- there are supposedly 9 admins for the windows1 slave, but only one is sporadically active. I've requested access to the machine, but got the answer: "nine is enough." A suggestions there was actually only one, with 8 ghosts fell on deaf ears. Apparently, it makes no sense to remove old, inactive admins and add new, active ones
- since the windows1 slave is old, full and overworked, it regularly went down for days on end. We are one of the few projects that uses the windows slaves, so I ended up being the guy who always complains the slave is down...
- the one active admin is now working on a second slave (windows2). In itself, that is a very good thing. However, in his own words, "he feels entitled to use our builds to experiment." I feel that is wrong, but I know better than to further aggravate my relation with him by objecting too strongly.
The point of this elaborate introduction is this: somewhere in his experiments he broke the Windows slaves for our builds. We have not had a successful build in a week. Normally, not that big a deal, but with the third party IDE people working on FlexJS and the very active mobile development both relying on nightly builds, I feel this is not a time to NOT have clean, daily builds of all our projects...
Anything 'negative' I say on the builds list will certainly make things worse - my NL temperament and lack of finesse often does not sit well with US recipients ;-) - so I would ask you to please chime in on the builds list and that we together get our builds back to functioning.
Thanks!
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl