Pashmina, have you looked into this? I think the CI asjs builds are failing 
because of this. I imagine you are busy but the longer asjs builds fail the 
more difficult it is diagnose problems. Please let us know how you plan to 
handle this. Thanks.

From: Yishay Weiss<mailto:yishayj...@hotmail.com>
Sent: Friday, September 17, 2021 10:17 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>; 
pashminak...@gmail.com<mailto:pashminak...@gmail.com>
Subject: RE: Error in SWF mxtests

Rolling back to 458422fda1652198b03a4e03ae39117ba519e7df fixes it. All commits 
since then except one were done by 
@pashminak...@gmail.com<mailto:pashminak...@gmail.com>. 
@pashminak...@gmail.com<mailto:pashminak...@gmail.com>, can you please debug 
this? If you are unsure how to debug this you can simply rollback to various 
commits since 458422fda1652198b03a4e03ae39117ba519e7df , run mxtests, and see 
which commit is responsible for the failure.

To run mxtests, simply run ‘ant mxtests’ from royale-asjs

Let us know if you need guidance.

Thanks.

From: Edward Stangler<mailto:estang...@bradmark.com>
Sent: Thursday, September 16, 2021 3:39 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Error in SWF mxtests

With latest everything, fresh everything, getting an error in SWF side of 
mxtests:

ant mxtests

TypeError: Error #1009: Cannot access a property or method of a null object 
reference.
    at 
UnitTester$/init()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:321]
    at 
mx.managers::SystemManager/kickOff()[/org/apache/royale/0.9.9/mx/managers/SystemManager.as:2821]
    at 
mx.managers::SystemManager/docFrameHandler()[/org/apache/royale/0.9.9/mx/managers/SystemManager.as:2724]
    at flash.display::MovieClip/nextFrame()
    at 
mx.managers::SystemManager/nextFrameTimerHandler()[/org/apache/royale/0.9.9/mx/managers/SystemManager.as:2952]
    at flash.utils::Timer/_timerDispatch()
    at flash.utils::Timer/tick()

The error happens on this line:

        else if(root.parent != root.stage && root.loaderInfo.applicationDomain 
!= root.parent.parent.loaderInfo.applicationDomain)

Because root.parent.parent is null.

Anybody else getting this?  Dunno what changed;  don't think this was happening 
a few months ago.


Reply via email to