Buildbot is ignoring important CMake settings in buildbot/config/blender_linux.cmake #88431
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Blender Version
Broken: all builds made with the new buildbot
Worked: old buildbot
Short description of error
The new buildbot infrastructure ignores the settings in buildbot/config/blender_linux.cmake.
Note that this affects other builds as well: 2.83, 2.93, and
master
.Exact steps for others to reproduce the error
Run
ldd bin/blender
on a recent buildbot build, and see that it links tolibpulse.so.0
:This library (and others) should be dynloaded, as per the config in
blender_linux.cmake
. Furthermore, that file contains some important linker options (CMAKE_EXE_LINKER_FLAGS
).Suggested short-term solution: update the buildbot to also load that configuration file.
Suggested longer-term solution: remove the
build_files/buildbot
directory altogether, and make sure the regular CMake configbuild_files/cmake/config/blender_release.cmake
is updated so that it has the correct options for Blender release versions.Added subscriber: @dr.sybren
#88387 was marked as duplicate of this issue
I'm classifying this as "Unbreak Now!" as 2.93 is in BCON4 now, and this really must be resolved before a release is released into the wild.
Buildbot always used the
build_files/cmake/config/blender_release.cmake
file.I don't think we can remove all of
build_files/buildbot
just yet.I would need to have a chat to get more details.
Added subscriber: @Sergey
Yes, but indirectly on Linux. It would use
buildbot/config/blender_linux.cmake
, which first runsinclude("${CMAKE_CURRENT_LIST_DIR}/../../cmake/config/blender_release.cmake")
and then sets some extra settings. Source: @Sergey is sitting here next to me saying "yeah, yeah" while I type this :)In the end, the previous buildbot produced files that don't directly link
libpulse.so.0
and the current buildbot produces files that do link there. Since PulseAudio is not installed on the render farm workers, Blender can't run there. Even though it's started with the-noaudio
CLI option.Ok, I can change the pipeline to always use the correct cmake file.
This file would be different per tracked version ?
Changed status from 'Needs Triage' to: 'Confirmed'
👍
What does that mean?
Added subscriber: @brecht
As far as I can tell this is just an error in the
work_compile.py
in thebdr-devops-core
repo.It sets
config_file_path
toblender_linux.cmake
too late.I could install PulseAudio if we need it ?
From the logs, I think it's already there.
https://builder.blender.org/admin/#/builders/10/builds/257/steps/6/logs/stdio
However it seems to not find OpenMP and Jack, which is an issue.
Ah easy fix this, will check
Do we need to install missing packages on the machines ?
Added subscriber: @Memento
And PipeWire, as it is used in the latest Fedora 34 Workstation?
Installed pulseaudio on all Centos 7 machines
Starting linux builds on all branches.
See if that helps for some of the issues.
Issues ?
OpenMP
Jack
Anyone know the package names for those on Centos 7 ?
I added a filter to show missing options into warnings
{F10133532,size=full}
https://builder.blender.org/admin/#/builders/10/builds/268/steps/6/logs/stdio
Will check the sequence of of the cmake calls in script.
The config file path was updated after the option was added to command line.
Looking at the logs is best way to find out what happened in the build.
https://builder.blender.org/admin/#/builders/10/builds/268/steps/6/logs/stdio
Line 91-92
Testing it then will pushing to buildbot.
Will start jobs.
v283
I looked on the old Linux worker machine, OpenMP with pthread was not setup there either.
{F10133817,size=full}
This is not relevant to the current issue.
Changed status from 'Confirmed' to: 'Resolved'
Added subscribers: @mcq, @scurest, @lichtwerk, @ponderz