I think it is reasonable, due to big size issue in NOOPT.

Thank you
Yao, Jiewen

From: Li, Yi1 <yi1.li@intel.com>
Sent: Monday, June 12, 2023 2:53 PM
To: devel@edk2.groups.io; Ard Biesheuvel <ardb+tianocore@kernel.org>; Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan L <jordan.l.justen@intel.com>; Gerd Hoffmann <kraxel@redhat.com>
Subject: [edk2-devel] Question about limit size of OvmfPkg NOOPT build

Hello all,

I am working on OPENSSL30 upgrade of CryptoPkg.
The upgrade of the OPENSSL submodule will increase the size of binaries and break the CI build check: PlatformCI_OvmfPkg_Ubuntu_GCC5_PR (Platform_CI OVMF_IA32X64_FULL_NOOPT):
https://github.com/tianocore/edk2/pull/4391/

The size change is hard to avoid, can we skip this build of GCC just like we did for VS2019?
https://github.com/tianocore/edk2/blob/8314a85893f5b75baa0031a5138028188a626243/OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml#L112-L123
OvmfPkg/PlatformCI/.azurepipelines/Windows-VS2019.yml#L112-L123:
    # This currently creates a very large image which is too big for the FDF declared range
    #   Ovmf maintainers suggest to skip this build for now.
    #
    #       OVMF_IA32X64_FULL_NOOPT:
    #         Build.File: "$(package)/PlatformCI/PlatformBuild.py"
    #         Build.Arch: "IA32,X64"
    #         Build.Flags: "BLD_*_SECURE_BOOT_ENABLE=1 BLD_*_SMM_REQUIRE=1  BLD_*_TPM2_ENABLE=1 BLD_*_NETWORK_TLS_ENABLE=1 BLD_*_NETWORK_IP6_ENABLE=1 BLD_*_NETWORK_HTTP_BOOT_ENABLE=1"
    #         Build.Target: "NOOPT"
    #         Run.Flags: $(run_flags)
    #         Run: $(should_run)

Regards,
Yi