You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Harbs <ha...@gmail.com> on 2015/01/04 13:03:51 UTC

TLF test output

Erik, I think this question is for you.

Is there any way to see the output files from the TLF unit tests on the Jenkins server?

They should be located here: [TLF]/bin/apps/automation_apps/bin

I’d like to be able to check the output and stack trace of failed tests.

Thanks,
Harbs

Re: TLF test output

Posted by piotrz <pi...@gmail.com>.
Maybe some other ant script than this in TLF folder are cleaning bin
directory. Just a thought.

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44138.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF test output

Posted by piotrz <pi...@gmail.com>.
I know why these reports are not appear on build VM.

Once build of TLF is finished, automatically is launching build of flex-sdk.
Flex SDK is launching build.xml file from this location
frameworks\projects\textLayout\build.xml
and there is a target:

<target name="clean-external" description="clean in flex-tlf repo"
unless="src.folder.exists">
        <echo message="cleaning ${TLF_HOME}" />
        <ant dir="${TLF_HOME}" target="clean"/>
    </target>

The console output is saying:

clean-external:
     [echo] cleaning c:\Jenkins\workspace\flex-sdk/../flex-tlf
     [echo] FLEX_HOME is c:\Jenkins\workspace\flex-sdk
     [echo] Minimal test is set false
  [taskdef] Could not load definitions from resource flexTasks.tasks. It
could not be found.

clean:
   [delete] Deleting directory c:\Jenkins\workspace\flex-tlf\bin 

I'm wondering whether 
<ant dir="${TLF_HOME}" target="clean"/>
these command is launching "clean" from flex-tlf\build.xml.  Anyone know how
it's working ?

If it is we should write some custom clean which won't remove our flex unit
reports.

Piotr





-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44139.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF test output

Posted by piotrz <pi...@gmail.com>.
Hi Guys,

This is really weird, reports should appear in this location
/bin/apps/automation_apps/bin.

I will try to place tests reports in other location. Will see how jenkins
respond. 

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44137.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF test output

Posted by Harbs <ha...@gmail.com>.
Interesting.

I’m not sure how to follow up on the failures. Do you get any of the failures on your local machine?

