You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2014/10/22 16:59:12 UTC
Checked in failling flexmojos-with-falcon modules
Hi,
I just committed all the projects currently failing in the flexmojos testsuite when using falcon instead of the default compiler. The tests are in the "feature/flexmojos" branch.
While a lot of tests are failing because of unsupported compiler options such as advancedTelemetry or ASDoc generation. One test completely locks up the compiler and some result in Errors.
Debugging them should be easy, especially if you have IntelliJ Utlimate at hands. What you do need however is a mavenized 4.13 FDK as well as access to the Sonatype and Apache Snapshot repositories.
If you have this, simply by setting a breakpoint in the compiler should let you debug the problems (At least this is how I always do it)
About 50% of the tests are succeeding, more than 50% of the failing tests are because of missing ASDoc, missing advancedTelemetry support or seem to be failing because the maven build seems to be running fine, but some other condition the Unit Test checks is not met (I have commented all of these out for now).
It would be great, if the one or the other could check this and help sort out the problems. Certainly this would greatly speed up the time to which we could start actually working with Falcon from Maven.
Chris
AW: Checked in failling flexmojos-with-falcon modules
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... so before anyone starts yelling at me because of license stuff ...
I removed my branch from the Apache repo and created a FlexMojos branch :-)
https://github.com/chrisdutz/flexmojos/tree/feature/falcon
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 22. Oktober 2014 16:59:12
An: dev@flex.apache.org
Betreff: Checked in failling flexmojos-with-falcon modules
Hi,
I just committed all the projects currently failing in the flexmojos testsuite when using falcon instead of the default compiler. The tests are in the "feature/flexmojos" branch.
While a lot of tests are failing because of unsupported compiler options such as advancedTelemetry or ASDoc generation. One test completely locks up the compiler and some result in Errors.
Debugging them should be easy, especially if you have IntelliJ Utlimate at hands. What you do need however is a mavenized 4.13 FDK as well as access to the Sonatype and Apache Snapshot repositories.
If you have this, simply by setting a breakpoint in the compiler should let you debug the problems (At least this is how I always do it)
About 50% of the tests are succeeding, more than 50% of the failing tests are because of missing ASDoc, missing advancedTelemetry support or seem to be failing because the maven build seems to be running fine, but some other condition the Unit Test checks is not met (I have commented all of these out for now).
It would be great, if the one or the other could check this and help sort out the problems. Certainly this would greatly speed up the time to which we could start actually working with Falcon from Maven.
Chris
Re: Final list of issues when running the Flexmojos testsuite with
Falcon
Posted by Alex Harui <ah...@adobe.com>.
Hi Chris,
Great work, thanks for the list.
-Alex
On 10/23/14, 6:33 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Ok ... so now I finished going through the failled tests, I categorized
>them and created new projects demonstrating each individual problem.
>
>Here the summary of problems I found (unfortunately the list isn't really
>small):
>- ASDoc not supported at all
>- Building of Modules with MXML root fails (AS root works however)
>- CSS Style with missing namespace produces NullPointerException
>- SWFs with generated sources with (multiple source paths) are not
>executable
>- Using defines for conditional compilation seems to work, accessing the
>value however doesn't
>- Test SWFs for Air artifacts are not executable in ADL (return Error
>Code 9).
>- Runtime loaded locales don't seem to work at all
>- FontEmbedding doesn't work at all
>- Image embedding doesn't work if the resources are located in a separate
>source path (src/main/resources)
>- Apparat claims the output of Falcon not to be valid SWF files
>
>As I posted earlier, I checked in the tests here:
>https://github.com/chrisdutz/flexmojos/tree/feature/falcon/test/flexmojos-
>tests/identified-problems
>
>Some of these should be easy to fix, some more difficult, but I would
>really like to get started in fixing them. Help greatly appreciated.
>
>At least I now know the things I sort of have to avoid when setting up my
>coding demo for ApacheCon EU
>
>Chris
AW: Final list of issues when running the Flexmojos testsuite with
Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
And I just added the Apache Headers to my test-files ...
they're now all in the falcon repository under my "feature/flexmojos-tests" branch in the Apache repo.
Hope this will help the problems get sorted out sooner.
By the way ... I found a Problem in ScopeStackUnderflowProblem which seemed to have a wrong error message referencing Operand Stack underflow errors instead of Stack Underflows.
Chris
-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Samstag, 25. Oktober 2014 17:38
An: dev@flex.apache.org
Betreff: AW: Final list of issues when running the Flexmojos testsuite with Falcon
Ok today I have investigated more problems and added test-cases for them:
- Usage of mx:Repeater causes "operand stack underflow errors".
- Annotating an Interface with "Bindable" will cause problems.
Chris
-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Donnerstag, 23. Oktober 2014 15:33
An: dev@flex.apache.org
Betreff: Final list of issues when running the Flexmojos testsuite with Falcon
Ok ... so now I finished going through the failled tests, I categorized them and created new projects demonstrating each individual problem.
Here the summary of problems I found (unfortunately the list isn't really small):
- ASDoc not supported at all
- Building of Modules with MXML root fails (AS root works however)
- CSS Style with missing namespace produces NullPointerException
- SWFs with generated sources with (multiple source paths) are not executable
- Using defines for conditional compilation seems to work, accessing the value however doesn't
- Test SWFs for Air artifacts are not executable in ADL (return Error Code 9).
- Runtime loaded locales don't seem to work at all
- FontEmbedding doesn't work at all
- Image embedding doesn't work if the resources are located in a separate source path (src/main/resources)
- Apparat claims the output of Falcon not to be valid SWF files
As I posted earlier, I checked in the tests here: https://github.com/chrisdutz/flexmojos/tree/feature/falcon/test/flexmojos-tests/identified-problems
Some of these should be easy to fix, some more difficult, but I would really like to get started in fixing them. Help greatly appreciated.
At least I now know the things I sort of have to avoid when setting up my coding demo for ApacheCon EU
Chris
AW: Final list of issues when running the Flexmojos testsuite with
Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok today I have investigated more problems and added test-cases for them:
- Usage of mx:Repeater causes "operand stack underflow errors".
- Annotating an Interface with "Bindable" will cause problems.
Chris
-----Ursprüngliche Nachricht-----
Von: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Gesendet: Donnerstag, 23. Oktober 2014 15:33
An: dev@flex.apache.org
Betreff: Final list of issues when running the Flexmojos testsuite with Falcon
Ok ... so now I finished going through the failled tests, I categorized them and created new projects demonstrating each individual problem.
Here the summary of problems I found (unfortunately the list isn't really small):
- ASDoc not supported at all
- Building of Modules with MXML root fails (AS root works however)
- CSS Style with missing namespace produces NullPointerException
- SWFs with generated sources with (multiple source paths) are not executable
- Using defines for conditional compilation seems to work, accessing the value however doesn't
- Test SWFs for Air artifacts are not executable in ADL (return Error Code 9).
- Runtime loaded locales don't seem to work at all
- FontEmbedding doesn't work at all
- Image embedding doesn't work if the resources are located in a separate source path (src/main/resources)
- Apparat claims the output of Falcon not to be valid SWF files
As I posted earlier, I checked in the tests here: https://github.com/chrisdutz/flexmojos/tree/feature/falcon/test/flexmojos-tests/identified-problems
Some of these should be easy to fix, some more difficult, but I would really like to get started in fixing them. Help greatly appreciated.
At least I now know the things I sort of have to avoid when setting up my coding demo for ApacheCon EU
Chris
Final list of issues when running the Flexmojos testsuite with Falcon
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok ... so now I finished going through the failled tests, I categorized them and created new projects demonstrating each individual problem.
Here the summary of problems I found (unfortunately the list isn't really small):
- ASDoc not supported at all
- Building of Modules with MXML root fails (AS root works however)
- CSS Style with missing namespace produces NullPointerException
- SWFs with generated sources with (multiple source paths) are not executable
- Using defines for conditional compilation seems to work, accessing the value however doesn't
- Test SWFs for Air artifacts are not executable in ADL (return Error Code 9).
- Runtime loaded locales don't seem to work at all
- FontEmbedding doesn't work at all
- Image embedding doesn't work if the resources are located in a separate source path (src/main/resources)
- Apparat claims the output of Falcon not to be valid SWF files
As I posted earlier, I checked in the tests here: https://github.com/chrisdutz/flexmojos/tree/feature/falcon/test/flexmojos-tests/identified-problems
Some of these should be easy to fix, some more difficult, but I would really like to get started in fixing them. Help greatly appreciated.
At least I now know the things I sort of have to avoid when setting up my coding demo for ApacheCon EU
Chris
AW: Checked in failling flexmojos-with-falcon modules
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Alex,
while I haven't done any performance tests yet it is still my impression that Falcon is quite a bit faster, but as long as 40% of the tests don't seem to be providing useable results, it's too early to be happy about that. Don't know if the fixes to the remaining problems would slow things down.
I found some more problem Areas:
- It seems to be impossible to build MXML based Modules, while AS base Modules compile nicely MXML ones don't and it doesn't matter if they are based upon Spark or MX Module.
- If someone uses a CSS with styles without a namespace, Falcon dies of a NullPointerException
- If I have an Application that uses a generated source class, the compiler seems to finish without complaining, but when executing the resulting SWF the flashplayer claims that for example the generated class is trying to reference an unknown function (One which is definitely part of Object).
While some of the problems seem to be related with compiling really old flex 2 and flex 3 applications, some things however are real problems.
I added a sub-folder to my flexmojos Falcon testsuite in which I manually created some tiny projects that reproduce the errors I identified in the official testsuite (https://github.com/chrisdutz/flexmojos/tree/feature/falcon/test/flexmojos-tests/identified-problems). I will be able to place these in the Apache repo, but I'm still working through the failled tests to find out what's going wrong. And I'll continue spotting the problems. It would be great if someone could have a look the how to fix them, doing both is a really huge task.
Chris
________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Donnerstag, 23. Oktober 2014 03:28
An: dev@flex.apache.org
Betreff: Re: Checked in failling flexmojos-with-falcon modules
Hi,
> While a lot of tests are failing because of unsupported compiler options such as advancedTelemetry
Advanced telemetry should be relatively easy to add (and quite useful) ,I add it to the existing compc compiler and basically it's just flag in the swf header.
> or ASDoc generation.
That's probably going to be a little harder, the current solution is a mess of XML and HTML templates, XML style sheets, and Java code that's not that straight forward to modified. It wouldn't be easy to port across.
Out of interest is there any performance tests in there? Would be interesting to know if you getter better performance (esp on Java 1.8).
Thanks,
Justin
Re: Checked in failling flexmojos-with-falcon modules
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> While a lot of tests are failing because of unsupported compiler options such as advancedTelemetry
Advanced telemetry should be relatively easy to add (and quite useful) ,I add it to the existing compc compiler and basically it's just flag in the swf header.
> or ASDoc generation.
That's probably going to be a little harder, the current solution is a mess of XML and HTML templates, XML style sheets, and Java code that's not that straight forward to modified. It wouldn't be easy to port across.
Out of interest is there any performance tests in there? Would be interesting to know if you getter better performance (esp on Java 1.8).
Thanks,
Justin