Ran the tests myself. The bitmap shows a horizontal line through the
reference image that is not in the result image. Please verify that you
are seeing the same. You'll need to investigate whether that line should
be there or not and if it is, figure out which code change resulted in the
line no
On 9/5/13 3:43 PM, "Mark Kessler" wrote:
>Ok so I ran [1] with createdImages and the test passed. Deleted the two
>XML files it created and ran [2] without the create option and it still
>passed. Image looks fine. So do I upload the two new baseline images ?
Well, what are the differences be
Ok so I ran [1] with createdImages and the test passed. Deleted the two
XML files it created and ran [2] without the create option and it still
passed. Image looks fine. So do I upload the two new baseline images ?
[1] mini_run.sh -caseName=Editable_variableRowHeight
tests/gumbo/components/Dat
Hi,
We can fix things in release (vi hotfixs or directly) but the changes need to
be tested, develop is the best place to do that as that's what the CI runs off.
Last release we made changes in release and merge back to develop frequently.
Even if we didn't do this at some point you need to mer
On 9/5/13 3:04 AM, "Erik de Bruin" wrote:
>Alex, you wrote:
>
>"That's why I've invested my time on other mustella tools. If you
>compile every test, then run MustellaDependencyDB, it will create a
>database of dependencies such that, if you run MustellaTestChooser, it
>will generate a list of
I reproduced the failures on Mac and AIR3.4. My run took 77 minutes but
my computer was slow. Totals: 3958 passes, 2 failures. Did you see that
many tests run? And more importantly, did the tests that we see fail
pass? Maybe the tests never ran.
My local.properties only has target_os_name=and
The only thing making this model merging back the release branch to the dev
one is they allow hotfixing on the release branch, so, yes, if they are
some, we need to merge them back but here at Apache Flex we don't have this
emergency to deliver, so, the bugs can be fixed on the dev branch and
anoth
Maybe I'm not understanding the diagram on their page. To me there is a
line back from release branch to develop. It shouldn't have anything to
do with hotfixes, just bug fixes found and fixed after the release branch
is cut. I think the recommended practice when you have a release branch
is to
On 9/5/13 6:47 AM, "Kessler CTR Mark J" wrote:
>Not sure how we changed a bitmap for variableRowHeight with the 3 below
>commits. I can look at the bitmaps when I get home. If it looks
>correct, how do I update the bitmap it uses to check with? Just copy
>it's compared one and push it back t
Hi, bug https://issues.apache.org/jira/browse/FLEX-32599 still not in
release build 4.10.0 runtime still exist
On Wed, May 29, 2013 at 10:35 AM, Justin Mclean (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/FLEX-32599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabp
In this particular case, merging fixes made on branches are enough IMO, no
needs to merge back the entire release, I guess it should be a painful job
sorting out what to keep or not otherwise.
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : jeudi 5 septembre 2013 18
Not sure how to tell all the settings its using, but the bottom of the Jenkins
report says
Settings:
player.version = 11.1
air.version = 3.7
Hope fully it's something simple like you're anti-aliasing idea.
Thanks Alex,
-Mark
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com
On 9/5/13 3:23 AM, "Frédéric THOMAS" wrote:
>After running sdk/ant, git status report only " flex-sdk-description.xml"
>as
>modified file, that's 5 months or so I didn't have a look in the SDK,
>could
>you tell me what should be done in order the build number be created only
>on
>the release bu
I meant: that means that all suites run on the same player combination
about once every two days ;-)
EdB
On Thu, Sep 5, 2013 at 5:28 PM, Erik de Bruin wrote:
> And done. The 3 suites (main, AIR and mobile) now rotate these player
> combinations:
>
> 11.1/3.7
> 11.7/3.7
> 11.8/3.8
> 11.9/3.9
>
And done. The 3 suites (main, AIR and mobile) now rotate these player
combinations:
11.1/3.7
11.7/3.7
11.8/3.8
11.9/3.9
That means each suite is run about once every two days.
EdB
On Thu, Sep 5, 2013 at 6:59 AM, Erik de Bruin wrote:
> On it.
>
> EdB
>
>
>
> On Thursday, September 5, 2013, Ju
Not sure how we changed a bitmap for variableRowHeight with the 3 below
commits. I can look at the bitmaps when I get home. If it looks correct, how
do I update the bitmap it uses to check with? Just copy it's compared one and
push it back to the sdk?
-Mark
-Original Message-
From:
After running sdk/ant, git status report only " flex-sdk-description.xml" as
modified file, that's 5 months or so I didn't have a look in the SDK, could
you tell me what should be done in order the build number be created only on
the release build envisioning what impact it could introduce ?
-Fred
Yup. What I meant was, there used to be a working demo of the code, just
below the code snippet. But now it just displays 'Not found'. So I think,
working link might have got changed. Not sure what's wrong though.
On Thu, Sep 5, 2013 at 3:20 PM, Kessler CTR Mark J <
mark.kessler@usmc.mil> wro
Alex, you wrote:
"That's why I've invested my time on other mustella tools. If you
compile every test, then run MustellaDependencyDB, it will create a
database of dependencies such that, if you run MustellaTestChooser, it
will generate a list of tests that need to be run based on the changed
file
It actually has a modified 404 page in it, apparently.
EdB
On Thu, Sep 5, 2013 at 11:50 AM, Kessler CTR Mark J
wrote:
> You mean where the example is supposed to be shown it has the main page in it
> instead?
>
> -Mark
>
> -Original Message-
> From: Deepak MS [mailto:megharajdee...@gm
Also, all tests are run against at least AIR 3.7.
EdB
On Thu, Sep 5, 2013 at 11:46 AM, Erik de Bruin wrote:
> The VM runs Windows, maybe that is a factor?
>
> EdB
>
>
>
> On Thu, Sep 5, 2013 at 11:44 AM, Justin Mclean
> wrote:
>> Hi,
>>
>> OK no idea what's going on here but if I run the mob
You mean where the example is supposed to be shown it has the main page in it
instead?
-Mark
-Original Message-
From: Deepak MS [mailto:megharajdee...@gmail.com]
Sent: Thursday, September 05, 2013 1:12 AM
To: dev@flex.apache.org
Subject: Re: http://blog.flexexamples.com/
I tried to bro
The VM runs Windows, maybe that is a factor?
EdB
On Thu, Sep 5, 2013 at 11:44 AM, Justin Mclean wrote:
> Hi,
>
> OK no idea what's going on here but if I run the mobile tests like so on OSX:
>
> ./mini_run.sh -mobile tests/mobile
>
> I get zero failures after about it runs for about 25 minut
Sorry for the delay, I was reading this before to go to sleep, it was more
than 5am so, I answer only now.
> It mostly likely be fixed on the release branch and merged back to develop
when done, but fixing on develop, testing (see CI above) and then merging
into release may also be an option.
You
Hi,
OK no idea what's going on here but if I run the mobile tests like so on OSX:
./mini_run.sh -mobile tests/mobile
I get zero failures after about it runs for about 25 minutes.
The local.properties file contains this:
use_apollo=true
run_mobile_tests=true
target_os_name=android
device_name=
On 04.09.2013 21:48, Alex Harui wrote:
It is interesting that folks using IntelliJ don't complain about
compile time issues yet IntelliJ doesn't use incremental compiles.
Actually they do [1]. Users ask to bring back support of incremental
fcsh compiler because it gives performance gain for som
26 matches
Mail list logo
