OK, this makes it 'official': these tests only fail on FP 16!
Given that nugget of info, can anyone suggest a 'solution'?
EdB
On Tue, Jan 6, 2015 at 7:04 PM, wrote:
> rc_flex-sdk_mustella - Build # 86 - Failure:
>
> http://flex-mustella.cloudapp.net/job/rc_flex-sdk_mustella/86/
>
> Changes f
>
> Hi Mahmoud,
>
> I think you should commit this fix into develop branch and Erik will
> "cherry
> pick up it" if he decide that is valuable for current release. :)
>
Ok, thanks! :)
I like me some cherries, so I picked yours up for this release ;-)
Thanks!
EdB
On Wed, Jan 7, 2015 at 9:54 AM, Mahmoud Ali wrote:
>>
>> Hi Mahmoud,
>>
>> I think you should commit this fix into develop branch and Erik will
>> "cherry
>> pick up it" if he decide that is valuable for current re
If you go to:
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_test/
Click on 'Latest Test Result', and expand one of the failing tests, it
shows you the stack trace.
EdB
On Tue, Jan 6, 2015 at 7:04 PM, Mihai Chira wrote:
> I've got a problem running FLEX_34625_Tests.as. The test report
P.S. I picked up these fixes because FlatSpark is a high profile new
feature for this release, and we want to make a good impression. Any
other changes to 'develop' will likely not be part of the release
(sorry, Mihai).
EdB
On Wed, Jan 7, 2015 at 11:35 AM, Erik de Bruin wrote:
> I like me some
>
> I like me some cherries, so I picked yours up for this release ;-)
>
Awesome, Erik! Thanks! :)
Mihai,
Thanks for taking the effort to figure out how to automate the
FlexUnit tests using the new framework. I'm sorry you had to figure it
out on your own. However, it did shame me into 'finishing' the Wiki
entry on the subject. Maybe you can have a look at it and see if it
makes sense from your
I'm trying to receive mouseover events on a FlexJS object whose element is a
. I've discovered this code in
org.apache.flex.events.EventDispatcher.prototype.addEventListener:
/**
* A bit of a hack, but for 'native' HTML element based controls, we
* want to listen to the 'native' events f
That 'hack' seems vaguely familiar... ;-)
In your source's inheritance chain, is there either a base class
'goog.ui.component' or 'goog.ui.control'?
EdB
On Wed, Jan 7, 2015 at 1:26 PM, Peter Ent wrote:
> I'm trying to receive mouseover events on a FlexJS object whose element is a
> . I've di
flex-sdk_release-candidate - Build #62 - Successful
Changes since last build:
[erik] Fixes a bug on FlatSpark Button and ButtonIcon skins when borderRadius
is changed
[erik] FlatSpark: Fixes an error when applying chromeColor, FLEX-34696
For more information, check the console output at
http:
Should there be a general property added to the AS classes that passes the
JS/html equivalent?
-Mark
-Original Message-
From: Erik de Bruin [mailto:e...@ixsoftware.nl]
Sent: Wednesday, January 07, 2015 7:44 AM
To: dev@flex.apache.org
Subject: Re: [FlexJS] Listening for mouse events
That
Peter, try syncing up to the repo. The hack has been ‘improved’ and
should give you what you need.
-Alex
On 1/7/15, 4:44 AM, "Erik de Bruin" wrote:
>That 'hack' seems vaguely familiar... ;-)
>
>In your source's inheritance chain, is there either a base class
>'goog.ui.component' or 'goog.ui.co
On 1/7/15, 12:16 AM, "Erik de Bruin" wrote:
>OK, this makes it 'official': these tests only fail on FP 16!
>
>Given that nugget of info, can anyone suggest a 'solution'?
Should be something like this:
1) See if any of the images are OS specific. If so, find one of those
machines, otherwise y
The failing suites are:
1 - List
The failures here were due to a previous fix to the way the
selectedIndices are stored, so I fixed the Mustella test to reflect
the new property value.
2 - SpinnerList (fails 2)
This was indeed a question of resetting the 'accentColor' style to
'#00', which fi
OK, we're getting closer:
- still hoping for an AIR 16 release
- Justin needs a bit more time for the final fixes for the 'legal' issues
- we have two sets of Mustella failures to worry about:
- FXG tests fail with FP/AIR 16
- a whole bunch of mobile tests fail
I'm sure the first two will res
It has come to my attention that FlexUnit has some metadata tags wrongly
defined, in org.flexunit.runner.FlexUnitCore there are:
[Event(type="testsComplete", type="flash.events.Event")]
[Event(type="runnerStart", type="flash.events.Event")]
[Event(type="testsStopped", type="flash.events.Event")
On 1/7/15, 7:17 AM, "Erik de Bruin" wrote:
>
> - a whole bunch of mobile tests fail
I looked into this last night. I think there may be several issues, but I
think most failures are caused by a slight change to the graphics for the
BusyIndicator used in the test. IOW, most ActionBar tests a
> Separately, are we ready to remove the OSMF and SWFObject prompts from the
> install scripts?
If I understood correctly, Justin has picked that up... Justin?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Didn't fix it, turns out I was still running local tests on 4.13 build
- which I created when looking for 'last known good' :-(
EdB
On Wed, Jan 7, 2015 at 5:35 PM, wrote:
> Repository: flex-sdk
> Updated Branches:
> refs/heads/release4.14.0 c81e27134 -> 51a6c519d
>
>
> Revert "Fix last 2 Sp
flex-sdk_release-candidate - Build #63 - Successful
Changes since last build:
[erik] Fixes most (not all) SpinnerList failures in the mobile Mustella suite
[erik] Fix test to match 'new' selectedIndices value (FLEX-34657)
For more information, check the console output at
http://apacheflexbuild
flex-sdk_release-candidate - Build #64 - Successful
Changes since last build:
[erik] Fix last 2 SpinnerList failures
[erik] Revert "Fix last 2 SpinnerList failures"
For more information, check the console output at
http://apacheflexbuild.cloudapp.net:8080/job/flex-sdk_release-candidate/64/.
Hi,
I have removed "Ignore" tag from the test "spanElementReplaceTextInvalidPos"
-> ElementOperationTest.
There is something interesting happening there which might not be exactly
related to the TLF.
We have this part of code.
https://paste.apache.org/44I4
It's failing because it do not find t
Interestingly, the meta tags have been wrong since they were first added
nearly 5 years ago:
https://github.com/apache/flex-flexunit/commit/d594ab33d62bc5ba6f70888bfbe23a1bb2280d0b
On Wed, Jan 7, 2015 at 4:43 PM, Héctor A wrote:
> It has come to my attention that FlexUnit has some metadata tag
I came across a little bug using the calloutButton. I can duplicate the bug
everytime. When the callout of the calloutButton is open during a device
screen rotatation, the popup repositions incorrectly. The bug does not show
up on the simulator, but only on each of the 3 android devices that I used
Wondering if I can use Java 1.7 APIs for some code that would go in the
utilities repository or if I should stay with 1.6?
Thanks,
-Darrell
Hi Kevin,
One thing after first look into your code.
Once screen rotated did you try call method invalidatePosition() in your
event listener instead adding new flag ? It should do the job and reposition
Callout. If it won't have any effect try add also invalidateDisplayList();
Thanks,
Piotr
In my opinion, there is no need to stick to outdated versions of Java.
EdB
On Thu, Jan 8, 2015 at 4:41 AM, Darrell Loverin
wrote:
> Wondering if I can use Java 1.7 APIs for some code that would go in the
> utilities repository or if I should stay with 1.6?
>
> Thanks,
>
>
> -Darrell
--
Ix
Hi Neverbirth,
I've just changed it. Let's see what will happened. If you will have time
try to test it.
I think artefacts will be available after the build here:
http://apacheflexbuild.cloudapp.net:8080/job/flex-flexunit/
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this me
28 matches
Mail list logo
