-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Parallel build are failed on master branch #4912
Comments
can you provide the log file for this one? libsaivs-dev_1.0.0_amd64.deb-uninstall.log it should be under target/debs/stretch/ |
|
Team, I've also faced the same issue where the parallel build was failing. Logs: |
it is likely due to this pr. The pr that introduce this issue is likely this following PR. 58632e6#diff-54252fe595f09e268f275810298a4beeR494 I did put a lock here. 58632e6#diff-54252fe595f09e268f275810298a4beeR508 So, I haven’t figure out the root cause yet. |
when parallel build is enabled, both docker-fpm-frr and docker-syncd-brcm is built at the same time, docker-fpm-frr requires swss which requires to install libsaivs-dev. docker-syncd-brcm requires syncd package which requires to install libsaibcm-dev. since libsaivs-dev and libsaibcm-dev install the sai header in the same location, these two packages cannot be installed at the same time. Therefore, we need to serialize the build between these two packages. The previous solution is not good enough. Now, the new solution is to have one package wait for another package to be uninstalled. For example, if syncd is built first, then it will install libsaibcm-dev. Meanwhile, if the swss build job starts, and tries to install libsaivs-dev, it will first try to query if libsaibcm-dev is installed or not. if it is installed, then it will wait until libsaibcm-dev is uninstalled. After syncd job is finished, it will uninstall libsaibcm-dev and swss build job will be unblocked. To solve this issue, _UNINSTALLS is introduced to uninstall a package that is no longer needed and to allow parallel job to go on. |
Description
I tried to build SONiC with PLATFORM=broadcom and SONIC_CONFIG_BUILD_JOBS = 8 on master branch, it got build failure.
Other platform except for vs has same problem, I think.
Build successful with SONIC_CONFIG_BUILD_JOBS = 1 but build speed are too slow.
Steps to reproduce the issue:
1 edit rules/config, SONIC_CONFIG_BUILD_JOBS = 8
2. make init
3. make configure PLATFORM=broadcom
4. make all
Describe the results you received:
Describe the results you expected:
build successful.
Additional information you deem important (e.g. issue happens only occasionally):
My build environment: RYZEN 5 3600, Ubuntu 20.04LTS
tested on commit ec0c826
affected by commit 0a260b7 , I think.
The text was updated successfully, but these errors were encountered: