47.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36181.html
Sent from the Apache Flex Development mailing list archive at Nabble.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 local
otoko�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
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/MUSTELLA-H
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" wrote:
>Exactly Alex, it failed after all tests I think so. This runid.properties
>is
>used in UnitTesters line 212. Strange. :/
>
>req.url = "htt
pache Flex Committer
piotrzarzyck...@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.
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" 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
>
>Wh
MustellaResultsParser should have ignored those and reported success. Did
it report failure?
On 3/20/14 12:30 AM, "piotrz" 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 ?
>Bec
p://apache-flex-development.247.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36115.html
Sent from the Apache Flex Development mailing list archive at Nabble.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) howev
2
Piotr
-
Apache Flex Committer
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36111.html
Sent from the Apache Flex Development mailing list archive at Nabble.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" wrote:
>This exactly what I did run checkintests from ant and got that error after
>all passed tests.
>
>
.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36107.html
Sent from the Apache Flex Development mailing list archive at Nabble.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
247.n4.nabble.com/MUSTELLA-Help-diagnose-Mustella-failures-tp21123p36094.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I figured out where the problem came from. The wiki page for Mustella [1]
has the wrong path for the location of the trust cfg files. I was blindly
following along and was misled - even though I had fixed the same issue on
the Apache Jenkins server a while ago :-)
The correct path is:
C:\Users\Y
Also, try c:\apacheflex in the trust file. I'm not sure if it knows how to
handle just drive names.
On 2/27/13 1:41 PM, "Alex Harui" wrote:
> If you run mustella on your own windows machine what kind of paths to do you
> see?
>
>
> On 2/27/13 12:36 PM, "Om" wrote:
>
>> I do have the trust
If you run mustella on your own windows machine what kind of paths to do you
see?
On 2/27/13 12:36 PM, "Om" wrote:
> I do have the trust file here:
>
> C:\Users\Administrator\AppData\Roaming\Macromedia\Flash
> Player#Security\FlashPlayerTrust\flex.cfg
>
> The contents of flex.cfg are:
>
> ==
I do have the trust file here:
C:\Users\Administrator\AppData\Roaming\Macromedia\Flash
Player#Security\FlashPlayerTrust\flex.cfg
The contents of flex.cfg are:
===
c:
C|
===
This would be the most permissive setting - even this does not fix the
issue.
I am wondering if the file
You need to put a FlashPlayerTrust file in the appropriate place with the
appropriate settings. We had this issue with Jenkins.
On 2/27/13 12:19 PM, "Om" wrote:
> The player had a security dialog that was preventing it from opening. I
> fixed that. Now I am getting this:
>
> Hello from excl
The player had a security dialog that was preventing it from opening. I
fixed that. Now I am getting this:
Hello from excludes at: Wed Feb 27 12:16:30 GMT-0800 2013
excludes loadTryFile Wed Feb 27 12:16:30 GMT-0800 2013
Exclude: try load from:
file:///C|/apacheflex/mustella/tests/ExcludeListWin.
The player is not running the SWFs. It isn't even getting far enough to
generate a log file.
I hit this once after a new install when the security dialog came up to ask
if it was ok to run the player.exe and never ran the actual player.
On 2/27/13 11:28 AM, "Om" wrote:
> I am trying to run Mu
I am trying to run Mustella on Chris' Win 2008 server. I tried a couple of
tests to see if things work. I did run it 3 times and it fails always.
Peter/Alex, can one of you help out?
Here is what I am running:
Administrator@WIN-2LPF6H9B0Z1 /cygdrive/c/apacheflex/mustella
$ ./mini_run.sh tests/
22 matches
Mail list logo
