I can confirm that the original exception is fixed, in the latest.
But now there is another exception (return type mismatch) in fdb in the new
file ContainerRawChildrenList.as:
[trace] TestCase Start: ButtonTestScript$ButtonTest1
[trace]
[trace] return types dont match
[trace] virt flash.display::DisplayObject
mx.core::IChildList/mx.core:IChildList::addChild()
[trace] over mx.core::UIComponent
mx.core::ContainerRawChildrenList/addChild()
[Fault] exception, information=VerifyError: Error #1053: Illegal override of
ContainerRawChildrenList in mx.core.ContainerRawChildrenList.
at mx.core::Container/get
rawChildren()[/org/apache/royale/0.9.9/mx/core/Container.as:1807]
at
UnitTester$/_getObjectsUnderPoint()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:1130]
at
UnitTester$/_getObjectsUnderPoint()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:1134]
at
UnitTester$/getObjectsUnderPoint()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:706]
at
DispatchMouseEvent/doStep()[c:\somewhere\royale-asjs\mustella\src\main\royale\DispatchMouseEvent.as:122]
at
TestStep/execute()[c:\somewhere\royale-asjs\mustella\src\main\royale\TestStep.as:75]
at
DispatchMouseEvent/execute()[c:\somewhere\royale-asjs\mustella\src\main\royale\DispatchMouseEvent.as:0]
at
TestCase/runSteps()[c:\somewhere\royale-asjs\mustella\src\main\royale\TestCase.as:443]
at
TestCase/runBody()[c:\somewhere\royale-asjs\mustella\src\main\royale\TestCase.as:318]
at
TestCase/runSetup()[c:\somewhere\royale-asjs\mustella\src\main\royale\TestCase.as:296]
at
TestCase/runTest()[c:\somewhere\royale-asjs\mustella\src\main\royale\TestCase.as:264]
at
UnitTester/runTests()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:2113]
at
UnitTester/runMoreTests()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:2159]
at
UnitTester$/enterFrameHandler()[c:\somewhere\royale-asjs\mustella\src\main\royale\UnitTester.as:1253]
On 9/20/2021 7:43 AM, Pashmina Kazi wrote:
Hi Yishay,
I have commented my changes in SystemManager.as and ISystemManager.as to get
mxtests works now it is throwing that error:
[image.png]
Regards,
Pashmina
On Mon, Sep 20, 2021 at 12:33 AM Yishay Weiss wrote:
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
Sent: Friday, September 17, 2021 10:17 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: Error in SWF mxtests
Rolling back to 458422fda1652198b03a4e03ae39117ba519e7df fixes it. All commits
since then except one were done by
@pashminakazi<mailto:[email protected]>, 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
Sent: Thursday, September 16, 2021 3:39 AM
To: [email protected]<mailto:[email protected]>
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.
