You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by piotrz <pi...@gmail.com> on 2014/03/20 00:15:26 UTC
Re: [MUSTELLA] Help diagnose Mustella failures
Hi guys!
I've fixed some bug in sdk. Now I would like to run mustella tests, so based
on point 7 (Bug fixing) from wiki I should run chackintests?? I did it and
all tests theoretically passed but at the end I got this error
http://images.devs-on.net/Image/1yFAdwWTMkGLa5uS-Obszar.png
I don't see anything specific. Is this error mean there is something wrong
with MustellaResultsParser class?
I think probably is something wrong with my configuration...
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36094.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
Thanks Alex. Finally all checkintests passed. I've started to look at TLF
tests. I see that they are Flash Builder projects. Will see if I could run
them.
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36181.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Alex Harui <ah...@adobe.com>.
Seems like someone hit this before. I have to stop for the evening, but
maybe the archives will have the answer, or maybe the simplest is to add
those string to MustellaResultsParser.java so it ignores them.
IIRC, you have to run in the en_US locale and this output might mean you
don't have localhost or you have port restrictions. Not sure.
Thanks,
-Alex
On 3/20/14 11:32 PM, "piotrz" <pi...@gmail.com> wrote:
>I don't know how bot once checking tests passed without errors, but it
>happened only once.
>
>This is the last lines of my console output:
>
>creating macro tar-gzip
>Build sequence for target(s) `mustellaresultsparser' is
>[mustellaresultsparser]
>Complete build sequence is [mustellaresultsparser, check-air-home,
>check-runtime-env, runtime-setup, load-task, ja-locale-samples,
>antTasks-package, additional-packages, clean-temp, fcsh-package,
>stage-lib,
>airspark-compile, check-playerglobal-home, check-tlf-home,
>check-compile-env, modules-dev, asdoc, stage-frameworks-tests,
>graphics-mustella, clean-dependencychecker, setup-dependencychecker,
>stage-modules, states-mustella, componentsmoke-mustella,
>create-description,
>thirdparty-clean, setup-binary-release, thirdparty-downloads, prebuild,
>modules, frameworks, ide, post-build, main, frameworks-rsls,
>sample-themes,
>mustella-setup, basictests, basictests-mustella, checkintests, doc,
>other.locales, binary-package, binary-release, binary-package-tgz,
>stage-mustella, rat-taskdef, sparkTest-mustella, asc-tests, asdoc-package,
>stage-source, source-package-zip, source-package-tgz, source-package,
>fxgCompileTest-mustella, no-rattasks, stage-tlf, create-config,
>source-release-noclean, stage-bin, rat-check,
>source-package-zip-pixelbender, modules-clean, frameworks-clean,
>frameworks-rsls-clean, package-clean, checkintests-clean, clean,
>super-clean, binary-package-zip-pixelbender, no-greptask, rat-dir,
>stage-frameworks, archive-pbj, airmobile-basictests, rat-unzip,
>airmobile-basictests-mustella, checkintests-mobile, help,
>stage-source-pixelbender, source-package-tgz-pixelbender,
>source-package-pixelbender, have-rattasks, layout-mustella,
>check-adobe-extension-manager-env, source-release, release, have-greptask,
>framework-compile, dependencychecker-framework, checkinapp-mustella,
>checkintests-mustella, oldcheckintests, binary-release-noclean,
>rat-check-mustella, air-installers, binary-package-tgz-pixelbender,
>binary-package-zip, javadocs, doc-packages, spark-compile,
>build-pixelbender, version-update, stage-antTasks, dev, antTasks,
>create-md5-pixelbender, create-md5, stage-locales,
>binary-package-pixelbender, release-pixelbender, player-clean,
>airframework-compile, ]
>Entering I:\flexsdk\flex-repo\flex-sdk\build.xml...
>Build sequence for target(s) `mustellaresultsparser' is
>[mustellaresultsparser]
>Complete build sequence is [mustellaresultsparser, check-air-home,
>check-runtime-env, runtime-setup, load-task, ja-locale-samples,
>antTasks-package, additional-packages, clean-temp, fcsh-package,
>stage-lib,
>airspark-compile, check-playerglobal-home, check-tlf-home,
>check-compile-env, modules-dev, asdoc, stage-frameworks-tests,
>graphics-mustella, clean-dependencychecker, setup-dependencychecker,
>stage-modules, states-mustella, componentsmoke-mustella,
>create-description,
>thirdparty-clean, setup-binary-release, thirdparty-downloads, prebuild,
>modules, frameworks, ide, post-build, main, frameworks-rsls,
>sample-themes,
>mustella-setup, basictests, basictests-mustella, checkintests, doc,
>other.locales, binary-package, binary-release, binary-package-tgz,
>stage-mustella, rat-taskdef, sparkTest-mustella, asc-tests, asdoc-package,
>stage-source, source-package-zip, source-package-tgz, source-package,
>fxgCompileTest-mustella, no-rattasks, stage-tlf, create-config,
>source-release-noclean, stage-bin, rat-check,
>source-package-zip-pixelbender, modules-clean, frameworks-clean,
>frameworks-rsls-clean, package-clean, checkintests-clean, clean,
>super-clean, binary-package-zip-pixelbender, no-greptask, rat-dir,
>stage-frameworks, archive-pbj, airmobile-basictests, rat-unzip,
>airmobile-basictests-mustella, checkintests-mobile, help,
>stage-source-pixelbender, source-package-tgz-pixelbender,
>source-package-pixelbender, have-rattasks, layout-mustella,
>check-adobe-extension-manager-env, source-release, release, have-greptask,
>framework-compile, dependencychecker-framework, checkinapp-mustella,
>checkintests-mustella, oldcheckintests, binary-release-noclean,
>rat-check-mustella, air-installers, binary-package-tgz-pixelbender,
>binary-package-zip, javadocs, doc-packages, spark-compile,
>build-pixelbender, version-update, stage-antTasks, dev, antTasks,
>create-md5-pixelbender, create-md5, stage-locales,
>binary-package-pixelbender, release-pixelbender, player-clean,
>airframework-compile, ]
>mustellaresultsparser
>java
>running mustella.MustellaResultsParser with default permissions (exit
>forbidden)
>Running in same VM Executing 'mustella.MustellaResultsParser'
>The ' characters around the executable and arguments are
>not part of the command.
>Unexpected Trace: Uwaga! B��d protoko�u HTTP dotycz�cy ��dania wys�ania,
>12029: /runid.properties?0.43128014821559191395383421111
>Unexpected Trace: Uwaga! B��d protoko�u HTTP dotycz�cy ��dania wys�ania,
>12029: /step_timeout
>results: FAILED
>I:\flexsdk\flex-repo\flex-sdk\build.xml:1677: Java returned: 1
>
>
>
>
>
>-----
>Apache Flex Committer
>piotrzarzycki21@gmail.com
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnos
>e-Mustella-failures-tp21123p36147.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
I don't know how bot once checking tests passed without errors, but it
happened only once.
This is the last lines of my console output:
creating macro tar-gzip
Build sequence for target(s) `mustellaresultsparser' is
[mustellaresultsparser]
Complete build sequence is [mustellaresultsparser, check-air-home,
check-runtime-env, runtime-setup, load-task, ja-locale-samples,
antTasks-package, additional-packages, clean-temp, fcsh-package, stage-lib,
airspark-compile, check-playerglobal-home, check-tlf-home,
check-compile-env, modules-dev, asdoc, stage-frameworks-tests,
graphics-mustella, clean-dependencychecker, setup-dependencychecker,
stage-modules, states-mustella, componentsmoke-mustella, create-description,
thirdparty-clean, setup-binary-release, thirdparty-downloads, prebuild,
modules, frameworks, ide, post-build, main, frameworks-rsls, sample-themes,
mustella-setup, basictests, basictests-mustella, checkintests, doc,
other.locales, binary-package, binary-release, binary-package-tgz,
stage-mustella, rat-taskdef, sparkTest-mustella, asc-tests, asdoc-package,
stage-source, source-package-zip, source-package-tgz, source-package,
fxgCompileTest-mustella, no-rattasks, stage-tlf, create-config,
source-release-noclean, stage-bin, rat-check,
source-package-zip-pixelbender, modules-clean, frameworks-clean,
frameworks-rsls-clean, package-clean, checkintests-clean, clean,
super-clean, binary-package-zip-pixelbender, no-greptask, rat-dir,
stage-frameworks, archive-pbj, airmobile-basictests, rat-unzip,
airmobile-basictests-mustella, checkintests-mobile, help,
stage-source-pixelbender, source-package-tgz-pixelbender,
source-package-pixelbender, have-rattasks, layout-mustella,
check-adobe-extension-manager-env, source-release, release, have-greptask,
framework-compile, dependencychecker-framework, checkinapp-mustella,
checkintests-mustella, oldcheckintests, binary-release-noclean,
rat-check-mustella, air-installers, binary-package-tgz-pixelbender,
binary-package-zip, javadocs, doc-packages, spark-compile,
build-pixelbender, version-update, stage-antTasks, dev, antTasks,
create-md5-pixelbender, create-md5, stage-locales,
binary-package-pixelbender, release-pixelbender, player-clean,
airframework-compile, ]
Entering I:\flexsdk\flex-repo\flex-sdk\build.xml...
Build sequence for target(s) `mustellaresultsparser' is
[mustellaresultsparser]
Complete build sequence is [mustellaresultsparser, check-air-home,
check-runtime-env, runtime-setup, load-task, ja-locale-samples,
antTasks-package, additional-packages, clean-temp, fcsh-package, stage-lib,
airspark-compile, check-playerglobal-home, check-tlf-home,
check-compile-env, modules-dev, asdoc, stage-frameworks-tests,
graphics-mustella, clean-dependencychecker, setup-dependencychecker,
stage-modules, states-mustella, componentsmoke-mustella, create-description,
thirdparty-clean, setup-binary-release, thirdparty-downloads, prebuild,
modules, frameworks, ide, post-build, main, frameworks-rsls, sample-themes,
mustella-setup, basictests, basictests-mustella, checkintests, doc,
other.locales, binary-package, binary-release, binary-package-tgz,
stage-mustella, rat-taskdef, sparkTest-mustella, asc-tests, asdoc-package,
stage-source, source-package-zip, source-package-tgz, source-package,
fxgCompileTest-mustella, no-rattasks, stage-tlf, create-config,
source-release-noclean, stage-bin, rat-check,
source-package-zip-pixelbender, modules-clean, frameworks-clean,
frameworks-rsls-clean, package-clean, checkintests-clean, clean,
super-clean, binary-package-zip-pixelbender, no-greptask, rat-dir,
stage-frameworks, archive-pbj, airmobile-basictests, rat-unzip,
airmobile-basictests-mustella, checkintests-mobile, help,
stage-source-pixelbender, source-package-tgz-pixelbender,
source-package-pixelbender, have-rattasks, layout-mustella,
check-adobe-extension-manager-env, source-release, release, have-greptask,
framework-compile, dependencychecker-framework, checkinapp-mustella,
checkintests-mustella, oldcheckintests, binary-release-noclean,
rat-check-mustella, air-installers, binary-package-tgz-pixelbender,
binary-package-zip, javadocs, doc-packages, spark-compile,
build-pixelbender, version-update, stage-antTasks, dev, antTasks,
create-md5-pixelbender, create-md5, stage-locales,
binary-package-pixelbender, release-pixelbender, player-clean,
airframework-compile, ]
mustellaresultsparser
java
running mustella.MustellaResultsParser with default permissions (exit
forbidden)
Running in same VM Executing 'mustella.MustellaResultsParser'
The ' characters around the executable and arguments are
not part of the command.
Unexpected Trace: Uwaga! B��d protoko�u HTTP dotycz�cy ��dania wys�ania,
12029: /runid.properties?0.43128014821559191395383421111
Unexpected Trace: Uwaga! B��d protoko�u HTTP dotycz�cy ��dania wys�ania,
12029: /step_timeout
results: FAILED
I:\flexsdk\flex-repo\flex-sdk\build.xml:1677: Java returned: 1
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36147.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Alex Harui <ah...@adobe.com>.
I know that is in there, but I'm not sure why I'm not seeing it.
How/where does it show up in the console output?
-Alex
On 3/20/14 3:19 PM, "piotrz" <pi...@gmail.com> wrote:
>Exactly Alex, it failed after all tests I think so. This runid.properties
>is
>used in UnitTesters line 212. Strange. :/
>
>req.url = "http://localhost:" + portNumber + "/runid.properties" + endBit;
>
>Tomorrow I will try to play with sh script for mustella tests.
>
>Piotr
>
>
>
>-----
>Apache Flex Committer
>piotrzarzycki21@gmail.com
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnos
>e-Mustella-failures-tp21123p36144.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
Exactly Alex, it failed after all tests I think so. This runid.properties is
used in UnitTesters line 212. Strange. :/
req.url = "http://localhost:" + portNumber + "/runid.properties" + endBit;
Tomorrow I will try to play with sh script for mustella tests.
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36144.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Alex Harui <ah...@adobe.com>.
MustellaResultsParser should have ignored those and reported success. Did
it report failure?
On 3/20/14 12:30 AM, "piotrz" <pi...@gmail.com> wrote:
>Thanks Alex, Justin. Yes it was some problem with my paths to mm.cfg nad
>flashlog.txt - Now it's ok.
>
>Another question what should I see after those tests ?
>Because I got errors something with HTTP -> 12029: /step_timeout and
>12029:
>/runid.properties?0.84386098850518471395300252962
>
>Piotr
>
>
>
>-----
>Apache Flex Committer
>piotrzarzycki21@gmail.com
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnos
>e-Mustella-failures-tp21123p36111.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
Thanks Alex, Justin. Yes it was some problem with my paths to mm.cfg nad
flashlog.txt - Now it's ok.
Another question what should I see after those tests ?
Because I got errors something with HTTP -> 12029: /step_timeout and 12029:
/runid.properties?0.84386098850518471395300252962
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36111.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
I'm just trying to figure out how it works.
Probably yes Justin I should run TLF tests but now I hope to resolve this
problems and later I'm going to run mustella by mini_run.sh.
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36115.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Alex Harui <ah...@adobe.com>.
I think I saw some tests in the TLF repo, but I've never tried to run them.
On 3/20/14 12:34 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>HI,
>
>> This exactly what I did run checkintests from ant and got that error
>>after
>> all passed tests.
>>
>> Fix -> https://issues.apache.org/jira/browse/FLEX-34057
>
>While the mustella test may pick up something obvious. It may be better
>to run the TLF tests (depending on where your change is) however I don't
>think they are in a working state/or were fully donated - anyone know?
>
>Justin
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> This exactly what I did run checkintests from ant and got that error after
> all passed tests.
>
> Fix -> https://issues.apache.org/jira/browse/FLEX-34057
While the mustella test may pick up something obvious. It may be better to run the TLF tests (depending on where your change is) however I don't think they are in a working state/or were fully donated - anyone know?
Justin
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Alex Harui <ah...@adobe.com>.
There's something wrong with your setup, like mm.cfg is not in the right
place or configured correctly so flashlog.txt isn't being output in the
expected place.
On 3/19/14 10:41 PM, "piotrz" <pi...@gmail.com> wrote:
>This exactly what I did run checkintests from ant and got that error after
>all passed tests.
>
>Fix -> https://issues.apache.org/jira/browse/FLEX-34057
>
>Piotr
>
>
>
>-----
>Apache Flex Committer
>piotrzarzycki21@gmail.com
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnos
>e-Mustella-failures-tp21123p36107.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by piotrz <pi...@gmail.com>.
This exactly what I did run checkintests from ant and got that error after
all passed tests.
Fix -> https://issues.apache.org/jira/browse/FLEX-34057
Piotr
-----
Apache Flex Committer
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36107.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: [MUSTELLA] Help diagnose Mustella failures
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> I've fixed some bug in sdk. Now I would like to run mustella tests, so based
> on point 7 (Bug fixing) from wiki I should run chackintests??
Run checkin test first by doing:
ant checkintests
The mustella tests can be run from the mustella directory using mini_run.sh but you generally only want to run a subset of them - what was the fix for?
Thanks,
Justin