-
Notifications
You must be signed in to change notification settings - Fork 349
.github/build-tools: build again verbose and single threaded after a failure #5640
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
Conversation
Building in parallel is much faster but it makes logs unreadable and build failures impossible to understand. This is especially true when building with recent ALSA that produces of deprecation warnings, see examples below. For test topologies the problem is even worse: its XARGS parallel build provides no log at all. To find what actually fails, it is required to fall back on a single threaded and verbose build and this is achieved with the variables USE_XARGS, NO_PROCESSORS and VERBOSE. Pass these through docker-run.sh and CMake. Examples from thesofproject#5608 https://github.com/thesofproject/sof/runs/5717553555?check_suite_focus=true https://sof-ci.01.org/sofpr/PR5608/build12556/build/tools.txt ALSA pcm.c:1523:(parse_hw_config) deprecated fsync value 'codec_slave',... ALSA pcm.c:1471:(parse_hw_config) deprecated bclk value 'codec_slave',... ALSA pcm.c:1523:(parse_hw_config) deprecated fsync value 'codec_slave',... ALSA pcm.c:1471:(parse_hw_config) deprecated bclk value 'codec_slave',... ALSA pcm.c:1523:(parse_hw_config) deprecated fsync value 'codec_slave',... Signed-off-by: Marc Herbert <marc.herbert@intel.com>
Building in parallel is much faster but it makes logs unreadable and build failures impossible to understand. This is especially true when building with recent ALSA that produces of deprecation warnings. To show what actually fails, try to build again with a single thread. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
|
Test results are in throw-way PR #5639 where this was combined with build failures for demonstration purposes. |
|
ICL is broken as often @kkarask in https://sof-ci.01.org/sof-pr-viewer/#/build/PR5640/build8993943. Maybe we should stop testing ICL? The two failures in https://sof-ci.01.org/sofpr/PR5640/build12608/devicetest/ are unrelated #5352 |
This one is just is usually the DUT needing a reboot. |
|
We struggle with several issues on CI platforms now (ICL, TGL, JSL). It could take a while to solve all problems. |
|
@marc-hb @lgirdwood |
2 commits, see commit messages.
Building in parallel is much faster but it makes logs unreadable and
build failures impossible to understand.
To show errors, try to build again with a single thread on failure.