On Jan 4, 2015, at 3:58 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> My bad: I see the output you're looking for on my local machine. On
> the build VM however, the 'bin' dir only contains the SWC and no sub
> dirs :-(
> 
> EdB
> 
> 
> 
> On Sun, Jan 4, 2015 at 1:26 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> I don't see that path, neither on the build machine nor on my local machine :-(
>> 
>> Is there maybe a cleanup after a run when you do 'ant all' that makes
>> the 'bin' directory go away?
>> 
>> EdB
>> 
>> 
>> 
>> On Sun, Jan 4, 2015 at 1:03 PM, Harbs <ha...@gmail.com> wrote:
>>> Erik, I think this question is for you.
>>> 
>>> Is there any way to see the output files from the TLF unit tests on the Jenkins server?
>>> 
>>> They should be located here: [TLF]/bin/apps/automation_apps/bin
>>> 
>>> I’d like to be able to check the output and stack trace of failed tests.
>>> 
>>> Thanks,
>>> Harbs
>> 
>> 
>> 
>> --
>> 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: TLF test output

Posted by Harbs <ha...@gmail.com>.
Awesome!

This will be very helpful. Thanks!

On Jan 5, 2015, at 11:10 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> The job status screen:
> 
> http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/
> 
> Now holds both an 'artifacts' section, where the XMLs are archived, as
> well as an 'test results' section, where you get a JUnit style report.
> 
> HTH,
> 
> EdB
> 
> 
> 
> On Mon, Jan 5, 2015 at 9:09 AM, piotrz <pi...@gmail.com> wrote:
>> Great Erik! Just let us know in what location archived reports will be
>> stored.
>> 
>> Piotr
>> 
>> 
>> 
>> -----
>> Apache Flex PMC
>> piotrzarzycki21@gmail.com
>> --
>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44148.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl


Re: TLF test output

Posted by Erik de Bruin <er...@ixsoftware.nl>.
The job status screen:

http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/

Now holds both an 'artifacts' section, where the XMLs are archived, as
well as an 'test results' section, where you get a JUnit style report.

HTH,

EdB



On Mon, Jan 5, 2015 at 9:09 AM, piotrz <pi...@gmail.com> wrote:
> Great Erik! Just let us know in what location archived reports will be
> stored.
>
> Piotr
>
>
>
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44148.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF test output

Posted by piotrz <pi...@gmail.com>.
Great Erik! Just let us know in what location archived reports will be
stored.

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44148.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF test output

Posted by Erik de Bruin <er...@ixsoftware.nl>.
Now I know where they end up, I'll 'archive' them using Jenkins, and
have Jenkins 'analyze' them as well. That way we get a report AND keep
the files (of the last run) in a readily available URL.

EdB



On Mon, Jan 5, 2015 at 7:43 AM, Harbs <ha...@gmail.com> wrote:
> Why don’t we just output the test results to somewhere outside the bin directory?
>
> Maybe test_output or something?
>
> On Jan 5, 2015, at 8:32 AM, piotrz <pi...@gmail.com> wrote:
>
>> The second thing about that is - Maybe we shouldn't build SDK right after
>> building of TLF ?
>>
>> It will resolve the problem without modifying code.
>>
>> Erik what do you thing about that ?
>>
>> Piotr
>>
>>
>>
>> -----
>> Apache Flex PMC
>> piotrzarzycki21@gmail.com
>> --
>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44143.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF test output

Posted by Harbs <ha...@gmail.com>.
Why don’t we just output the test results to somewhere outside the bin directory?

Maybe test_output or something?

On Jan 5, 2015, at 8:32 AM, piotrz <pi...@gmail.com> wrote:

> The second thing about that is - Maybe we shouldn't build SDK right after
> building of TLF ?
> 
> It will resolve the problem without modifying code. 
> 
> Erik what do you thing about that ?
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44143.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.


Re: TLF test output

Posted by piotrz <pi...@gmail.com>.
The second thing about that is - Maybe we shouldn't build SDK right after
building of TLF ?

It will resolve the problem without modifying code. 

Erik what do you thing about that ?

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/TLF-test-output-tp44123p44143.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF test output

Posted by Erik de Bruin <er...@ixsoftware.nl>.
My bad: I see the output you're looking for on my local machine. On
the build VM however, the 'bin' dir only contains the SWC and no sub
dirs :-(

EdB



On Sun, Jan 4, 2015 at 1:26 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> I don't see that path, neither on the build machine nor on my local machine :-(
>
> Is there maybe a cleanup after a run when you do 'ant all' that makes
> the 'bin' directory go away?
>
> EdB
>
>
>
> On Sun, Jan 4, 2015 at 1:03 PM, Harbs <ha...@gmail.com> wrote:
>> Erik, I think this question is for you.
>>
>> Is there any way to see the output files from the TLF unit tests on the Jenkins server?
>>
>> They should be located here: [TLF]/bin/apps/automation_apps/bin
>>
>> I’d like to be able to check the output and stack trace of failed tests.
>>
>> Thanks,
>> Harbs
>
>
>
> --
> 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: TLF test output

Posted by Erik de Bruin <er...@ixsoftware.nl>.
I don't see that path, neither on the build machine nor on my local machine :-(

Is there maybe a cleanup after a run when you do 'ant all' that makes
the 'bin' directory go away?

EdB



On Sun, Jan 4, 2015 at 1:03 PM, Harbs <ha...@gmail.com> wrote:
> Erik, I think this question is for you.
>
> Is there any way to see the output files from the TLF unit tests on the Jenkins server?
>
> They should be located here: [TLF]/bin/apps/automation_apps/bin
>
> I’d like to be able to check the output and stack trace of failed tests.
>
> Thanks,
> Harbs



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl