You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2013/12/04 09:15:58 UTC
[windows1] Pixelbender installation
Hi,
Our builds stopped working yesterday :-(
This is the error I get:
pixelbender-compile:
[exec] ERROR: AIF Internal exception
[exec] Result: 1
The build assumes Pixelbender is installed at:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
CS5/Pixel\ Bender\ Toolkit\ 2
Is that still the correct path and does the application start without
errors when you launch it manually?
Thanks!
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Gavin McDonald [mailto:gavin@16degrees.com.au]
> Sent: Sunday, 15 December 2013 10:18 AM
> To: builds@apache.org; 'Erik de Bruin'
> Subject: RE: [windows1] Pixelbender installation
>
>
>
> > -----Original Message-----
> > From: Alex Harui [mailto:aharui@adobe.com]
> > Sent: Sunday, 15 December 2013 4:19 AM
> > To: builds@apache.org; gavin@16degrees.com.au; 'Erik de Bruin'
> > Subject: Re: [windows1] Pixelbender installation
> >
> > Hi Gavin,
> >
> > The build script is using a simple Ant Delete task and can't delete jars.
> > Can you assist in investigating why the delete is failing?
>
> Seems the jars think they are still being used, and refuse to delete.
>
> At the next opportunity when no or little builds running, I'll have to reboot
> the slave.
Done, and the lib/ dir with all jars deleted.
Gav...
>
> To answer another question, this slave has not been rebuilt or modified in
> any way prior to these builds starting to fail (that I know of). Only thing I've
> been doing extra to investigating your builds is also building a new windows2
> slave that is obviously needed.
>
> Note also my delayed replies are due to me being GMT + 10
>
> Gav...
>
> >
> > Thanks,
> > -Alex
> >
> >
> > On 12/14/13 7:33 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> > >It occurred to me that the tests are also going to want a window so
> > >if we're having issues with that, it could have causes the tests to
> > >hang waiting for them to even run.
> > >
> > >I've removed the test target and started a new build. But we'll see
> > >if it can delete those jars or not.
> > >
> > >-Alex
> > >
> > >On 12/14/13 7:12 AM, "Alex Harui" <ah...@adobe.com> wrote:
> > >
> > >>Hi Gavin,
> > >>
> > >>Looks like build are running. Jenkins says that a flex-sdk build
> > >>was running, compiled cleanly but timed out after an hour while
> > >>running tests, and then the next flex-sdk build failed because it
> > >>couldn't delete some jars.
> > >>
> > >>I'm wondering if the job that was running tests somehow locked those
> > >>jars?
> > >> Can you delete those jars manually (or tell me how to; I'm a newbie
> > >>at Jenkins? Also, can you confirm that the server was not rebuilt.
> > >>Our build will fail and get stuck running tests if the FlashPlayer "trust"
> > >>files are not set up properly which I believe is a manual step on a
> > >>fresh setup.
> > >>
> > >>Thanks,
> > >>-Alex
> > >>
> > >>On 12/14/13 2:05 AM, "Gavin McDonald" <ga...@16degrees.com.au>
> > wrote:
> > >>
> > >>>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> > >>>> Sent: Saturday, 14 December 2013 6:00 PM
> > >>>> To: Alex Harui
> > >>>> Cc: builds@apache.org; gavin@16degrees.com.au
> > >>>> Subject: Re: [windows1] Pixelbender installation
> > >>>>
> > >>>> Gavin, please, please, pretty please, can you have a look at the
> > >>>>'windows1'
> > >>>> situation? Please?
> > >>>>
> > >>>> Or, if you don't have time - which I would totally understand and
> > >>>>respect - please tell us so one of the other 8 admins on the
> > >>>>'windows1' slave can step in.
> > >>>>
> > >>>> Our project needs the builds, as I explained in earlier
> > >>>>communications, third party teams depend on them and I think we
> > may
> > >>>>be loosing their cooperation and contributions if we don't
> > >>>>deliver soon.
> > >>>
> > >>>Yep, totally understand about that. Rest assured the stability of
> > >>>the Jenkins and buildbot builds is a priority.
> > >>>
> > >>>Gav...
> > >>>
> > >>>>
> > >>>> EdB
> > >>>>
> > >>>>
> > >>>>
> > >>>> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com>
> > wrote:
> > >>>> > We just pushed changes to put all the pixel bender stuff in its
> > >>>> > own upstream package that won't be built by Jenkins (because it
> > >>>> > rarely changes). Theoretically, this eliminates the need for
> > >>>> > the Flex
> > >>>>build
> > >>>> > to need a window. We'll see how the next builds come out.
> > >>>> >
> > >>>> > Thank you for trying to fix this. Creating the upstream
> > >>>> > package
> > >>>>isn't
> > >>>> > just a workaround for this issue, it also gives us a more
> > >>>> > consistent build experience for our Linux users as the
> > >>>> > PixelBender compiler
> > >>>>does
> > >>>> > not work on Linux.
> > >>>> >
> > >>>> > Hopefully the builds will start to work now, but I won't be
> > >>>>surprised
> > >>>> > if there is some other issue waiting to be discovered.
> > >>>> >
> > >>>> > Thanks,
> > >>>> > -Alex
> > >>>> >
> > >>>> > On 12/12/13 8:24 AM, "OmPrakash Muppirala"
> > <bi...@gmail.com>
> > >>>> wrote:
> > >>>> >
> > >>>> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald"
> > >>>> >><ga...@16degrees.com.au>
> > >>>> wrote:
> > >>>> >>>
> > >>>> >>> So, the slave is configured for Œweb start¹ via JNLP and that
> > >>>> >>> is
> > >>>>how
> > >>>> >>> it
> > >>>> >>is currently connected.
> > >>>> >>>
> > >>>> >>> The Œservice¹ was also running (which JNLP can control too)
> > >>>> >>> so I turned
> > >>>> >>that off and set it to
> > >>>> >>>
> > >>>> >>> Œmaunal¹ start only.
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> There are 3 builds running. I¹ll reboot the server at an
> > >>>>appropriate
> > >>>> >>interval within the next hour or
> > >>>> >>>
> > >>>> >>> so and we¹ll try again.
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> GavŠ
> > >>>> >>>
> > >>>> >>
> > >>>> >>Okay, can you please let me know when you start it again?
> > >>>> >>
> > >>>> >>Thanks,
> > >>>> >>Om
> > >>>> >>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On
> > Behalf Of
> > >>>> >>>OmPrakash
> > >>>> >>Muppirala
> > >>>> >>> Sent: Thursday, 12 December 2013 7:15 PM
> > >>>> >>> To: builds@apache.org; Gavin McDonald
> > >>>> >>> Cc: Erik de Bruin
> > >>>> >>>
> > >>>> >>> Subject: Re: [windows1] Pixelbender installation
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> Hi Gav,
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> Any updates on this issue?
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> Thanks,
> > >>>> >>>
> > >>>> >>> Om
> > >>>> >>>
> > >>>> >>>
> > >>>> >>>
> > >>>> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
> > >>>> >>><bi...@gmail.com>
> > >>>> >>wrote:
> > >>>> >>>>
> > >>>> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
> > >>>> >>>><ga...@16degrees.com.au>
> > >>>> >>wrote:
> > >>>> >>>>>
> > >>>> >>>>>
> > >>>> >>>>>
> > >>>> >>>>> > -----Original Message-----
> > >>>> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com]
> On
> > >>>> >>>>> > Behalf
> > >>>> Of
> > >>>> >>>>> > OmPrakash Muppirala
> > >>>> >>>>>
> > >>>> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
> > >>>> >>>>> > To: Gavin McDonald
> > >>>> >>>>> > Cc: builds@apache.org; Erik de Bruin
> > >>>> >>>>> > Subject: Re: [windows1] Pixelbender installation
> > >>>> >>>>> >
> > >>>> >>>>>
> > >>>> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> > >>>> >>>>> > <bi...@gmail.com>wrote:
> > >>>> >>>>> >
> > >>>> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> > >>>> >>>>> > <ga...@16degrees.com.au>wrote:
> > >>>> >>>>> > >
> > >>>> >>>>> > >> Interesting, and puzzling why, but interactive desktop
> > >>>> >>>>> > >> flag was turned off.
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> I've now re-enabled it, please try again.
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>>
> > >>>> >>>>> > >> Gav.
> > >>>> >>>>>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > > Great! I have kicked off a build. Will report back in
> > >>>> >>>>> > > a
> > >>>>bit.
> > >>>> >>>>> > >
> > >>>> >>>>> > > Was the windows1 slave started via JNLP or as a windows
> > >>>>service?
> > >>>> >>>>> > > Starting via JNLP (using webstart) ensures that the
> > >>>> >>>>> > > interactive
> > >>>> >>flag is
> > >>>> >>>>> set.
> > >>>> >>>>> > > Whereas if it is modified to be started as a service,
> > >>>> >>>>> > > you
> > >>>>will
> > >>>> >>>>>have
> > >>>> >>to
> > >>>> >>>>> > > manually turn the interactive flag (which sometimes may
> > >>>> >>>>> > > not
> > >>>> >>propagate
> > >>>> >>>>> > > all the way down the process we try to invoke)
> > >>>> >>>>> > >
> > >>>> >>>>> > > If this does not work, will you be able to restart the
> > >>>> >>>>> > > slave via
> > >>>> >>JNLP?
> > >>>> >>>>> > >
> > >>>> >>>>> > > Thanks,
> > >>>> >>>>> > > Om
> > >>>> >>>>> > >
> > >>>> >>>>> >
> > >>>> >>>>> > Yes, the build failed as I was typing my previous response.
> > >>>> >>>>> >
> > >>>> >>>>> > Any chance you could restart the windows1 Jenkins
> > >>>> >>>>> > instance as just a
> > >>>> >>JNLP
> > >>>> >>>>> > slave agent instead of modifying it into windows
> webservice?
> > >>>>[1]
> > >>>> >>>>>
> > >>>> >>>>> I could, but I don't understand, this Jenkins slave has
> > >>>> >>>>>been running as
> > >>>> >>a
> > >>>> >>>>> service since the day
> > >>>> >>>>> I built it years ago.
> > >>>> >>>>>
> > >>>> >>>>> Gav...
> > >>>> >>>>
> > >>>> >>>>
> > >>>> >>>>
> > >>>> >>>> I don't understand too, but doing this in our test
> > >>>> >>>>environment fixed the
> > >>>> >>problem, whereas manually setting the interactive flag did not.
> > >>>> >>As you mentioned earlier, something somewhere reset the
> > >>>> >>interactive
> > >>>>flag
> > >>>> >>on the root process. Unless you want to dig deeper and figure
> > >>>> >>out what happened, I think that restarting it to run as a JNLP
> > >>>> >>slave
> > >>>>agent
> > >>>> >>should fix the problem (as per Jenkins' docs) .
> > >>>> >>>>
> > >>>> >>>> Do you have any other ideas on how to fix this?
> > >>>> >>>>
> > >>>> >>>> Thanks,
> > >>>> >>>> Om
> > >>>> >>>>
> > >>>> >>>>
> > >>>> >>>>
> > >>>> >>>>>
> > >>>> >>>>>
> > >>>> >>>>> >
> > >>>> >>>>> > Thanks,
> > >>>> >>>>> > Om
> > >>>> >>>>> >
> > >>>> >>>>> > [1]
> > >>>> >>>>> > https://wiki.jenkins-
> > >>>> >>>>> >
> > >>>>
> >
> >>>>>>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#I
> > ns
> > >>>>>>tal
> > >>>>>>l
> > >>>> >>ingJ
> > >>>> >>>>> > enkinsasaWindowsservice-
> > >>>> >>>>> >
> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
> > >>>> >>>>>
> > >>>> >>>>> >
> > >>>> >>>>> >
> > >>>> >>>>> >
> > >>>> >>>>> > >
> > >>>> >>>>> > >
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> *From:* omuppi1@gmail.com
> > [mailto:omuppi1@gmail.com] *On
> > >>>> >>>>> > >> Behalf
> > >>>> >>>>> > Of
> > >>>> >>>>> > >> *OmPrakash Muppirala
> > >>>> >>>>>
> > >>>> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> > >>>> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
> > >>>> >>>>> > >> *Cc:* Erik de Bruin
> > >>>> >>>>>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>>
> > >>>> >>>>> > >> Thanks Gav!
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> We did a bunch of tests to repro this issue on our side.
> > >>>>One
> > >>>> >>>>> > >> way
> > >>>> >>we
> > >>>> >>>>> > >> could reproduce this on our Jenkins installation was
> > >>>> >>>>> > >> that
> > >>>>if
> > >>>> >>>>> > >> we
> > >>>> >>>>>ran
> > >>>> >>>>> > >> the job as a service, we are getting the same error
> > >>>>messages
> > >>>> >>>>> > >> (AIF Internal exception).
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> Jenkins docs says that for jobs that require Desktop
> > >>>> >>>>> > >> Access
> > >>>> >>>>>(which
> > >>>> >>>>> > >> Pixel Bender does), the root service process that is
> > >>>>running
> > >>>> >>>>> > >> the
> > >>>> >>job
> > >>>> >>>>> > >> needs to have the 'interactive flag' enabled in the
> > >>>> >>>>> > >> Windows
> > >>>> >>>>>Service
> > >>>> >>>>> > >> Manager. [1]
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> One way this setting could have changed is if the way
> > >>>> >>>>> > >> the windows slave starts was modified.
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> Can you please take a look under the hood and see if
> > >>>> >>>>> > >> you
> > >>>>find
> > >>>> >>>>> > >> something amiss?
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> Thanks,
> > >>>> >>>>> > >> Om
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> [1]
> > >>>> >>>>> > >> https://wiki.jenkins-
> > >>>> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
> > >>>> >>>>> > >> computer+but+not+on+Jenkins
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> > >>>> >>>>> > >> <ga...@16degrees.com.au>
> > >>>> >>>>> > >> wrote:
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> > -----Original Message-----
> > >>>> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
> > >>>> >>>>> > >> > To: builds@apache.org
> > >>>> >>>>> > >> > Cc: Gavin McDonald
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
> > >>>> >>>>> > >> >
> > >>>> >>>>> > >> > 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\shaderClasse
> > >>>> >>>>>s
> > >>>> \Color.
> > >>>> >>>>> > >> > pbk"
> > >>>> >>>>> > >> > "F:\hudson\hudson-slave\workspace\flex-
> > >>>> >>>>> > >> >
> > >>>> >>>>> >
> > >>>>
> >
> >>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasse
> > >>>> >>>>>s
> > >>>> \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...
> > >>>> >>>>> > >>
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> >
> > >>>> >>>>> > >> > EdB
> > >>>> >>>>> > >> >
> > >>>> >>>>> > >> >
> > >>>> >>>>> > >> >
> > >>>> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash
> Muppirala
> > >>>> >>>>> > >> > <bi...@gmail.com> wrote:
> > >>>> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> > >>>> >>>>> > >> > <ga...@16degrees.com.au>wrote:
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to
> > >>>> >>>>> > >> > >> get across
> > >>>> >>>>>is
> > >>>> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows
> slave,
> > so
> > >>>> >>>>> > >> > >> is
> > >>>>it
> > >>>> >>>>> > >> > >> very slightly possible that the build is failing
> > >>>> >>>>> > >> > >> due
> > >>>>to
> > >>>> >>>>> > >> > >> a coding error? In other words, I've been blamed
> > >>>>several
> > >>>> >>>>> > >> > >> times now
> > >>>> >>>>>for
> > >>>> >>>>> > >> > >> breaking the build when I haven't been anywhere
> > >>>> >>>>> > >> > >> near
> > >>>>the
> > >>>> >>machine
> > >>>> >>>>> > in question.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > > The build does not fail on my or other committers'
> > >>>>machines.
> > >>>> >> It
> > >>>> >>>>> > >> > > must be something specific to whats happening in
> > >>>>Windows1.
> > >>>> >> Sorry
> > >>>> >>>>> > >> > > if it sounds like we are blaming you. We are just
> > >>>>trying
> > >>>> >>>>> > >> > > to troubleshoot and are running blind here.
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Either way I'll look.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > > Thanks!
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> And so that we are clear, windows1 is not going
> > >>>> >>>>> > >> > >> away,
> > >>>>it
> > >>>> >>>>> > >> > >> is
> > >>>> >>very
> > >>>> >>>>> > >> > >> heavily used, folks are always complaining it is
> > >>>> >>>>> > >> > >> down, so
> > >>>> >>>>>I'm
> > >>>> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the
> > >>>> >>>>> > >> > >> windows1
> > >>>> >>>>>slave.
> > >>>> >>>>> > >> > >> Point is, you need to be configured to use both
> > >>>> >>>>> > >> > >> slaves for
> > >>>> >>>>>it
> > >>>> >>to
> > >>>> >>>>> > >> > >> work, or my time
> > >>>> >>>>> > >> > building a 2ndmachine is wasted and you'll continue
> > >>>> >>>>> > >> > to complain about
> > >>>> >>>>> > >> the
> > >>>> >>>>> > >> 1
> > >>>> >>>>> > >> > st windows box being overloaded all the time.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > > We welcome the addition of a new windows slave, no
> > >>>>doubt.
> > >>>> >> Which
> > >>>> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise
> > >>>> >>>>> > >> > > it
> > >>>>will
> > >>>> >>>>> > >> > > lead
> > >>>> >>to
> > >>>> >>>>> > >> > > more variables to troubleshoot.
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > > On that note, perhaps you can image windows1 and
> > >>>> >>>>> > >> > > create
> > >>>> >>windows2
> > >>>> >>>>> > >> > > as a clone of it?
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > > Regards,
> > >>>> >>>>> > >> > > Om
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >> > >
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> > >> Gav.
> > >>>> >>>>> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> *From:* omuppi1@gmail.com
> > >>>> [mailto:omuppi1@gmail.com] *On
> > >>>> >>>>> > Behalf
> > >>>> >>>>> > >> > Of
> > >>>> >>>>> > >> > >> *OmPrakash Muppirala
> > >>>> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> > >>>> >>>>> > >> > >> *To:* builds@apache.org
> > >>>> >>>>> > >> > >> *Cc:* Gavin McDonald
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender
> > >>>> >>>>> > >> > >> installation
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Gavin,
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our
> > >>>> >>>>> > >> > >> long running
> > >>>> >>job
> > >>>> >>>>> > >> > >> on
> > >>>> >>>>> > >> > >> Windows1 has started failing for the past few days.
> > >>>>Can
> > >>>> >>>>> > >> > >> we first fix that before we start working on
> > Windows2?
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Thanks,
> > >>>> >>>>> > >> > >> Om
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> > >>>> >>>>> > >> > >> <er...@ixsoftware.nl>
> > >>>> >>>>> > >> > wrote:
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Ok, from the top of this thread:
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> "The build on windows1 is failing on the
> 'Pixelbender'
> > >>>>task:
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> The build assumes Pixelbender is installed at:
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
> > >>>> (x86)/Adobe/Adobe
> > >>>> >>>>> > >> > >> Utilities\ -
> > >>>> >>>>> > >> > \
> > >>>> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Is that still the correct path and does the
> > >>>>application
> > >>>> >>>>>start
> > >>>> >>>>> > >> > >> without errors when you launch it manually?"
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> In another email in this thread I've listed the
> > >>>>software
> > >>>> >>>>>that
> > >>>> >>>>> > >> > >> needs to be on windows2.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Is there a way to have all our builds run on
> > >>>> >>>>> > >> > >> either
> > >>>> >>>>> > >> > >> windows1
> > >>>> >>OR
> > >>>> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
> > >>>> >>>>> > >> > >> workspaces
> > >>>> >>of
> > >>>> >>>>> > >> > >> some of our other builds, in order to save on
> > >>>> >>>>> > >> > >> disk
> > >>>>space
> > >>>> >>>>> > >> > >> and
> > >>>> >>build
> > >>>> >>>>> > time.
> > >>>> >>>>> > >> > >> If we remove these dependencies, we'd basically
> > >>>> >>>>> > >> > >> be forced to copy each build into each other build.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Since it is the weekend, I'll have limited time
> > >>>> >>>>> > >> > >> to
> > >>>>work
> > >>>> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
> > >>>> >>>>> > >> > >> check/test/adjust whatever needs
> > >>>> checking/testing/adjusting.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> Please keep in mind that we are at a very
> > >>>> >>>>> > >> > >> important
> > >>>> >>>>>milestone
> > >>>> >>>>> > >> > >> for our project, and with third party teams
> > >>>> >>>>> > >> > >> relying on our nightly builds, we'd greatly
> > >>>> >>>>> > >> > >> appreciate a
> > >>>>successful
> > >>>> >>>>> > >> > >> run of
> > >>>> >>all
> > >>>> >>>>> > >> > >> our jobs, on whatever slave works.
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >>
> > >>>> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Alex Harui [mailto:aharui@adobe.com]
> Sent: Sunday, 15 December 2013 4:19 AM
> To: builds@apache.org; gavin@16degrees.com.au; 'Erik de Bruin'
> Subject: Re: [windows1] Pixelbender installation
>
> Hi Gavin,
>
> The build script is using a simple Ant Delete task and can't delete jars.
> Can you assist in investigating why the delete is failing?
Seems the jars think they are still being used, and refuse to delete.
At the next opportunity when no or little builds running, I'll have to reboot
the slave.
To answer another question, this slave has not been rebuilt or modified in any way
prior to these builds starting to fail (that I know of). Only thing I've been doing extra
to investigating your builds is also building a new windows2 slave that is obviously needed.
Note also my delayed replies are due to me being GMT + 10
Gav...
>
> Thanks,
> -Alex
>
>
> On 12/14/13 7:33 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >It occurred to me that the tests are also going to want a window so if
> >we're having issues with that, it could have causes the tests to hang
> >waiting for them to even run.
> >
> >I've removed the test target and started a new build. But we'll see if
> >it can delete those jars or not.
> >
> >-Alex
> >
> >On 12/14/13 7:12 AM, "Alex Harui" <ah...@adobe.com> wrote:
> >
> >>Hi Gavin,
> >>
> >>Looks like build are running. Jenkins says that a flex-sdk build was
> >>running, compiled cleanly but timed out after an hour while running
> >>tests, and then the next flex-sdk build failed because it couldn't
> >>delete some jars.
> >>
> >>I'm wondering if the job that was running tests somehow locked those
> >>jars?
> >> Can you delete those jars manually (or tell me how to; I'm a newbie
> >>at Jenkins? Also, can you confirm that the server was not rebuilt.
> >>Our build will fail and get stuck running tests if the FlashPlayer "trust"
> >>files are not set up properly which I believe is a manual step on a
> >>fresh setup.
> >>
> >>Thanks,
> >>-Alex
> >>
> >>On 12/14/13 2:05 AM, "Gavin McDonald" <ga...@16degrees.com.au>
> wrote:
> >>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>>> Sent: Saturday, 14 December 2013 6:00 PM
> >>>> To: Alex Harui
> >>>> Cc: builds@apache.org; gavin@16degrees.com.au
> >>>> Subject: Re: [windows1] Pixelbender installation
> >>>>
> >>>> Gavin, please, please, pretty please, can you have a look at the
> >>>>'windows1'
> >>>> situation? Please?
> >>>>
> >>>> Or, if you don't have time - which I would totally understand and
> >>>>respect - please tell us so one of the other 8 admins on the
> >>>>'windows1' slave can step in.
> >>>>
> >>>> Our project needs the builds, as I explained in earlier
> >>>>communications, third party teams depend on them and I think we
> may
> >>>>be loosing their cooperation and contributions if we don't deliver
> >>>>soon.
> >>>
> >>>Yep, totally understand about that. Rest assured the stability of the
> >>>Jenkins and buildbot builds is a priority.
> >>>
> >>>Gav...
> >>>
> >>>>
> >>>> EdB
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com>
> wrote:
> >>>> > We just pushed changes to put all the pixel bender stuff in its
> >>>> > own upstream package that won't be built by Jenkins (because it
> >>>> > rarely changes). Theoretically, this eliminates the need for the
> >>>> > Flex
> >>>>build
> >>>> > to need a window. We'll see how the next builds come out.
> >>>> >
> >>>> > Thank you for trying to fix this. Creating the upstream package
> >>>>isn't
> >>>> > just a workaround for this issue, it also gives us a more
> >>>> > consistent build experience for our Linux users as the
> >>>> > PixelBender compiler
> >>>>does
> >>>> > not work on Linux.
> >>>> >
> >>>> > Hopefully the builds will start to work now, but I won't be
> >>>>surprised
> >>>> > if there is some other issue waiting to be discovered.
> >>>> >
> >>>> > Thanks,
> >>>> > -Alex
> >>>> >
> >>>> > On 12/12/13 8:24 AM, "OmPrakash Muppirala"
> <bi...@gmail.com>
> >>>> wrote:
> >>>> >
> >>>> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald"
> >>>> >><ga...@16degrees.com.au>
> >>>> wrote:
> >>>> >>>
> >>>> >>> So, the slave is configured for Œweb start¹ via JNLP and that
> >>>> >>> is
> >>>>how
> >>>> >>> it
> >>>> >>is currently connected.
> >>>> >>>
> >>>> >>> The Œservice¹ was also running (which JNLP can control too) so
> >>>> >>> I turned
> >>>> >>that off and set it to
> >>>> >>>
> >>>> >>> Œmaunal¹ start only.
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> There are 3 builds running. I¹ll reboot the server at an
> >>>>appropriate
> >>>> >>interval within the next hour or
> >>>> >>>
> >>>> >>> so and we¹ll try again.
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> GavŠ
> >>>> >>>
> >>>> >>
> >>>> >>Okay, can you please let me know when you start it again?
> >>>> >>
> >>>> >>Thanks,
> >>>> >>Om
> >>>> >>
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On
> Behalf Of
> >>>> >>>OmPrakash
> >>>> >>Muppirala
> >>>> >>> Sent: Thursday, 12 December 2013 7:15 PM
> >>>> >>> To: builds@apache.org; Gavin McDonald
> >>>> >>> Cc: Erik de Bruin
> >>>> >>>
> >>>> >>> Subject: Re: [windows1] Pixelbender installation
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> Hi Gav,
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> Any updates on this issue?
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> Thanks,
> >>>> >>>
> >>>> >>> Om
> >>>> >>>
> >>>> >>>
> >>>> >>>
> >>>> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
> >>>> >>><bi...@gmail.com>
> >>>> >>wrote:
> >>>> >>>>
> >>>> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
> >>>> >>>><ga...@16degrees.com.au>
> >>>> >>wrote:
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>> > -----Original Message-----
> >>>> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On
> >>>> >>>>> > Behalf
> >>>> Of
> >>>> >>>>> > OmPrakash Muppirala
> >>>> >>>>>
> >>>> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
> >>>> >>>>> > To: Gavin McDonald
> >>>> >>>>> > Cc: builds@apache.org; Erik de Bruin
> >>>> >>>>> > Subject: Re: [windows1] Pixelbender installation
> >>>> >>>>> >
> >>>> >>>>>
> >>>> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> >>>> >>>>> > <bi...@gmail.com>wrote:
> >>>> >>>>> >
> >>>> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> >>>> >>>>> > <ga...@16degrees.com.au>wrote:
> >>>> >>>>> > >
> >>>> >>>>> > >> Interesting, and puzzling why, but interactive desktop
> >>>> >>>>> > >> flag was turned off.
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> I've now re-enabled it, please try again.
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>>
> >>>> >>>>> > >> Gav.
> >>>> >>>>>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > > Great! I have kicked off a build. Will report back in a
> >>>>bit.
> >>>> >>>>> > >
> >>>> >>>>> > > Was the windows1 slave started via JNLP or as a windows
> >>>>service?
> >>>> >>>>> > > Starting via JNLP (using webstart) ensures that the
> >>>> >>>>> > > interactive
> >>>> >>flag is
> >>>> >>>>> set.
> >>>> >>>>> > > Whereas if it is modified to be started as a service, you
> >>>>will
> >>>> >>>>>have
> >>>> >>to
> >>>> >>>>> > > manually turn the interactive flag (which sometimes may
> >>>> >>>>> > > not
> >>>> >>propagate
> >>>> >>>>> > > all the way down the process we try to invoke)
> >>>> >>>>> > >
> >>>> >>>>> > > If this does not work, will you be able to restart the
> >>>> >>>>> > > slave via
> >>>> >>JNLP?
> >>>> >>>>> > >
> >>>> >>>>> > > Thanks,
> >>>> >>>>> > > Om
> >>>> >>>>> > >
> >>>> >>>>> >
> >>>> >>>>> > Yes, the build failed as I was typing my previous response.
> >>>> >>>>> >
> >>>> >>>>> > Any chance you could restart the windows1 Jenkins instance
> >>>> >>>>> > as just a
> >>>> >>JNLP
> >>>> >>>>> > slave agent instead of modifying it into windows webservice?
> >>>>[1]
> >>>> >>>>>
> >>>> >>>>> I could, but I don't understand, this Jenkins slave has been
> >>>> >>>>>running as
> >>>> >>a
> >>>> >>>>> service since the day
> >>>> >>>>> I built it years ago.
> >>>> >>>>>
> >>>> >>>>> Gav...
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>> I don't understand too, but doing this in our test environment
> >>>> >>>>fixed the
> >>>> >>problem, whereas manually setting the interactive flag did not.
> >>>> >>As you mentioned earlier, something somewhere reset the
> >>>> >>interactive
> >>>>flag
> >>>> >>on the root process. Unless you want to dig deeper and figure
> >>>> >>out what happened, I think that restarting it to run as a JNLP
> >>>> >>slave
> >>>>agent
> >>>> >>should fix the problem (as per Jenkins' docs) .
> >>>> >>>>
> >>>> >>>> Do you have any other ideas on how to fix this?
> >>>> >>>>
> >>>> >>>> Thanks,
> >>>> >>>> Om
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>>
> >>>> >>>>>
> >>>> >>>>> >
> >>>> >>>>> > Thanks,
> >>>> >>>>> > Om
> >>>> >>>>> >
> >>>> >>>>> > [1]
> >>>> >>>>> > https://wiki.jenkins-
> >>>> >>>>> >
> >>>>
> >>>>>>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#I
> ns
> >>>>>>tal
> >>>>>>l
> >>>> >>ingJ
> >>>> >>>>> > enkinsasaWindowsservice-
> >>>> >>>>> >
> InstallSlaveasaWindowsservice%28require.NET2.0framework%29
> >>>> >>>>>
> >>>> >>>>> >
> >>>> >>>>> >
> >>>> >>>>> >
> >>>> >>>>> > >
> >>>> >>>>> > >
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> *From:* omuppi1@gmail.com
> [mailto:omuppi1@gmail.com] *On
> >>>> >>>>> > >> Behalf
> >>>> >>>>> > Of
> >>>> >>>>> > >> *OmPrakash Muppirala
> >>>> >>>>>
> >>>> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> >>>> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
> >>>> >>>>> > >> *Cc:* Erik de Bruin
> >>>> >>>>>
> >>>> >>>>> > >>
> >>>> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>>
> >>>> >>>>> > >> Thanks Gav!
> >>>> >>>>> > >>
> >>>> >>>>> > >> We did a bunch of tests to repro this issue on our side.
> >>>>One
> >>>> >>>>> > >> way
> >>>> >>we
> >>>> >>>>> > >> could reproduce this on our Jenkins installation was
> >>>> >>>>> > >> that
> >>>>if
> >>>> >>>>> > >> we
> >>>> >>>>>ran
> >>>> >>>>> > >> the job as a service, we are getting the same error
> >>>>messages
> >>>> >>>>> > >> (AIF Internal exception).
> >>>> >>>>> > >>
> >>>> >>>>> > >> Jenkins docs says that for jobs that require Desktop
> >>>> >>>>> > >> Access
> >>>> >>>>>(which
> >>>> >>>>> > >> Pixel Bender does), the root service process that is
> >>>>running
> >>>> >>>>> > >> the
> >>>> >>job
> >>>> >>>>> > >> needs to have the 'interactive flag' enabled in the
> >>>> >>>>> > >> Windows
> >>>> >>>>>Service
> >>>> >>>>> > >> Manager. [1]
> >>>> >>>>> > >>
> >>>> >>>>> > >> One way this setting could have changed is if the way
> >>>> >>>>> > >> the windows slave starts was modified.
> >>>> >>>>> > >>
> >>>> >>>>> > >> Can you please take a look under the hood and see if you
> >>>>find
> >>>> >>>>> > >> something amiss?
> >>>> >>>>> > >>
> >>>> >>>>> > >> Thanks,
> >>>> >>>>> > >> Om
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> [1]
> >>>> >>>>> > >> https://wiki.jenkins-
> >>>> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
> >>>> >>>>> > >> computer+but+not+on+Jenkins
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> >>>> >>>>> > >> <ga...@16degrees.com.au>
> >>>> >>>>> > >> wrote:
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> > -----Original Message-----
> >>>> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>>> >>>>> > >>
> >>>> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
> >>>> >>>>> > >> > To: builds@apache.org
> >>>> >>>>> > >> > Cc: Gavin McDonald
> >>>> >>>>> > >>
> >>>> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
> >>>> >>>>> > >> >
> >>>> >>>>> > >> > 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\shaderClasse
> >>>> >>>>>s
> >>>> \Color.
> >>>> >>>>> > >> > pbk"
> >>>> >>>>> > >> > "F:\hudson\hudson-slave\workspace\flex-
> >>>> >>>>> > >> >
> >>>> >>>>> >
> >>>>
> >>>>>sdk\frameworks\projects\framework\src\mx\graphics\shaderClasse
> >>>> >>>>>s
> >>>> \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...
> >>>> >>>>> > >>
> >>>> >>>>> > >>
> >>>> >>>>> > >> >
> >>>> >>>>> > >> > EdB
> >>>> >>>>> > >> >
> >>>> >>>>> > >> >
> >>>> >>>>> > >> >
> >>>> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> >>>> >>>>> > >> > <bi...@gmail.com> wrote:
> >>>> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> >>>> >>>>> > >> > <ga...@16degrees.com.au>wrote:
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to
> >>>> >>>>> > >> > >> get across
> >>>> >>>>>is
> >>>> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave,
> so
> >>>> >>>>> > >> > >> is
> >>>>it
> >>>> >>>>> > >> > >> very slightly possible that the build is failing
> >>>> >>>>> > >> > >> due
> >>>>to
> >>>> >>>>> > >> > >> a coding error? In other words, I've been blamed
> >>>>several
> >>>> >>>>> > >> > >> times now
> >>>> >>>>>for
> >>>> >>>>> > >> > >> breaking the build when I haven't been anywhere
> >>>> >>>>> > >> > >> near
> >>>>the
> >>>> >>machine
> >>>> >>>>> > in question.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > > The build does not fail on my or other committers'
> >>>>machines.
> >>>> >> It
> >>>> >>>>> > >> > > must be something specific to whats happening in
> >>>>Windows1.
> >>>> >> Sorry
> >>>> >>>>> > >> > > if it sounds like we are blaming you. We are just
> >>>>trying
> >>>> >>>>> > >> > > to troubleshoot and are running blind here.
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Either way I'll look.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > > Thanks!
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> And so that we are clear, windows1 is not going
> >>>> >>>>> > >> > >> away,
> >>>>it
> >>>> >>>>> > >> > >> is
> >>>> >>very
> >>>> >>>>> > >> > >> heavily used, folks are always complaining it is
> >>>> >>>>> > >> > >> down, so
> >>>> >>>>>I'm
> >>>> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the
> >>>> >>>>> > >> > >> windows1
> >>>> >>>>>slave.
> >>>> >>>>> > >> > >> Point is, you need to be configured to use both
> >>>> >>>>> > >> > >> slaves for
> >>>> >>>>>it
> >>>> >>to
> >>>> >>>>> > >> > >> work, or my time
> >>>> >>>>> > >> > building a 2ndmachine is wasted and you'll continue to
> >>>> >>>>> > >> > complain about
> >>>> >>>>> > >> the
> >>>> >>>>> > >> 1
> >>>> >>>>> > >> > st windows box being overloaded all the time.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > > We welcome the addition of a new windows slave, no
> >>>>doubt.
> >>>> >> Which
> >>>> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise it
> >>>>will
> >>>> >>>>> > >> > > lead
> >>>> >>to
> >>>> >>>>> > >> > > more variables to troubleshoot.
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > > On that note, perhaps you can image windows1 and
> >>>> >>>>> > >> > > create
> >>>> >>windows2
> >>>> >>>>> > >> > > as a clone of it?
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > > Regards,
> >>>> >>>>> > >> > > Om
> >>>> >>>>> > >> > >
> >>>> >>>>> > >> > >
> >>>> >>>>> > >>
> >>>> >>>>> > >> > >> Gav.
> >>>> >>>>> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> *From:* omuppi1@gmail.com
> >>>> [mailto:omuppi1@gmail.com] *On
> >>>> >>>>> > Behalf
> >>>> >>>>> > >> > Of
> >>>> >>>>> > >> > >> *OmPrakash Muppirala
> >>>> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >>>> >>>>> > >> > >> *To:* builds@apache.org
> >>>> >>>>> > >> > >> *Cc:* Gavin McDonald
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Gavin,
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our
> >>>> >>>>> > >> > >> long running
> >>>> >>job
> >>>> >>>>> > >> > >> on
> >>>> >>>>> > >> > >> Windows1 has started failing for the past few days.
> >>>>Can
> >>>> >>>>> > >> > >> we first fix that before we start working on
> Windows2?
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Thanks,
> >>>> >>>>> > >> > >> Om
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> >>>> >>>>> > >> > >> <er...@ixsoftware.nl>
> >>>> >>>>> > >> > wrote:
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Ok, from the top of this thread:
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender'
> >>>>task:
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> The build assumes Pixelbender is installed at:
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
> >>>> (x86)/Adobe/Adobe
> >>>> >>>>> > >> > >> Utilities\ -
> >>>> >>>>> > >> > \
> >>>> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Is that still the correct path and does the
> >>>>application
> >>>> >>>>>start
> >>>> >>>>> > >> > >> without errors when you launch it manually?"
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> In another email in this thread I've listed the
> >>>>software
> >>>> >>>>>that
> >>>> >>>>> > >> > >> needs to be on windows2.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Is there a way to have all our builds run on either
> >>>> >>>>> > >> > >> windows1
> >>>> >>OR
> >>>> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
> >>>> >>>>> > >> > >> workspaces
> >>>> >>of
> >>>> >>>>> > >> > >> some of our other builds, in order to save on disk
> >>>>space
> >>>> >>>>> > >> > >> and
> >>>> >>build
> >>>> >>>>> > time.
> >>>> >>>>> > >> > >> If we remove these dependencies, we'd basically be
> >>>> >>>>> > >> > >> forced to copy each build into each other build.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Since it is the weekend, I'll have limited time to
> >>>>work
> >>>> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
> >>>> >>>>> > >> > >> check/test/adjust whatever needs
> >>>> checking/testing/adjusting.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> Please keep in mind that we are at a very important
> >>>> >>>>>milestone
> >>>> >>>>> > >> > >> for our project, and with third party teams relying
> >>>> >>>>> > >> > >> on our nightly builds, we'd greatly appreciate a
> >>>>successful
> >>>> >>>>> > >> > >> run of
> >>>> >>all
> >>>> >>>>> > >> > >> our jobs, on whatever slave works.
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >>
> >>>> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Alex Harui <ah...@adobe.com>.
Hi Gavin,
The build script is using a simple Ant Delete task and can't delete jars.
Can you assist in investigating why the delete is failing?
Thanks,
-Alex
On 12/14/13 7:33 AM, "Alex Harui" <ah...@adobe.com> wrote:
>It occurred to me that the tests are also going to want a window so if
>we're having issues with that, it could have causes the tests to hang
>waiting for them to even run.
>
>I've removed the test target and started a new build. But we'll see if it
>can delete those jars or not.
>
>-Alex
>
>On 12/14/13 7:12 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>Hi Gavin,
>>
>>Looks like build are running. Jenkins says that a flex-sdk build was
>>running, compiled cleanly but timed out after an hour while running
>>tests,
>>and then the next flex-sdk build failed because it couldn't delete some
>>jars.
>>
>>I'm wondering if the job that was running tests somehow locked those
>>jars?
>> Can you delete those jars manually (or tell me how to; I'm a newbie at
>>Jenkins? Also, can you confirm that the server was not rebuilt. Our
>>build will fail and get stuck running tests if the FlashPlayer "trust"
>>files are not set up properly which I believe is a manual step on a fresh
>>setup.
>>
>>Thanks,
>>-Alex
>>
>>On 12/14/13 2:05 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>> Sent: Saturday, 14 December 2013 6:00 PM
>>>> To: Alex Harui
>>>> Cc: builds@apache.org; gavin@16degrees.com.au
>>>> Subject: Re: [windows1] Pixelbender installation
>>>>
>>>> Gavin, please, please, pretty please, can you have a look at the
>>>>'windows1'
>>>> situation? Please?
>>>>
>>>> Or, if you don't have time - which I would totally understand and
>>>>respect -
>>>> please tell us so one of the other 8 admins on the 'windows1' slave
>>>>can
>>>>step
>>>> in.
>>>>
>>>> Our project needs the builds, as I explained in earlier
>>>>communications,
>>>>third
>>>> party teams depend on them and I think we may be loosing their
>>>> cooperation and contributions if we don't deliver soon.
>>>
>>>Yep, totally understand about that. Rest assured the stability of the
>>>Jenkins and buildbot
>>>builds is a priority.
>>>
>>>Gav...
>>>
>>>>
>>>> EdB
>>>>
>>>>
>>>>
>>>> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com> wrote:
>>>> > We just pushed changes to put all the pixel bender stuff in its own
>>>> > upstream package that won't be built by Jenkins (because it rarely
>>>> > changes). Theoretically, this eliminates the need for the Flex
>>>>build
>>>> > to need a window. We'll see how the next builds come out.
>>>> >
>>>> > Thank you for trying to fix this. Creating the upstream package
>>>>isn't
>>>> > just a workaround for this issue, it also gives us a more consistent
>>>> > build experience for our Linux users as the PixelBender compiler
>>>>does
>>>> > not work on Linux.
>>>> >
>>>> > Hopefully the builds will start to work now, but I won't be
>>>>surprised
>>>> > if there is some other issue waiting to be discovered.
>>>> >
>>>> > Thanks,
>>>> > -Alex
>>>> >
>>>> > On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>>> wrote:
>>>> >
>>>> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au>
>>>> wrote:
>>>> >>>
>>>> >>> So, the slave is configured for Œweb start¹ via JNLP and that is
>>>>how
>>>> >>> it
>>>> >>is currently connected.
>>>> >>>
>>>> >>> The Œservice¹ was also running (which JNLP can control too) so I
>>>> >>> turned
>>>> >>that off and set it to
>>>> >>>
>>>> >>> Œmaunal¹ start only.
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> There are 3 builds running. I¹ll reboot the server at an
>>>>appropriate
>>>> >>interval within the next hour or
>>>> >>>
>>>> >>> so and we¹ll try again.
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> GavŠ
>>>> >>>
>>>> >>
>>>> >>Okay, can you please let me know when you start it again?
>>>> >>
>>>> >>Thanks,
>>>> >>Om
>>>> >>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>>> >>>OmPrakash
>>>> >>Muppirala
>>>> >>> Sent: Thursday, 12 December 2013 7:15 PM
>>>> >>> To: builds@apache.org; Gavin McDonald
>>>> >>> Cc: Erik de Bruin
>>>> >>>
>>>> >>> Subject: Re: [windows1] Pixelbender installation
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> Hi Gav,
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> Any updates on this issue?
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> Thanks,
>>>> >>>
>>>> >>> Om
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
>>>> >>><bi...@gmail.com>
>>>> >>wrote:
>>>> >>>>
>>>> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>>>> >>>><ga...@16degrees.com.au>
>>>> >>wrote:
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> > -----Original Message-----
>>>> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf
>>>> Of
>>>> >>>>> > OmPrakash Muppirala
>>>> >>>>>
>>>> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>>>> >>>>> > To: Gavin McDonald
>>>> >>>>> > Cc: builds@apache.org; Erik de Bruin
>>>> >>>>> > Subject: Re: [windows1] Pixelbender installation
>>>> >>>>> >
>>>> >>>>>
>>>> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>>>> >>>>> > <bi...@gmail.com>wrote:
>>>> >>>>> >
>>>> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>>>> >>>>> > <ga...@16degrees.com.au>wrote:
>>>> >>>>> > >
>>>> >>>>> > >> Interesting, and puzzling why, but interactive desktop flag
>>>> >>>>> > >> was turned off.
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> I've now re-enabled it, please try again.
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>>
>>>> >>>>> > >> Gav.
>>>> >>>>>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > > Great! I have kicked off a build. Will report back in a
>>>>bit.
>>>> >>>>> > >
>>>> >>>>> > > Was the windows1 slave started via JNLP or as a windows
>>>>service?
>>>> >>>>> > > Starting via JNLP (using webstart) ensures that the
>>>> >>>>> > > interactive
>>>> >>flag is
>>>> >>>>> set.
>>>> >>>>> > > Whereas if it is modified to be started as a service, you
>>>>will
>>>> >>>>>have
>>>> >>to
>>>> >>>>> > > manually turn the interactive flag (which sometimes may not
>>>> >>propagate
>>>> >>>>> > > all the way down the process we try to invoke)
>>>> >>>>> > >
>>>> >>>>> > > If this does not work, will you be able to restart the slave
>>>> >>>>> > > via
>>>> >>JNLP?
>>>> >>>>> > >
>>>> >>>>> > > Thanks,
>>>> >>>>> > > Om
>>>> >>>>> > >
>>>> >>>>> >
>>>> >>>>> > Yes, the build failed as I was typing my previous response.
>>>> >>>>> >
>>>> >>>>> > Any chance you could restart the windows1 Jenkins instance as
>>>> >>>>> > just a
>>>> >>JNLP
>>>> >>>>> > slave agent instead of modifying it into windows webservice?
>>>>[1]
>>>> >>>>>
>>>> >>>>> I could, but I don't understand, this Jenkins slave has been
>>>> >>>>>running as
>>>> >>a
>>>> >>>>> service since the day
>>>> >>>>> I built it years ago.
>>>> >>>>>
>>>> >>>>> Gav...
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> I don't understand too, but doing this in our test environment
>>>> >>>>fixed the
>>>> >>problem, whereas manually setting the interactive flag did not. As
>>>> >>you mentioned earlier, something somewhere reset the interactive
>>>>flag
>>>> >>on the root process. Unless you want to dig deeper and figure out
>>>> >>what happened, I think that restarting it to run as a JNLP slave
>>>>agent
>>>> >>should fix the problem (as per Jenkins' docs) .
>>>> >>>>
>>>> >>>> Do you have any other ideas on how to fix this?
>>>> >>>>
>>>> >>>> Thanks,
>>>> >>>> Om
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> >
>>>> >>>>> > Thanks,
>>>> >>>>> > Om
>>>> >>>>> >
>>>> >>>>> > [1]
>>>> >>>>> > https://wiki.jenkins-
>>>> >>>>> >
>>>>
>>>>>>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#Instal
>>>>>>l
>>>> >>ingJ
>>>> >>>>> > enkinsasaWindowsservice-
>>>> >>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>>>> >>>>>
>>>> >>>>> >
>>>> >>>>> >
>>>> >>>>> >
>>>> >>>>> > >
>>>> >>>>> > >
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>>>> >>>>> > >> Behalf
>>>> >>>>> > Of
>>>> >>>>> > >> *OmPrakash Muppirala
>>>> >>>>>
>>>> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>>>> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
>>>> >>>>> > >> *Cc:* Erik de Bruin
>>>> >>>>>
>>>> >>>>> > >>
>>>> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>>
>>>> >>>>> > >> Thanks Gav!
>>>> >>>>> > >>
>>>> >>>>> > >> We did a bunch of tests to repro this issue on our side.
>>>>One
>>>> >>>>> > >> way
>>>> >>we
>>>> >>>>> > >> could reproduce this on our Jenkins installation was that
>>>>if
>>>> >>>>> > >> we
>>>> >>>>>ran
>>>> >>>>> > >> the job as a service, we are getting the same error
>>>>messages
>>>> >>>>> > >> (AIF Internal exception).
>>>> >>>>> > >>
>>>> >>>>> > >> Jenkins docs says that for jobs that require Desktop Access
>>>> >>>>>(which
>>>> >>>>> > >> Pixel Bender does), the root service process that is
>>>>running
>>>> >>>>> > >> the
>>>> >>job
>>>> >>>>> > >> needs to have the 'interactive flag' enabled in the Windows
>>>> >>>>>Service
>>>> >>>>> > >> Manager. [1]
>>>> >>>>> > >>
>>>> >>>>> > >> One way this setting could have changed is if the way the
>>>> >>>>> > >> windows slave starts was modified.
>>>> >>>>> > >>
>>>> >>>>> > >> Can you please take a look under the hood and see if you
>>>>find
>>>> >>>>> > >> something amiss?
>>>> >>>>> > >>
>>>> >>>>> > >> Thanks,
>>>> >>>>> > >> Om
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> [1]
>>>> >>>>> > >> https://wiki.jenkins-
>>>> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>>>> >>>>> > >> computer+but+not+on+Jenkins
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>>>> >>>>> > >> <ga...@16degrees.com.au>
>>>> >>>>> > >> wrote:
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> > -----Original Message-----
>>>> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>> >>>>> > >>
>>>> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>>>> >>>>> > >> > To: builds@apache.org
>>>> >>>>> > >> > Cc: Gavin McDonald
>>>> >>>>> > >>
>>>> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
>>>> >>>>> > >> >
>>>> >>>>> > >> > 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...
>>>> >>>>> > >>
>>>> >>>>> > >>
>>>> >>>>> > >> >
>>>> >>>>> > >> > EdB
>>>> >>>>> > >> >
>>>> >>>>> > >> >
>>>> >>>>> > >> >
>>>> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>>>> >>>>> > >> > <bi...@gmail.com> wrote:
>>>> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>>>> >>>>> > >> > <ga...@16degrees.com.au>wrote:
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get
>>>> >>>>> > >> > >> across
>>>> >>>>>is
>>>> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is
>>>>it
>>>> >>>>> > >> > >> very slightly possible that the build is failing due
>>>>to
>>>> >>>>> > >> > >> a coding error? In other words, I've been blamed
>>>>several
>>>> >>>>> > >> > >> times now
>>>> >>>>>for
>>>> >>>>> > >> > >> breaking the build when I haven't been anywhere near
>>>>the
>>>> >>machine
>>>> >>>>> > in question.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > > The build does not fail on my or other committers'
>>>>machines.
>>>> >> It
>>>> >>>>> > >> > > must be something specific to whats happening in
>>>>Windows1.
>>>> >> Sorry
>>>> >>>>> > >> > > if it sounds like we are blaming you. We are just
>>>>trying
>>>> >>>>> > >> > > to troubleshoot and are running blind here.
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Either way I'll look.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >
>>>> >>>>> > >> > > Thanks!
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> And so that we are clear, windows1 is not going away,
>>>>it
>>>> >>>>> > >> > >> is
>>>> >>very
>>>> >>>>> > >> > >> heavily used, folks are always complaining it is down,
>>>> >>>>> > >> > >> so
>>>> >>>>>I'm
>>>> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
>>>> >>>>>slave.
>>>> >>>>> > >> > >> Point is, you need to be configured to use both slaves
>>>> >>>>> > >> > >> for
>>>> >>>>>it
>>>> >>to
>>>> >>>>> > >> > >> work, or my time
>>>> >>>>> > >> > building a 2ndmachine is wasted and you'll continue to
>>>> >>>>> > >> > complain about
>>>> >>>>> > >> the
>>>> >>>>> > >> 1
>>>> >>>>> > >> > st windows box being overloaded all the time.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >
>>>> >>>>> > >> > > We welcome the addition of a new windows slave, no
>>>>doubt.
>>>> >> Which
>>>> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise it
>>>>will
>>>> >>>>> > >> > > lead
>>>> >>to
>>>> >>>>> > >> > > more variables to troubleshoot.
>>>> >>>>> > >> > >
>>>> >>>>> > >> > > On that note, perhaps you can image windows1 and create
>>>> >>windows2
>>>> >>>>> > >> > > as a clone of it?
>>>> >>>>> > >> > >
>>>> >>>>> > >> > > Regards,
>>>> >>>>> > >> > > Om
>>>> >>>>> > >> > >
>>>> >>>>> > >> > >
>>>> >>>>> > >>
>>>> >>>>> > >> > >> Gav.
>>>> >>>>> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> *From:* omuppi1@gmail.com
>>>> [mailto:omuppi1@gmail.com] *On
>>>> >>>>> > Behalf
>>>> >>>>> > >> > Of
>>>> >>>>> > >> > >> *OmPrakash Muppirala
>>>> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>>>> >>>>> > >> > >> *To:* builds@apache.org
>>>> >>>>> > >> > >> *Cc:* Gavin McDonald
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Gavin,
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long
>>>> >>>>> > >> > >> running
>>>> >>job
>>>> >>>>> > >> > >> on
>>>> >>>>> > >> > >> Windows1 has started failing for the past few days.
>>>>Can
>>>> >>>>> > >> > >> we first fix that before we start working on Windows2?
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Thanks,
>>>> >>>>> > >> > >> Om
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>>>> >>>>> > >> > >> <er...@ixsoftware.nl>
>>>> >>>>> > >> > wrote:
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Ok, from the top of this thread:
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender'
>>>>task:
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> The build assumes Pixelbender is installed at:
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
>>>> (x86)/Adobe/Adobe
>>>> >>>>> > >> > >> Utilities\ -
>>>> >>>>> > >> > \
>>>> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Is that still the correct path and does the
>>>>application
>>>> >>>>>start
>>>> >>>>> > >> > >> without errors when you launch it manually?"
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> In another email in this thread I've listed the
>>>>software
>>>> >>>>>that
>>>> >>>>> > >> > >> needs to be on windows2.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Is there a way to have all our builds run on either
>>>> >>>>> > >> > >> windows1
>>>> >>OR
>>>> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
>>>> >>>>> > >> > >> workspaces
>>>> >>of
>>>> >>>>> > >> > >> some of our other builds, in order to save on disk
>>>>space
>>>> >>>>> > >> > >> and
>>>> >>build
>>>> >>>>> > time.
>>>> >>>>> > >> > >> If we remove these dependencies, we'd basically be
>>>> >>>>> > >> > >> forced to copy each build into each other build.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Since it is the weekend, I'll have limited time to
>>>>work
>>>> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
>>>> >>>>> > >> > >> check/test/adjust whatever needs
>>>> checking/testing/adjusting.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> Please keep in mind that we are at a very important
>>>> >>>>>milestone
>>>> >>>>> > >> > >> for our project, and with third party teams relying on
>>>> >>>>> > >> > >> our nightly builds, we'd greatly appreciate a
>>>>successful
>>>> >>>>> > >> > >> run of
>>>> >>all
>>>> >>>>> > >> > >> our jobs, on whatever slave works.
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >>
>>>> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Alex Harui <ah...@adobe.com>.
It occurred to me that the tests are also going to want a window so if
we're having issues with that, it could have causes the tests to hang
waiting for them to even run.
I've removed the test target and started a new build. But we'll see if it
can delete those jars or not.
-Alex
On 12/14/13 7:12 AM, "Alex Harui" <ah...@adobe.com> wrote:
>Hi Gavin,
>
>Looks like build are running. Jenkins says that a flex-sdk build was
>running, compiled cleanly but timed out after an hour while running tests,
>and then the next flex-sdk build failed because it couldn't delete some
>jars.
>
>I'm wondering if the job that was running tests somehow locked those jars?
> Can you delete those jars manually (or tell me how to; I'm a newbie at
>Jenkins? Also, can you confirm that the server was not rebuilt. Our
>build will fail and get stuck running tests if the FlashPlayer "trust"
>files are not set up properly which I believe is a manual step on a fresh
>setup.
>
>Thanks,
>-Alex
>
>On 12/14/13 2:05 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>
>>
>>
>>> -----Original Message-----
>>> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>> Sent: Saturday, 14 December 2013 6:00 PM
>>> To: Alex Harui
>>> Cc: builds@apache.org; gavin@16degrees.com.au
>>> Subject: Re: [windows1] Pixelbender installation
>>>
>>> Gavin, please, please, pretty please, can you have a look at the
>>>'windows1'
>>> situation? Please?
>>>
>>> Or, if you don't have time - which I would totally understand and
>>>respect -
>>> please tell us so one of the other 8 admins on the 'windows1' slave can
>>>step
>>> in.
>>>
>>> Our project needs the builds, as I explained in earlier communications,
>>>third
>>> party teams depend on them and I think we may be loosing their
>>> cooperation and contributions if we don't deliver soon.
>>
>>Yep, totally understand about that. Rest assured the stability of the
>>Jenkins and buildbot
>>builds is a priority.
>>
>>Gav...
>>
>>>
>>> EdB
>>>
>>>
>>>
>>> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com> wrote:
>>> > We just pushed changes to put all the pixel bender stuff in its own
>>> > upstream package that won't be built by Jenkins (because it rarely
>>> > changes). Theoretically, this eliminates the need for the Flex build
>>> > to need a window. We'll see how the next builds come out.
>>> >
>>> > Thank you for trying to fix this. Creating the upstream package
>>>isn't
>>> > just a workaround for this issue, it also gives us a more consistent
>>> > build experience for our Linux users as the PixelBender compiler does
>>> > not work on Linux.
>>> >
>>> > Hopefully the builds will start to work now, but I won't be surprised
>>> > if there is some other issue waiting to be discovered.
>>> >
>>> > Thanks,
>>> > -Alex
>>> >
>>> > On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>>> wrote:
>>> >
>>> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au>
>>> wrote:
>>> >>>
>>> >>> So, the slave is configured for Œweb start¹ via JNLP and that is
>>>how
>>> >>> it
>>> >>is currently connected.
>>> >>>
>>> >>> The Œservice¹ was also running (which JNLP can control too) so I
>>> >>> turned
>>> >>that off and set it to
>>> >>>
>>> >>> Œmaunal¹ start only.
>>> >>>
>>> >>>
>>> >>>
>>> >>> There are 3 builds running. I¹ll reboot the server at an
>>>appropriate
>>> >>interval within the next hour or
>>> >>>
>>> >>> so and we¹ll try again.
>>> >>>
>>> >>>
>>> >>>
>>> >>> GavŠ
>>> >>>
>>> >>
>>> >>Okay, can you please let me know when you start it again?
>>> >>
>>> >>Thanks,
>>> >>Om
>>> >>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>> >>>OmPrakash
>>> >>Muppirala
>>> >>> Sent: Thursday, 12 December 2013 7:15 PM
>>> >>> To: builds@apache.org; Gavin McDonald
>>> >>> Cc: Erik de Bruin
>>> >>>
>>> >>> Subject: Re: [windows1] Pixelbender installation
>>> >>>
>>> >>>
>>> >>>
>>> >>> Hi Gav,
>>> >>>
>>> >>>
>>> >>>
>>> >>> Any updates on this issue?
>>> >>>
>>> >>>
>>> >>>
>>> >>> Thanks,
>>> >>>
>>> >>> Om
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
>>> >>><bi...@gmail.com>
>>> >>wrote:
>>> >>>>
>>> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>>> >>>><ga...@16degrees.com.au>
>>> >>wrote:
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> > -----Original Message-----
>>> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf
>>> Of
>>> >>>>> > OmPrakash Muppirala
>>> >>>>>
>>> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>>> >>>>> > To: Gavin McDonald
>>> >>>>> > Cc: builds@apache.org; Erik de Bruin
>>> >>>>> > Subject: Re: [windows1] Pixelbender installation
>>> >>>>> >
>>> >>>>>
>>> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>>> >>>>> > <bi...@gmail.com>wrote:
>>> >>>>> >
>>> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>>> >>>>> > <ga...@16degrees.com.au>wrote:
>>> >>>>> > >
>>> >>>>> > >> Interesting, and puzzling why, but interactive desktop flag
>>> >>>>> > >> was turned off.
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> I've now re-enabled it, please try again.
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>>
>>> >>>>> > >> Gav.
>>> >>>>>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > > Great! I have kicked off a build. Will report back in a
>>>bit.
>>> >>>>> > >
>>> >>>>> > > Was the windows1 slave started via JNLP or as a windows
>>>service?
>>> >>>>> > > Starting via JNLP (using webstart) ensures that the
>>> >>>>> > > interactive
>>> >>flag is
>>> >>>>> set.
>>> >>>>> > > Whereas if it is modified to be started as a service, you
>>>will
>>> >>>>>have
>>> >>to
>>> >>>>> > > manually turn the interactive flag (which sometimes may not
>>> >>propagate
>>> >>>>> > > all the way down the process we try to invoke)
>>> >>>>> > >
>>> >>>>> > > If this does not work, will you be able to restart the slave
>>> >>>>> > > via
>>> >>JNLP?
>>> >>>>> > >
>>> >>>>> > > Thanks,
>>> >>>>> > > Om
>>> >>>>> > >
>>> >>>>> >
>>> >>>>> > Yes, the build failed as I was typing my previous response.
>>> >>>>> >
>>> >>>>> > Any chance you could restart the windows1 Jenkins instance as
>>> >>>>> > just a
>>> >>JNLP
>>> >>>>> > slave agent instead of modifying it into windows webservice?
>>>[1]
>>> >>>>>
>>> >>>>> I could, but I don't understand, this Jenkins slave has been
>>> >>>>>running as
>>> >>a
>>> >>>>> service since the day
>>> >>>>> I built it years ago.
>>> >>>>>
>>> >>>>> Gav...
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> I don't understand too, but doing this in our test environment
>>> >>>>fixed the
>>> >>problem, whereas manually setting the interactive flag did not. As
>>> >>you mentioned earlier, something somewhere reset the interactive flag
>>> >>on the root process. Unless you want to dig deeper and figure out
>>> >>what happened, I think that restarting it to run as a JNLP slave
>>>agent
>>> >>should fix the problem (as per Jenkins' docs) .
>>> >>>>
>>> >>>> Do you have any other ideas on how to fix this?
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Om
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> >
>>> >>>>> > Thanks,
>>> >>>>> > Om
>>> >>>>> >
>>> >>>>> > [1]
>>> >>>>> > https://wiki.jenkins-
>>> >>>>> >
>>>
>>>>>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#Install
>>> >>ingJ
>>> >>>>> > enkinsasaWindowsservice-
>>> >>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>>> >>>>>
>>> >>>>> >
>>> >>>>> >
>>> >>>>> >
>>> >>>>> > >
>>> >>>>> > >
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>>> >>>>> > >> Behalf
>>> >>>>> > Of
>>> >>>>> > >> *OmPrakash Muppirala
>>> >>>>>
>>> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>>> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
>>> >>>>> > >> *Cc:* Erik de Bruin
>>> >>>>>
>>> >>>>> > >>
>>> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>>
>>> >>>>> > >> Thanks Gav!
>>> >>>>> > >>
>>> >>>>> > >> We did a bunch of tests to repro this issue on our side.
>>>One
>>> >>>>> > >> way
>>> >>we
>>> >>>>> > >> could reproduce this on our Jenkins installation was that if
>>> >>>>> > >> we
>>> >>>>>ran
>>> >>>>> > >> the job as a service, we are getting the same error messages
>>> >>>>> > >> (AIF Internal exception).
>>> >>>>> > >>
>>> >>>>> > >> Jenkins docs says that for jobs that require Desktop Access
>>> >>>>>(which
>>> >>>>> > >> Pixel Bender does), the root service process that is running
>>> >>>>> > >> the
>>> >>job
>>> >>>>> > >> needs to have the 'interactive flag' enabled in the Windows
>>> >>>>>Service
>>> >>>>> > >> Manager. [1]
>>> >>>>> > >>
>>> >>>>> > >> One way this setting could have changed is if the way the
>>> >>>>> > >> windows slave starts was modified.
>>> >>>>> > >>
>>> >>>>> > >> Can you please take a look under the hood and see if you
>>>find
>>> >>>>> > >> something amiss?
>>> >>>>> > >>
>>> >>>>> > >> Thanks,
>>> >>>>> > >> Om
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> [1]
>>> >>>>> > >> https://wiki.jenkins-
>>> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>>> >>>>> > >> computer+but+not+on+Jenkins
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>>> >>>>> > >> <ga...@16degrees.com.au>
>>> >>>>> > >> wrote:
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> > -----Original Message-----
>>> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>> >>>>> > >>
>>> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>>> >>>>> > >> > To: builds@apache.org
>>> >>>>> > >> > Cc: Gavin McDonald
>>> >>>>> > >>
>>> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
>>> >>>>> > >> >
>>> >>>>> > >> > 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...
>>> >>>>> > >>
>>> >>>>> > >>
>>> >>>>> > >> >
>>> >>>>> > >> > EdB
>>> >>>>> > >> >
>>> >>>>> > >> >
>>> >>>>> > >> >
>>> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>>> >>>>> > >> > <bi...@gmail.com> wrote:
>>> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>>> >>>>> > >> > <ga...@16degrees.com.au>wrote:
>>> >>>>> > >> > >
>>> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get
>>> >>>>> > >> > >> across
>>> >>>>>is
>>> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it
>>> >>>>> > >> > >> very slightly possible that the build is failing due to
>>> >>>>> > >> > >> a coding error? In other words, I've been blamed
>>>several
>>> >>>>> > >> > >> times now
>>> >>>>>for
>>> >>>>> > >> > >> breaking the build when I haven't been anywhere near
>>>the
>>> >>machine
>>> >>>>> > in question.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > > The build does not fail on my or other committers'
>>>machines.
>>> >> It
>>> >>>>> > >> > > must be something specific to whats happening in
>>>Windows1.
>>> >> Sorry
>>> >>>>> > >> > > if it sounds like we are blaming you. We are just
>>>trying
>>> >>>>> > >> > > to troubleshoot and are running blind here.
>>> >>>>> > >> > >
>>> >>>>> > >> > >
>>> >>>>> > >> > >
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Either way I'll look.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >
>>> >>>>> > >> > > Thanks!
>>> >>>>> > >> > >
>>> >>>>> > >> > >
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> And so that we are clear, windows1 is not going away,
>>>it
>>> >>>>> > >> > >> is
>>> >>very
>>> >>>>> > >> > >> heavily used, folks are always complaining it is down,
>>> >>>>> > >> > >> so
>>> >>>>>I'm
>>> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
>>> >>>>>slave.
>>> >>>>> > >> > >> Point is, you need to be configured to use both slaves
>>> >>>>> > >> > >> for
>>> >>>>>it
>>> >>to
>>> >>>>> > >> > >> work, or my time
>>> >>>>> > >> > building a 2ndmachine is wasted and you'll continue to
>>> >>>>> > >> > complain about
>>> >>>>> > >> the
>>> >>>>> > >> 1
>>> >>>>> > >> > st windows box being overloaded all the time.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >
>>> >>>>> > >> > > We welcome the addition of a new windows slave, no
>>>doubt.
>>> >> Which
>>> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise it will
>>> >>>>> > >> > > lead
>>> >>to
>>> >>>>> > >> > > more variables to troubleshoot.
>>> >>>>> > >> > >
>>> >>>>> > >> > > On that note, perhaps you can image windows1 and create
>>> >>windows2
>>> >>>>> > >> > > as a clone of it?
>>> >>>>> > >> > >
>>> >>>>> > >> > > Regards,
>>> >>>>> > >> > > Om
>>> >>>>> > >> > >
>>> >>>>> > >> > >
>>> >>>>> > >>
>>> >>>>> > >> > >> Gav.
>>> >>>>> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> *From:* omuppi1@gmail.com
>>> [mailto:omuppi1@gmail.com] *On
>>> >>>>> > Behalf
>>> >>>>> > >> > Of
>>> >>>>> > >> > >> *OmPrakash Muppirala
>>> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>>> >>>>> > >> > >> *To:* builds@apache.org
>>> >>>>> > >> > >> *Cc:* Gavin McDonald
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Gavin,
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long
>>> >>>>> > >> > >> running
>>> >>job
>>> >>>>> > >> > >> on
>>> >>>>> > >> > >> Windows1 has started failing for the past few days.
>>>Can
>>> >>>>> > >> > >> we first fix that before we start working on Windows2?
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Thanks,
>>> >>>>> > >> > >> Om
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>>> >>>>> > >> > >> <er...@ixsoftware.nl>
>>> >>>>> > >> > wrote:
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Ok, from the top of this thread:
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender'
>>>task:
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> The build assumes Pixelbender is installed at:
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
>>> (x86)/Adobe/Adobe
>>> >>>>> > >> > >> Utilities\ -
>>> >>>>> > >> > \
>>> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Is that still the correct path and does the application
>>> >>>>>start
>>> >>>>> > >> > >> without errors when you launch it manually?"
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> In another email in this thread I've listed the
>>>software
>>> >>>>>that
>>> >>>>> > >> > >> needs to be on windows2.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Is there a way to have all our builds run on either
>>> >>>>> > >> > >> windows1
>>> >>OR
>>> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
>>> >>>>> > >> > >> workspaces
>>> >>of
>>> >>>>> > >> > >> some of our other builds, in order to save on disk
>>>space
>>> >>>>> > >> > >> and
>>> >>build
>>> >>>>> > time.
>>> >>>>> > >> > >> If we remove these dependencies, we'd basically be
>>> >>>>> > >> > >> forced to copy each build into each other build.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Since it is the weekend, I'll have limited time to work
>>> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
>>> >>>>> > >> > >> check/test/adjust whatever needs
>>> checking/testing/adjusting.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> Please keep in mind that we are at a very important
>>> >>>>>milestone
>>> >>>>> > >> > >> for our project, and with third party teams relying on
>>> >>>>> > >> > >> our nightly builds, we'd greatly appreciate a
>>>successful
>>> >>>>> > >> > >> run of
>>> >>all
>>> >>>>> > >> > >> our jobs, on whatever slave works.
>>> >>>>> > >> > >>
>>> >>>>> > >> > >>
>>> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Alex Harui <ah...@adobe.com>.
Hi Gavin,
Looks like build are running. Jenkins says that a flex-sdk build was
running, compiled cleanly but timed out after an hour while running tests,
and then the next flex-sdk build failed because it couldn't delete some
jars.
I'm wondering if the job that was running tests somehow locked those jars?
Can you delete those jars manually (or tell me how to; I'm a newbie at
Jenkins? Also, can you confirm that the server was not rebuilt. Our
build will fail and get stuck running tests if the FlashPlayer "trust"
files are not set up properly which I believe is a manual step on a fresh
setup.
Thanks,
-Alex
On 12/14/13 2:05 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>
>
>> -----Original Message-----
>> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>> Sent: Saturday, 14 December 2013 6:00 PM
>> To: Alex Harui
>> Cc: builds@apache.org; gavin@16degrees.com.au
>> Subject: Re: [windows1] Pixelbender installation
>>
>> Gavin, please, please, pretty please, can you have a look at the
>>'windows1'
>> situation? Please?
>>
>> Or, if you don't have time - which I would totally understand and
>>respect -
>> please tell us so one of the other 8 admins on the 'windows1' slave can
>>step
>> in.
>>
>> Our project needs the builds, as I explained in earlier communications,
>>third
>> party teams depend on them and I think we may be loosing their
>> cooperation and contributions if we don't deliver soon.
>
>Yep, totally understand about that. Rest assured the stability of the
>Jenkins and buildbot
>builds is a priority.
>
>Gav...
>
>>
>> EdB
>>
>>
>>
>> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com> wrote:
>> > We just pushed changes to put all the pixel bender stuff in its own
>> > upstream package that won't be built by Jenkins (because it rarely
>> > changes). Theoretically, this eliminates the need for the Flex build
>> > to need a window. We'll see how the next builds come out.
>> >
>> > Thank you for trying to fix this. Creating the upstream package isn't
>> > just a workaround for this issue, it also gives us a more consistent
>> > build experience for our Linux users as the PixelBender compiler does
>> > not work on Linux.
>> >
>> > Hopefully the builds will start to work now, but I won't be surprised
>> > if there is some other issue waiting to be discovered.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com>
>> wrote:
>> >
>> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au>
>> wrote:
>> >>>
>> >>> So, the slave is configured for Œweb start¹ via JNLP and that is how
>> >>> it
>> >>is currently connected.
>> >>>
>> >>> The Œservice¹ was also running (which JNLP can control too) so I
>> >>> turned
>> >>that off and set it to
>> >>>
>> >>> Œmaunal¹ start only.
>> >>>
>> >>>
>> >>>
>> >>> There are 3 builds running. I¹ll reboot the server at an appropriate
>> >>interval within the next hour or
>> >>>
>> >>> so and we¹ll try again.
>> >>>
>> >>>
>> >>>
>> >>> GavŠ
>> >>>
>> >>
>> >>Okay, can you please let me know when you start it again?
>> >>
>> >>Thanks,
>> >>Om
>> >>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>> >>>OmPrakash
>> >>Muppirala
>> >>> Sent: Thursday, 12 December 2013 7:15 PM
>> >>> To: builds@apache.org; Gavin McDonald
>> >>> Cc: Erik de Bruin
>> >>>
>> >>> Subject: Re: [windows1] Pixelbender installation
>> >>>
>> >>>
>> >>>
>> >>> Hi Gav,
>> >>>
>> >>>
>> >>>
>> >>> Any updates on this issue?
>> >>>
>> >>>
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Om
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
>> >>><bi...@gmail.com>
>> >>wrote:
>> >>>>
>> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>> >>>><ga...@16degrees.com.au>
>> >>wrote:
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> > -----Original Message-----
>> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf
>> Of
>> >>>>> > OmPrakash Muppirala
>> >>>>>
>> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>> >>>>> > To: Gavin McDonald
>> >>>>> > Cc: builds@apache.org; Erik de Bruin
>> >>>>> > Subject: Re: [windows1] Pixelbender installation
>> >>>>> >
>> >>>>>
>> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>> >>>>> > <bi...@gmail.com>wrote:
>> >>>>> >
>> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>> >>>>> > <ga...@16degrees.com.au>wrote:
>> >>>>> > >
>> >>>>> > >> Interesting, and puzzling why, but interactive desktop flag
>> >>>>> > >> was turned off.
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> I've now re-enabled it, please try again.
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>>
>> >>>>> > >> Gav.
>> >>>>>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > > Great! I have kicked off a build. Will report back in a bit.
>> >>>>> > >
>> >>>>> > > Was the windows1 slave started via JNLP or as a windows
>>service?
>> >>>>> > > Starting via JNLP (using webstart) ensures that the
>> >>>>> > > interactive
>> >>flag is
>> >>>>> set.
>> >>>>> > > Whereas if it is modified to be started as a service, you will
>> >>>>>have
>> >>to
>> >>>>> > > manually turn the interactive flag (which sometimes may not
>> >>propagate
>> >>>>> > > all the way down the process we try to invoke)
>> >>>>> > >
>> >>>>> > > If this does not work, will you be able to restart the slave
>> >>>>> > > via
>> >>JNLP?
>> >>>>> > >
>> >>>>> > > Thanks,
>> >>>>> > > Om
>> >>>>> > >
>> >>>>> >
>> >>>>> > Yes, the build failed as I was typing my previous response.
>> >>>>> >
>> >>>>> > Any chance you could restart the windows1 Jenkins instance as
>> >>>>> > just a
>> >>JNLP
>> >>>>> > slave agent instead of modifying it into windows webservice? [1]
>> >>>>>
>> >>>>> I could, but I don't understand, this Jenkins slave has been
>> >>>>>running as
>> >>a
>> >>>>> service since the day
>> >>>>> I built it years ago.
>> >>>>>
>> >>>>> Gav...
>> >>>>
>> >>>>
>> >>>>
>> >>>> I don't understand too, but doing this in our test environment
>> >>>>fixed the
>> >>problem, whereas manually setting the interactive flag did not. As
>> >>you mentioned earlier, something somewhere reset the interactive flag
>> >>on the root process. Unless you want to dig deeper and figure out
>> >>what happened, I think that restarting it to run as a JNLP slave agent
>> >>should fix the problem (as per Jenkins' docs) .
>> >>>>
>> >>>> Do you have any other ideas on how to fix this?
>> >>>>
>> >>>> Thanks,
>> >>>> Om
>> >>>>
>> >>>>
>> >>>>
>> >>>>>
>> >>>>>
>> >>>>> >
>> >>>>> > Thanks,
>> >>>>> > Om
>> >>>>> >
>> >>>>> > [1]
>> >>>>> > https://wiki.jenkins-
>> >>>>> >
>> >>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#Install
>> >>ingJ
>> >>>>> > enkinsasaWindowsservice-
>> >>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>> >>>>>
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> > >
>> >>>>> > >
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>> >>>>> > >> Behalf
>> >>>>> > Of
>> >>>>> > >> *OmPrakash Muppirala
>> >>>>>
>> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
>> >>>>> > >> *Cc:* Erik de Bruin
>> >>>>>
>> >>>>> > >>
>> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>>
>> >>>>> > >> Thanks Gav!
>> >>>>> > >>
>> >>>>> > >> We did a bunch of tests to repro this issue on our side. One
>> >>>>> > >> way
>> >>we
>> >>>>> > >> could reproduce this on our Jenkins installation was that if
>> >>>>> > >> we
>> >>>>>ran
>> >>>>> > >> the job as a service, we are getting the same error messages
>> >>>>> > >> (AIF Internal exception).
>> >>>>> > >>
>> >>>>> > >> Jenkins docs says that for jobs that require Desktop Access
>> >>>>>(which
>> >>>>> > >> Pixel Bender does), the root service process that is running
>> >>>>> > >> the
>> >>job
>> >>>>> > >> needs to have the 'interactive flag' enabled in the Windows
>> >>>>>Service
>> >>>>> > >> Manager. [1]
>> >>>>> > >>
>> >>>>> > >> One way this setting could have changed is if the way the
>> >>>>> > >> windows slave starts was modified.
>> >>>>> > >>
>> >>>>> > >> Can you please take a look under the hood and see if you find
>> >>>>> > >> something amiss?
>> >>>>> > >>
>> >>>>> > >> Thanks,
>> >>>>> > >> Om
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> [1]
>> >>>>> > >> https://wiki.jenkins-
>> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>> >>>>> > >> computer+but+not+on+Jenkins
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>> >>>>> > >> <ga...@16degrees.com.au>
>> >>>>> > >> wrote:
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> > -----Original Message-----
>> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>> >>>>> > >>
>> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>> >>>>> > >> > To: builds@apache.org
>> >>>>> > >> > Cc: Gavin McDonald
>> >>>>> > >>
>> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
>> >>>>> > >> >
>> >>>>> > >> > 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...
>> >>>>> > >>
>> >>>>> > >>
>> >>>>> > >> >
>> >>>>> > >> > EdB
>> >>>>> > >> >
>> >>>>> > >> >
>> >>>>> > >> >
>> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>> >>>>> > >> > <bi...@gmail.com> wrote:
>> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>> >>>>> > >> > <ga...@16degrees.com.au>wrote:
>> >>>>> > >> > >
>> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get
>> >>>>> > >> > >> across
>> >>>>>is
>> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it
>> >>>>> > >> > >> very slightly possible that the build is failing due to
>> >>>>> > >> > >> a coding error? In other words, I've been blamed several
>> >>>>> > >> > >> times now
>> >>>>>for
>> >>>>> > >> > >> breaking the build when I haven't been anywhere near the
>> >>machine
>> >>>>> > in question.
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > > The build does not fail on my or other committers'
>>machines.
>> >> It
>> >>>>> > >> > > must be something specific to whats happening in
>>Windows1.
>> >> Sorry
>> >>>>> > >> > > if it sounds like we are blaming you. We are just trying
>> >>>>> > >> > > to troubleshoot and are running blind here.
>> >>>>> > >> > >
>> >>>>> > >> > >
>> >>>>> > >> > >
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> Either way I'll look.
>> >>>>> > >> > >>
>> >>>>> > >> > >
>> >>>>> > >> > > Thanks!
>> >>>>> > >> > >
>> >>>>> > >> > >
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> And so that we are clear, windows1 is not going away, it
>> >>>>> > >> > >> is
>> >>very
>> >>>>> > >> > >> heavily used, folks are always complaining it is down,
>> >>>>> > >> > >> so
>> >>>>>I'm
>> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
>> >>>>>slave.
>> >>>>> > >> > >> Point is, you need to be configured to use both slaves
>> >>>>> > >> > >> for
>> >>>>>it
>> >>to
>> >>>>> > >> > >> work, or my time
>> >>>>> > >> > building a 2ndmachine is wasted and you'll continue to
>> >>>>> > >> > complain about
>> >>>>> > >> the
>> >>>>> > >> 1
>> >>>>> > >> > st windows box being overloaded all the time.
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >
>> >>>>> > >> > > We welcome the addition of a new windows slave, no doubt.
>> >> Which
>> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise it will
>> >>>>> > >> > > lead
>> >>to
>> >>>>> > >> > > more variables to troubleshoot.
>> >>>>> > >> > >
>> >>>>> > >> > > On that note, perhaps you can image windows1 and create
>> >>windows2
>> >>>>> > >> > > as a clone of it?
>> >>>>> > >> > >
>> >>>>> > >> > > Regards,
>> >>>>> > >> > > Om
>> >>>>> > >> > >
>> >>>>> > >> > >
>> >>>>> > >>
>> >>>>> > >> > >> Gav.
>> >>>>> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> *From:* omuppi1@gmail.com
>> [mailto:omuppi1@gmail.com] *On
>> >>>>> > Behalf
>> >>>>> > >> > Of
>> >>>>> > >> > >> *OmPrakash Muppirala
>> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>> >>>>> > >> > >> *To:* builds@apache.org
>> >>>>> > >> > >> *Cc:* Gavin McDonald
>> >>>>> > >> > >>
>> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> Gavin,
>> >>>>> > >> > >>
>> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long
>> >>>>> > >> > >> running
>> >>job
>> >>>>> > >> > >> on
>> >>>>> > >> > >> Windows1 has started failing for the past few days. Can
>> >>>>> > >> > >> we first fix that before we start working on Windows2?
>> >>>>> > >> > >>
>> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> Thanks,
>> >>>>> > >> > >> Om
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>> >>>>> > >> > >> <er...@ixsoftware.nl>
>> >>>>> > >> > wrote:
>> >>>>> > >> > >>
>> >>>>> > >> > >> Ok, from the top of this thread:
>> >>>>> > >> > >>
>> >>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender'
>>task:
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> The build assumes Pixelbender is installed at:
>> >>>>> > >> > >>
>> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
>> (x86)/Adobe/Adobe
>> >>>>> > >> > >> Utilities\ -
>> >>>>> > >> > \
>> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>> >>>>> > >> > >>
>> >>>>> > >> > >> Is that still the correct path and does the application
>> >>>>>start
>> >>>>> > >> > >> without errors when you launch it manually?"
>> >>>>> > >> > >>
>> >>>>> > >> > >> In another email in this thread I've listed the software
>> >>>>>that
>> >>>>> > >> > >> needs to be on windows2.
>> >>>>> > >> > >>
>> >>>>> > >> > >> Is there a way to have all our builds run on either
>> >>>>> > >> > >> windows1
>> >>OR
>> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
>> >>>>> > >> > >> workspaces
>> >>of
>> >>>>> > >> > >> some of our other builds, in order to save on disk space
>> >>>>> > >> > >> and
>> >>build
>> >>>>> > time.
>> >>>>> > >> > >> If we remove these dependencies, we'd basically be
>> >>>>> > >> > >> forced to copy each build into each other build.
>> >>>>> > >> > >>
>> >>>>> > >> > >> Since it is the weekend, I'll have limited time to work
>> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
>> >>>>> > >> > >> check/test/adjust whatever needs
>> checking/testing/adjusting.
>> >>>>> > >> > >>
>> >>>>> > >> > >> Please keep in mind that we are at a very important
>> >>>>>milestone
>> >>>>> > >> > >> for our project, and with third party teams relying on
>> >>>>> > >> > >> our nightly builds, we'd greatly appreciate a successful
>> >>>>> > >> > >> run of
>> >>all
>> >>>>> > >> > >> our jobs, on whatever slave works.
>> >>>>> > >> > >>
>> >>>>> > >> > >>
>> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> Sent: Saturday, 14 December 2013 6:00 PM
> To: Alex Harui
> Cc: builds@apache.org; gavin@16degrees.com.au
> Subject: Re: [windows1] Pixelbender installation
>
> Gavin, please, please, pretty please, can you have a look at the 'windows1'
> situation? Please?
>
> Or, if you don't have time - which I would totally understand and respect -
> please tell us so one of the other 8 admins on the 'windows1' slave can step
> in.
>
> Our project needs the builds, as I explained in earlier communications, third
> party teams depend on them and I think we may be loosing their
> cooperation and contributions if we don't deliver soon.
Yep, totally understand about that. Rest assured the stability of the Jenkins and buildbot
builds is a priority.
Gav...
>
> EdB
>
>
>
> On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com> wrote:
> > We just pushed changes to put all the pixel bender stuff in its own
> > upstream package that won't be built by Jenkins (because it rarely
> > changes). Theoretically, this eliminates the need for the Flex build
> > to need a window. We'll see how the next builds come out.
> >
> > Thank you for trying to fix this. Creating the upstream package isn't
> > just a workaround for this issue, it also gives us a more consistent
> > build experience for our Linux users as the PixelBender compiler does
> > not work on Linux.
> >
> > Hopefully the builds will start to work now, but I won't be surprised
> > if there is some other issue waiting to be discovered.
> >
> > Thanks,
> > -Alex
> >
> > On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com>
> wrote:
> >
> >>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au>
> wrote:
> >>>
> >>> So, the slave is configured for Œweb start¹ via JNLP and that is how
> >>> it
> >>is currently connected.
> >>>
> >>> The Œservice¹ was also running (which JNLP can control too) so I
> >>> turned
> >>that off and set it to
> >>>
> >>> Œmaunal¹ start only.
> >>>
> >>>
> >>>
> >>> There are 3 builds running. I¹ll reboot the server at an appropriate
> >>interval within the next hour or
> >>>
> >>> so and we¹ll try again.
> >>>
> >>>
> >>>
> >>> GavŠ
> >>>
> >>
> >>Okay, can you please let me know when you start it again?
> >>
> >>Thanks,
> >>Om
> >>
> >>>
> >>>
> >>>
> >>>
> >>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
> >>>OmPrakash
> >>Muppirala
> >>> Sent: Thursday, 12 December 2013 7:15 PM
> >>> To: builds@apache.org; Gavin McDonald
> >>> Cc: Erik de Bruin
> >>>
> >>> Subject: Re: [windows1] Pixelbender installation
> >>>
> >>>
> >>>
> >>> Hi Gav,
> >>>
> >>>
> >>>
> >>> Any updates on this issue?
> >>>
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Om
> >>>
> >>>
> >>>
> >>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
> >>><bi...@gmail.com>
> >>wrote:
> >>>>
> >>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
> >>>><ga...@16degrees.com.au>
> >>wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>> > -----Original Message-----
> >>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf
> Of
> >>>>> > OmPrakash Muppirala
> >>>>>
> >>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
> >>>>> > To: Gavin McDonald
> >>>>> > Cc: builds@apache.org; Erik de Bruin
> >>>>> > Subject: Re: [windows1] Pixelbender installation
> >>>>> >
> >>>>>
> >>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> >>>>> > <bi...@gmail.com>wrote:
> >>>>> >
> >>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> >>>>> > <ga...@16degrees.com.au>wrote:
> >>>>> > >
> >>>>> > >> Interesting, and puzzling why, but interactive desktop flag
> >>>>> > >> was turned off.
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> I've now re-enabled it, please try again.
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>>
> >>>>> > >> Gav.
> >>>>>
> >>>>> > >>
> >>>>> > >>
> >>>>> > > Great! I have kicked off a build. Will report back in a bit.
> >>>>> > >
> >>>>> > > Was the windows1 slave started via JNLP or as a windows service?
> >>>>> > > Starting via JNLP (using webstart) ensures that the
> >>>>> > > interactive
> >>flag is
> >>>>> set.
> >>>>> > > Whereas if it is modified to be started as a service, you will
> >>>>>have
> >>to
> >>>>> > > manually turn the interactive flag (which sometimes may not
> >>propagate
> >>>>> > > all the way down the process we try to invoke)
> >>>>> > >
> >>>>> > > If this does not work, will you be able to restart the slave
> >>>>> > > via
> >>JNLP?
> >>>>> > >
> >>>>> > > Thanks,
> >>>>> > > Om
> >>>>> > >
> >>>>> >
> >>>>> > Yes, the build failed as I was typing my previous response.
> >>>>> >
> >>>>> > Any chance you could restart the windows1 Jenkins instance as
> >>>>> > just a
> >>JNLP
> >>>>> > slave agent instead of modifying it into windows webservice? [1]
> >>>>>
> >>>>> I could, but I don't understand, this Jenkins slave has been
> >>>>>running as
> >>a
> >>>>> service since the day
> >>>>> I built it years ago.
> >>>>>
> >>>>> Gav...
> >>>>
> >>>>
> >>>>
> >>>> I don't understand too, but doing this in our test environment
> >>>>fixed the
> >>problem, whereas manually setting the interactive flag did not. As
> >>you mentioned earlier, something somewhere reset the interactive flag
> >>on the root process. Unless you want to dig deeper and figure out
> >>what happened, I think that restarting it to run as a JNLP slave agent
> >>should fix the problem (as per Jenkins' docs) .
> >>>>
> >>>> Do you have any other ideas on how to fix this?
> >>>>
> >>>> Thanks,
> >>>> Om
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>> >
> >>>>> > Thanks,
> >>>>> > Om
> >>>>> >
> >>>>> > [1]
> >>>>> > https://wiki.jenkins-
> >>>>> >
> >>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#Install
> >>ingJ
> >>>>> > enkinsasaWindowsservice-
> >>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
> >>>>>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > >
> >>>>> > >
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
> >>>>> > >> Behalf
> >>>>> > Of
> >>>>> > >> *OmPrakash Muppirala
> >>>>>
> >>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> >>>>> > >> *To:* builds@apache.org; Gavin McDonald
> >>>>> > >> *Cc:* Erik de Bruin
> >>>>>
> >>>>> > >>
> >>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>>
> >>>>> > >> Thanks Gav!
> >>>>> > >>
> >>>>> > >> We did a bunch of tests to repro this issue on our side. One
> >>>>> > >> way
> >>we
> >>>>> > >> could reproduce this on our Jenkins installation was that if
> >>>>> > >> we
> >>>>>ran
> >>>>> > >> the job as a service, we are getting the same error messages
> >>>>> > >> (AIF Internal exception).
> >>>>> > >>
> >>>>> > >> Jenkins docs says that for jobs that require Desktop Access
> >>>>>(which
> >>>>> > >> Pixel Bender does), the root service process that is running
> >>>>> > >> the
> >>job
> >>>>> > >> needs to have the 'interactive flag' enabled in the Windows
> >>>>>Service
> >>>>> > >> Manager. [1]
> >>>>> > >>
> >>>>> > >> One way this setting could have changed is if the way the
> >>>>> > >> windows slave starts was modified.
> >>>>> > >>
> >>>>> > >> Can you please take a look under the hood and see if you find
> >>>>> > >> something amiss?
> >>>>> > >>
> >>>>> > >> Thanks,
> >>>>> > >> Om
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> [1]
> >>>>> > >> https://wiki.jenkins-
> >>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
> >>>>> > >> computer+but+not+on+Jenkins
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> >>>>> > >> <ga...@16degrees.com.au>
> >>>>> > >> wrote:
> >>>>> > >>
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> > -----Original Message-----
> >>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>>>> > >>
> >>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
> >>>>> > >> > To: builds@apache.org
> >>>>> > >> > Cc: Gavin McDonald
> >>>>> > >>
> >>>>> > >> > Subject: Re: [windows1] Pixelbender installation
> >>>>> > >> >
> >>>>> > >> > 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...
> >>>>> > >>
> >>>>> > >>
> >>>>> > >> >
> >>>>> > >> > EdB
> >>>>> > >> >
> >>>>> > >> >
> >>>>> > >> >
> >>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> >>>>> > >> > <bi...@gmail.com> wrote:
> >>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> >>>>> > >> > <ga...@16degrees.com.au>wrote:
> >>>>> > >> > >
> >>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get
> >>>>> > >> > >> across
> >>>>>is
> >>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it
> >>>>> > >> > >> very slightly possible that the build is failing due to
> >>>>> > >> > >> a coding error? In other words, I've been blamed several
> >>>>> > >> > >> times now
> >>>>>for
> >>>>> > >> > >> breaking the build when I haven't been anywhere near the
> >>machine
> >>>>> > in question.
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > > The build does not fail on my or other committers' machines.
> >> It
> >>>>> > >> > > must be something specific to whats happening in Windows1.
> >> Sorry
> >>>>> > >> > > if it sounds like we are blaming you. We are just trying
> >>>>> > >> > > to troubleshoot and are running blind here.
> >>>>> > >> > >
> >>>>> > >> > >
> >>>>> > >> > >
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> Either way I'll look.
> >>>>> > >> > >>
> >>>>> > >> > >
> >>>>> > >> > > Thanks!
> >>>>> > >> > >
> >>>>> > >> > >
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> And so that we are clear, windows1 is not going away, it
> >>>>> > >> > >> is
> >>very
> >>>>> > >> > >> heavily used, folks are always complaining it is down,
> >>>>> > >> > >> so
> >>>>>I'm
> >>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
> >>>>>slave.
> >>>>> > >> > >> Point is, you need to be configured to use both slaves
> >>>>> > >> > >> for
> >>>>>it
> >>to
> >>>>> > >> > >> work, or my time
> >>>>> > >> > building a 2ndmachine is wasted and you'll continue to
> >>>>> > >> > complain about
> >>>>> > >> the
> >>>>> > >> 1
> >>>>> > >> > st windows box being overloaded all the time.
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >
> >>>>> > >> > > We welcome the addition of a new windows slave, no doubt.
> >> Which
> >>>>> > >> > > is why we want to fix Windows1 first. Otherwise it will
> >>>>> > >> > > lead
> >>to
> >>>>> > >> > > more variables to troubleshoot.
> >>>>> > >> > >
> >>>>> > >> > > On that note, perhaps you can image windows1 and create
> >>windows2
> >>>>> > >> > > as a clone of it?
> >>>>> > >> > >
> >>>>> > >> > > Regards,
> >>>>> > >> > > Om
> >>>>> > >> > >
> >>>>> > >> > >
> >>>>> > >>
> >>>>> > >> > >> Gav.
> >>>>> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> *From:* omuppi1@gmail.com
> [mailto:omuppi1@gmail.com] *On
> >>>>> > Behalf
> >>>>> > >> > Of
> >>>>> > >> > >> *OmPrakash Muppirala
> >>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >>>>> > >> > >> *To:* builds@apache.org
> >>>>> > >> > >> *Cc:* Gavin McDonald
> >>>>> > >> > >>
> >>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> Gavin,
> >>>>> > >> > >>
> >>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long
> >>>>> > >> > >> running
> >>job
> >>>>> > >> > >> on
> >>>>> > >> > >> Windows1 has started failing for the past few days. Can
> >>>>> > >> > >> we first fix that before we start working on Windows2?
> >>>>> > >> > >>
> >>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> Thanks,
> >>>>> > >> > >> Om
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> >>>>> > >> > >> <er...@ixsoftware.nl>
> >>>>> > >> > wrote:
> >>>>> > >> > >>
> >>>>> > >> > >> Ok, from the top of this thread:
> >>>>> > >> > >>
> >>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> The build assumes Pixelbender is installed at:
> >>>>> > >> > >>
> >>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\
> (x86)/Adobe/Adobe
> >>>>> > >> > >> Utilities\ -
> >>>>> > >> > \
> >>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> >>>>> > >> > >>
> >>>>> > >> > >> Is that still the correct path and does the application
> >>>>>start
> >>>>> > >> > >> without errors when you launch it manually?"
> >>>>> > >> > >>
> >>>>> > >> > >> In another email in this thread I've listed the software
> >>>>>that
> >>>>> > >> > >> needs to be on windows2.
> >>>>> > >> > >>
> >>>>> > >> > >> Is there a way to have all our builds run on either
> >>>>> > >> > >> windows1
> >>OR
> >>>>> > >> > >> windows2? Most of our jobs depend on files in the
> >>>>> > >> > >> workspaces
> >>of
> >>>>> > >> > >> some of our other builds, in order to save on disk space
> >>>>> > >> > >> and
> >>build
> >>>>> > time.
> >>>>> > >> > >> If we remove these dependencies, we'd basically be
> >>>>> > >> > >> forced to copy each build into each other build.
> >>>>> > >> > >>
> >>>>> > >> > >> Since it is the weekend, I'll have limited time to work
> >>>>> > >> > >> with you, sorry. Next Monday I'll be glad to
> >>>>> > >> > >> check/test/adjust whatever needs
> checking/testing/adjusting.
> >>>>> > >> > >>
> >>>>> > >> > >> Please keep in mind that we are at a very important
> >>>>>milestone
> >>>>> > >> > >> for our project, and with third party teams relying on
> >>>>> > >> > >> our nightly builds, we'd greatly appreciate a successful
> >>>>> > >> > >> run of
> >>all
> >>>>> > >> > >> our jobs, on whatever slave works.
> >>>>> > >> > >>
> >>>>> > >> > >>
> >>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Gavin, please, please, pretty please, can you have a look at the
'windows1' situation? Please?
Or, if you don't have time - which I would totally understand and
respect - please tell us so one of the other 8 admins on the
'windows1' slave can step in.
Our project needs the builds, as I explained in earlier
communications, third party teams depend on them and I think we may be
loosing their cooperation and contributions if we don't deliver soon.
EdB
On Fri, Dec 13, 2013 at 8:19 AM, Alex Harui <ah...@adobe.com> wrote:
> We just pushed changes to put all the pixel bender stuff in its own
> upstream package that won't be built by Jenkins (because it rarely
> changes). Theoretically, this eliminates the need for the Flex build to
> need a window. We'll see how the next builds come out.
>
> Thank you for trying to fix this. Creating the upstream package isn't
> just a workaround for this issue, it also gives us a more consistent build
> experience for our Linux users as the PixelBender compiler does not work
> on Linux.
>
> Hopefully the builds will start to work now, but I won't be surprised if
> there is some other issue waiting to be discovered.
>
> Thanks,
> -Alex
>
> On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>
>>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>>>
>>> So, the slave is configured for Œweb start¹ via JNLP and that is how it
>>is currently connected.
>>>
>>> The Œservice¹ was also running (which JNLP can control too) so I turned
>>that off and set it to
>>>
>>> Œmaunal¹ start only.
>>>
>>>
>>>
>>> There are 3 builds running. I¹ll reboot the server at an appropriate
>>interval within the next hour or
>>>
>>> so and we¹ll try again.
>>>
>>>
>>>
>>> GavŠ
>>>
>>
>>Okay, can you please let me know when you start it again?
>>
>>Thanks,
>>Om
>>
>>>
>>>
>>>
>>>
>>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>>OmPrakash
>>Muppirala
>>> Sent: Thursday, 12 December 2013 7:15 PM
>>> To: builds@apache.org; Gavin McDonald
>>> Cc: Erik de Bruin
>>>
>>> Subject: Re: [windows1] Pixelbender installation
>>>
>>>
>>>
>>> Hi Gav,
>>>
>>>
>>>
>>> Any updates on this issue?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Om
>>>
>>>
>>>
>>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
>>><bi...@gmail.com>
>>wrote:
>>>>
>>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>>>><ga...@16degrees.com.au>
>>wrote:
>>>>>
>>>>>
>>>>>
>>>>> > -----Original Message-----
>>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>>>> > OmPrakash Muppirala
>>>>>
>>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>>>>> > To: Gavin McDonald
>>>>> > Cc: builds@apache.org; Erik de Bruin
>>>>> > Subject: Re: [windows1] Pixelbender installation
>>>>> >
>>>>>
>>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>>>>> > <bi...@gmail.com>wrote:
>>>>> >
>>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>>>>> > <ga...@16degrees.com.au>wrote:
>>>>> > >
>>>>> > >> Interesting, and puzzling why, but interactive desktop flag was
>>>>> > >> turned off.
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> I've now re-enabled it, please try again.
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>>
>>>>> > >> Gav.
>>>>>
>>>>> > >>
>>>>> > >>
>>>>> > > Great! I have kicked off a build. Will report back in a bit.
>>>>> > >
>>>>> > > Was the windows1 slave started via JNLP or as a windows service?
>>>>> > > Starting via JNLP (using webstart) ensures that the interactive
>>flag is
>>>>> set.
>>>>> > > Whereas if it is modified to be started as a service, you will
>>>>>have
>>to
>>>>> > > manually turn the interactive flag (which sometimes may not
>>propagate
>>>>> > > all the way down the process we try to invoke)
>>>>> > >
>>>>> > > If this does not work, will you be able to restart the slave via
>>JNLP?
>>>>> > >
>>>>> > > Thanks,
>>>>> > > Om
>>>>> > >
>>>>> >
>>>>> > Yes, the build failed as I was typing my previous response.
>>>>> >
>>>>> > Any chance you could restart the windows1 Jenkins instance as just a
>>JNLP
>>>>> > slave agent instead of modifying it into windows webservice? [1]
>>>>>
>>>>> I could, but I don't understand, this Jenkins slave has been running
>>>>>as
>>a
>>>>> service since the day
>>>>> I built it years ago.
>>>>>
>>>>> Gav...
>>>>
>>>>
>>>>
>>>> I don't understand too, but doing this in our test environment fixed
>>>>the
>>problem, whereas manually setting the interactive flag did not. As you
>>mentioned earlier, something somewhere reset the interactive flag on the
>>root process. Unless you want to dig deeper and figure out what happened,
>>I think that restarting it to run as a JNLP slave agent should fix the
>>problem (as per Jenkins' docs) .
>>>>
>>>> Do you have any other ideas on how to fix this?
>>>>
>>>> Thanks,
>>>> Om
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>> >
>>>>> > Thanks,
>>>>> > Om
>>>>> >
>>>>> > [1]
>>>>> > https://wiki.jenkins-
>>>>> >
>>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
>>>>> > enkinsasaWindowsservice-
>>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> > >
>>>>> > >
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
>>>>> > Of
>>>>> > >> *OmPrakash Muppirala
>>>>>
>>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>>>>> > >> *To:* builds@apache.org; Gavin McDonald
>>>>> > >> *Cc:* Erik de Bruin
>>>>>
>>>>> > >>
>>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>>
>>>>> > >> Thanks Gav!
>>>>> > >>
>>>>> > >> We did a bunch of tests to repro this issue on our side. One way
>>we
>>>>> > >> could reproduce this on our Jenkins installation was that if we
>>>>>ran
>>>>> > >> the job as a service, we are getting the same error messages (AIF
>>>>> > >> Internal exception).
>>>>> > >>
>>>>> > >> Jenkins docs says that for jobs that require Desktop Access
>>>>>(which
>>>>> > >> Pixel Bender does), the root service process that is running the
>>job
>>>>> > >> needs to have the 'interactive flag' enabled in the Windows
>>>>>Service
>>>>> > >> Manager. [1]
>>>>> > >>
>>>>> > >> One way this setting could have changed is if the way the windows
>>>>> > >> slave starts was modified.
>>>>> > >>
>>>>> > >> Can you please take a look under the hood and see if you find
>>>>> > >> something amiss?
>>>>> > >>
>>>>> > >> Thanks,
>>>>> > >> Om
>>>>> > >>
>>>>> > >>
>>>>> > >> [1]
>>>>> > >> https://wiki.jenkins-
>>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>>>>> > >> computer+but+not+on+Jenkins
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>>>>> > >> <ga...@16degrees.com.au>
>>>>> > >> wrote:
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> > -----Original Message-----
>>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>>> > >>
>>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>>>>> > >> > To: builds@apache.org
>>>>> > >> > Cc: Gavin McDonald
>>>>> > >>
>>>>> > >> > Subject: Re: [windows1] Pixelbender installation
>>>>> > >> >
>>>>> > >> > 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...
>>>>> > >>
>>>>> > >>
>>>>> > >> >
>>>>> > >> > EdB
>>>>> > >> >
>>>>> > >> >
>>>>> > >> >
>>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>>>>> > >> > <bi...@gmail.com> wrote:
>>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>>>>> > >> > <ga...@16degrees.com.au>wrote:
>>>>> > >> > >
>>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get across
>>>>>is
>>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
>>>>> > >> > >> slightly possible that the build is failing due to a coding
>>>>> > >> > >> error? In other words, I've been blamed several times now
>>>>>for
>>>>> > >> > >> breaking the build when I haven't been anywhere near the
>>machine
>>>>> > in question.
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > > The build does not fail on my or other committers' machines.
>> It
>>>>> > >> > > must be something specific to whats happening in Windows1.
>> Sorry
>>>>> > >> > > if it sounds like we are blaming you. We are just trying to
>>>>> > >> > > troubleshoot and are running blind here.
>>>>> > >> > >
>>>>> > >> > >
>>>>> > >> > >
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> Either way I'll look.
>>>>> > >> > >>
>>>>> > >> > >
>>>>> > >> > > Thanks!
>>>>> > >> > >
>>>>> > >> > >
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> And so that we are clear, windows1 is not going away, it is
>>very
>>>>> > >> > >> heavily used, folks are always complaining it is down, so
>>>>>I'm
>>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
>>>>>slave.
>>>>> > >> > >> Point is, you need to be configured to use both slaves for
>>>>>it
>>to
>>>>> > >> > >> work, or my time
>>>>> > >> > building a 2ndmachine is wasted and you'll continue to complain
>>>>> > >> > about
>>>>> > >> the
>>>>> > >> 1
>>>>> > >> > st windows box being overloaded all the time.
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >
>>>>> > >> > > We welcome the addition of a new windows slave, no doubt.
>> Which
>>>>> > >> > > is why we want to fix Windows1 first. Otherwise it will lead
>>to
>>>>> > >> > > more variables to troubleshoot.
>>>>> > >> > >
>>>>> > >> > > On that note, perhaps you can image windows1 and create
>>windows2
>>>>> > >> > > as a clone of it?
>>>>> > >> > >
>>>>> > >> > > Regards,
>>>>> > >> > > Om
>>>>> > >> > >
>>>>> > >> > >
>>>>> > >>
>>>>> > >> > >> Gav.
>>>>> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>>>>> > Behalf
>>>>> > >> > Of
>>>>> > >> > >> *OmPrakash Muppirala
>>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>>>>> > >> > >> *To:* builds@apache.org
>>>>> > >> > >> *Cc:* Gavin McDonald
>>>>> > >> > >>
>>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> Gavin,
>>>>> > >> > >>
>>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long running
>>job
>>>>> > >> > >> on
>>>>> > >> > >> Windows1 has started failing for the past few days. Can we
>>>>> > >> > >> first fix that before we start working on Windows2?
>>>>> > >> > >>
>>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> Thanks,
>>>>> > >> > >> Om
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>>>>> > >> > >> <er...@ixsoftware.nl>
>>>>> > >> > wrote:
>>>>> > >> > >>
>>>>> > >> > >> Ok, from the top of this thread:
>>>>> > >> > >>
>>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> The build assumes Pixelbender is installed at:
>>>>> > >> > >>
>>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
>>>>> > >> > >> Utilities\ -
>>>>> > >> > \
>>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>>>>> > >> > >>
>>>>> > >> > >> Is that still the correct path and does the application
>>>>>start
>>>>> > >> > >> without errors when you launch it manually?"
>>>>> > >> > >>
>>>>> > >> > >> In another email in this thread I've listed the software
>>>>>that
>>>>> > >> > >> needs to be on windows2.
>>>>> > >> > >>
>>>>> > >> > >> Is there a way to have all our builds run on either windows1
>>OR
>>>>> > >> > >> windows2? Most of our jobs depend on files in the workspaces
>>of
>>>>> > >> > >> some of our other builds, in order to save on disk space and
>>build
>>>>> > time.
>>>>> > >> > >> If we remove these dependencies, we'd basically be forced to
>>>>> > >> > >> copy each build into each other build.
>>>>> > >> > >>
>>>>> > >> > >> Since it is the weekend, I'll have limited time to work with
>>>>> > >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
>>>>> > >> > >> whatever needs checking/testing/adjusting.
>>>>> > >> > >>
>>>>> > >> > >> Please keep in mind that we are at a very important
>>>>>milestone
>>>>> > >> > >> for our project, and with third party teams relying on our
>>>>> > >> > >> nightly builds, we'd greatly appreciate a successful run of
>>all
>>>>> > >> > >> our jobs, on whatever slave works.
>>>>> > >> > >>
>>>>> > >> > >>
>>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Alex Harui <ah...@adobe.com>.
We just pushed changes to put all the pixel bender stuff in its own
upstream package that won't be built by Jenkins (because it rarely
changes). Theoretically, this eliminates the need for the Flex build to
need a window. We'll see how the next builds come out.
Thank you for trying to fix this. Creating the upstream package isn't
just a workaround for this issue, it also gives us a more consistent build
experience for our Linux users as the PixelBender compiler does not work
on Linux.
Hopefully the builds will start to work now, but I won't be surprised if
there is some other issue waiting to be discovered.
Thanks,
-Alex
On 12/12/13 8:24 AM, "OmPrakash Muppirala" <bi...@gmail.com> wrote:
>On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>>
>> So, the slave is configured for Œweb start¹ via JNLP and that is how it
>is currently connected.
>>
>> The Œservice¹ was also running (which JNLP can control too) so I turned
>that off and set it to
>>
>> Œmaunal¹ start only.
>>
>>
>>
>> There are 3 builds running. I¹ll reboot the server at an appropriate
>interval within the next hour or
>>
>> so and we¹ll try again.
>>
>>
>>
>> GavŠ
>>
>
>Okay, can you please let me know when you start it again?
>
>Thanks,
>Om
>
>>
>>
>>
>>
>> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>OmPrakash
>Muppirala
>> Sent: Thursday, 12 December 2013 7:15 PM
>> To: builds@apache.org; Gavin McDonald
>> Cc: Erik de Bruin
>>
>> Subject: Re: [windows1] Pixelbender installation
>>
>>
>>
>> Hi Gav,
>>
>>
>>
>> Any updates on this issue?
>>
>>
>>
>> Thanks,
>>
>> Om
>>
>>
>>
>> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
>><bi...@gmail.com>
>wrote:
>>>
>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>>><ga...@16degrees.com.au>
>wrote:
>>>>
>>>>
>>>>
>>>> > -----Original Message-----
>>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>>> > OmPrakash Muppirala
>>>>
>>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>>>> > To: Gavin McDonald
>>>> > Cc: builds@apache.org; Erik de Bruin
>>>> > Subject: Re: [windows1] Pixelbender installation
>>>> >
>>>>
>>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>>>> > <bi...@gmail.com>wrote:
>>>> >
>>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>>>> > <ga...@16degrees.com.au>wrote:
>>>> > >
>>>> > >> Interesting, and puzzling why, but interactive desktop flag was
>>>> > >> turned off.
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> I've now re-enabled it, please try again.
>>>> > >>
>>>> > >>
>>>> > >>
>>>>
>>>> > >> Gav.
>>>>
>>>> > >>
>>>> > >>
>>>> > > Great! I have kicked off a build. Will report back in a bit.
>>>> > >
>>>> > > Was the windows1 slave started via JNLP or as a windows service?
>>>> > > Starting via JNLP (using webstart) ensures that the interactive
>flag is
>>>> set.
>>>> > > Whereas if it is modified to be started as a service, you will
>>>>have
>to
>>>> > > manually turn the interactive flag (which sometimes may not
>propagate
>>>> > > all the way down the process we try to invoke)
>>>> > >
>>>> > > If this does not work, will you be able to restart the slave via
>JNLP?
>>>> > >
>>>> > > Thanks,
>>>> > > Om
>>>> > >
>>>> >
>>>> > Yes, the build failed as I was typing my previous response.
>>>> >
>>>> > Any chance you could restart the windows1 Jenkins instance as just a
>JNLP
>>>> > slave agent instead of modifying it into windows webservice? [1]
>>>>
>>>> I could, but I don't understand, this Jenkins slave has been running
>>>>as
>a
>>>> service since the day
>>>> I built it years ago.
>>>>
>>>> Gav...
>>>
>>>
>>>
>>> I don't understand too, but doing this in our test environment fixed
>>>the
>problem, whereas manually setting the interactive flag did not. As you
>mentioned earlier, something somewhere reset the interactive flag on the
>root process. Unless you want to dig deeper and figure out what happened,
>I think that restarting it to run as a JNLP slave agent should fix the
>problem (as per Jenkins' docs) .
>>>
>>> Do you have any other ideas on how to fix this?
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>>
>>>>
>>>>
>>>> >
>>>> > Thanks,
>>>> > Om
>>>> >
>>>> > [1]
>>>> > https://wiki.jenkins-
>>>> >
>ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
>>>> > enkinsasaWindowsservice-
>>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>>>>
>>>> >
>>>> >
>>>> >
>>>> > >
>>>> > >
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
>>>> > Of
>>>> > >> *OmPrakash Muppirala
>>>>
>>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>>>> > >> *To:* builds@apache.org; Gavin McDonald
>>>> > >> *Cc:* Erik de Bruin
>>>>
>>>> > >>
>>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>> > >>
>>>> > >>
>>>> > >>
>>>>
>>>> > >> Thanks Gav!
>>>> > >>
>>>> > >> We did a bunch of tests to repro this issue on our side. One way
>we
>>>> > >> could reproduce this on our Jenkins installation was that if we
>>>>ran
>>>> > >> the job as a service, we are getting the same error messages (AIF
>>>> > >> Internal exception).
>>>> > >>
>>>> > >> Jenkins docs says that for jobs that require Desktop Access
>>>>(which
>>>> > >> Pixel Bender does), the root service process that is running the
>job
>>>> > >> needs to have the 'interactive flag' enabled in the Windows
>>>>Service
>>>> > >> Manager. [1]
>>>> > >>
>>>> > >> One way this setting could have changed is if the way the windows
>>>> > >> slave starts was modified.
>>>> > >>
>>>> > >> Can you please take a look under the hood and see if you find
>>>> > >> something amiss?
>>>> > >>
>>>> > >> Thanks,
>>>> > >> Om
>>>> > >>
>>>> > >>
>>>> > >> [1]
>>>> > >> https://wiki.jenkins-
>>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>>>> > >> computer+but+not+on+Jenkins
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>>>> > >> <ga...@16degrees.com.au>
>>>> > >> wrote:
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >> > -----Original Message-----
>>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>>> > >>
>>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>>>> > >> > To: builds@apache.org
>>>> > >> > Cc: Gavin McDonald
>>>> > >>
>>>> > >> > Subject: Re: [windows1] Pixelbender installation
>>>> > >> >
>>>> > >> > 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...
>>>> > >>
>>>> > >>
>>>> > >> >
>>>> > >> > EdB
>>>> > >> >
>>>> > >> >
>>>> > >> >
>>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>>>> > >> > <bi...@gmail.com> wrote:
>>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>>>> > >> > <ga...@16degrees.com.au>wrote:
>>>> > >> > >
>>>> > >> > >> That's fine, I'll take a look. All I'm trying to get across
>>>>is
>>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
>>>> > >> > >> slightly possible that the build is failing due to a coding
>>>> > >> > >> error? In other words, I've been blamed several times now
>>>>for
>>>> > >> > >> breaking the build when I haven't been anywhere near the
>machine
>>>> > in question.
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > > The build does not fail on my or other committers' machines.
> It
>>>> > >> > > must be something specific to whats happening in Windows1.
> Sorry
>>>> > >> > > if it sounds like we are blaming you. We are just trying to
>>>> > >> > > troubleshoot and are running blind here.
>>>> > >> > >
>>>> > >> > >
>>>> > >> > >
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> Either way I'll look.
>>>> > >> > >>
>>>> > >> > >
>>>> > >> > > Thanks!
>>>> > >> > >
>>>> > >> > >
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> And so that we are clear, windows1 is not going away, it is
>very
>>>> > >> > >> heavily used, folks are always complaining it is down, so
>>>>I'm
>>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1
>>>>slave.
>>>> > >> > >> Point is, you need to be configured to use both slaves for
>>>>it
>to
>>>> > >> > >> work, or my time
>>>> > >> > building a 2ndmachine is wasted and you'll continue to complain
>>>> > >> > about
>>>> > >> the
>>>> > >> 1
>>>> > >> > st windows box being overloaded all the time.
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >
>>>> > >> > > We welcome the addition of a new windows slave, no doubt.
> Which
>>>> > >> > > is why we want to fix Windows1 first. Otherwise it will lead
>to
>>>> > >> > > more variables to troubleshoot.
>>>> > >> > >
>>>> > >> > > On that note, perhaps you can image windows1 and create
>windows2
>>>> > >> > > as a clone of it?
>>>> > >> > >
>>>> > >> > > Regards,
>>>> > >> > > Om
>>>> > >> > >
>>>> > >> > >
>>>> > >>
>>>> > >> > >> Gav.
>>>> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>>>> > Behalf
>>>> > >> > Of
>>>> > >> > >> *OmPrakash Muppirala
>>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>>>> > >> > >> *To:* builds@apache.org
>>>> > >> > >> *Cc:* Gavin McDonald
>>>> > >> > >>
>>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> Gavin,
>>>> > >> > >>
>>>> > >> > >> This issue is unrelated to Windows2 slave. Our long running
>job
>>>> > >> > >> on
>>>> > >> > >> Windows1 has started failing for the past few days. Can we
>>>> > >> > >> first fix that before we start working on Windows2?
>>>> > >> > >>
>>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> Thanks,
>>>> > >> > >> Om
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>>>> > >> > >> <er...@ixsoftware.nl>
>>>> > >> > wrote:
>>>> > >> > >>
>>>> > >> > >> Ok, from the top of this thread:
>>>> > >> > >>
>>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> The build assumes Pixelbender is installed at:
>>>> > >> > >>
>>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
>>>> > >> > >> Utilities\ -
>>>> > >> > \
>>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>>>> > >> > >>
>>>> > >> > >> Is that still the correct path and does the application
>>>>start
>>>> > >> > >> without errors when you launch it manually?"
>>>> > >> > >>
>>>> > >> > >> In another email in this thread I've listed the software
>>>>that
>>>> > >> > >> needs to be on windows2.
>>>> > >> > >>
>>>> > >> > >> Is there a way to have all our builds run on either windows1
>OR
>>>> > >> > >> windows2? Most of our jobs depend on files in the workspaces
>of
>>>> > >> > >> some of our other builds, in order to save on disk space and
>build
>>>> > time.
>>>> > >> > >> If we remove these dependencies, we'd basically be forced to
>>>> > >> > >> copy each build into each other build.
>>>> > >> > >>
>>>> > >> > >> Since it is the weekend, I'll have limited time to work with
>>>> > >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
>>>> > >> > >> whatever needs checking/testing/adjusting.
>>>> > >> > >>
>>>> > >> > >> Please keep in mind that we are at a very important
>>>>milestone
>>>> > >> > >> for our project, and with third party teams relying on our
>>>> > >> > >> nightly builds, we'd greatly appreciate a successful run of
>all
>>>> > >> > >> our jobs, on whatever slave works.
>>>> > >> > >>
>>>> > >> > >>
>>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Dec 12, 2013 12:45 AM, "Gavin McDonald" <ga...@16degrees.com.au> wrote:
>
> So, the slave is configured for ‘web start’ via JNLP and that is how it
is currently connected.
>
> The ‘service’ was also running (which JNLP can control too) so I turned
that off and set it to
>
> ‘maunal’ start only.
>
>
>
> There are 3 builds running. I’ll reboot the server at an appropriate
interval within the next hour or
>
> so and we’ll try again.
>
>
>
> Gav…
>
Okay, can you please let me know when you start it again?
Thanks,
Om
>
>
>
>
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash
Muppirala
> Sent: Thursday, 12 December 2013 7:15 PM
> To: builds@apache.org; Gavin McDonald
> Cc: Erik de Bruin
>
> Subject: Re: [windows1] Pixelbender installation
>
>
>
> Hi Gav,
>
>
>
> Any updates on this issue?
>
>
>
> Thanks,
>
> Om
>
>
>
> On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala <bi...@gmail.com>
wrote:
>>
>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald <ga...@16degrees.com.au>
wrote:
>>>
>>>
>>>
>>> > -----Original Message-----
>>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>>> > OmPrakash Muppirala
>>>
>>> > Sent: Wednesday, 11 December 2013 10:51 AM
>>> > To: Gavin McDonald
>>> > Cc: builds@apache.org; Erik de Bruin
>>> > Subject: Re: [windows1] Pixelbender installation
>>> >
>>>
>>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>>> > <bi...@gmail.com>wrote:
>>> >
>>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>>> > <ga...@16degrees.com.au>wrote:
>>> > >
>>> > >> Interesting, and puzzling why, but interactive desktop flag was
>>> > >> turned off.
>>> > >>
>>> > >>
>>> > >>
>>> > >> I've now re-enabled it, please try again.
>>> > >>
>>> > >>
>>> > >>
>>>
>>> > >> Gav.
>>>
>>> > >>
>>> > >>
>>> > > Great! I have kicked off a build. Will report back in a bit.
>>> > >
>>> > > Was the windows1 slave started via JNLP or as a windows service?
>>> > > Starting via JNLP (using webstart) ensures that the interactive
flag is
>>> set.
>>> > > Whereas if it is modified to be started as a service, you will have
to
>>> > > manually turn the interactive flag (which sometimes may not
propagate
>>> > > all the way down the process we try to invoke)
>>> > >
>>> > > If this does not work, will you be able to restart the slave via
JNLP?
>>> > >
>>> > > Thanks,
>>> > > Om
>>> > >
>>> >
>>> > Yes, the build failed as I was typing my previous response.
>>> >
>>> > Any chance you could restart the windows1 Jenkins instance as just a
JNLP
>>> > slave agent instead of modifying it into windows webservice? [1]
>>>
>>> I could, but I don't understand, this Jenkins slave has been running as
a
>>> service since the day
>>> I built it years ago.
>>>
>>> Gav...
>>
>>
>>
>> I don't understand too, but doing this in our test environment fixed the
problem, whereas manually setting the interactive flag did not. As you
mentioned earlier, something somewhere reset the interactive flag on the
root process. Unless you want to dig deeper and figure out what happened,
I think that restarting it to run as a JNLP slave agent should fix the
problem (as per Jenkins' docs) .
>>
>> Do you have any other ideas on how to fix this?
>>
>> Thanks,
>> Om
>>
>>
>>
>>>
>>>
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > [1]
>>> > https://wiki.jenkins-
>>> >
ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
>>> > enkinsasaWindowsservice-
>>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>>>
>>> >
>>> >
>>> >
>>> > >
>>> > >
>>> > >>
>>> > >>
>>> > >>
>>> > >>
>>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
>>> > Of
>>> > >> *OmPrakash Muppirala
>>>
>>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>>> > >> *To:* builds@apache.org; Gavin McDonald
>>> > >> *Cc:* Erik de Bruin
>>>
>>> > >>
>>> > >> *Subject:* Re: [windows1] Pixelbender installation
>>> > >>
>>> > >>
>>> > >>
>>>
>>> > >> Thanks Gav!
>>> > >>
>>> > >> We did a bunch of tests to repro this issue on our side. One way
we
>>> > >> could reproduce this on our Jenkins installation was that if we ran
>>> > >> the job as a service, we are getting the same error messages (AIF
>>> > >> Internal exception).
>>> > >>
>>> > >> Jenkins docs says that for jobs that require Desktop Access (which
>>> > >> Pixel Bender does), the root service process that is running the
job
>>> > >> needs to have the 'interactive flag' enabled in the Windows Service
>>> > >> Manager. [1]
>>> > >>
>>> > >> One way this setting could have changed is if the way the windows
>>> > >> slave starts was modified.
>>> > >>
>>> > >> Can you please take a look under the hood and see if you find
>>> > >> something amiss?
>>> > >>
>>> > >> Thanks,
>>> > >> Om
>>> > >>
>>> > >>
>>> > >> [1]
>>> > >> https://wiki.jenkins-
>>> > ci.org/display/JENKINS/My+software+builds+on+my+
>>> > >> computer+but+not+on+Jenkins
>>> > >>
>>> > >>
>>> > >>
>>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>>> > >> <ga...@16degrees.com.au>
>>> > >> wrote:
>>> > >>
>>> > >>
>>> > >>
>>> > >> > -----Original Message-----
>>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>> > >>
>>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>>> > >> > To: builds@apache.org
>>> > >> > Cc: Gavin McDonald
>>> > >>
>>> > >> > Subject: Re: [windows1] Pixelbender installation
>>> > >> >
>>> > >> > 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...
>>> > >>
>>> > >>
>>> > >> >
>>> > >> > EdB
>>> > >> >
>>> > >> >
>>> > >> >
>>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>>> > >> > <bi...@gmail.com> wrote:
>>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>>> > >> > <ga...@16degrees.com.au>wrote:
>>> > >> > >
>>> > >> > >> That's fine, I'll take a look. All I'm trying to get across is
>>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
>>> > >> > >> slightly possible that the build is failing due to a coding
>>> > >> > >> error? In other words, I've been blamed several times now for
>>> > >> > >> breaking the build when I haven't been anywhere near the
machine
>>> > in question.
>>> > >> > >>
>>> > >> > >>
>>> > >> > > The build does not fail on my or other committers' machines.
It
>>> > >> > > must be something specific to whats happening in Windows1.
Sorry
>>> > >> > > if it sounds like we are blaming you. We are just trying to
>>> > >> > > troubleshoot and are running blind here.
>>> > >> > >
>>> > >> > >
>>> > >> > >
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> Either way I'll look.
>>> > >> > >>
>>> > >> > >
>>> > >> > > Thanks!
>>> > >> > >
>>> > >> > >
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> And so that we are clear, windows1 is not going away, it is
very
>>> > >> > >> heavily used, folks are always complaining it is down, so I'm
>>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1 slave.
>>> > >> > >> Point is, you need to be configured to use both slaves for it
to
>>> > >> > >> work, or my time
>>> > >> > building a 2ndmachine is wasted and you'll continue to complain
>>> > >> > about
>>> > >> the
>>> > >> 1
>>> > >> > st windows box being overloaded all the time.
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >
>>> > >> > > We welcome the addition of a new windows slave, no doubt.
Which
>>> > >> > > is why we want to fix Windows1 first. Otherwise it will lead
to
>>> > >> > > more variables to troubleshoot.
>>> > >> > >
>>> > >> > > On that note, perhaps you can image windows1 and create
windows2
>>> > >> > > as a clone of it?
>>> > >> > >
>>> > >> > > Regards,
>>> > >> > > Om
>>> > >> > >
>>> > >> > >
>>> > >>
>>> > >> > >> Gav.
>>> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>>> > Behalf
>>> > >> > Of
>>> > >> > >> *OmPrakash Muppirala
>>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>>> > >> > >> *To:* builds@apache.org
>>> > >> > >> *Cc:* Gavin McDonald
>>> > >> > >>
>>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> Gavin,
>>> > >> > >>
>>> > >> > >> This issue is unrelated to Windows2 slave. Our long running
job
>>> > >> > >> on
>>> > >> > >> Windows1 has started failing for the past few days. Can we
>>> > >> > >> first fix that before we start working on Windows2?
>>> > >> > >>
>>> > >> > >> Or, is Windows2 a replacement for Windows1?
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> Thanks,
>>> > >> > >> Om
>>> > >> > >>
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>>> > >> > >> <er...@ixsoftware.nl>
>>> > >> > wrote:
>>> > >> > >>
>>> > >> > >> Ok, from the top of this thread:
>>> > >> > >>
>>> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> The build assumes Pixelbender is installed at:
>>> > >> > >>
>>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
>>> > >> > >> Utilities\ -
>>> > >> > \
>>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>>> > >> > >>
>>> > >> > >> Is that still the correct path and does the application start
>>> > >> > >> without errors when you launch it manually?"
>>> > >> > >>
>>> > >> > >> In another email in this thread I've listed the software that
>>> > >> > >> needs to be on windows2.
>>> > >> > >>
>>> > >> > >> Is there a way to have all our builds run on either windows1
OR
>>> > >> > >> windows2? Most of our jobs depend on files in the workspaces
of
>>> > >> > >> some of our other builds, in order to save on disk space and
build
>>> > time.
>>> > >> > >> If we remove these dependencies, we'd basically be forced to
>>> > >> > >> copy each build into each other build.
>>> > >> > >>
>>> > >> > >> Since it is the weekend, I'll have limited time to work with
>>> > >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
>>> > >> > >> whatever needs checking/testing/adjusting.
>>> > >> > >>
>>> > >> > >> Please keep in mind that we are at a very important milestone
>>> > >> > >> for our project, and with third party teams relying on our
>>> > >> > >> nightly builds, we'd greatly appreciate a successful run of
all
>>> > >> > >> our jobs, on whatever slave works.
>>> > >> > >>
>>> > >> > >>
>>> > >> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
So, the slave is configured for 'web start' via JNLP and that is how it is
currently connected.
The 'service' was also running (which JNLP can control too) so I turned that
off and set it to
'maunal' start only.
There are 3 builds running. I'll reboot the server at an appropriate
interval within the next hour or
so and we'll try again.
Gav.
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Thursday, 12 December 2013 7:15 PM
To: builds@apache.org; Gavin McDonald
Cc: Erik de Bruin
Subject: Re: [windows1] Pixelbender installation
Hi Gav,
Any updates on this issue?
Thanks,
Om
On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala <bigosmallm@gmail.com
<ma...@gmail.com> > wrote:
On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald <gavin@16degrees.com.au
<ma...@16degrees.com.au> > wrote:
> -----Original Message-----
> From: omuppi1@gmail.com <ma...@gmail.com>
[mailto:omuppi1@gmail.com <ma...@gmail.com> ] On Behalf Of
> OmPrakash Muppirala
> Sent: Wednesday, 11 December 2013 10:51 AM
> To: Gavin McDonald
> Cc: builds@apache.org <ma...@apache.org> ; Erik de Bruin
> Subject: Re: [windows1] Pixelbender installation
>
> On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> <bigosmallm@gmail.com <ma...@gmail.com> >wrote:
>
> > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> <gavin@16degrees.com.au <ma...@16degrees.com.au> >wrote:
> >
> >> Interesting, and puzzling why, but interactive desktop flag was
> >> turned off.
> >>
> >>
> >>
> >> I've now re-enabled it, please try again.
> >>
> >>
> >>
> >> Gav.
> >>
> >>
> > Great! I have kicked off a build. Will report back in a bit.
> >
> > Was the windows1 slave started via JNLP or as a windows service?
> > Starting via JNLP (using webstart) ensures that the interactive flag is
set.
> > Whereas if it is modified to be started as a service, you will have to
> > manually turn the interactive flag (which sometimes may not propagate
> > all the way down the process we try to invoke)
> >
> > If this does not work, will you be able to restart the slave via JNLP?
> >
> > Thanks,
> > Om
> >
>
> Yes, the build failed as I was typing my previous response.
>
> Any chance you could restart the windows1 Jenkins instance as just a JNLP
> slave agent instead of modifying it into windows webservice? [1]
I could, but I don't understand, this Jenkins slave has been running as a
service since the day
I built it years ago.
Gav...
I don't understand too, but doing this in our test environment fixed the
problem, whereas manually setting the interactive flag did not. As you
mentioned earlier, something somewhere reset the interactive flag on the
root process. Unless you want to dig deeper and figure out what happened, I
think that restarting it to run as a JNLP slave agent should fix the problem
(as per Jenkins' docs) .
Do you have any other ideas on how to fix this?
Thanks,
Om
>
> Thanks,
> Om
>
> [1]
> https://wiki.jenkins-
> ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
<http://ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#Insta
llingJ>
> enkinsasaWindowsservice-
> InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>
>
>
> >
> >
> >>
> >>
> >>
> >>
> >> *From:* omuppi1@gmail.com <ma...@gmail.com>
[mailto:omuppi1@gmail.com <ma...@gmail.com> ] *On Behalf
> Of
> >> *OmPrakash Muppirala
> >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> >> *To:* builds@apache.org <ma...@apache.org> ; Gavin McDonald
> >> *Cc:* Erik de Bruin
> >>
> >> *Subject:* Re: [windows1] Pixelbender installation
> >>
> >>
> >>
> >> Thanks Gav!
> >>
> >> We did a bunch of tests to repro this issue on our side. One way we
> >> could reproduce this on our Jenkins installation was that if we ran
> >> the job as a service, we are getting the same error messages (AIF
> >> Internal exception).
> >>
> >> Jenkins docs says that for jobs that require Desktop Access (which
> >> Pixel Bender does), the root service process that is running the job
> >> needs to have the 'interactive flag' enabled in the Windows Service
> >> Manager. [1]
> >>
> >> One way this setting could have changed is if the way the windows
> >> slave starts was modified.
> >>
> >> Can you please take a look under the hood and see if you find
> >> something amiss?
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >> [1]
> >> https://wiki.jenkins-
> ci.org/display/JENKINS/My+software+builds+on+my+
<http://ci.org/display/JENKINS/My+software+builds+on+my+>
> >> computer+but+not+on+Jenkins
> >>
> >>
> >>
> >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> >> <gavin@16degrees.com.au <ma...@16degrees.com.au> >
> >> wrote:
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl
<ma...@ixsoftware.nl> ]
> >>
> >> > Sent: Tuesday, 10 December 2013 7:14 PM
> >> > To: builds@apache.org <ma...@apache.org>
> >> > Cc: Gavin McDonald
> >>
> >> > Subject: Re: [windows1] Pixelbender installation
> >> >
> >> > 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...
> >>
> >>
> >> >
> >> > EdB
> >> >
> >> >
> >> >
> >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> >> > <bigosmallm@gmail.com <ma...@gmail.com> > wrote:
> >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> >> > <gavin@16degrees.com.au <ma...@16degrees.com.au> >wrote:
> >> > >
> >> > >> That's fine, I'll take a look. All I'm trying to get across is
> >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
> >> > >> slightly possible that the build is failing due to a coding
> >> > >> error? In other words, I've been blamed several times now for
> >> > >> breaking the build when I haven't been anywhere near the machine
> in question.
> >> > >>
> >> > >>
> >> > > The build does not fail on my or other committers' machines. It
> >> > > must be something specific to whats happening in Windows1. Sorry
> >> > > if it sounds like we are blaming you. We are just trying to
> >> > > troubleshoot and are running blind here.
> >> > >
> >> > >
> >> > >
> >> > >>
> >> > >>
> >> > >> Either way I'll look.
> >> > >>
> >> > >
> >> > > Thanks!
> >> > >
> >> > >
> >> > >>
> >> > >>
> >> > >> And so that we are clear, windows1 is not going away, it is very
> >> > >> heavily used, folks are always complaining it is down, so I'm
> >> > >> adding a 2ndwindows2 slave in addition to the windows1 slave.
> >> > >> Point is, you need to be configured to use both slaves for it to
> >> > >> work, or my time
> >> > building a 2ndmachine is wasted and you'll continue to complain
> >> > about
> >> the
> >> 1
> >> > st windows box being overloaded all the time.
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >> > > We welcome the addition of a new windows slave, no doubt. Which
> >> > > is why we want to fix Windows1 first. Otherwise it will lead to
> >> > > more variables to troubleshoot.
> >> > >
> >> > > On that note, perhaps you can image windows1 and create windows2
> >> > > as a clone of it?
> >> > >
> >> > > Regards,
> >> > > Om
> >> > >
> >> > >
> >>
> >> > >> Gav.
> >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >> *From:* omuppi1@gmail.com <ma...@gmail.com>
[mailto:omuppi1@gmail.com <ma...@gmail.com> ] *On
> Behalf
> >> > Of
> >> > >> *OmPrakash Muppirala
> >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >> > >> *To:* builds@apache.org <ma...@apache.org>
> >> > >> *Cc:* Gavin McDonald
> >> > >>
> >> > >> *Subject:* Re: [windows1] Pixelbender installation
> >> > >>
> >> > >>
> >> > >>
> >> > >> Gavin,
> >> > >>
> >> > >> This issue is unrelated to Windows2 slave. Our long running job
> >> > >> on
> >> > >> Windows1 has started failing for the past few days. Can we
> >> > >> first fix that before we start working on Windows2?
> >> > >>
> >> > >> Or, is Windows2 a replacement for Windows1?
> >> > >>
> >> > >>
> >> > >>
> >> > >> Thanks,
> >> > >> Om
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> >> > >> <erik@ixsoftware.nl <ma...@ixsoftware.nl> >
> >> > wrote:
> >> > >>
> >> > >> Ok, from the top of this thread:
> >> > >>
> >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> >> > >>
> >> > >>
> >> > >> The build assumes Pixelbender is installed at:
> >> > >>
> >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
> >> > >> Utilities\ -
> >> > \
> >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> >> > >>
> >> > >> Is that still the correct path and does the application start
> >> > >> without errors when you launch it manually?"
> >> > >>
> >> > >> In another email in this thread I've listed the software that
> >> > >> needs to be on windows2.
> >> > >>
> >> > >> Is there a way to have all our builds run on either windows1 OR
> >> > >> windows2? Most of our jobs depend on files in the workspaces of
> >> > >> some of our other builds, in order to save on disk space and build
> time.
> >> > >> If we remove these dependencies, we'd basically be forced to
> >> > >> copy each build into each other build.
> >> > >>
> >> > >> Since it is the weekend, I'll have limited time to work with
> >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
> >> > >> whatever needs checking/testing/adjusting.
> >> > >>
> >> > >> Please keep in mind that we are at a very important milestone
> >> > >> for our project, and with third party teams relying on our
> >> > >> nightly builds, we'd greatly appreciate a successful run of all
> >> > >> our jobs, on whatever slave works.
> >> > >>
> >> > >>
> >> > >> EdB
> >> > >>
> >> > >>
> >> > >>
> >> > >> --
> >> > >> Ix Multimedia Software
> >> > >>
> >> > >> Jan Luykenstraat 27
> >> > >> 3521 VB Utrecht
> >> > >>
> >> > >> T. 06-51952295
> >> > >> I. www.ixsoftware.nl <http://www.ixsoftware.nl>
> >> > >>
> >> > >>
> >> > >>
> >> >
> >> >
> >> >
> >> > --
> >> > Ix Multimedia Software
> >> >
> >> > Jan Luykenstraat 27
> >> > 3521 VB Utrecht
> >> >
> >> > T. 06-51952295
> >> > I. www.ixsoftware.nl <http://www.ixsoftware.nl>
> >>
> >>
> >>
> >
> >
Re: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Hi Gav,
Any updates on this issue?
Thanks,
Om
On Tue, Dec 10, 2013 at 4:02 PM, OmPrakash Muppirala
<bi...@gmail.com>wrote:
> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
>> > OmPrakash Muppirala
>> > Sent: Wednesday, 11 December 2013 10:51 AM
>> > To: Gavin McDonald
>> > Cc: builds@apache.org; Erik de Bruin
>> > Subject: Re: [windows1] Pixelbender installation
>> >
>> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
>> > <bi...@gmail.com>wrote:
>> >
>> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
>> > <ga...@16degrees.com.au>wrote:
>> > >
>> > >> Interesting, and puzzling why, but interactive desktop flag was
>> > >> turned off.
>> > >>
>> > >>
>> > >>
>> > >> I've now re-enabled it, please try again.
>> > >>
>> > >>
>> > >>
>> > >> Gav.
>> > >>
>> > >>
>> > > Great! I have kicked off a build. Will report back in a bit.
>> > >
>> > > Was the windows1 slave started via JNLP or as a windows service?
>> > > Starting via JNLP (using webstart) ensures that the interactive flag
>> is
>> set.
>> > > Whereas if it is modified to be started as a service, you will have to
>> > > manually turn the interactive flag (which sometimes may not propagate
>> > > all the way down the process we try to invoke)
>> > >
>> > > If this does not work, will you be able to restart the slave via JNLP?
>> > >
>> > > Thanks,
>> > > Om
>> > >
>> >
>> > Yes, the build failed as I was typing my previous response.
>> >
>> > Any chance you could restart the windows1 Jenkins instance as just a
>> JNLP
>> > slave agent instead of modifying it into windows webservice? [1]
>>
>> I could, but I don't understand, this Jenkins slave has been running as a
>> service since the day
>> I built it years ago.
>>
>> Gav...
>>
>
> I don't understand too, but doing this in our test environment fixed the
> problem, whereas manually setting the interactive flag did not. As you
> mentioned earlier, something somewhere reset the interactive flag on the
> root process. Unless you want to dig deeper and figure out what happened,
> I think that restarting it to run as a JNLP slave agent should fix the
> problem (as per Jenkins' docs) .
>
> Do you have any other ideas on how to fix this?
>
> Thanks,
> Om
>
>
>
>>
>> >
>> > Thanks,
>> > Om
>> >
>> > [1]
>> > https://wiki.jenkins-
>> >
>> ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
>> > enkinsasaWindowsservice-
>> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>> >
>> >
>> >
>> > >
>> > >
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
>> > Of
>> > >> *OmPrakash Muppirala
>> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
>> > >> *To:* builds@apache.org; Gavin McDonald
>> > >> *Cc:* Erik de Bruin
>> > >>
>> > >> *Subject:* Re: [windows1] Pixelbender installation
>> > >>
>> > >>
>> > >>
>> > >> Thanks Gav!
>> > >>
>> > >> We did a bunch of tests to repro this issue on our side. One way we
>> > >> could reproduce this on our Jenkins installation was that if we ran
>> > >> the job as a service, we are getting the same error messages (AIF
>> > >> Internal exception).
>> > >>
>> > >> Jenkins docs says that for jobs that require Desktop Access (which
>> > >> Pixel Bender does), the root service process that is running the job
>> > >> needs to have the 'interactive flag' enabled in the Windows Service
>> > >> Manager. [1]
>> > >>
>> > >> One way this setting could have changed is if the way the windows
>> > >> slave starts was modified.
>> > >>
>> > >> Can you please take a look under the hood and see if you find
>> > >> something amiss?
>> > >>
>> > >> Thanks,
>> > >> Om
>> > >>
>> > >>
>> > >> [1]
>> > >> https://wiki.jenkins-
>> > ci.org/display/JENKINS/My+software+builds+on+my+
>> > >> computer+but+not+on+Jenkins
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
>> > >> <ga...@16degrees.com.au>
>> > >> wrote:
>> > >>
>> > >>
>> > >>
>> > >> > -----Original Message-----
>> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>> > >>
>> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
>> > >> > To: builds@apache.org
>> > >> > Cc: Gavin McDonald
>> > >>
>> > >> > Subject: Re: [windows1] Pixelbender installation
>> > >> >
>> > >> > 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...
>> > >>
>> > >>
>> > >> >
>> > >> > EdB
>> > >> >
>> > >> >
>> > >> >
>> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>> > >> > <bi...@gmail.com> wrote:
>> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>> > >> > <ga...@16degrees.com.au>wrote:
>> > >> > >
>> > >> > >> That's fine, I'll take a look. All I'm trying to get across is
>> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
>> > >> > >> slightly possible that the build is failing due to a coding
>> > >> > >> error? In other words, I've been blamed several times now for
>> > >> > >> breaking the build when I haven't been anywhere near the machine
>> > in question.
>> > >> > >>
>> > >> > >>
>> > >> > > The build does not fail on my or other committers' machines. It
>> > >> > > must be something specific to whats happening in Windows1. Sorry
>> > >> > > if it sounds like we are blaming you. We are just trying to
>> > >> > > troubleshoot and are running blind here.
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > >>
>> > >> > >>
>> > >> > >> Either way I'll look.
>> > >> > >>
>> > >> > >
>> > >> > > Thanks!
>> > >> > >
>> > >> > >
>> > >> > >>
>> > >> > >>
>> > >> > >> And so that we are clear, windows1 is not going away, it is very
>> > >> > >> heavily used, folks are always complaining it is down, so I'm
>> > >> > >> adding a 2ndwindows2 slave in addition to the windows1 slave.
>> > >> > >> Point is, you need to be configured to use both slaves for it to
>> > >> > >> work, or my time
>> > >> > building a 2ndmachine is wasted and you'll continue to complain
>> > >> > about
>> > >> the
>> > >> 1
>> > >> > st windows box being overloaded all the time.
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >
>> > >> > > We welcome the addition of a new windows slave, no doubt. Which
>> > >> > > is why we want to fix Windows1 first. Otherwise it will lead to
>> > >> > > more variables to troubleshoot.
>> > >> > >
>> > >> > > On that note, perhaps you can image windows1 and create windows2
>> > >> > > as a clone of it?
>> > >> > >
>> > >> > > Regards,
>> > >> > > Om
>> > >> > >
>> > >> > >
>> > >>
>> > >> > >> Gav.
>> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
>> > Behalf
>> > >> > Of
>> > >> > >> *OmPrakash Muppirala
>> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>> > >> > >> *To:* builds@apache.org
>> > >> > >> *Cc:* Gavin McDonald
>> > >> > >>
>> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >> Gavin,
>> > >> > >>
>> > >> > >> This issue is unrelated to Windows2 slave. Our long running job
>> > >> > >> on
>> > >> > >> Windows1 has started failing for the past few days. Can we
>> > >> > >> first fix that before we start working on Windows2?
>> > >> > >>
>> > >> > >> Or, is Windows2 a replacement for Windows1?
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >> Thanks,
>> > >> > >> Om
>> > >> > >>
>> > >> > >>
>> > >> > >>
>> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
>> > >> > >> <er...@ixsoftware.nl>
>> > >> > wrote:
>> > >> > >>
>> > >> > >> Ok, from the top of this thread:
>> > >> > >>
>> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
>> > >> > >>
>> > >> > >>
>> > >> > >> The build assumes Pixelbender is installed at:
>> > >> > >>
>> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
>> > >> > >> Utilities\ -
>> > >> > \
>> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>> > >> > >>
>> > >> > >> Is that still the correct path and does the application start
>> > >> > >> without errors when you launch it manually?"
>> > >> > >>
>> > >> > >> In another email in this thread I've listed the software that
>> > >> > >> needs to be on windows2.
>> > >> > >>
>> > >> > >> Is there a way to have all our builds run on either windows1 OR
>> > >> > >> windows2? Most of our jobs depend on files in the workspaces of
>> > >> > >> some of our other builds, in order to save on disk space and
>> build
>> > time.
>> > >> > >> If we remove these dependencies, we'd basically be forced to
>> > >> > >> copy each build into each other build.
>> > >> > >>
>> > >> > >> Since it is the weekend, I'll have limited time to work with
>> > >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
>> > >> > >> whatever needs checking/testing/adjusting.
>> > >> > >>
>> > >> > >> Please keep in mind that we are at a very important milestone
>> > >> > >> for our project, and with third party teams relying on our
>> > >> > >> nightly builds, we'd greatly appreciate a successful run of all
>> > >> > >> our jobs, on whatever slave works.
>> > >> > >>
>> > >> > >>
>> > >> > >> 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: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
>
>
> > -----Original Message-----
> > From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
> > OmPrakash Muppirala
> > Sent: Wednesday, 11 December 2013 10:51 AM
> > To: Gavin McDonald
> > Cc: builds@apache.org; Erik de Bruin
> > Subject: Re: [windows1] Pixelbender installation
> >
> > On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> > <bi...@gmail.com>wrote:
> >
> > > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> > <ga...@16degrees.com.au>wrote:
> > >
> > >> Interesting, and puzzling why, but interactive desktop flag was
> > >> turned off.
> > >>
> > >>
> > >>
> > >> I've now re-enabled it, please try again.
> > >>
> > >>
> > >>
> > >> Gav.
> > >>
> > >>
> > > Great! I have kicked off a build. Will report back in a bit.
> > >
> > > Was the windows1 slave started via JNLP or as a windows service?
> > > Starting via JNLP (using webstart) ensures that the interactive flag is
> set.
> > > Whereas if it is modified to be started as a service, you will have to
> > > manually turn the interactive flag (which sometimes may not propagate
> > > all the way down the process we try to invoke)
> > >
> > > If this does not work, will you be able to restart the slave via JNLP?
> > >
> > > Thanks,
> > > Om
> > >
> >
> > Yes, the build failed as I was typing my previous response.
> >
> > Any chance you could restart the windows1 Jenkins instance as just a JNLP
> > slave agent instead of modifying it into windows webservice? [1]
>
> I could, but I don't understand, this Jenkins slave has been running as a
> service since the day
> I built it years ago.
>
> Gav...
>
I don't understand too, but doing this in our test environment fixed the
problem, whereas manually setting the interactive flag did not. As you
mentioned earlier, something somewhere reset the interactive flag on the
root process. Unless you want to dig deeper and figure out what happened,
I think that restarting it to run as a JNLP slave agent should fix the
problem (as per Jenkins' docs) .
Do you have any other ideas on how to fix this?
Thanks,
Om
>
> >
> > Thanks,
> > Om
> >
> > [1]
> > https://wiki.jenkins-
> >
> ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
> > enkinsasaWindowsservice-
> > InstallSlaveasaWindowsservice%28require.NET2.0framework%29
> >
> >
> >
> > >
> > >
> > >>
> > >>
> > >>
> > >>
> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
> > Of
> > >> *OmPrakash Muppirala
> > >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> > >> *To:* builds@apache.org; Gavin McDonald
> > >> *Cc:* Erik de Bruin
> > >>
> > >> *Subject:* Re: [windows1] Pixelbender installation
> > >>
> > >>
> > >>
> > >> Thanks Gav!
> > >>
> > >> We did a bunch of tests to repro this issue on our side. One way we
> > >> could reproduce this on our Jenkins installation was that if we ran
> > >> the job as a service, we are getting the same error messages (AIF
> > >> Internal exception).
> > >>
> > >> Jenkins docs says that for jobs that require Desktop Access (which
> > >> Pixel Bender does), the root service process that is running the job
> > >> needs to have the 'interactive flag' enabled in the Windows Service
> > >> Manager. [1]
> > >>
> > >> One way this setting could have changed is if the way the windows
> > >> slave starts was modified.
> > >>
> > >> Can you please take a look under the hood and see if you find
> > >> something amiss?
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >>
> > >> [1]
> > >> https://wiki.jenkins-
> > ci.org/display/JENKINS/My+software+builds+on+my+
> > >> computer+but+not+on+Jenkins
> > >>
> > >>
> > >>
> > >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> > >> <ga...@16degrees.com.au>
> > >> wrote:
> > >>
> > >>
> > >>
> > >> > -----Original Message-----
> > >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> > >>
> > >> > Sent: Tuesday, 10 December 2013 7:14 PM
> > >> > To: builds@apache.org
> > >> > Cc: Gavin McDonald
> > >>
> > >> > Subject: Re: [windows1] Pixelbender installation
> > >> >
> > >> > 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...
> > >>
> > >>
> > >> >
> > >> > EdB
> > >> >
> > >> >
> > >> >
> > >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> > >> > <bi...@gmail.com> wrote:
> > >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> > >> > <ga...@16degrees.com.au>wrote:
> > >> > >
> > >> > >> That's fine, I'll take a look. All I'm trying to get across is
> > >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
> > >> > >> slightly possible that the build is failing due to a coding
> > >> > >> error? In other words, I've been blamed several times now for
> > >> > >> breaking the build when I haven't been anywhere near the machine
> > in question.
> > >> > >>
> > >> > >>
> > >> > > The build does not fail on my or other committers' machines. It
> > >> > > must be something specific to whats happening in Windows1. Sorry
> > >> > > if it sounds like we are blaming you. We are just trying to
> > >> > > troubleshoot and are running blind here.
> > >> > >
> > >> > >
> > >> > >
> > >> > >>
> > >> > >>
> > >> > >> Either way I'll look.
> > >> > >>
> > >> > >
> > >> > > Thanks!
> > >> > >
> > >> > >
> > >> > >>
> > >> > >>
> > >> > >> And so that we are clear, windows1 is not going away, it is very
> > >> > >> heavily used, folks are always complaining it is down, so I'm
> > >> > >> adding a 2ndwindows2 slave in addition to the windows1 slave.
> > >> > >> Point is, you need to be configured to use both slaves for it to
> > >> > >> work, or my time
> > >> > building a 2ndmachine is wasted and you'll continue to complain
> > >> > about
> > >> the
> > >> 1
> > >> > st windows box being overloaded all the time.
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >
> > >> > > We welcome the addition of a new windows slave, no doubt. Which
> > >> > > is why we want to fix Windows1 first. Otherwise it will lead to
> > >> > > more variables to troubleshoot.
> > >> > >
> > >> > > On that note, perhaps you can image windows1 and create windows2
> > >> > > as a clone of it?
> > >> > >
> > >> > > Regards,
> > >> > > Om
> > >> > >
> > >> > >
> > >>
> > >> > >> Gav.
> > >>
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
> > Behalf
> > >> > Of
> > >> > >> *OmPrakash Muppirala
> > >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> > >> > >> *To:* builds@apache.org
> > >> > >> *Cc:* Gavin McDonald
> > >> > >>
> > >> > >> *Subject:* Re: [windows1] Pixelbender installation
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> Gavin,
> > >> > >>
> > >> > >> This issue is unrelated to Windows2 slave. Our long running job
> > >> > >> on
> > >> > >> Windows1 has started failing for the past few days. Can we
> > >> > >> first fix that before we start working on Windows2?
> > >> > >>
> > >> > >> Or, is Windows2 a replacement for Windows1?
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> Thanks,
> > >> > >> Om
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> > >> > >> <er...@ixsoftware.nl>
> > >> > wrote:
> > >> > >>
> > >> > >> Ok, from the top of this thread:
> > >> > >>
> > >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> > >> > >>
> > >> > >>
> > >> > >> The build assumes Pixelbender is installed at:
> > >> > >>
> > >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
> > >> > >> Utilities\ -
> > >> > \
> > >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> > >> > >>
> > >> > >> Is that still the correct path and does the application start
> > >> > >> without errors when you launch it manually?"
> > >> > >>
> > >> > >> In another email in this thread I've listed the software that
> > >> > >> needs to be on windows2.
> > >> > >>
> > >> > >> Is there a way to have all our builds run on either windows1 OR
> > >> > >> windows2? Most of our jobs depend on files in the workspaces of
> > >> > >> some of our other builds, in order to save on disk space and
> build
> > time.
> > >> > >> If we remove these dependencies, we'd basically be forced to
> > >> > >> copy each build into each other build.
> > >> > >>
> > >> > >> Since it is the weekend, I'll have limited time to work with
> > >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
> > >> > >> whatever needs checking/testing/adjusting.
> > >> > >>
> > >> > >> Please keep in mind that we are at a very important milestone
> > >> > >> for our project, and with third party teams relying on our
> > >> > >> nightly builds, we'd greatly appreciate a successful run of all
> > >> > >> our jobs, on whatever slave works.
> > >> > >>
> > >> > >>
> > >> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of
> OmPrakash Muppirala
> Sent: Wednesday, 11 December 2013 10:51 AM
> To: Gavin McDonald
> Cc: builds@apache.org; Erik de Bruin
> Subject: Re: [windows1] Pixelbender installation
>
> On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
> <bi...@gmail.com>wrote:
>
> > On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald
> <ga...@16degrees.com.au>wrote:
> >
> >> Interesting, and puzzling why, but interactive desktop flag was
> >> turned off.
> >>
> >>
> >>
> >> I've now re-enabled it, please try again.
> >>
> >>
> >>
> >> Gav.
> >>
> >>
> > Great! I have kicked off a build. Will report back in a bit.
> >
> > Was the windows1 slave started via JNLP or as a windows service?
> > Starting via JNLP (using webstart) ensures that the interactive flag is
set.
> > Whereas if it is modified to be started as a service, you will have to
> > manually turn the interactive flag (which sometimes may not propagate
> > all the way down the process we try to invoke)
> >
> > If this does not work, will you be able to restart the slave via JNLP?
> >
> > Thanks,
> > Om
> >
>
> Yes, the build failed as I was typing my previous response.
>
> Any chance you could restart the windows1 Jenkins instance as just a JNLP
> slave agent instead of modifying it into windows webservice? [1]
I could, but I don't understand, this Jenkins slave has been running as a
service since the day
I built it years ago.
Gav...
>
> Thanks,
> Om
>
> [1]
> https://wiki.jenkins-
> ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJ
> enkinsasaWindowsservice-
> InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>
>
>
> >
> >
> >>
> >>
> >>
> >>
> >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
> Of
> >> *OmPrakash Muppirala
> >> *Sent:* Wednesday, 11 December 2013 9:36 AM
> >> *To:* builds@apache.org; Gavin McDonald
> >> *Cc:* Erik de Bruin
> >>
> >> *Subject:* Re: [windows1] Pixelbender installation
> >>
> >>
> >>
> >> Thanks Gav!
> >>
> >> We did a bunch of tests to repro this issue on our side. One way we
> >> could reproduce this on our Jenkins installation was that if we ran
> >> the job as a service, we are getting the same error messages (AIF
> >> Internal exception).
> >>
> >> Jenkins docs says that for jobs that require Desktop Access (which
> >> Pixel Bender does), the root service process that is running the job
> >> needs to have the 'interactive flag' enabled in the Windows Service
> >> Manager. [1]
> >>
> >> One way this setting could have changed is if the way the windows
> >> slave starts was modified.
> >>
> >> Can you please take a look under the hood and see if you find
> >> something amiss?
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >> [1]
> >> https://wiki.jenkins-
> ci.org/display/JENKINS/My+software+builds+on+my+
> >> computer+but+not+on+Jenkins
> >>
> >>
> >>
> >> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald
> >> <ga...@16degrees.com.au>
> >> wrote:
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> >>
> >> > Sent: Tuesday, 10 December 2013 7:14 PM
> >> > To: builds@apache.org
> >> > Cc: Gavin McDonald
> >>
> >> > Subject: Re: [windows1] Pixelbender installation
> >> >
> >> > 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...
> >>
> >>
> >> >
> >> > EdB
> >> >
> >> >
> >> >
> >> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> >> > <bi...@gmail.com> wrote:
> >> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> >> > <ga...@16degrees.com.au>wrote:
> >> > >
> >> > >> That's fine, I'll take a look. All I'm trying to get across is
> >> > >> that NOTHING HAS CHANGED on the Windows slave, so is it very
> >> > >> slightly possible that the build is failing due to a coding
> >> > >> error? In other words, I've been blamed several times now for
> >> > >> breaking the build when I haven't been anywhere near the machine
> in question.
> >> > >>
> >> > >>
> >> > > The build does not fail on my or other committers' machines. It
> >> > > must be something specific to whats happening in Windows1. Sorry
> >> > > if it sounds like we are blaming you. We are just trying to
> >> > > troubleshoot and are running blind here.
> >> > >
> >> > >
> >> > >
> >> > >>
> >> > >>
> >> > >> Either way I'll look.
> >> > >>
> >> > >
> >> > > Thanks!
> >> > >
> >> > >
> >> > >>
> >> > >>
> >> > >> And so that we are clear, windows1 is not going away, it is very
> >> > >> heavily used, folks are always complaining it is down, so I'm
> >> > >> adding a 2ndwindows2 slave in addition to the windows1 slave.
> >> > >> Point is, you need to be configured to use both slaves for it to
> >> > >> work, or my time
> >> > building a 2ndmachine is wasted and you'll continue to complain
> >> > about
> >> the
> >> 1
> >> > st windows box being overloaded all the time.
> >> > >>
> >> > >>
> >> > >>
> >> > >
> >> > > We welcome the addition of a new windows slave, no doubt. Which
> >> > > is why we want to fix Windows1 first. Otherwise it will lead to
> >> > > more variables to troubleshoot.
> >> > >
> >> > > On that note, perhaps you can image windows1 and create windows2
> >> > > as a clone of it?
> >> > >
> >> > > Regards,
> >> > > Om
> >> > >
> >> > >
> >>
> >> > >> Gav.
> >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On
> Behalf
> >> > Of
> >> > >> *OmPrakash Muppirala
> >> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >> > >> *To:* builds@apache.org
> >> > >> *Cc:* Gavin McDonald
> >> > >>
> >> > >> *Subject:* Re: [windows1] Pixelbender installation
> >> > >>
> >> > >>
> >> > >>
> >> > >> Gavin,
> >> > >>
> >> > >> This issue is unrelated to Windows2 slave. Our long running job
> >> > >> on
> >> > >> Windows1 has started failing for the past few days. Can we
> >> > >> first fix that before we start working on Windows2?
> >> > >>
> >> > >> Or, is Windows2 a replacement for Windows1?
> >> > >>
> >> > >>
> >> > >>
> >> > >> Thanks,
> >> > >> Om
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin
> >> > >> <er...@ixsoftware.nl>
> >> > wrote:
> >> > >>
> >> > >> Ok, from the top of this thread:
> >> > >>
> >> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> >> > >>
> >> > >>
> >> > >> The build assumes Pixelbender is installed at:
> >> > >>
> >> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe
> >> > >> Utilities\ -
> >> > \
> >> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> >> > >>
> >> > >> Is that still the correct path and does the application start
> >> > >> without errors when you launch it manually?"
> >> > >>
> >> > >> In another email in this thread I've listed the software that
> >> > >> needs to be on windows2.
> >> > >>
> >> > >> Is there a way to have all our builds run on either windows1 OR
> >> > >> windows2? Most of our jobs depend on files in the workspaces of
> >> > >> some of our other builds, in order to save on disk space and build
> time.
> >> > >> If we remove these dependencies, we'd basically be forced to
> >> > >> copy each build into each other build.
> >> > >>
> >> > >> Since it is the weekend, I'll have limited time to work with
> >> > >> you, sorry. Next Monday I'll be glad to check/test/adjust
> >> > >> whatever needs checking/testing/adjusting.
> >> > >>
> >> > >> Please keep in mind that we are at a very important milestone
> >> > >> for our project, and with third party teams relying on our
> >> > >> nightly builds, we'd greatly appreciate a successful run of all
> >> > >> our jobs, on whatever slave works.
> >> > >>
> >> > >>
> >> > >> 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: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 3:46 PM, OmPrakash Muppirala
<bi...@gmail.com>wrote:
> On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
>
>> Interesting, and puzzling why, but interactive desktop flag was turned
>> off.
>>
>>
>>
>> I’ve now re-enabled it, please try again.
>>
>>
>>
>> Gav…
>>
>>
> Great! I have kicked off a build. Will report back in a bit.
>
> Was the windows1 slave started via JNLP or as a windows service? Starting
> via JNLP (using webstart) ensures that the interactive flag is set.
> Whereas if it is modified to be started as a service, you will have to
> manually turn the interactive flag (which sometimes may not propagate all
> the way down the process we try to invoke)
>
> If this does not work, will you be able to restart the slave via JNLP?
>
> Thanks,
> Om
>
Yes, the build failed as I was typing my previous response.
Any chance you could restart the windows1 Jenkins instance as just a JNLP
slave agent instead of modifying it into windows webservice? [1]
Thanks,
Om
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29
>
>
>>
>>
>>
>>
>> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf Of *OmPrakash
>> Muppirala
>> *Sent:* Wednesday, 11 December 2013 9:36 AM
>> *To:* builds@apache.org; Gavin McDonald
>> *Cc:* Erik de Bruin
>>
>> *Subject:* Re: [windows1] Pixelbender installation
>>
>>
>>
>> Thanks Gav!
>>
>> We did a bunch of tests to repro this issue on our side. One way we
>> could reproduce this on our Jenkins installation was that if we ran the job
>> as a service, we are getting the same error messages (AIF Internal
>> exception).
>>
>> Jenkins docs says that for jobs that require Desktop Access (which Pixel
>> Bender does), the root service process that is running the job needs to
>> have the 'interactive flag' enabled in the Windows Service Manager. [1]
>>
>> One way this setting could have changed is if the way the windows slave
>> starts was modified.
>>
>> Can you please take a look under the hood and see if you find something
>> amiss?
>>
>> Thanks,
>> Om
>>
>>
>> [1]
>> https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+computer+but+not+on+Jenkins
>>
>>
>>
>> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald <ga...@16degrees.com.au>
>> wrote:
>>
>>
>>
>> > -----Original Message-----
>> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>>
>> > Sent: Tuesday, 10 December 2013 7:14 PM
>> > To: builds@apache.org
>> > Cc: Gavin McDonald
>>
>> > Subject: Re: [windows1] Pixelbender installation
>> >
>> > 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...
>>
>>
>> >
>> > EdB
>> >
>> >
>> >
>> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
>> > <bi...@gmail.com> wrote:
>> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
>> > <ga...@16degrees.com.au>wrote:
>> > >
>> > >> That's fine, I'll take a look. All I'm trying to get across is that
>> > >> NOTHING HAS CHANGED on the Windows slave, so is it very slightly
>> > >> possible that the build is failing due to a coding error? In other
>> > >> words, I've been blamed several times now for breaking the build when
>> > >> I haven't been anywhere near the machine in question.
>> > >>
>> > >>
>> > > The build does not fail on my or other committers' machines. It must
>> > > be something specific to whats happening in Windows1. Sorry if it
>> > > sounds like we are blaming you. We are just trying to troubleshoot
>> > > and are running blind here.
>> > >
>> > >
>> > >
>> > >>
>> > >>
>> > >> Either way I'll look.
>> > >>
>> > >
>> > > Thanks!
>> > >
>> > >
>> > >>
>> > >>
>> > >> And so that we are clear, windows1 is not going away, it is very
>> > >> heavily used, folks are always complaining it is down, so I'm adding
>> > >> a 2ndwindows2 slave in addition to the windows1 slave. Point is, you
>> > >> need to be configured to use both slaves for it to work, or my time
>> > building a 2ndmachine is wasted and you'll continue to complain about
>> the
>> 1
>> > st windows box being overloaded all the time.
>> > >>
>> > >>
>> > >>
>> > >
>> > > We welcome the addition of a new windows slave, no doubt. Which is
>> > > why we want to fix Windows1 first. Otherwise it will lead to more
>> > > variables to troubleshoot.
>> > >
>> > > On that note, perhaps you can image windows1 and create windows2 as a
>> > > clone of it?
>> > >
>> > > Regards,
>> > > Om
>> > >
>> > >
>>
>> > >> Gav.
>>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
>> > Of
>> > >> *OmPrakash Muppirala
>> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
>> > >> *To:* builds@apache.org
>> > >> *Cc:* Gavin McDonald
>> > >>
>> > >> *Subject:* Re: [windows1] Pixelbender installation
>> > >>
>> > >>
>> > >>
>> > >> Gavin,
>> > >>
>> > >> This issue is unrelated to Windows2 slave. Our long running job on
>> > >> Windows1 has started failing for the past few days. Can we first fix
>> > >> that before we start working on Windows2?
>> > >>
>> > >> Or, is Windows2 a replacement for Windows1?
>> > >>
>> > >>
>> > >>
>> > >> Thanks,
>> > >> Om
>> > >>
>> > >>
>> > >>
>> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl>
>> > wrote:
>> > >>
>> > >> Ok, from the top of this thread:
>> > >>
>> > >> "The build on windows1 is failing on the 'Pixelbender' task:
>> > >>
>> > >>
>> > >> The build assumes Pixelbender is installed at:
>> > >>
>> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -
>> > \
>> > >> CS5/Pixel\ Bender\ Toolkit\ 2
>> > >>
>> > >> Is that still the correct path and does the application start without
>> > >> errors when you launch it manually?"
>> > >>
>> > >> In another email in this thread I've listed the software that needs
>> > >> to be on windows2.
>> > >>
>> > >> Is there a way to have all our builds run on either windows1 OR
>> > >> windows2? Most of our jobs depend on files in the workspaces of some
>> > >> of our other builds, in order to save on disk space and build time.
>> > >> If we remove these dependencies, we'd basically be forced to copy
>> > >> each build into each other build.
>> > >>
>> > >> Since it is the weekend, I'll have limited time to work with you,
>> > >> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
>> > >> checking/testing/adjusting.
>> > >>
>> > >> Please keep in mind that we are at a very important milestone for our
>> > >> project, and with third party teams relying on our nightly builds,
>> > >> we'd greatly appreciate a successful run of all our jobs, on whatever
>> > >> slave works.
>> > >>
>> > >>
>> > >> 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: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Tue, Dec 10, 2013 at 3:39 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
> Interesting, and puzzling why, but interactive desktop flag was turned off.
>
>
>
> I’ve now re-enabled it, please try again.
>
>
>
> Gav…
>
>
Great! I have kicked off a build. Will report back in a bit.
Was the windows1 slave started via JNLP or as a windows service? Starting
via JNLP (using webstart) ensures that the interactive flag is set.
Whereas if it is modified to be started as a service, you will have to
manually turn the interactive flag (which sometimes may not propagate all
the way down the process we try to invoke)
If this does not work, will you be able to restart the slave via JNLP?
Thanks,
Om
>
>
>
>
> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf Of *OmPrakash
> Muppirala
> *Sent:* Wednesday, 11 December 2013 9:36 AM
> *To:* builds@apache.org; Gavin McDonald
> *Cc:* Erik de Bruin
>
> *Subject:* Re: [windows1] Pixelbender installation
>
>
>
> Thanks Gav!
>
> We did a bunch of tests to repro this issue on our side. One way we could
> reproduce this on our Jenkins installation was that if we ran the job as a
> service, we are getting the same error messages (AIF Internal exception).
>
> Jenkins docs says that for jobs that require Desktop Access (which Pixel
> Bender does), the root service process that is running the job needs to
> have the 'interactive flag' enabled in the Windows Service Manager. [1]
>
> One way this setting could have changed is if the way the windows slave
> starts was modified.
>
> Can you please take a look under the hood and see if you find something
> amiss?
>
> Thanks,
> Om
>
>
> [1]
> https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+computer+but+not+on+Jenkins
>
>
>
> On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald <ga...@16degrees.com.au>
> wrote:
>
>
>
> > -----Original Message-----
> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
>
> > Sent: Tuesday, 10 December 2013 7:14 PM
> > To: builds@apache.org
> > Cc: Gavin McDonald
>
> > Subject: Re: [windows1] Pixelbender installation
> >
> > 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...
>
>
> >
> > EdB
> >
> >
> >
> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> > <bi...@gmail.com> wrote:
> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> > <ga...@16degrees.com.au>wrote:
> > >
> > >> That's fine, I'll take a look. All I'm trying to get across is that
> > >> NOTHING HAS CHANGED on the Windows slave, so is it very slightly
> > >> possible that the build is failing due to a coding error? In other
> > >> words, I've been blamed several times now for breaking the build when
> > >> I haven't been anywhere near the machine in question.
> > >>
> > >>
> > > The build does not fail on my or other committers' machines. It must
> > > be something specific to whats happening in Windows1. Sorry if it
> > > sounds like we are blaming you. We are just trying to troubleshoot
> > > and are running blind here.
> > >
> > >
> > >
> > >>
> > >>
> > >> Either way I'll look.
> > >>
> > >
> > > Thanks!
> > >
> > >
> > >>
> > >>
> > >> And so that we are clear, windows1 is not going away, it is very
> > >> heavily used, folks are always complaining it is down, so I'm adding
> > >> a 2ndwindows2 slave in addition to the windows1 slave. Point is, you
> > >> need to be configured to use both slaves for it to work, or my time
> > building a 2ndmachine is wasted and you'll continue to complain about the
> 1
> > st windows box being overloaded all the time.
> > >>
> > >>
> > >>
> > >
> > > We welcome the addition of a new windows slave, no doubt. Which is
> > > why we want to fix Windows1 first. Otherwise it will lead to more
> > > variables to troubleshoot.
> > >
> > > On that note, perhaps you can image windows1 and create windows2 as a
> > > clone of it?
> > >
> > > Regards,
> > > Om
> > >
> > >
>
> > >> Gav.
>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
> > Of
> > >> *OmPrakash Muppirala
> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> > >> *To:* builds@apache.org
> > >> *Cc:* Gavin McDonald
> > >>
> > >> *Subject:* Re: [windows1] Pixelbender installation
> > >>
> > >>
> > >>
> > >> Gavin,
> > >>
> > >> This issue is unrelated to Windows2 slave. Our long running job on
> > >> Windows1 has started failing for the past few days. Can we first fix
> > >> that before we start working on Windows2?
> > >>
> > >> Or, is Windows2 a replacement for Windows1?
> > >>
> > >>
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >>
> > >>
> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl>
> > wrote:
> > >>
> > >> Ok, from the top of this thread:
> > >>
> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> > >>
> > >>
> > >> The build assumes Pixelbender is installed at:
> > >>
> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -
> > \
> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> > >>
> > >> Is that still the correct path and does the application start without
> > >> errors when you launch it manually?"
> > >>
> > >> In another email in this thread I've listed the software that needs
> > >> to be on windows2.
> > >>
> > >> Is there a way to have all our builds run on either windows1 OR
> > >> windows2? Most of our jobs depend on files in the workspaces of some
> > >> of our other builds, in order to save on disk space and build time.
> > >> If we remove these dependencies, we'd basically be forced to copy
> > >> each build into each other build.
> > >>
> > >> Since it is the weekend, I'll have limited time to work with you,
> > >> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> > >> checking/testing/adjusting.
> > >>
> > >> Please keep in mind that we are at a very important milestone for our
> > >> project, and with third party teams relying on our nightly builds,
> > >> we'd greatly appreciate a successful run of all our jobs, on whatever
> > >> slave works.
> > >>
> > >>
> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
Interesting, and puzzling why, but interactive desktop flag was turned off.
I've now re-enabled it, please try again.
Gav.
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Wednesday, 11 December 2013 9:36 AM
To: builds@apache.org; Gavin McDonald
Cc: Erik de Bruin
Subject: Re: [windows1] Pixelbender installation
Thanks Gav!
We did a bunch of tests to repro this issue on our side. One way we could
reproduce this on our Jenkins installation was that if we ran the job as a
service, we are getting the same error messages (AIF Internal exception).
Jenkins docs says that for jobs that require Desktop Access (which Pixel
Bender does), the root service process that is running the job needs to have
the 'interactive flag' enabled in the Windows Service Manager. [1]
One way this setting could have changed is if the way the windows slave
starts was modified.
Can you please take a look under the hood and see if you find something
amiss?
Thanks,
Om
[1]
https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+compute
r+but+not+on+Jenkins
On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald <gavin@16degrees.com.au
<ma...@16degrees.com.au> > wrote:
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl <ma...@ixsoftware.nl>
]
> Sent: Tuesday, 10 December 2013 7:14 PM
> To: builds@apache.org <ma...@apache.org>
> Cc: Gavin McDonald
> Subject: Re: [windows1] Pixelbender installation
>
> 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...
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> <bigosmallm@gmail.com <ma...@gmail.com> > wrote:
> > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> <gavin@16degrees.com.au <ma...@16degrees.com.au> >wrote:
> >
> >> That's fine, I'll take a look. All I'm trying to get across is that
> >> NOTHING HAS CHANGED on the Windows slave, so is it very slightly
> >> possible that the build is failing due to a coding error? In other
> >> words, I've been blamed several times now for breaking the build when
> >> I haven't been anywhere near the machine in question.
> >>
> >>
> > The build does not fail on my or other committers' machines. It must
> > be something specific to whats happening in Windows1. Sorry if it
> > sounds like we are blaming you. We are just trying to troubleshoot
> > and are running blind here.
> >
> >
> >
> >>
> >>
> >> Either way I'll look.
> >>
> >
> > Thanks!
> >
> >
> >>
> >>
> >> And so that we are clear, windows1 is not going away, it is very
> >> heavily used, folks are always complaining it is down, so I'm adding
> >> a 2ndwindows2 slave in addition to the windows1 slave. Point is, you
> >> need to be configured to use both slaves for it to work, or my time
> building a 2ndmachine is wasted and you'll continue to complain about the
1
> st windows box being overloaded all the time.
> >>
> >>
> >>
> >
> > We welcome the addition of a new windows slave, no doubt. Which is
> > why we want to fix Windows1 first. Otherwise it will lead to more
> > variables to troubleshoot.
> >
> > On that note, perhaps you can image windows1 and create windows2 as a
> > clone of it?
> >
> > Regards,
> > Om
> >
> >
> >> Gav.
> >>
> >>
> >>
> >>
> >>
> >> *From:* omuppi1@gmail.com <ma...@gmail.com>
[mailto:omuppi1@gmail.com <ma...@gmail.com> ] *On Behalf
> Of
> >> *OmPrakash Muppirala
> >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >> *To:* builds@apache.org <ma...@apache.org>
> >> *Cc:* Gavin McDonald
> >>
> >> *Subject:* Re: [windows1] Pixelbender installation
> >>
> >>
> >>
> >> Gavin,
> >>
> >> This issue is unrelated to Windows2 slave. Our long running job on
> >> Windows1 has started failing for the past few days. Can we first fix
> >> that before we start working on Windows2?
> >>
> >> Or, is Windows2 a replacement for Windows1?
> >>
> >>
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>
> >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <erik@ixsoftware.nl
<ma...@ixsoftware.nl> >
> wrote:
> >>
> >> Ok, from the top of this thread:
> >>
> >> "The build on windows1 is failing on the 'Pixelbender' task:
> >>
> >>
> >> The build assumes Pixelbender is installed at:
> >>
> >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -
> \
> >> CS5/Pixel\ Bender\ Toolkit\ 2
> >>
> >> Is that still the correct path and does the application start without
> >> errors when you launch it manually?"
> >>
> >> In another email in this thread I've listed the software that needs
> >> to be on windows2.
> >>
> >> Is there a way to have all our builds run on either windows1 OR
> >> windows2? Most of our jobs depend on files in the workspaces of some
> >> of our other builds, in order to save on disk space and build time.
> >> If we remove these dependencies, we'd basically be forced to copy
> >> each build into each other build.
> >>
> >> Since it is the weekend, I'll have limited time to work with you,
> >> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> >> checking/testing/adjusting.
> >>
> >> Please keep in mind that we are at a very important milestone for our
> >> project, and with third party teams relying on our nightly builds,
> >> we'd greatly appreciate a successful run of all our jobs, on whatever
> >> slave works.
> >>
> >>
> >> EdB
> >>
> >>
> >>
> >> --
> >> Ix Multimedia Software
> >>
> >> Jan Luykenstraat 27
> >> 3521 VB Utrecht
> >>
> >> T. 06-51952295
> >> I. www.ixsoftware.nl <http://www.ixsoftware.nl>
> >>
> >>
> >>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl <http://www.ixsoftware.nl>
Re: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Thanks Gav!
We did a bunch of tests to repro this issue on our side. One way we could
reproduce this on our Jenkins installation was that if we ran the job as a
service, we are getting the same error messages (AIF Internal exception).
Jenkins docs says that for jobs that require Desktop Access (which Pixel
Bender does), the root service process that is running the job needs to
have the 'interactive flag' enabled in the Windows Service Manager. [1]
One way this setting could have changed is if the way the windows slave
starts was modified.
Can you please take a look under the hood and see if you find something
amiss?
Thanks,
Om
[1]
https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+computer+but+not+on+Jenkins
On Tue, Dec 10, 2013 at 2:11 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
>
>
> > -----Original Message-----
> > From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> > Sent: Tuesday, 10 December 2013 7:14 PM
> > To: builds@apache.org
> > Cc: Gavin McDonald
> > Subject: Re: [windows1] Pixelbender installation
> >
> > 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...
>
> >
> > EdB
> >
> >
> >
> > On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> > <bi...@gmail.com> wrote:
> > > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> > <ga...@16degrees.com.au>wrote:
> > >
> > >> That's fine, I'll take a look. All I'm trying to get across is that
> > >> NOTHING HAS CHANGED on the Windows slave, so is it very slightly
> > >> possible that the build is failing due to a coding error? In other
> > >> words, I've been blamed several times now for breaking the build when
> > >> I haven't been anywhere near the machine in question.
> > >>
> > >>
> > > The build does not fail on my or other committers' machines. It must
> > > be something specific to whats happening in Windows1. Sorry if it
> > > sounds like we are blaming you. We are just trying to troubleshoot
> > > and are running blind here.
> > >
> > >
> > >
> > >>
> > >>
> > >> Either way I'll look.
> > >>
> > >
> > > Thanks!
> > >
> > >
> > >>
> > >>
> > >> And so that we are clear, windows1 is not going away, it is very
> > >> heavily used, folks are always complaining it is down, so I'm adding
> > >> a 2ndwindows2 slave in addition to the windows1 slave. Point is, you
> > >> need to be configured to use both slaves for it to work, or my time
> > building a 2ndmachine is wasted and you'll continue to complain about the
> 1
> > st windows box being overloaded all the time.
> > >>
> > >>
> > >>
> > >
> > > We welcome the addition of a new windows slave, no doubt. Which is
> > > why we want to fix Windows1 first. Otherwise it will lead to more
> > > variables to troubleshoot.
> > >
> > > On that note, perhaps you can image windows1 and create windows2 as a
> > > clone of it?
> > >
> > > Regards,
> > > Om
> > >
> > >
> > >> Gav.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
> > Of
> > >> *OmPrakash Muppirala
> > >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> > >> *To:* builds@apache.org
> > >> *Cc:* Gavin McDonald
> > >>
> > >> *Subject:* Re: [windows1] Pixelbender installation
> > >>
> > >>
> > >>
> > >> Gavin,
> > >>
> > >> This issue is unrelated to Windows2 slave. Our long running job on
> > >> Windows1 has started failing for the past few days. Can we first fix
> > >> that before we start working on Windows2?
> > >>
> > >> Or, is Windows2 a replacement for Windows1?
> > >>
> > >>
> > >>
> > >> Thanks,
> > >> Om
> > >>
> > >>
> > >>
> > >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl>
> > wrote:
> > >>
> > >> Ok, from the top of this thread:
> > >>
> > >> "The build on windows1 is failing on the 'Pixelbender' task:
> > >>
> > >>
> > >> The build assumes Pixelbender is installed at:
> > >>
> > >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -
> > \
> > >> CS5/Pixel\ Bender\ Toolkit\ 2
> > >>
> > >> Is that still the correct path and does the application start without
> > >> errors when you launch it manually?"
> > >>
> > >> In another email in this thread I've listed the software that needs
> > >> to be on windows2.
> > >>
> > >> Is there a way to have all our builds run on either windows1 OR
> > >> windows2? Most of our jobs depend on files in the workspaces of some
> > >> of our other builds, in order to save on disk space and build time.
> > >> If we remove these dependencies, we'd basically be forced to copy
> > >> each build into each other build.
> > >>
> > >> Since it is the weekend, I'll have limited time to work with you,
> > >> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> > >> checking/testing/adjusting.
> > >>
> > >> Please keep in mind that we are at a very important milestone for our
> > >> project, and with third party teams relying on our nightly builds,
> > >> we'd greatly appreciate a successful run of all our jobs, on whatever
> > >> slave works.
> > >>
> > >>
> > >> 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: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> Sent: Tuesday, 10 December 2013 7:14 PM
> To: builds@apache.org
> Cc: Gavin McDonald
> Subject: Re: [windows1] Pixelbender installation
>
> 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...
>
> EdB
>
>
>
> On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
> <bi...@gmail.com> wrote:
> > On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald
> <ga...@16degrees.com.au>wrote:
> >
> >> That's fine, I'll take a look. All I'm trying to get across is that
> >> NOTHING HAS CHANGED on the Windows slave, so is it very slightly
> >> possible that the build is failing due to a coding error? In other
> >> words, I've been blamed several times now for breaking the build when
> >> I haven't been anywhere near the machine in question.
> >>
> >>
> > The build does not fail on my or other committers' machines. It must
> > be something specific to whats happening in Windows1. Sorry if it
> > sounds like we are blaming you. We are just trying to troubleshoot
> > and are running blind here.
> >
> >
> >
> >>
> >>
> >> Either way I'll look.
> >>
> >
> > Thanks!
> >
> >
> >>
> >>
> >> And so that we are clear, windows1 is not going away, it is very
> >> heavily used, folks are always complaining it is down, so I'm adding
> >> a 2ndwindows2 slave in addition to the windows1 slave. Point is, you
> >> need to be configured to use both slaves for it to work, or my time
> building a 2ndmachine is wasted and you'll continue to complain about the
1
> st windows box being overloaded all the time.
> >>
> >>
> >>
> >
> > We welcome the addition of a new windows slave, no doubt. Which is
> > why we want to fix Windows1 first. Otherwise it will lead to more
> > variables to troubleshoot.
> >
> > On that note, perhaps you can image windows1 and create windows2 as a
> > clone of it?
> >
> > Regards,
> > Om
> >
> >
> >> Gav.
> >>
> >>
> >>
> >>
> >>
> >> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf
> Of
> >> *OmPrakash Muppirala
> >> *Sent:* Tuesday, 10 December 2013 7:28 AM
> >> *To:* builds@apache.org
> >> *Cc:* Gavin McDonald
> >>
> >> *Subject:* Re: [windows1] Pixelbender installation
> >>
> >>
> >>
> >> Gavin,
> >>
> >> This issue is unrelated to Windows2 slave. Our long running job on
> >> Windows1 has started failing for the past few days. Can we first fix
> >> that before we start working on Windows2?
> >>
> >> Or, is Windows2 a replacement for Windows1?
> >>
> >>
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>
> >> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl>
> wrote:
> >>
> >> Ok, from the top of this thread:
> >>
> >> "The build on windows1 is failing on the 'Pixelbender' task:
> >>
> >>
> >> The build assumes Pixelbender is installed at:
> >>
> >> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -
> \
> >> CS5/Pixel\ Bender\ Toolkit\ 2
> >>
> >> Is that still the correct path and does the application start without
> >> errors when you launch it manually?"
> >>
> >> In another email in this thread I've listed the software that needs
> >> to be on windows2.
> >>
> >> Is there a way to have all our builds run on either windows1 OR
> >> windows2? Most of our jobs depend on files in the workspaces of some
> >> of our other builds, in order to save on disk space and build time.
> >> If we remove these dependencies, we'd basically be forced to copy
> >> each build into each other build.
> >>
> >> Since it is the weekend, I'll have limited time to work with you,
> >> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> >> checking/testing/adjusting.
> >>
> >> Please keep in mind that we are at a very important milestone for our
> >> project, and with third party teams relying on our nightly builds,
> >> we'd greatly appreciate a successful run of all our jobs, on whatever
> >> slave works.
> >>
> >>
> >> 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: [windows1] Pixelbender installation
Posted by Erik de Bruin <er...@ixsoftware.nl>.
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!
EdB
On Mon, Dec 9, 2013 at 11:16 PM, OmPrakash Muppirala
<bi...@gmail.com> wrote:
> On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
>
>> That’s fine, I’ll take a look. All I’m trying to get across is that
>> NOTHING HAS CHANGED on the Windows slave, so is it very slightly possible
>> that the build is failing due to a coding error? In other words, I’ve been
>> blamed several times now for breaking the build when I haven’t been
>> anywhere near the machine in question.
>>
>>
> The build does not fail on my or other committers' machines. It must be
> something specific to whats happening in Windows1. Sorry if it sounds like
> we are blaming you. We are just trying to troubleshoot and are running
> blind here.
>
>
>
>>
>>
>> Either way I’ll look.
>>
>
> Thanks!
>
>
>>
>>
>> And so that we are clear, windows1 is not going away, it is very heavily
>> used, folks are always complaining it is down, so I’m adding a 2ndwindows2 slave in addition to the windows1 slave. Point is, you need to be
>> configured to use both slaves for it to work, or my time building a 2ndmachine is wasted and you’ll continue to complain about the 1
>> st windows box being overloaded all the time.
>>
>>
>>
>
> We welcome the addition of a new windows slave, no doubt. Which is why we
> want to fix Windows1 first. Otherwise it will lead to more variables to
> troubleshoot.
>
> On that note, perhaps you can image windows1 and create windows2 as a clone
> of it?
>
> Regards,
> Om
>
>
>> Gav…
>>
>>
>>
>>
>>
>> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf Of *OmPrakash
>> Muppirala
>> *Sent:* Tuesday, 10 December 2013 7:28 AM
>> *To:* builds@apache.org
>> *Cc:* Gavin McDonald
>>
>> *Subject:* Re: [windows1] Pixelbender installation
>>
>>
>>
>> Gavin,
>>
>> This issue is unrelated to Windows2 slave. Our long running job on
>> Windows1 has started failing for the past few days. Can we first fix that
>> before we start working on Windows2?
>>
>> Or, is Windows2 a replacement for Windows1?
>>
>>
>>
>> Thanks,
>> Om
>>
>>
>>
>> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>
>> Ok, from the top of this thread:
>>
>> "The build on windows1 is failing on the 'Pixelbender' task:
>>
>>
>> The build assumes Pixelbender is installed at:
>>
>> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
>> CS5/Pixel\ Bender\ Toolkit\ 2
>>
>> Is that still the correct path and does the application start without
>> errors when you launch it manually?"
>>
>> In another email in this thread I've listed the software that needs to
>> be on windows2.
>>
>> Is there a way to have all our builds run on either windows1 OR
>> windows2? Most of our jobs depend on files in the workspaces of some
>> of our other builds, in order to save on disk space and build time. If
>> we remove these dependencies, we'd basically be forced to copy each
>> build into each other build.
>>
>> Since it is the weekend, I'll have limited time to work with you,
>> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
>> checking/testing/adjusting.
>>
>> Please keep in mind that we are at a very important milestone for our
>> project, and with third party teams relying on our nightly builds,
>> we'd greatly appreciate a successful run of all our jobs, on whatever
>> slave works.
>>
>>
>> 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: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
On Mon, Dec 9, 2013 at 2:02 PM, Gavin McDonald <ga...@16degrees.com.au>wrote:
> That’s fine, I’ll take a look. All I’m trying to get across is that
> NOTHING HAS CHANGED on the Windows slave, so is it very slightly possible
> that the build is failing due to a coding error? In other words, I’ve been
> blamed several times now for breaking the build when I haven’t been
> anywhere near the machine in question.
>
>
The build does not fail on my or other committers' machines. It must be
something specific to whats happening in Windows1. Sorry if it sounds like
we are blaming you. We are just trying to troubleshoot and are running
blind here.
>
>
> Either way I’ll look.
>
Thanks!
>
>
> And so that we are clear, windows1 is not going away, it is very heavily
> used, folks are always complaining it is down, so I’m adding a 2ndwindows2 slave in addition to the windows1 slave. Point is, you need to be
> configured to use both slaves for it to work, or my time building a 2ndmachine is wasted and you’ll continue to complain about the 1
> st windows box being overloaded all the time.
>
>
>
We welcome the addition of a new windows slave, no doubt. Which is why we
want to fix Windows1 first. Otherwise it will lead to more variables to
troubleshoot.
On that note, perhaps you can image windows1 and create windows2 as a clone
of it?
Regards,
Om
> Gav…
>
>
>
>
>
> *From:* omuppi1@gmail.com [mailto:omuppi1@gmail.com] *On Behalf Of *OmPrakash
> Muppirala
> *Sent:* Tuesday, 10 December 2013 7:28 AM
> *To:* builds@apache.org
> *Cc:* Gavin McDonald
>
> *Subject:* Re: [windows1] Pixelbender installation
>
>
>
> Gavin,
>
> This issue is unrelated to Windows2 slave. Our long running job on
> Windows1 has started failing for the past few days. Can we first fix that
> before we start working on Windows2?
>
> Or, is Windows2 a replacement for Windows1?
>
>
>
> Thanks,
> Om
>
>
>
> On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
> Ok, from the top of this thread:
>
> "The build on windows1 is failing on the 'Pixelbender' task:
>
>
> The build assumes Pixelbender is installed at:
>
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
> CS5/Pixel\ Bender\ Toolkit\ 2
>
> Is that still the correct path and does the application start without
> errors when you launch it manually?"
>
> In another email in this thread I've listed the software that needs to
> be on windows2.
>
> Is there a way to have all our builds run on either windows1 OR
> windows2? Most of our jobs depend on files in the workspaces of some
> of our other builds, in order to save on disk space and build time. If
> we remove these dependencies, we'd basically be forced to copy each
> build into each other build.
>
> Since it is the weekend, I'll have limited time to work with you,
> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> checking/testing/adjusting.
>
> Please keep in mind that we are at a very important milestone for our
> project, and with third party teams relying on our nightly builds,
> we'd greatly appreciate a successful run of all our jobs, on whatever
> slave works.
>
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
>
>
Re: [windows1] Pixelbender installation
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> All I'm trying to get across is that NOTHING HAS CHANGED on the Windows slave, so is it very slightly possible that the
> build is failing due to a coding error?
There not been any recent change to the build scripts or config that I can see that could cause this error. The current code in GIt can be checked out and compiled locally and our external Jenkins windows box (used to check builds for multiple versions of FP/AIR) also has no issues.
> In other words, I've been blamed several times now for breaking the build
We're just trying to find out what the issue is, and it currently that seems more likely to be an issue with windows1 at this point. It may be that someone made some other config change or some resource limit is being hit?
> Either way I'll look.
Thanks much appreciated.
Justin
RE: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
That's fine, I'll take a look. All I'm trying to get across is that NOTHING
HAS CHANGED on the Windows slave, so is it very slightly possible that the
build is failing due to a coding error? In other words, I've been blamed
several times now for breaking the build when I haven't been anywhere near
the machine in question.
Either way I'll look.
And so that we are clear, windows1 is not going away, it is very heavily
used, folks are always complaining it is down, so I'm adding a 2nd windows2
slave in addition to the windows1 slave. Point is, you need to be configured
to use both slaves for it to work, or my time building a 2nd machine is
wasted and you'll continue to complain about the 1st windows box being
overloaded all the time.
Gav.
From: omuppi1@gmail.com [mailto:omuppi1@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Tuesday, 10 December 2013 7:28 AM
To: builds@apache.org
Cc: Gavin McDonald
Subject: Re: [windows1] Pixelbender installation
Gavin,
This issue is unrelated to Windows2 slave. Our long running job on Windows1
has started failing for the past few days. Can we first fix that before we
start working on Windows2?
Or, is Windows2 a replacement for Windows1?
Thanks,
Om
On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <erik@ixsoftware.nl
<ma...@ixsoftware.nl> > wrote:
Ok, from the top of this thread:
"The build on windows1 is failing on the 'Pixelbender' task:
The build assumes Pixelbender is installed at:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
CS5/Pixel\ Bender\ Toolkit\ 2
Is that still the correct path and does the application start without
errors when you launch it manually?"
In another email in this thread I've listed the software that needs to
be on windows2.
Is there a way to have all our builds run on either windows1 OR
windows2? Most of our jobs depend on files in the workspaces of some
of our other builds, in order to save on disk space and build time. If
we remove these dependencies, we'd basically be forced to copy each
build into each other build.
Since it is the weekend, I'll have limited time to work with you,
sorry. Next Monday I'll be glad to check/test/adjust whatever needs
checking/testing/adjusting.
Please keep in mind that we are at a very important milestone for our
project, and with third party teams relying on our nightly builds,
we'd greatly appreciate a successful run of all our jobs, on whatever
slave works.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl <http://www.ixsoftware.nl>
Re: [windows1] Pixelbender installation
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Gavin,
This issue is unrelated to Windows2 slave. Our long running job on
Windows1 has started failing for the past few days. Can we first fix that
before we start working on Windows2?
Or, is Windows2 a replacement for Windows1?
Thanks,
Om
On Sat, Dec 7, 2013 at 12:35 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> Ok, from the top of this thread:
>
> "The build on windows1 is failing on the 'Pixelbender' task:
>
> The build assumes Pixelbender is installed at:
>
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
> CS5/Pixel\ Bender\ Toolkit\ 2
>
> Is that still the correct path and does the application start without
> errors when you launch it manually?"
>
> In another email in this thread I've listed the software that needs to
> be on windows2.
>
> Is there a way to have all our builds run on either windows1 OR
> windows2? Most of our jobs depend on files in the workspaces of some
> of our other builds, in order to save on disk space and build time. If
> we remove these dependencies, we'd basically be forced to copy each
> build into each other build.
>
> Since it is the weekend, I'll have limited time to work with you,
> sorry. Next Monday I'll be glad to check/test/adjust whatever needs
> checking/testing/adjusting.
>
> Please keep in mind that we are at a very important milestone for our
> project, and with third party teams relying on our nightly builds,
> we'd greatly appreciate a successful run of all our jobs, on whatever
> slave works.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
Re: [windows1] Pixelbender installation
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Ok, from the top of this thread:
"The build on windows1 is failing on the 'Pixelbender' task:
The build assumes Pixelbender is installed at:
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
CS5/Pixel\ Bender\ Toolkit\ 2
Is that still the correct path and does the application start without
errors when you launch it manually?"
In another email in this thread I've listed the software that needs to
be on windows2.
Is there a way to have all our builds run on either windows1 OR
windows2? Most of our jobs depend on files in the workspaces of some
of our other builds, in order to save on disk space and build time. If
we remove these dependencies, we'd basically be forced to copy each
build into each other build.
Since it is the weekend, I'll have limited time to work with you,
sorry. Next Monday I'll be glad to check/test/adjust whatever needs
checking/testing/adjusting.
Please keep in mind that we are at a very important milestone for our
project, and with third party teams relying on our nightly builds,
we'd greatly appreciate a successful run of all our jobs, on whatever
slave works.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> Sent: Thursday, 5 December 2013 6:51 PM
> To: builds@apache.org; Gavin McDonald
> Subject: Re: [windows1] Pixelbender installation
>
> >> Our builds stopped working yesterday :-(
> >
> > No they didn't.
> >
> > :)
>
> Yes, they did, and they still are.
>
> :(
>
> Not sure what you changed when worked on them, but even now I've
> changed the job back to run only on 'windows1', it still fails on the
> Pixelbender step...
Well I promise I did not touch windows1, but let me know what you want
looking into.
>
> Maybe next time I can get a heads up and some notification what's going to
> happen, please?
I asked if those projects with Windows builds would try the new slave and
test it.
No one did, so I was forced to start doing the work on my own. This is for
the projects' good so
that we could start splitting the load between them.
I spent quite some time installing stuff on windows1 for your project, I
remember working with you
on it. I feel entitled to use your project or any other to start bringing
windows2 into service. If you are
now around to help, great.
Gav...
> We're currently working with third party teams to get our
> new compiler running with their IDEs and they rely on a clean nightly
build... I
> could have told you an unmodified 'windows2' slave wouldn't be able to
build
> our jobs, and we could have prepared it together before running the tests.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: [windows1] Pixelbender installation
Posted by Erik de Bruin <er...@ixsoftware.nl>.
In order to build, our jobs require the following software installed:
- Flash Player Debugger (v 11.1[any release], 32 bit, debug):
- from: http://fpdownload.macromedia.com/get/flashplayer/installers/archive/fp_11.1.102.63_archive.zip
- to: C:/Program Files (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
- PixelBender:
- from: http://www.adobe.com/go/pixelbender_toolkit_zip/
- to: C:/Program Files (x86)/Adobe/Adobe Utilities - CS5/Pixel
Bender Toolkit 2
- Extension Manager:
- from: http://download.macromedia.com/pub/dw_exchange/extension_manager/win/AdobeExtensionManager5All.zip
- to: C:/Program Files (x86)/Adobe/Adobe Extension Manager CS5/Adobe
Extension Manager CS5.exe
Thanks,
EdB
On Thu, Dec 5, 2013 at 8:50 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>> Our builds stopped working yesterday :-(
>>
>> No they didn't.
>>
>> :)
>
> Yes, they did, and they still are.
>
> :(
>
> Not sure what you changed when worked on them, but even now I've
> changed the job back to run only on 'windows1', it still fails on the
> Pixelbender step...
>
> Maybe next time I can get a heads up and some notification what's
> going to happen, please? We're currently working with third party
> teams to get our new compiler running with their IDEs and they rely on
> a clean nightly build... I could have told you an unmodified
> 'windows2' slave wouldn't be able to build our jobs, and we could have
> prepared it together before running the tests.
>
> 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: [windows1] Pixelbender installation
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>> Our builds stopped working yesterday :-(
>
> No they didn't.
>
> :)
Yes, they did, and they still are.
:(
Not sure what you changed when worked on them, but even now I've
changed the job back to run only on 'windows1', it still fails on the
Pixelbender step...
Maybe next time I can get a heads up and some notification what's
going to happen, please? We're currently working with third party
teams to get our new compiler running with their IDEs and they rely on
a clean nightly build... I could have told you an unmodified
'windows2' slave wouldn't be able to build our jobs, and we could have
prepared it together before running the tests.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
RE: [windows1] Pixelbender installation
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Erik de Bruin [mailto:erik@ixsoftware.nl]
> Sent: Wednesday, 4 December 2013 7:16 PM
> To: builds@apache.org
> Subject: [windows1] Pixelbender installation
>
> Hi,
>
> Our builds stopped working yesterday :-(
No they didn't.
:)
>
> This is the error I get:
>
> pixelbender-compile:
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
>
> The build assumes Pixelbender is installed at:
>
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
> CS5/Pixel\ Bender\ Toolkit\ 2
>
> Is that still the correct path and does the application start without
errors
> when you launch it manually?
I tried your build on windows2 , a new slave.
That failed.
Can you give me a list of things I need to install on the new Windows slave
for your builds to pass,
so that we can configure your builds to use either slave.
Cheers
Gav...
>
> Thanks!
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl