You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Tom Chiverton <to...@apache.org> on 2014/11/02 00:23:02 UTC
Re: [mustella] all recent SDK tests failed
On Friday 31 Oct 2014 13:38:12 Erik de Bruin wrote:
> Ok, had to go into the Azure portal and hard reset the VM, for some reason.
> But it's rebooted, anyway. I also deleted all 'version.txt' files, so we're
> starting brand new and clean ;-)
The last run (#1133) seems to just have had some random timeout failures, so we'll see.
--
Tom
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I will give the VM twice the memory for the next 2 weeks, and reboot it in
the process. Let's see if that makes a difference. If not, a bit +1 on you
taking the time you need to figure out what's going wrong.
EdB
On Sun, Nov 9, 2014 at 4:16 PM, Alex Harui <ah...@adobe.com> wrote:
> I think the time as come to shut down Mustella Jenkins for a while. We
> just have to make sure it isn’t in the middle of the SDK job (ok to abort
> the Mobile or AIR run). That way, with the failing SWFs in the SDK
> workspace, I can try to do a remote debug session on them and try to
> figure out whether it is some code in the SDK that is result in the
> failures or the player just gets wonky for some reason. I can only do
> remote debugging at home after hours so that’s why it could take a while
> for me to get through it.
>
> -Alex
>
> On 11/6/14, 7:39 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >Yup, time to try moving the window again. I’m not near my RDP computer
> >today. Can you do it?
> >
> >-Alex
> >
> >On 11/6/14, 2:25 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
> >
> >>The last two runs had 386 bitmap failures
> >>
> http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/c
> >>o
> >>nsole
> >>which can not be correct.
> >>
> >>Tom
> >>
> >>On 04/11/14 17:14, Tom Chiverton wrote:
> >>> Ahh, cool.
> >>> I minimised the Jenkins status window too, just in case.
> >>>
> >>> Still an hour to run and I'm just off for the day.
> >>>
> >>> Tom
> >>>
> >>> On 04/11/14 15:27, Alex Harui wrote:
> >>>> That was me forgetting to close the explorer window. I logged on last
> >>>> night, opened a few players and moved the windows then too. I noted
> >>>> that
> >>>> 11.7 actually gave me a warning like it had never been run before.
> >>>>
> >>>> Got my finger’s crossed.
> >>>>
> >>>> On my computers (Mac and Windows), having the player window off-screen
> >>>> doesn’t affect results, but something is definitely more sensitive on
> >>>> the
> >>>> mustella server.
> >>>>
> >>>> -Alex
> >>>>
> >>>> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
> >>>>
> >>>>> And, of course, as I give up waiting and send it, the Player window
> >>>>> appears :-)
> >>>>>
> >>>>> So I moved it.
> >>>>>
> >>>>> Let's see what happens.
> >>>>>
> >>>>> Quite often the test SWF is at least partly off the right or bottom
> >>>>>of
> >>>>> the screen still, as it's larger than the desktop.
> >>>>>
> >>>>> Tom
> >>>>>
> >>>>> On 04/11/14 11:00, Tom Chiverton wrote:
> >>>>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
> >>>>>> hopefully I'll be able to catch the debug player window appearing in
> >>>>>> an hour or so once the compile finishes.
> >>>>>>
> >>>>>> If so, I'll move it to the top left as Alex suggested and post back
> >>>>>> here.
> >>>>>>
> >>>>>> Tom
> >>>>>>
> >>>>>> On 04/11/14 10:47, Erik de Bruin wrote:
> >>>>>>> It wasn't me ...
> >>>>>>>
> >>>>>>> EdB
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc@extravision.com
> >
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> On 03/11/14 20:07, Alex Harui wrote:
> >>>>>>>>
> >>>>>>>>> If you have time, you might see if you can catch the mustella VM
> >>>>>>>>> running
> >>>>>>>>> the SDK tests and grab a window and move it to the upper left.
> >>>>>>>>> That
> >>>>>>>>>
> >>>>>>>> I just logged in to do that and there was a File Browser window
> >>>>>>>>open
> >>>>>>>> that
> >>>>>>>> looked like someone was installing a new debug Player ?
> >>>>>>>>
> >>>>>>>> Tom
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>_____________________________________________________________________
> >>>>>>_
> >>>>>> This email has been scanned by the Symantec Email Security.cloud
> >>>>>> service.
> >>>>>> For more information please visit http://www.symanteccloud.com
> >>>>>>
> >>>>>>_____________________________________________________________________
> >>>>>>_
> >>>>
> >>>> ______________________________________________________________________
> >>>> This email has been scanned by the Symantec Email Security.cloud
> >>>> service.
> >>>> For more information please visit http://www.symanteccloud.com
> >>>> ______________________________________________________________________
> >>>>
> >>>
> >>>
> >>>
> >>> ______________________________________________________________________
> >>> This email has been scanned by the Symantec Email Security.cloud
> >>>service.
> >>> For more information please visit http://www.symanteccloud.com
> >>> ______________________________________________________________________
> >>
> >
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
I think the time as come to shut down Mustella Jenkins for a while. We
just have to make sure it isn’t in the middle of the SDK job (ok to abort
the Mobile or AIR run). That way, with the failing SWFs in the SDK
workspace, I can try to do a remote debug session on them and try to
figure out whether it is some code in the SDK that is result in the
failures or the player just gets wonky for some reason. I can only do
remote debugging at home after hours so that’s why it could take a while
for me to get through it.
-Alex
On 11/6/14, 7:39 AM, "Alex Harui" <ah...@adobe.com> wrote:
>Yup, time to try moving the window again. I’m not near my RDP computer
>today. Can you do it?
>
>-Alex
>
>On 11/6/14, 2:25 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>
>>The last two runs had 386 bitmap failures
>>http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/c
>>o
>>nsole
>>which can not be correct.
>>
>>Tom
>>
>>On 04/11/14 17:14, Tom Chiverton wrote:
>>> Ahh, cool.
>>> I minimised the Jenkins status window too, just in case.
>>>
>>> Still an hour to run and I'm just off for the day.
>>>
>>> Tom
>>>
>>> On 04/11/14 15:27, Alex Harui wrote:
>>>> That was me forgetting to close the explorer window. I logged on last
>>>> night, opened a few players and moved the windows then too. I noted
>>>> that
>>>> 11.7 actually gave me a warning like it had never been run before.
>>>>
>>>> Got my finger’s crossed.
>>>>
>>>> On my computers (Mac and Windows), having the player window off-screen
>>>> doesn’t affect results, but something is definitely more sensitive on
>>>> the
>>>> mustella server.
>>>>
>>>> -Alex
>>>>
>>>> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>>>>
>>>>> And, of course, as I give up waiting and send it, the Player window
>>>>> appears :-)
>>>>>
>>>>> So I moved it.
>>>>>
>>>>> Let's see what happens.
>>>>>
>>>>> Quite often the test SWF is at least partly off the right or bottom
>>>>>of
>>>>> the screen still, as it's larger than the desktop.
>>>>>
>>>>> Tom
>>>>>
>>>>> On 04/11/14 11:00, Tom Chiverton wrote:
>>>>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>>>>>> hopefully I'll be able to catch the debug player window appearing in
>>>>>> an hour or so once the compile finishes.
>>>>>>
>>>>>> If so, I'll move it to the top left as Alex suggested and post back
>>>>>> here.
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>> On 04/11/14 10:47, Erik de Bruin wrote:
>>>>>>> It wasn't me ...
>>>>>>>
>>>>>>> EdB
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>>>>>
>>>>>>>>> If you have time, you might see if you can catch the mustella VM
>>>>>>>>> running
>>>>>>>>> the SDK tests and grab a window and move it to the upper left.
>>>>>>>>> That
>>>>>>>>>
>>>>>>>> I just logged in to do that and there was a File Browser window
>>>>>>>>open
>>>>>>>> that
>>>>>>>> looked like someone was installing a new debug Player ?
>>>>>>>>
>>>>>>>> Tom
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>_____________________________________________________________________
>>>>>>_
>>>>>> This email has been scanned by the Symantec Email Security.cloud
>>>>>> service.
>>>>>> For more information please visit http://www.symanteccloud.com
>>>>>>
>>>>>>_____________________________________________________________________
>>>>>>_
>>>>
>>>> ______________________________________________________________________
>>>> This email has been scanned by the Symantec Email Security.cloud
>>>> service.
>>>> For more information please visit http://www.symanteccloud.com
>>>> ______________________________________________________________________
>>>>
>>>
>>>
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud
>>>service.
>>> For more information please visit http://www.symanteccloud.com
>>> ______________________________________________________________________
>>
>
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
I've relocated it near to the top left.
I notice each subsequent run however the new window moves down and
right, because of the cascade window placement Windows uses.
What I think of as 'normal' sized Player windows do now always stay in
the screen, without going behind the start bar or anything.
Let's give it a few runs and see ?
Tom
On 06/11/14 15:39, Alex Harui wrote:
> Yup, time to try moving the window again. I’m not near my RDP computer
> today. Can you do it?
>
> -Alex
>
> On 11/6/14, 2:25 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>
>> The last two runs had 386 bitmap failures
>> http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/co
>> nsole
>> which can not be correct.
>>
>> Tom
>>
>> On 04/11/14 17:14, Tom Chiverton wrote:
>>> Ahh, cool.
>>> I minimised the Jenkins status window too, just in case.
>>>
>>> Still an hour to run and I'm just off for the day.
>>>
>>> Tom
>>>
>>> On 04/11/14 15:27, Alex Harui wrote:
>>>> That was me forgetting to close the explorer window. I logged on last
>>>> night, opened a few players and moved the windows then too. I noted
>>>> that
>>>> 11.7 actually gave me a warning like it had never been run before.
>>>>
>>>> Got my finger’s crossed.
>>>>
>>>> On my computers (Mac and Windows), having the player window off-screen
>>>> doesn’t affect results, but something is definitely more sensitive on
>>>> the
>>>> mustella server.
>>>>
>>>> -Alex
>>>>
>>>> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>>>>
>>>>> And, of course, as I give up waiting and send it, the Player window
>>>>> appears :-)
>>>>>
>>>>> So I moved it.
>>>>>
>>>>> Let's see what happens.
>>>>>
>>>>> Quite often the test SWF is at least partly off the right or bottom of
>>>>> the screen still, as it's larger than the desktop.
>>>>>
>>>>> Tom
>>>>>
>>>>> On 04/11/14 11:00, Tom Chiverton wrote:
>>>>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>>>>>> hopefully I'll be able to catch the debug player window appearing in
>>>>>> an hour or so once the compile finishes.
>>>>>>
>>>>>> If so, I'll move it to the top left as Alex suggested and post back
>>>>>> here.
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>> On 04/11/14 10:47, Erik de Bruin wrote:
>>>>>>> It wasn't me ...
>>>>>>>
>>>>>>> EdB
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>>>>>
>>>>>>>>> If you have time, you might see if you can catch the mustella VM
>>>>>>>>> running
>>>>>>>>> the SDK tests and grab a window and move it to the upper left.
>>>>>>>>> That
>>>>>>>>>
>>>>>>>> I just logged in to do that and there was a File Browser window
>>>>>>>> open
>>>>>>>> that
>>>>>>>> looked like someone was installing a new debug Player ?
>>>>>>>>
>>>>>>>> Tom
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>> ______________________________________________________________________
>>>>>> This email has been scanned by the Symantec Email Security.cloud
>>>>>> service.
>>>>>> For more information please visit http://www.symanteccloud.com
>>>>>>
>>>>>> ______________________________________________________________________
>>>> ______________________________________________________________________
>>>> This email has been scanned by the Symantec Email Security.cloud
>>>> service.
>>>> For more information please visit http://www.symanteccloud.com
>>>> ______________________________________________________________________
>>>>
>>>
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud
>>> service.
>>> For more information please visit http://www.symanteccloud.com
>>> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
Yup, time to try moving the window again. I’m not near my RDP computer
today. Can you do it?
-Alex
On 11/6/14, 2:25 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>The last two runs had 386 bitmap failures
>http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/co
>nsole
>which can not be correct.
>
>Tom
>
>On 04/11/14 17:14, Tom Chiverton wrote:
>> Ahh, cool.
>> I minimised the Jenkins status window too, just in case.
>>
>> Still an hour to run and I'm just off for the day.
>>
>> Tom
>>
>> On 04/11/14 15:27, Alex Harui wrote:
>>> That was me forgetting to close the explorer window. I logged on last
>>> night, opened a few players and moved the windows then too. I noted
>>> that
>>> 11.7 actually gave me a warning like it had never been run before.
>>>
>>> Got my finger’s crossed.
>>>
>>> On my computers (Mac and Windows), having the player window off-screen
>>> doesn’t affect results, but something is definitely more sensitive on
>>> the
>>> mustella server.
>>>
>>> -Alex
>>>
>>> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>>>
>>>> And, of course, as I give up waiting and send it, the Player window
>>>> appears :-)
>>>>
>>>> So I moved it.
>>>>
>>>> Let's see what happens.
>>>>
>>>> Quite often the test SWF is at least partly off the right or bottom of
>>>> the screen still, as it's larger than the desktop.
>>>>
>>>> Tom
>>>>
>>>> On 04/11/14 11:00, Tom Chiverton wrote:
>>>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>>>>> hopefully I'll be able to catch the debug player window appearing in
>>>>> an hour or so once the compile finishes.
>>>>>
>>>>> If so, I'll move it to the top left as Alex suggested and post back
>>>>> here.
>>>>>
>>>>> Tom
>>>>>
>>>>> On 04/11/14 10:47, Erik de Bruin wrote:
>>>>>> It wasn't me ...
>>>>>>
>>>>>> EdB
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>>>>> wrote:
>>>>>>
>>>>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>>>>
>>>>>>>> If you have time, you might see if you can catch the mustella VM
>>>>>>>> running
>>>>>>>> the SDK tests and grab a window and move it to the upper left.
>>>>>>>> That
>>>>>>>>
>>>>>>> I just logged in to do that and there was a File Browser window
>>>>>>>open
>>>>>>> that
>>>>>>> looked like someone was installing a new debug Player ?
>>>>>>>
>>>>>>> Tom
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>______________________________________________________________________
>>>>> This email has been scanned by the Symantec Email Security.cloud
>>>>> service.
>>>>> For more information please visit http://www.symanteccloud.com
>>>>>
>>>>>______________________________________________________________________
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud
>>> service.
>>> For more information please visit http://www.symanteccloud.com
>>> ______________________________________________________________________
>>>
>>
>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud
>>service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
The last two runs had 386 bitmap failures
http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/console
which can not be correct.
Tom
On 04/11/14 17:14, Tom Chiverton wrote:
> Ahh, cool.
> I minimised the Jenkins status window too, just in case.
>
> Still an hour to run and I'm just off for the day.
>
> Tom
>
> On 04/11/14 15:27, Alex Harui wrote:
>> That was me forgetting to close the explorer window. I logged on last
>> night, opened a few players and moved the windows then too. I noted
>> that
>> 11.7 actually gave me a warning like it had never been run before.
>>
>> Got my finger’s crossed.
>>
>> On my computers (Mac and Windows), having the player window off-screen
>> doesn’t affect results, but something is definitely more sensitive on
>> the
>> mustella server.
>>
>> -Alex
>>
>> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>>
>>> And, of course, as I give up waiting and send it, the Player window
>>> appears :-)
>>>
>>> So I moved it.
>>>
>>> Let's see what happens.
>>>
>>> Quite often the test SWF is at least partly off the right or bottom of
>>> the screen still, as it's larger than the desktop.
>>>
>>> Tom
>>>
>>> On 04/11/14 11:00, Tom Chiverton wrote:
>>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>>>> hopefully I'll be able to catch the debug player window appearing in
>>>> an hour or so once the compile finishes.
>>>>
>>>> If so, I'll move it to the top left as Alex suggested and post back
>>>> here.
>>>>
>>>> Tom
>>>>
>>>> On 04/11/14 10:47, Erik de Bruin wrote:
>>>>> It wasn't me ...
>>>>>
>>>>> EdB
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>>>> wrote:
>>>>>
>>>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>>>
>>>>>>> If you have time, you might see if you can catch the mustella VM
>>>>>>> running
>>>>>>> the SDK tests and grab a window and move it to the upper left.
>>>>>>> That
>>>>>>>
>>>>>> I just logged in to do that and there was a File Browser window open
>>>>>> that
>>>>>> looked like someone was installing a new debug Player ?
>>>>>>
>>>>>> Tom
>>>>>>
>>>>>>
>>>>
>>>>
>>>> ______________________________________________________________________
>>>> This email has been scanned by the Symantec Email Security.cloud
>>>> service.
>>>> For more information please visit http://www.symanteccloud.com
>>>> ______________________________________________________________________
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud
>> service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
Ahh, cool.
I minimised the Jenkins status window too, just in case.
Still an hour to run and I'm just off for the day.
Tom
On 04/11/14 15:27, Alex Harui wrote:
> That was me forgetting to close the explorer window. I logged on last
> night, opened a few players and moved the windows then too. I noted that
> 11.7 actually gave me a warning like it had never been run before.
>
> Got my finger’s crossed.
>
> On my computers (Mac and Windows), having the player window off-screen
> doesn’t affect results, but something is definitely more sensitive on the
> mustella server.
>
> -Alex
>
> On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>
>> And, of course, as I give up waiting and send it, the Player window
>> appears :-)
>>
>> So I moved it.
>>
>> Let's see what happens.
>>
>> Quite often the test SWF is at least partly off the right or bottom of
>> the screen still, as it's larger than the desktop.
>>
>> Tom
>>
>> On 04/11/14 11:00, Tom Chiverton wrote:
>>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>>> hopefully I'll be able to catch the debug player window appearing in
>>> an hour or so once the compile finishes.
>>>
>>> If so, I'll move it to the top left as Alex suggested and post back
>>> here.
>>>
>>> Tom
>>>
>>> On 04/11/14 10:47, Erik de Bruin wrote:
>>>> It wasn't me ...
>>>>
>>>> EdB
>>>>
>>>>
>>>>
>>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>>> wrote:
>>>>
>>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>>
>>>>>> If you have time, you might see if you can catch the mustella VM
>>>>>> running
>>>>>> the SDK tests and grab a window and move it to the upper left. That
>>>>>>
>>>>> I just logged in to do that and there was a File Browser window open
>>>>> that
>>>>> looked like someone was installing a new debug Player ?
>>>>>
>>>>> Tom
>>>>>
>>>>>
>>>
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud
>>> service.
>>> For more information please visit http://www.symanteccloud.com
>>> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
That was me forgetting to close the explorer window. I logged on last
night, opened a few players and moved the windows then too. I noted that
11.7 actually gave me a warning like it had never been run before.
Got my finger’s crossed.
On my computers (Mac and Windows), having the player window off-screen
doesn’t affect results, but something is definitely more sensitive on the
mustella server.
-Alex
On 11/4/14, 3:17 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>And, of course, as I give up waiting and send it, the Player window
>appears :-)
>
>So I moved it.
>
>Let's see what happens.
>
>Quite often the test SWF is at least partly off the right or bottom of
>the screen still, as it's larger than the desktop.
>
>Tom
>
>On 04/11/14 11:00, Tom Chiverton wrote:
>> Also, the Jenkins web site says flex-sdk_mustella is running, so
>> hopefully I'll be able to catch the debug player window appearing in
>> an hour or so once the compile finishes.
>>
>> If so, I'll move it to the top left as Alex suggested and post back
>>here.
>>
>> Tom
>>
>> On 04/11/14 10:47, Erik de Bruin wrote:
>>> It wasn't me ...
>>>
>>> EdB
>>>
>>>
>>>
>>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>>> wrote:
>>>
>>>> On 03/11/14 20:07, Alex Harui wrote:
>>>>
>>>>> If you have time, you might see if you can catch the mustella VM
>>>>> running
>>>>> the SDK tests and grab a window and move it to the upper left. That
>>>>>
>>>> I just logged in to do that and there was a File Browser window open
>>>> that
>>>> looked like someone was installing a new debug Player ?
>>>>
>>>> Tom
>>>>
>>>>
>>>
>>
>>
>>
>> ______________________________________________________________________
>> This email has been scanned by the Symantec Email Security.cloud
>>service.
>> For more information please visit http://www.symanteccloud.com
>> ______________________________________________________________________
>
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
And, of course, as I give up waiting and send it, the Player window
appears :-)
So I moved it.
Let's see what happens.
Quite often the test SWF is at least partly off the right or bottom of
the screen still, as it's larger than the desktop.
Tom
On 04/11/14 11:00, Tom Chiverton wrote:
> Also, the Jenkins web site says flex-sdk_mustella is running, so
> hopefully I'll be able to catch the debug player window appearing in
> an hour or so once the compile finishes.
>
> If so, I'll move it to the top left as Alex suggested and post back here.
>
> Tom
>
> On 04/11/14 10:47, Erik de Bruin wrote:
>> It wasn't me ...
>>
>> EdB
>>
>>
>>
>> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com>
>> wrote:
>>
>>> On 03/11/14 20:07, Alex Harui wrote:
>>>
>>>> If you have time, you might see if you can catch the mustella VM
>>>> running
>>>> the SDK tests and grab a window and move it to the upper left. That
>>>>
>>> I just logged in to do that and there was a File Browser window open
>>> that
>>> looked like someone was installing a new debug Player ?
>>>
>>> Tom
>>>
>>>
>>
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
Also, the Jenkins web site says flex-sdk_mustella is running, so
hopefully I'll be able to catch the debug player window appearing in an
hour or so once the compile finishes.
If so, I'll move it to the top left as Alex suggested and post back here.
Tom
On 04/11/14 10:47, Erik de Bruin wrote:
> It wasn't me ...
>
> EdB
>
>
>
> On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com> wrote:
>
>> On 03/11/14 20:07, Alex Harui wrote:
>>
>>> If you have time, you might see if you can catch the mustella VM running
>>> the SDK tests and grab a window and move it to the upper left. That
>>>
>> I just logged in to do that and there was a File Browser window open that
>> looked like someone was installing a new debug Player ?
>>
>> Tom
>>
>>
>
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
It wasn't me ...
EdB
On Tue, Nov 4, 2014 at 10:46 AM, Tom Chiverton <tc...@extravision.com> wrote:
> On 03/11/14 20:07, Alex Harui wrote:
>
>> If you have time, you might see if you can catch the mustella VM running
>> the SDK tests and grab a window and move it to the upper left. That
>>
> I just logged in to do that and there was a File Browser window open that
> looked like someone was installing a new debug Player ?
>
> Tom
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
On 03/11/14 20:07, Alex Harui wrote:
> If you have time, you might see if you can catch the mustella VM running
> the SDK tests and grab a window and move it to the upper left. That
I just logged in to do that and there was a File Browser window open
that looked like someone was installing a new debug Player ?
Tom
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/14, 11:48 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>Too late, already reverted.
>
>Guess I'll have to learn to rerevert now ;-)
Two new things learned today! ;-)
If you have time, you might see if you can catch the mustella VM running
the SDK tests and grab a window and move it to the upper left. That
incantation worked last time. And if that works, I think we should
consider taking 11.7/3.7 out of the rotation. There could be some
idiosyncrasy about that combination and how it handles being off-screen or
a non-top-level window. I cannot get to the mustella VM from my office,
so I can’t try that incantation until later today.
-Alex
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Too late, already reverted.
Guess I'll have to learn to rerevert now ;-)
EdB
On Mon, Nov 3, 2014 at 8:45 PM, Alex Harui <ah...@adobe.com> wrote:
> The two tests passed locally for me on Mac, so that vindicates the code
> you checked-in so you can avoid learning git revert for now.
>
> I’ll try it on Windows tonight.
>
> -Alex
>
> On 11/3/14, 11:39 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> >You are right, I'll revert. I've never done that (still have love-hate
> >relation with Git), so 'fingers crossed' ;-)
> >
> >EdB
> >
> >
> >
> >On Mon, Nov 3, 2014 at 8:12 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 11/3/14, 10:55 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
> >>
> >> >>
> >> >> >I didn't run these locally, as I didn't expect changes to
> >> >>SystemManager to
> >> >> >affect anything but the very core of the SDK.
> >> >>
> >> >> I would be surprised if your changes made a difference as well but
> >>you
> >> >> never know. I thought the “unofficial” policy was that if your
> >>checkins
> >> >> are tied to a run that fails that you have to investigate, by at
> >> >>minimum,
> >> >> reverting or showing that the tests pass locally for you.
> >> >>
> >> >
> >> >I "wrote" that policy ;-) But there weren't any tests that consistently
> >> >failed, the failures have been all over the place. I could revert, but
> >>my
> >> >assessment was that not my changes, but something on the VM was the
> >>root
> >> >cause.
> >>
> >> I’m wondering if there is some easy way to show which tests are failing
> >> more often than not. My records show that these two tests:
> >>
> >> gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
> >> Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
> >> shown)(body:step 13) method returned , expected test1234
> >>
> >>
> >>gumbo/components/RichEditableText/Properties/RichEditableText_layout_test
> >>3
> >> RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step
> >>2)
> >> Timeout waiting for change from retEditable1
> >>
> >> failed in runs:
> >>
> >>
> >> 1137
> >> 1136
> >> 1135
> >> 1134
> >> 1133
> >> 1132
> >> 1129
> >> 1128
> >> 1126
> >> 1125
> >> 1124
> >> 1123
> >>
> >> Yes, there were other intermittent failures, and run #1130 was full of
> >>bad
> >> stuff. But #1121 passed, then #1123 with your changes, fails, and those
> >> two tests are the repeat offenders since. I have no idea how they can
> >>be
> >> broken by your changes either, but right or wrong, I think you have try
> >>a
> >> revert or see if the tests pass locally.
> >>
> >> -Alex
> >>
> >>
> >
> >
> >--
> >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: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
The two tests passed locally for me on Mac, so that vindicates the code
you checked-in so you can avoid learning git revert for now.
I’ll try it on Windows tonight.
-Alex
On 11/3/14, 11:39 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>You are right, I'll revert. I've never done that (still have love-hate
>relation with Git), so 'fingers crossed' ;-)
>
>EdB
>
>
>
>On Mon, Nov 3, 2014 at 8:12 PM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 11/3/14, 10:55 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> >>
>> >> >I didn't run these locally, as I didn't expect changes to
>> >>SystemManager to
>> >> >affect anything but the very core of the SDK.
>> >>
>> >> I would be surprised if your changes made a difference as well but
>>you
>> >> never know. I thought the “unofficial” policy was that if your
>>checkins
>> >> are tied to a run that fails that you have to investigate, by at
>> >>minimum,
>> >> reverting or showing that the tests pass locally for you.
>> >>
>> >
>> >I "wrote" that policy ;-) But there weren't any tests that consistently
>> >failed, the failures have been all over the place. I could revert, but
>>my
>> >assessment was that not my changes, but something on the VM was the
>>root
>> >cause.
>>
>> I’m wondering if there is some easy way to show which tests are failing
>> more often than not. My records show that these two tests:
>>
>> gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
>> Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
>> shown)(body:step 13) method returned , expected test1234
>>
>>
>>gumbo/components/RichEditableText/Properties/RichEditableText_layout_test
>>3
>> RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step
>>2)
>> Timeout waiting for change from retEditable1
>>
>> failed in runs:
>>
>>
>> 1137
>> 1136
>> 1135
>> 1134
>> 1133
>> 1132
>> 1129
>> 1128
>> 1126
>> 1125
>> 1124
>> 1123
>>
>> Yes, there were other intermittent failures, and run #1130 was full of
>>bad
>> stuff. But #1121 passed, then #1123 with your changes, fails, and those
>> two tests are the repeat offenders since. I have no idea how they can
>>be
>> broken by your changes either, but right or wrong, I think you have try
>>a
>> revert or see if the tests pass locally.
>>
>> -Alex
>>
>>
>
>
>--
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
You are right, I'll revert. I've never done that (still have love-hate
relation with Git), so 'fingers crossed' ;-)
EdB
On Mon, Nov 3, 2014 at 8:12 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
> On 11/3/14, 10:55 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
> >>
> >> >I didn't run these locally, as I didn't expect changes to
> >>SystemManager to
> >> >affect anything but the very core of the SDK.
> >>
> >> I would be surprised if your changes made a difference as well but you
> >> never know. I thought the “unofficial” policy was that if your checkins
> >> are tied to a run that fails that you have to investigate, by at
> >>minimum,
> >> reverting or showing that the tests pass locally for you.
> >>
> >
> >I "wrote" that policy ;-) But there weren't any tests that consistently
> >failed, the failures have been all over the place. I could revert, but my
> >assessment was that not my changes, but something on the VM was the root
> >cause.
>
> I’m wondering if there is some easy way to show which tests are failing
> more often than not. My records show that these two tests:
>
> gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
> Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
> shown)(body:step 13) method returned , expected test1234
>
> gumbo/components/RichEditableText/Properties/RichEditableText_layout_test3
> RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step 2)
> Timeout waiting for change from retEditable1
>
> failed in runs:
>
>
> 1137
> 1136
> 1135
> 1134
> 1133
> 1132
> 1129
> 1128
> 1126
> 1125
> 1124
> 1123
>
> Yes, there were other intermittent failures, and run #1130 was full of bad
> stuff. But #1121 passed, then #1123 with your changes, fails, and those
> two tests are the repeat offenders since. I have no idea how they can be
> broken by your changes either, but right or wrong, I think you have try a
> revert or see if the tests pass locally.
>
> -Alex
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/14, 10:55 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>> >I didn't run these locally, as I didn't expect changes to
>>SystemManager to
>> >affect anything but the very core of the SDK.
>>
>> I would be surprised if your changes made a difference as well but you
>> never know. I thought the “unofficial” policy was that if your checkins
>> are tied to a run that fails that you have to investigate, by at
>>minimum,
>> reverting or showing that the tests pass locally for you.
>>
>
>I "wrote" that policy ;-) But there weren't any tests that consistently
>failed, the failures have been all over the place. I could revert, but my
>assessment was that not my changes, but something on the VM was the root
>cause.
I’m wondering if there is some easy way to show which tests are failing
more often than not. My records show that these two tests:
gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
shown)(body:step 13) method returned , expected test1234
gumbo/components/RichEditableText/Properties/RichEditableText_layout_test3
RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step 2)
Timeout waiting for change from retEditable1
failed in runs:
1137
1136
1135
1134
1133
1132
1129
1128
1126
1125
1124
1123
Yes, there were other intermittent failures, and run #1130 was full of bad
stuff. But #1121 passed, then #1123 with your changes, fails, and those
two tests are the repeat offenders since. I have no idea how they can be
broken by your changes either, but right or wrong, I think you have try a
revert or see if the tests pass locally.
-Alex
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>
> >I didn't run these locally, as I didn't expect changes to SystemManager to
> >affect anything but the very core of the SDK.
>
> I would be surprised if your changes made a difference as well but you
> never know. I thought the “unofficial” policy was that if your checkins
> are tied to a run that fails that you have to investigate, by at minimum,
> reverting or showing that the tests pass locally for you.
>
I "wrote" that policy ;-) But there weren't any tests that consistently
failed, the failures have been all over the place. I could revert, but my
assessment was that not my changes, but something on the VM was the root
cause.
I've rebooted and reset Mustella, but tests are still failing (again, not
twice the same ones, as far as I can tell). Next on my list would be to
increase the VM size to have more memory and CPU horsepower, see if that
changes anything ...
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/14, 10:21 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
>I didn't run these locally, as I didn't expect changes to SystemManager to
>affect anything but the very core of the SDK.
I would be surprised if your changes made a difference as well but you
never know. I thought the “unofficial” policy was that if your checkins
are tied to a run that fails that you have to investigate, by at minimum,
reverting or showing that the tests pass locally for you.
I’m about to sync up and try it myself as I have an SDK fix to check in.
-Alex
Re: [mustella] all recent SDK tests failed
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I see these tests failing on the VM:
[java] gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
shown)(body:step 13) method returned , expected test1234
[java] gumbo/components/ListDragDrop/events/SparkDNDList_events
ListAbcDND1_dragDrop Failed CompareBitmap(body:step 16) compare
returned[object BitmapData]
[java] gumbo/components/RichEditableText/Properties/RichEditableText_layout_test3
RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step 2)
Timeout waiting for change from retEditable1
I didn't run these locally, as I didn't expect changes to SystemManager to
affect anything but the very core of the SDK.
EdB
On Mon, Nov 3, 2014 at 6:29 PM, Alex Harui <ah...@adobe.com> wrote:
>
> On 11/3/14, 1:08 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
> >Hmm. Still no successes being recorded.
> >
> >This is the most recent failure:
> >
> http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/co
> >nsole
> >
> >There seems to be timeouts in the DataGrid tests consistently.
> >Did anyone change anything in this area in the last two weeks ?
>
> The three errors from that run are:
>
> 1) gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
> Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
> shown)(body:step 13) method returned , expected test1234
>
> 2) gumbo/components/ListDragDrop/events/SparkDNDList_events
> ListAbcDND1_dragDrop Failed CompareBitmap(body:step 16) compare
> returned[object BitmapData]
>
> 3)
> gumbo/components/RichEditableText/Properties/RichEditableText_layout_test3
> RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step 2)
> Timeout waiting for change from retEditable1
>
>
> I don’t see any timeout issues for DataGrid. The DND failure (#2) has
> been intermittent since forever. The other two first appeared in run
> #1123 with Erik’s changes:
>
> Changes for Build #1123
> [erik] Added FP 15 swfversion condition
>
> [erik] Minor rewrite to avoid multiple catch blocks in one statement (JS
> no likey)
>
> [erik] Increment and counterpart don't work with FlexJS '_get()' and
> '_set()'
>
> Run #1121 passed, I don’t know what happened to #1122. Erik are these
> tests passing for you locally?
>
>
> -Alex
>
>
>
>
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: [mustella] all recent SDK tests failed
Posted by Alex Harui <ah...@adobe.com>.
On 11/3/14, 1:08 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>Hmm. Still no successes being recorded.
>
>This is the most recent failure:
>http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/co
>nsole
>
>There seems to be timeouts in the DataGrid tests consistently.
>Did anyone change anything in this area in the last two weeks ?
The three errors from that run are:
1) gumbo/components/DataGrid/Properties/DataGrid_Properties_editable
Editable_twoWayBinding_test Failed AssertMethodValue (method cannot be
shown)(body:step 13) method returned , expected test1234
2) gumbo/components/ListDragDrop/events/SparkDNDList_events
ListAbcDND1_dragDrop Failed CompareBitmap(body:step 16) compare
returned[object BitmapData]
3)
gumbo/components/RichEditableText/Properties/RichEditableText_layout_test3
RichEditableText_Property_maxChars_1 Failed DispatchKeyEvent(body:step 2)
Timeout waiting for change from retEditable1
I don’t see any timeout issues for DataGrid. The DND failure (#2) has
been intermittent since forever. The other two first appeared in run
#1123 with Erik’s changes:
Changes for Build #1123
[erik] Added FP 15 swfversion condition
[erik] Minor rewrite to avoid multiple catch blocks in one statement (JS
no likey)
[erik] Increment and counterpart don't work with FlexJS '_get()' and
'_set()'
Run #1121 passed, I don’t know what happened to #1122. Erik are these
tests passing for you locally?
-Alex
Re: [mustella] all recent SDK tests failed
Posted by Tom Chiverton <tc...@extravision.com>.
On 01/11/14 23:23, Tom Chiverton wrote:
> On Friday 31 Oct 2014 13:38:12 Erik de Bruin wrote:
>> Ok, had to go into the Azure portal and hard reset the VM, for some reason.
>> But it's rebooted, anyway. I also deleted all 'version.txt' files, so we're
>> starting brand new and clean ;-)
> The last run (#1133) seems to just have had some random timeout failures, so we'll see.
>
Hmm. Still no successes being recorded.
This is the most recent failure:
http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/lastFailedBuild/console
There seems to be timeouts in the DataGrid tests consistently.
Did anyone change anything in this area in the last two weeks ?
Tom