Royale_Release_Step_008 - Build # 31 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 31 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/31/
 to view the results.

Royale_Release_Step_008 - Build # 30 - Failure!

[apacheroyaleci]

Royale_Release_Step_008 - Build # 30 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_008/30/
 to view the results.

Release Step 007 Succeeded

[apacheroyaleci]

>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.8 
-DskipTests=true
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.8-rc4

You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the
following commands:
git push

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_005 - Build # 17 - Still Failing!

[apacheroyaleci]

Royale_Release_Step_005 - Build # 17 - Still Failing:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/17/
 to view the results.

Royale_Release_Step_005 - Build # 16 - Failure!

[apacheroyaleci]

Royale_Release_Step_005 - Build # 16 - Failure:

Check console output at 
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_005/16/
 to view the results.

Release Step 004 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands:
git push
git checkout release/0.9.8
git push -u origin release/0.9.8

You will need your Apache/Github username and 2FA token.

Release Step 003 Succeeded

[apacheroyaleci]

>From the royale-compiler repo:
1. Run:
  ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.8
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign 
-Drelease.version=0.9.8
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload 
-Drelease.version=0.9.8
This will upload the signed artifacts to Maven Release Staging. If you are 
getting 401 responses from Nexus (permission denied) please be sure to have 
your apache creedentials configured in your .m2/settings.xml file. 

Feel free to use this template if you haven't got a settings.xml yet:


http://maven.apache.org/SETTINGS/1.1.0 
http://maven.apache.org/xsd/settings-1.1.0.xsd; 
xmlns="http://maven.apache.org/SETTINGS/1.1.0;
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>
  


  apache.releases.https
  {your apache user id}
  {your apache user password}

  


(Be sure to replace the placeholders with your actual apache committer id and 
your Apache password)

If you already have a settings.xml, just be sure the "server" block containing 
your credentials is added to a servers block in that file.

Do not "Close" the staging repository until the other repos have been added.

Release Step 002 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.8-rc4

You will need your Apache/Github username and 2FA token.

Release Step 001 Succeeded

[apacheroyaleci]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.8
git push -u origin release/0.9.8

You will need your Apache/Github username and 2FA token.

RE: Mustella Tests

[Yishay Weiss]

Merged it, thanks.

From: Edward Stangler
Sent: Wednesday, July 21, 2021 7:31 AM
To: ‪Yishay Weiss; 
dev@royale.apache.org
Subject: Re: Mustella Tests


PR #1134 fixes the issue.



On 7/9/2021 7:37 AM, Edward Stangler wrote:

Yes, I've reproduced with a stand-alone test case based on the tests.

I know what the problem is, now.

The fix is easy, and I've tested it, but I need a little more time with it.



On 7/9/2021 6:53 AM, ‪Yishay Weiss wrote:
Good to know you are working on it. Were you able to run the tests? If not, it 
may be enough to run an app with an includeIn and a state change. As you can 
see up thread contanerviiew.addviewport is what's failing.

My CLT-L09. On O2.


 Original message 
From: Edward Stangler
Date: Fri, 9 Jul 2021, 05:07
To: Yishay Weiss , 
dev@royale.apache.org
Subject: Re: Mustella Tests

I think the last few comments in PR 1041 are the same issue.  I started to 
explain why I made this commit.

Basically, the commit was needed so that I could do more important work in 
other areas, to fix several difficult issues.  (I have uncommitted work from 
that time period.)  For one thing, it made debugging much much easier.  And it 
helped in some other ways.  (I understand what Alex mentioned, but I think the 
commit was an improvement.  But I need to see if I left something out of the 
commit.  Obviously, if this test error remains, the commit needs to be rolled 
back.)

Sorry for the delay in addressing this.  I'm working on it right now (trying to 
get the tests running on my PC).



On 7/8/2021 7:52 AM, Yishay Weiss wrote:

Looks like reverting 6d1c020577cec69b6207a5b46356b6a2b74f308c fixes it



@Edward Stangler , do you think you can have a 
look?



Here’s what I needed to do to run Mustella tests:


a.   Make sure the following env vars are defined (I’m giving my values for 
reference)



AIR_HOME=C:\MoonshineSDKs\Flex_SDK\Flex_4.16.1_AIR_32.0

FLASHPLAYER_DEBUGGER=C:\dev\content_debugger\flashplayer_32_sa_debug.exe

GOOG_HOME=C:\dev\full_royale_sdk\royale-asjs\js\lib\google\closure-library

PLAYERGLOBAL_HOME=C:\dev\player


b.   Make sure %PLAYERGLOBAL_HOME%/11.1/playerglobal.swc exists
c.   Make sure ~/mm.cfg exists and contains the following line



TraceOutputFileEnable=1


d.   cd …/royale-asjs/
e.   ant basictests



From: Yishay Weiss
Sent: Thursday, July 8, 2021 9:23 AM
To: dev@royale.apache.org
Subject: RE: Mustella Tests



Ok, got it. I do not have a Mac. I’ll look at the Git log for changes to 
containerview.



Enjoy your vacation!



From: Alex Harui
Sent: Wednesday, July 7, 2021 8:37 PM
To: dev@royale.apache.org
Subject: Re: Mustella Tests



I'm on a family trip and took my windows laptop instead of my Mac.  I debugged 
into it and now wonder how it passed on the Mac.  There were changes to basic 
containerview that don't seem right for swf.
Maybe you can debug on Mac in containerview addviewport or maybe Mac isn't 
output log and we are looking at old log.

Sent via the Samsung Galaxy A51 5G, an AT 5G smartphone
Get Outlook for Android


From: Yishay Weiss 
Sent: Tuesday, July 6, 2021 8:56:42 AM
To: dev@royale.apache.org 

Subject: RE: Mustella Tests

Did you rule out fp versions and different env vars?

From: Alex Harui
Sent: Tuesday, July 6, 2021 9:12 AM
To: 
dev@royale.apache.org
Subject: Re: Mustella Tests

I got the same error on my Windows machine, but it passed on my Mac.  Very 
strange because I don't think we have much mac vs win code.  Not sure if I'll 
have time to debug into it.

-Alex

On 7/5/21, 2:42 AM, "Yishay Weiss" 
 wrote:


Hi Guys,

We’re close to having a release out. The hurdle right now is that Mustella 
tests are failing on the CI. Does anyone have time to test if they are passing 
locally on their pc? Right now it fails for me with


>scriptName=halo.scripts::ButtonTestScript=SetupButtonTest=fail=13=body=1625149537338==ArgumentError:
 Error #2024: An object cannot be added as a child of itself.^

Looking at ButtonTest I think this is caused by a state change that 
manifests in an includeIn command. I don't know if includeIn stopped working in 
swf (this test passed previously) or if I’m missing some env var on CI.

I will probably revisit this by the end of the week if nobody else beats me 
to it.

Thanks.