What is the best way to determine why a managed package upgrade hammer test returned a fatal error? We are an ISV and just made our final managed package builds and are testing customer upgrades prior to releasing on the AppExchange. It doesn't get to the Apex tests, so it seems to be during the upgrade process. However any scratch or sandbox org I have tried to manually upgrade outside of Hammer Tests do not have return any errors.
Command:
sfdx force:package:hammertest:run --targetusername XXXXXXXX@xxxxx.com --packageversionids 04tXXXXXXXXX --subscriberfile c:\hammer\CUSTOMER_PROD_orgs.txt --preview --json --apextests -d "2020-07-06 11:45:00"
Here are the results:
=== SubscriberOrgId: 00DEXXXXXXXXXXXXX
=== Status: PACKAGE_HAMMER_FAILED
=== LastModified: Mon Jul 06 22:10:56 GMT 2020
===
=== PackageVersionId: 04XXXXXXXXXXX
=== OrderIndex: 1
=== Conclusion: FATAL
=== Message: Fatal error executing package install/upgrade test.
=== No Package Apex test failures to show.
Thank you,
Justin
@Justin Richmond When we hit a system issue, either while making a copy of the subscriber org or while running the ISV hammer on the copy of the subscriber org, we throw a Fatal Error (mostly the former case). It generates an action item for the ISV Hammer dev team to triage and fix. Since the issue is on the product side, you would not be able to determine why it turned fatal.
I would recommend trying the another run with another subscriber org.
