## gactest/strong name assembly loader tests fail on FullAOT lanes

_Submitted by Andi McClure \[MSFT\] on 2017-05-03 20:19 UTC_

If you look at our FullAOT test lanes:

<https://jenkins.mono-project.com/view/All/job/jenkins-testresult-viewer/Test_Result_View/builds-plus.html#LinuxARM32el=Hide&LinuxARM32elFullAOT=Show&LinuxARM32elPR=Hide&LinuxARM32hf=Hide&LinuxARM32hfFullAOT=Show&LinuxARM32hfPR=Hide&LinuxARM64=Hide&LinuxARM64FullAOT=Show&LinuxARM64PR=Hide&LinuxIntel32=Hide&LinuxIntel32Coop=Hide&LinuxIntel32FullAOT=Show&LinuxIntel32PR=Hide&LinuxIntel64=Hide&LinuxIntel64Bitcode=Hide&LinuxIntel64BitcodeValgrind=Hide&LinuxIntel64Checked=Hide&LinuxIntel64Coop=Hide&LinuxIntel64FullAOT=Show&LinuxIntel64FullAOTPR=Show&LinuxIntel64HybridAOT=Hide&LinuxIntel64MCS=Hide&LinuxIntel64MCSPR=Hide&LinuxIntel64PR=Hide&MacIntel32=Hide&MacIntel32PR=Hide&MacIntel64=Hide&MacIntel64PR=Hide&WindowsIntel32=Hide&WindowsIntel32PR=Hide&WindowsIntel64=Hide&WindowsIntel64PR=Hide&groupBy=Builds&span=Last7Days>

The "make -C mono/tests -k test-wrench" ("runtime") step is failing on every lane (Except intel32, but I think that is being masked by other failures). The failure appears to be something with the strong name assembly feature:

MONO\_PATH=/mnt/jenkins/workspace/test-mono-mainline-fullaot/label/ubuntu-1404-amd64/mcs/class/lib/testing\_aot\_full ../../../runtime/mono-wrapper --runtime=mobile -O=gsharedvt --aot=full,nimt-trampolines=2000,ntrampolines=8000,nrgctx-fetch-trampolines=256,ngsharedvt-trampolines=4000 app-v1.exe
Unable to compile method 'void App:Main ()' due to: 'Could not load file or assembly 'gactestlib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=537eab56aa911cb7' or one of its dependencies. assembly:gactestlib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=537eab56aa911cb7 type:\<unknown type\> member:\<none\>'.

app-v1.exe is a test which only runs on fullAOT and hybridAOT test lanes.

Note we have not yet had a FullAOT test run incorporating the results of turning strict strongname loading off by default (but this shouldn't matter since these tests are supposed to have strongname loading hardwired on).

* * *

_Reference: <https://bugzilla.xamarin.com/show_bug.cgi?id=55933>_