Add error handling for sgx ci

[lum1n0us]

Process completed with exit code 143.

It is a known issue with GitHub-hosted runners. Usually, increasing the swap file can help avoid it. However, sometimes error 143 still occurs. To prevent confusion, let's capture error 143 and allow the CI to pass.

[TianlongLiang]

LGTM

[yamt]

It is a known issue with GitHub-hosted runners. Usually, increasing the swap file can help avoid it.

do you have a reference to a bug ticket or something?

[xujuntwt95329]

LGTM

[TianlongLiang]

It is a known issue with GitHub-hosted runners. Usually, increasing the swap file can help avoid it.

do you have a reference to a bug ticket or something?

actions/runner-images#6680, there is also an approach we can try: adding -large suffix to ubuntu runner(runs-on: ubuntu-latest-large //THIS LINE HERE)

[yamt]

It is a known issue with GitHub-hosted runners. Usually, increasing the swap file can help avoid it.

do you have a reference to a bug ticket or something?

actions/runner-images#6680, there is also an approach we can try: adding -large suffix to ubuntu runner(runs-on: ubuntu-latest-large //THIS LINE HERE)

large runners require some extra money, don't they?

[lum1n0us]

Larger runners have more resources than the standard GitHub-hosted runners, but they require access granted by Enterprise administrators or organization owners. Additionally, they are not free.

• https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#larger-runners
• https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/managing-larger-runners#allowing-repositories-to-access-larger-runners
• https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates