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 <aha...@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" <bigosma...@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: omup...@gmail.com [mailto:omup...@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
>>><bigosma...@gmail.com>
>>wrote:
>>>>
>>>> On Tue, Dec 10, 2013 at 3:53 PM, Gavin McDonald
>>>><ga...@16degrees.com.au>
>>wrote:
>>>>>
>>>>>
>>>>>
>>>>> > -----Original Message-----
>>>>> > From: omup...@gmail.com [mailto:omup...@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
>>>>> > <bigosma...@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:* omup...@gmail.com [mailto:omup...@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:e...@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
>>>>> > >> > <bigosma...@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:* omup...@gmail.com [mailto:omup...@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
>>>>> > >> > >> <e...@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

Reply via email to