flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christofer Dutz <christofer.d...@c-ware.de>
Subject AW: AW: AW: Test Failures when building flex-falcon
Date Thu, 01 Oct 2015 15:48:53 GMT
Ok ... so I got the flex-sdk to checkout and start compiling. 
In order to be able to run "ant release" I need to do the download thing to download the playerglobal.swc
Unfortunately after downloading the release targets delete everything again ... so how can
I still build everything?
I need something like a "ant allmost-the-same-as-release-but-without-deleting-the-thirdparty-libs"


Von: Christofer Dutz <christofer.dutz@c-ware.de>
Gesendet: Donnerstag, 1. Oktober 2015 13:40
An: Alex Harui; dev@flex.apache.org
Betreff: AW: AW: AW: Test Failures when building flex-falcon

Well I want SNAPSHOTS to be published every day ... in order to do that I need to setup a
Jenkins Job on builds.apache.org ... or someone else configures his private machine to do
that manually using his credentials.

We need more than 3-4 people testing this. In order to get them we need to make it easy for
them to do so. There's no use in writing READMEs with:

1. First you have to download 10 different thing
2. Then you need to Set 20 Environment Variables
3. Then Run task A ... this will fail, but just ignore
4. After that run task Y on project B ...
5. Now you can run Task A again ... this time it will succeed :-)

Like this I predict the number of people will not grow as fast as it simply has to. That's
why I think we should concentrate a little more on making the build easier.


Von: Alex Harui <aharui@adobe.com>
Gesendet: Donnerstag, 1. Oktober 2015 10:51
An: Christofer Dutz; dev@flex.apache.org
Betreff: Re: AW: AW: Test Failures when building flex-falcon

Yes, it could be better.  Feel free to make it better or at least explain
how you would make it better.

I have put together ant targets in flex-asjs where you can use that as the
starting point for building everything.  That is what I expected the
consumers of the proposed release bits to experience.  It builds
falcon/compiler and falcon/compiler.jx and skips the tests.  It doesn’t
lend itself to Jenkins builds which is what you are experiencing.  I don’t
expect many of the consumers of our release to create Jenkins builds.

Is this issue really worth holding up the release?  It doesn’t have to be
fixed by changing the release bits.  You could lock the Falcon Build to
some recent download of FlexJS, instead of the latest build, but do we
want to do that?


On 10/1/15, 12:46 AM, "Christofer Dutz" <christofer.dutz@c-ware.de> wrote:

>Well that seems to be the only option and it's the only way for me to
>have something to show later on, but I'll never vote +1 on a software
>that I have to build this way. So it needs fixing before initiating a
>Von: omuppi1@gmail.com <omuppi1@gmail.com> im Auftrag von OmPrakash
>Muppirala <bigosmallm@gmail.com>
>Gesendet: Donnerstag, 1. Oktober 2015 09:43
>An: dev@flex.apache.org
>Cc: Alex Harui
>Betreff: Re: AW: Test Failures when building flex-falcon
>Don't know the exact details, but perhaps disable the failing tests for
>build to succeed.  Then enable them and build again?
>On Thu, Oct 1, 2015 at 9:06 AM, Christofer Dutz
>> So the falcon test fails, cause the asjs is not compiled? And asjs
>> compile without falcon ... so who can point out the problem with this?
>> Chris
>> ________________________________________
>> Von: Alex Harui <aharui@adobe.com>
>> Gesendet: Donnerstag, 1. Oktober 2015 05:32
>> An: Christofer Dutz; dev@flex.apache.org
>> Betreff: Re: AW: Test Failures when building flex-falcon
>> On 9/30/15, 2:37 PM, "Christofer Dutz" <christofer.dutz@c-ware.de>
>> >Ok, now after using the maven-central download I managed to have the
>> >release" build pass successfully, now I can also see the rb.swc files
>> >created successfully ... so I re-tried the falcon build "ant main" and
>> >still this stupid test is failing ... so please don't start a vote on
>> >falcon till the testsuite passes. In order to have the demos for my
>> >tomorrow working, I'll let the build continue with failures, but this
>> >to be fixed ASAP.
>> AFAICT, the test that is failing is depending on SWCs from flex-asjs,
>> which don’t exist because that build still fails.
>> HTH,
>> -Alex

View raw message