This is an automated email from the ASF dual-hosted git repository.

yuanz pushed a commit to branch main
in repository 
https://gitbox.apache.org/repos/asf/incubator-teaclave-trustzone-sdk.git

commit ece214bbde7ff0e520f2489aa231e10a5217145c
Author: Yuan Zhuang <[email protected]>
AuthorDate: Tue Mar 4 03:26:08 2025 +0000

    ci: Workaround for LTO error
    
    The following error sometimes occurs during the build process:
    "error: failed to get bitcode from object file for LTO (could not
    find requested section)".
    This issue is often observed when building with multiple parallel
    jobs. As a temporary workaround, the number of parallel jobs has
    been reduced to mitigate the error.
    
    Signed-off-by: Yuan Zhuang <[email protected]>
    Reviewed-by: Zehui Chen <[email protected]>
---
 .github/workflows/ci.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 693e3e3..eae52e4 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -117,10 +117,10 @@ jobs:
           source environment
 
           # Build OP-TEE Rust examples for Arm 64-bit both host and TA
-          make -j`nproc`
+          make -j2
 
           # Build project
-          (cd projects/web3/eth_wallet && make -j`nproc`)
+          (cd projects/web3/eth_wallet && make)
       - name: Run tests for Arm 64-bit both host and TA
         run: |
           export STD=y
@@ -151,10 +151,10 @@ jobs:
           source environment
 
           # Build OP-TEE Rust examples for Arm 64-bit both host and TA
-          make -j`nproc`
+          make -j2
 
           # Build project
-          (cd projects/web3/eth_wallet && make -j`nproc`)
+          (cd projects/web3/eth_wallet && make)
       - name: Run tests for Arm 32-bit both host and TA
         run: |
           export ARCH_TA=arm


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to