Skip to content

lvm/utils/release/test-release.sh parallel compilation parameter "-j" is not applied to all modules #81813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
songdongsheng opened this issue Feb 15, 2024 · 2 comments
Labels
infrastructure Bugs about LLVM infrastructure

Comments

@songdongsheng
Copy link

On a 16-core machine, although the parameter "-j3" is used, there are mostly 3 compilation processes during execution, but no less than 10 compilation processes can still be seen running.

cd /opt/llvm-build/llvm-18.x &&
    /usr/bin/time -v ./llvm/utils/release/test-release.sh \
        -release 18.1.0 \
        -rc 2 \
        -triple x86_64-unknown-linux-gnu \
        -j 3 \
        -use-ninja \
        -no-checkout \
        -no-compare-files
@tstellar
Copy link
Collaborator

My guess is that this is the same as #80999.

@EugeneZelenko EugeneZelenko added infrastructure Bugs about LLVM infrastructure and removed new issue labels Feb 16, 2024
@llvmbot
Copy link
Member

llvmbot commented Feb 16, 2024

@llvm/issue-subscribers-infrastructure

Author: songdongsheng (songdongsheng)

On a 16-core machine, although the parameter "-j3" is used, there are mostly 3 compilation processes during execution, but no less than 10 compilation processes can still be seen running.
cd /opt/llvm-build/llvm-18.x &&
    /usr/bin/time -v ./llvm/utils/release/test-release.sh \
        -release 18.1.0 \
        -rc 2 \
        -triple x86_64-unknown-linux-gnu \
        -j 3 \
        -use-ninja \
        -no-checkout \
        -no-compare-files

@joker-eph joker-eph changed the title The parallel compilation parameter "-j" is not applied to all modules lvm/utils/release/test-release.sh parallel compilation parameter "-j" is not applied to all modules Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Bugs about LLVM infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants