在定制仓组件下进行bmcgo build -jit 编译时报错 bingo命令错误或产品与平台版

root@DESKTOP-740JDI4:/home/workspace/OpenUBMC/Alibaba# bmcgo build -jit

whoami
root
当前skill自动更新状态已开启,如需关闭请执行bingo config skill.sync=false
conan版本: 2.13.0
导入模块 full_component 失败
============== 组件 mds schema 校验开始 ==============
WARN: 文件 /home/workspace/OpenUBMC/Alibaba/mds/schema.json 配置的 https://json-schema.org/draft/2019-09/schema# 为外部schema, 跳过检查
WARN: >>>>>> /home/workspace/OpenUBMC/Alibaba/mds/model.json 校验失败 <<<<<<
Unevaluated properties are not allowed (‘readOnly’ was unexpected)

Failed validating ‘unevaluatedProperties’ in schema[‘patternProperties’][‘[1][a-zA-Z0-9]$‘][‘properties’][‘properties’][‘patternProperties’][’[2][a-zA-Z0-9]$’]:
{‘type’: ‘object’,
‘description’: ‘私有属性引用,继承CommonProp的关键字,使用部分限制关键字’,
‘allOf’: [{‘$ref’: ‘#/$defs/commonProp’},
{‘$ref’: ‘#/$defs/baseTypeManage’},
{‘properties’: {‘description’: {‘type’: ‘string’,
‘minLength’: 1},
‘deprecated’: {‘description’: ‘表示废弃属性,当属性不再需要持久化时,需要通过deprecated标记’,
‘type’: ‘boolean’}}}],
‘unevaluatedProperties’: False}

On instance[‘SensorCategory’][‘properties’][‘Value’]:
{‘usage’: [‘CSR’],
‘baseType’: ‘Double’,
‘readOnly’: True,
‘description’: ‘传感器真实读数’}
WARN: >>>>>> /home/workspace/OpenUBMC/Alibaba/mds/ipmi.json 校验失败 <<<<<<
Additional properties are not allowed (‘maxLength’, ‘minLength’ were unexpected)

Failed validating ‘additionalProperties’ in schema[‘properties’][‘cmds’][‘patternProperties’][‘[3][a-zA-Z0-9]$'][‘properties’][‘req’][‘items’]:
{‘type’: ‘object’,
‘additionalProperties’: False,
‘properties’: {‘data’: {‘description’: ‘表示req/rsq的字段名称,采用大驼峰命名风格’,
‘type’: ‘string’,
‘pattern’: '
[4][a-zA-Z0-9]$’},
‘baseType’: {‘description’: ‘表示字段类型’,
‘type’: ‘string’,
‘enum’: [‘Boolean’,
‘U8’,
‘U8’,
‘U16’,
‘U16’,
‘U32’,
‘U32’,
‘U64’,
‘U64’,
‘S16’,
‘S16’,
‘S32’,
‘S32’,
‘S64’,
‘S64’,
‘Double’,
‘Double’,
‘String’,
‘String’,
‘Struct’,
‘Enum’,
‘Array’,
‘Dictionary’]},
‘len’: {‘description’: ‘表示字段长度’, ‘type’: ‘string’},
‘value’: {‘description’: ‘表示字段的值’, ‘type’: ‘string’},
‘customizedRule’: {‘description’: ‘表示定制化规则,当前仅支持厂商定制化Manufacturer(请求或响应中的字段将被替换为定制厂商标识)’,
‘type’: ‘string’,
‘enum’: [‘Manufacturer’]}}}

On instance[‘cmds’][‘SetVncPassword’][‘req’][2]:
{‘data’: ‘Password’,
‘baseType’: ‘String’,
‘len’: ‘*’,
‘minLength’: 1,
‘maxLength’: 32}
ERROR: >>>>>> /home/workspace/OpenUBMC/Alibaba/mds/service.json 校验失败 <<<<<<
‘version’ is a required property

Failed validating ‘required’ in schema[‘properties’][‘codegen_policy’]:
{‘description’: ‘组件代码生成策略, 代码生成工具将基于生成策略指定的版本等信息生成配套的代码’,
‘type’: ‘object’,
‘required’: [‘version’],
‘properties’: {‘version’: {‘description’: '使用的codegen版本, ’
‘可以使用精准版本或大于等于最低版本’,
‘anyOf’: [{‘type’: ‘string’,
‘pattern’: ‘^(>=)?[0-9]+$’},
{‘type’: ‘integer’}]}}}

On instance[‘codegen_policy’]:
{‘Version’: 15}
ERROR: 请仔细阅读报错日志, 日志中会提示哪些是必要属性, 或哪个属性配置错误
mds schema 校验结果不通过
错误信息:所有 .yml/.yaml 文件检查失败, 请仔细检查报错并解决问题项
============== csr schema 校验开始 =============
WARN: >>>>>> /home/workspace/OpenUBMC/Alibaba/sr/platform_cust.sr 校验失败 <<<<<<
1.0 is not of type ‘string’

Failed validating ‘type’ in schema[‘properties’][‘FormatVersion’]:
{‘type’: ‘string’, ‘description’: ‘格式版本,表示CSR数据格式及整体结构’}

On instance[‘FormatVersion’]:
1.0
WARN: >>>>>> /home/workspace/OpenUBMC/Alibaba/sr/14100513_Sensor_0_cust.sr 校验失败 <<<<<<
3.0 is not of type ‘string’

Failed validating ‘type’ in schema[‘properties’][‘FormatVersion’]:
{‘type’: ‘string’, ‘description’: ‘格式版本,表示CSR数据格式及整体结构’}

On instance[‘FormatVersion’]:
3.0
============== csr schema 校验成功 ==============
仓库地址为: https://git.codehub.xfusion.com/ManagementSoftware/openUBMC/Alibaba.git

conan create --name alibaba --version 1.60.23 . -pr:h profile.ini -pr:b profile.dt.ini -s:h build_type=Debug --user openubmc.dev --channel dev -o /:enable_luajit=True --build=alibaba/* --build=missing -f json --out-file=/tmp/tmptckwa_58.graph.json -tf=

======== Exporting recipe to the cache ========
WARN: User containing special chars is discouraged ‘openubmc.dev’
alibaba/1.60.23@openubmc.dev/dev: Exporting package recipe: /home/workspace/OpenUBMC/Alibaba/conanfile.py
alibaba/1.60.23@openubmc.dev/dev: Calling export()
alibaba/1.60.23@openubmc.dev/dev: RUN: git log --no-merges -n 1
alibaba/1.60.23@openubmc.dev/dev: RUN: git status . --short --no-branch --untracked-files
alibaba/1.60.23@openubmc.dev/dev: Copied 2 ‘.py’ files: conanbase.py, conanfile.py
alibaba/1.60.23@openubmc.dev/dev: Copied 1 ‘.yml’ file: conandata.yml
alibaba/1.60.23@openubmc.dev/dev: Exported to cache folder: /root/.conan2/p/alibab3238bc1f3c49/e
alibaba/1.60.23@openubmc.dev/dev: Exported: alibaba/1.60.23@openubmc.dev/dev#1b30ba0d8311207b88b224d159d8471d (2026-08-06 02:44:58 UTC)

======== Input profiles ========
Profile host:
[settings]
arch=armv8
build_type=Debug
compiler=gcc
compiler.libcxx=libstdc++
compiler.version=14.3
os=Linux
[options]
/:enable_luajit=True
[conf]
tools.build:sysroot=/opt/RTOS/208.11.0/arm64le_5.10_ek_preempt_pro/sdk
tools.gnu:host_triplet=aarch64-target-linux-gnu
user.tools:luajit=luajit/2.1.0.b024@openubmc/stable
user.tools:skynet=skynet/1.8.0.b001_020@openubmc/stable
[buildenv]
PATH=+(path)/opt/hcc_arm64le/bin
KERNEL_PATH=/opt/RTOS/208.11.0/arm64le_5.10_ek_preempt_pro/sdk/usr/src/kernel/
CONAN_CMAKE_SYSROOT=/opt/RTOS/208.11.0/arm64le_5.10_ek_preempt_pro/sdk
CONAN_CMAKE_FIND_SDK_ROOT=/opt/hi1711sdk
CHOST=aarch64-target-linux-gnu
AR=aarch64-target-linux-gnu-ar
AS=aarch64-target-linux-gnu-as
RANLIB=aarch64-target-linux-gnu-ranlib
LD=aarch64-target-linux-gnu-ld
STRIP=aarch64-target-linux-gnu-strip
CC=aarch64-target-linux-gnu-gcc
HOSTCC=gcc
CXX=aarch64-target-linux-gnu-g++
PKG_CONFIG_PATH=/opt/RTOS/208.11.0/arm64le_5.10_ek_preempt_pro/sdk/lib64/pkgconfig:/opt/RTOS/208.11.0/arm64le_5.10_ek_preempt_pro/sdk/usr/lib64/pkgconfig
PKG_CONFIG=/usr/share/bingo/pkg_config.sh
CFLAGS=-Wall -fPIC -fstack-protector-all -Os -fPIE -pie -fno-common -std=gnu11
CXXFLAGS=-I/opt/hcc_arm64le/aarch64-target-linux-gnu/lib/include -Wall -fPIC -fstack-protector-all -Os -fPIE -pie -fno-common -std=c++17
LDFLAGS=-Wl,-z,relro,-z,now,-z,noexecstack

Profile build:
[settings]
arch=x86_64
build_type=Debug
compiler=gcc
compiler.libcxx=libstdc++11
compiler.version=9
os=Linux
[conf]
user.tools:luajit=luajit/2.1.0.b024@openubmc/stable
user.tools:skynet=skynet/1.8.0.b001_020@openubmc/stable
[buildenv]
CFLAGS=-Wall -fPIC -fstack-protector-all -pie -fno-common -std=gnu11
CXXFLAGS=-Wall -fPIC -fstack-protector-all -pie -fno-common -std=c++17
LDFLAGS=-Wl,-z,relro,-z,now,-z,noexecstack
AR=ar
AS=as
LD=ld
STRIP=strip
CC=gcc
HOSTCC=gcc
CXX=g++

======== Computing dependency graph ========
WARN: include_prerelease version range option in “>=3.42.0, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
WARN: include_prerelease version range option in “>=3.42.0, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
WARN: include_prerelease version range option in “>=1.90.0, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
WARN: include_prerelease version range option in “>=1.90.0, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
WARN: include_prerelease version range option in “>=1.70.6, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
WARN: include_prerelease version range option in “>=1.70.6, include_prerelease=True” does not take an attribute, its presence unconditionally enables prereleases
Graph root
cli
Requirements
alibaba/1.60.23@openubmc.dev/dev#1b30ba0d8311207b88b224d159d8471d - Cache
bios/1.110.17.001@kl.ibmc.master_dev/stable#6e747a012df519c7b4d4ce075213ce8a - Cache
boost/1.87.0.b004@openubmc/stable#474a998ecff6a2c2fe44673ef3174cc6 - Cache
hisec_tls/26.0.2@openubmc/stable#1ff091f755b5cb792d26f828dc0fadf7 - Cache
huawei_secure_c/1.0.4@openubmc/stable#6e31783683a334cbab3af35099bffb1b - Cache
json/b003_00004@openubmc/stable#d4cfc42df5879e88ef2df22b86a6d6cd - Cache
kmc/26.0.0.b011@openubmc/stable#ce14a45101f8f825c72b173ac85e181e - Cache
liblogger/1.110.0@openubmc/stable#25365ee5b6b74797aae9c54f5a3de93c - Cache
libmc4lua/1.120.48@openubmc/stable#968c2702d097e1b861cfb82de17e9eb7 - Cache
libmgmt_protocol/1.90.20@openubmc/stable#498b3c736ecd53e16fb55f0fcabe99d6 - Cache
libroute_mapper/1.120.7@openubmc/stable#ed238b7290df7c0afd6f1559c58c8800 - Cache
libsoc_adapter/1.120.109@openubmc/stable#2efa1953845decff636e9c4a0b159571 - Cache
libsomp/3.0.0@openubmc/stable#518420d848e645c12491650d10e0a6f3 - Cache
luajit/2.1.0.b024@openubmc/stable#d5f1164970eb12e740fb7f609492f0c2 - Cache
mdb_interface/1.110.10.001@kl.ibmc.master_dev/stable#6becba31a8f4fbd0cf9a8d3ef50c3257 - Cache
rackmount/1.110.69.003@kl.ibmc.master_dev/stable#d34333dc632037589b47d4121d73527a - Cache
signature_verify_cbb_library/26.0.0.b006_001@openubmc/stable#cfa6e471fe890861518d8c89ab4552ba - Cache
skynet/1.8.0.b001_020@openubmc/stable#4e5ffac164a26d1bec9348dc5cb938cb - Cache
sqlite3/3.42.0-4.oe2403sp3-h2@openubmc/stable#1b01d27b0dd093ee31733945c026d2d8 - Cache
vpp/300.1.7@openubmc/stable#62a06fdc4374775d34742847116ac43c - Cache
Build requirements
luajit/2.1.0.b024@openubmc/stable#d5f1164970eb12e740fb7f609492f0c2 - Cache
skynet/1.8.0.b001_020@openubmc/stable#4e5ffac164a26d1bec9348dc5cb938cb - Cache
Resolved version ranges
bios/[>1.0.0]@kl.ibmc.master_dev/stable: bios/1.110.17.001@kl.ibmc.master_dev/stable
hisec_tls/[>=26.0.0]@openubmc/stable: hisec_tls/26.0.2@openubmc/stable
huawei_secure_c/[>=1.0.0]@openubmc/stable: huawei_secure_c/1.0.4@openubmc/stable
json/[>1.0.0]@openubmc/stable: json/b003_00004@openubmc/stable
kmc/[>=25.0.5]@openubmc/stable: kmc/26.0.0.b011@openubmc/stable
liblogger/[>=1.80.5]@openubmc/stable: liblogger/1.110.0@openubmc/stable
libmc4lua/[>=0.0.229]@openubmc/stable: libmc4lua/1.120.48@openubmc/stable
libmgmt_protocol/[>=1.70.6, include_prerelease=True]@openubmc/stable: libmgmt_protocol/1.90.20@openubmc/stable
libroute_mapper/[>=0.0.1]@openubmc/stable: libroute_mapper/1.120.7@openubmc/stable
libsoc_adapter/[<1.130.0]@openubmc/stable: libsoc_adapter/1.120.109@openubmc/stable
libsomp/[<3.10.0]@openubmc/stable: libsomp/3.0.0@openubmc/stable
luajit/[>=2.1.0]@openubmc/stable: luajit/2.1.0.b024@openubmc/stable
mdb_interface/[>=1.90.0, include_prerelease=True]@kl.ibmc.master_dev/stable: mdb_interface/1.110.10.001@kl.ibmc.master_dev/stable
rackmount/[>=1.0.13]@kl.ibmc.master_dev/stable: rackmount/1.110.69.003@kl.ibmc.master_dev/stable
skynet/[>=1.8.0]@openubmc/stable: skynet/1.8.0.b001_020@openubmc/stable
sqlite3/[>=3.42.0, include_prerelease=True]@openubmc/stable: sqlite3/3.42.0-4.oe2403sp3-h2@openubmc/stable
vpp/[>=300.0.0 <300.25.0]@openubmc/stable: vpp/300.1.7@openubmc/stable

======== Computing necessary packages ========
Connecting to remote ‘master_dev’ with user ‘openubmc’
Connecting to remote ‘br_release_bytedance_kunlun2280v3_6.0.6’ with user ‘openubmc’
Connecting to remote ‘br_develop_KunLun5290TXV2_6.0.0’ with user ‘openubmc’
alibaba/1.60.23@openubmc.dev/dev: Forced build from source
Requirements
alibaba/1.60.23@openubmc.dev/dev#1b30ba0d8311207b88b224d159d8471d:398ab6108dfdea5744c3946cb786864c1f01fde5 - Build
bios/1.110.17.001@kl.ibmc.master_dev/stable#6e747a012df519c7b4d4ce075213ce8a:53b7c24c63a3f39a0be9e4ce609a6584db4c8711 - Build
boost/1.87.0.b004@openubmc/stable#474a998ecff6a2c2fe44673ef3174cc6:04cf5598e344c2416a2941025b17f4416b3876e6#f551496bc1c89e5409ffe63092f7c86a - Cache
hisec_tls/26.0.2@openubmc/stable#1ff091f755b5cb792d26f828dc0fadf7:da39a3ee5e6b4b0d3255bfef95601890afd80709#0ba8627bd47edc3a501e8f0eb9a79e5e - Cache
huawei_secure_c/1.0.4@openubmc/stable#6e31783683a334cbab3af35099bffb1b:fb395055c08492eaa1f2bfb114ebafc06988eedd#b02c10abcf96064ca75126b02ddbe84d - Cache
json/b003_00004@openubmc/stable#d4cfc42df5879e88ef2df22b86a6d6cd:196ffea52222b282191f2cf6055950f63b305680#b9de5441f6bc86f1d65ecdaa5fcd5c15 - Cache
kmc/26.0.0.b011@openubmc/stable#ce14a45101f8f825c72b173ac85e181e:d47e6aeb165d4ea918032260c8e42ba181bb33fb#e82f5070e6811014bcdd72b981d31907 - Cache
liblogger/1.110.0@openubmc/stable#25365ee5b6b74797aae9c54f5a3de93c:6614c40742e090c2fcc7e64f76dc2b433ec96b80#745981ff6f55ed945d4cd065519f1632 - Cache
libmc4lua/1.120.48@openubmc/stable#968c2702d097e1b861cfb82de17e9eb7:d905004543fbbe97fcdb95ffc836dbc3c38f6778#c20b07f620879d5e8e13b456a7cb27cb - Cache
libmgmt_protocol/1.90.20@openubmc/stable#498b3c736ecd53e16fb55f0fcabe99d6:ef2abd22cd5b84d83d96756dea82ae0d83b71d9f#af819e65823b0a7aeabc732af2885c41 - Cache
libroute_mapper/1.120.7@openubmc/stable#ed238b7290df7c0afd6f1559c58c8800:4cb7f43d7da3e563462f1d0de7c8907aec3bc764#10aa900fa9b226ee860492188c2d1bc8 - Cache
libsoc_adapter/1.120.109@openubmc/stable#2efa1953845decff636e9c4a0b159571:9646a6df6c7ee6f31b12a8740ec655d533205911 - Build
libsomp/3.0.0@openubmc/stable#518420d848e645c12491650d10e0a6f3:a3fce3c93e74b5246fcb70e3b2416ae865ccc806#88e65f6167f34d636c5e570824a09d1b - Cache
luajit/2.1.0.b024@openubmc/stable#d5f1164970eb12e740fb7f609492f0c2:9107db905d75e75226134b3cca785d5984cce5c4#de0bf52ab2a2e742f714cdb40c83e774 - Cache
mdb_interface/1.110.10.001@kl.ibmc.master_dev/stable#6becba31a8f4fbd0cf9a8d3ef50c3257:b157f5ab1b55c63c4ce259836f645862396ea7cf#d47b266c20376793e27547951e73da4d - Cache
rackmount/1.110.69.003@kl.ibmc.master_dev/stable#d34333dc632037589b47d4121d73527a:5ddfa2294acadb332775f170098ef9bca281ab96#f08ee41cd028c62ca157d082055550fb - Cache
signature_verify_cbb_library/26.0.0.b006_001@openubmc/stable#cfa6e471fe890861518d8c89ab4552ba:dd8fc20e50162709b59334742a0476e5157f6f63#8282d0127ec9aa8ba4362e68b3aeca4f - Cache
skynet/1.8.0.b001_020@openubmc/stable#4e5ffac164a26d1bec9348dc5cb938cb:16c8892085231ccdbbe098f7c20651ef432eeb55#4ff3d1be2cd2b825acea53ec96c82493 - Cache
sqlite3/3.42.0-4.oe2403sp3-h2@openubmc/stable#1b01d27b0dd093ee31733945c026d2d8:04cf5598e344c2416a2941025b17f4416b3876e6#b9a4cd29594d64f3925a89555e644932 - Cache
vpp/300.1.7@openubmc/stable#62a06fdc4374775d34742847116ac43c:dc36fbfabb3798563b6f386e05e21ed54905949a#a863ac5d7fff8361da0f77792102e9b5 - Cache
Build requirements
luajit/2.1.0.b024@openubmc/stable#d5f1164970eb12e740fb7f609492f0c2:4c79b8249782bc51dc4f86889679a28732d86e75#2b52fa5c57cc16c2060c98e95803ea59 - Cache
skynet/1.8.0.b001_020@openubmc/stable#4e5ffac164a26d1bec9348dc5cb938cb:31227cd5386c5d59403e23fcef314eb048bea70f#d4deb81dfd01f6bf1598bfecbc049b0f - Cache

======== Installing packages ========
boost/1.87.0.b004@openubmc/stable: Already installed! (1 of 22)
hisec_tls/26.0.2@openubmc/stable: Already installed! (2 of 22)
huawei_secure_c/1.0.4@openubmc/stable: Already installed! (3 of 22)
luajit/2.1.0.b024@openubmc/stable: Already installed! (4 of 22)
luajit/2.1.0.b024@openubmc/stable: Already installed! (5 of 22)
sqlite3/3.42.0-4.oe2403sp3-h2@openubmc/stable: Already installed! (6 of 22)
mdb_interface/1.110.10.001@kl.ibmc.master_dev/stable: Already installed! (7 of 22)
rackmount/1.110.69.003@kl.ibmc.master_dev/stable: Already installed! (8 of 22)
skynet/1.8.0.b001_020@openubmc/stable: Already installed! (9 of 22)
skynet/1.8.0.b001_020@openubmc/stable: Already installed! (10 of 22)
json/b003_00004@openubmc/stable: Already installed! (11 of 22)
liblogger/1.110.0@openubmc/stable: Already installed! (12 of 22)
signature_verify_cbb_library/26.0.0.b006_001@openubmc/stable: Already installed! (13 of 22)
vpp/300.1.7@openubmc/stable: Already installed! (14 of 22)
kmc/26.0.0.b011@openubmc/stable: Already installed! (15 of 22)
libsomp/3.0.0@openubmc/stable: Already installed! (16 of 22)
libsoc_adapter/1.120.109@openubmc/stable: WARN: Trying to remove corrupted source folder
libsoc_adapter/1.120.109@openubmc/stable: WARN: This can take a while for big packages
libsoc_adapter/1.120.109@openubmc/stable: Calling source() in /root/.conan2/p/libsoe966a8dd09521/s
ERROR: libsoc_adapter/1.120.109@openubmc/stable: Error in source() method, line 40
super().source()
KeyError: ‘pwd’
ERROR: 执行命令 conan create --name alibaba --version 1.60.23 . -pr:h profile.ini -pr:b profile.dt.ini -s:h build_type=Debug --user openubmc.dev --channel dev -o /:enable_luajit=True --build=alibaba/* --build=missing -f json --out-file=/tmp/tmptckwa_58.graph.json -tf= 错误, 日志: /root/.bmcgo_log/bingo.log
ERROR: Command ‘[‘conan’, ‘create’, ‘–name’, ‘alibaba’, ‘–version’, ‘1.60.23’, ‘.’, ‘-pr:h’, ‘profile.ini’, ‘-pr:b’, ‘profile.dt.ini’, ‘-s:h’, ‘build_type=Debug’, ‘–user’, ‘openubmc.dev’, ‘–channel’, ‘dev’, ‘-o’, ‘/:enable_luajit=True’, ‘–build=alibaba/*’, ‘–build=missing’, ‘-f’, ‘json’, ‘–out-file=/tmp/tmptckwa_58.graph.json’, ‘-tf=’]’ returned non-zero exit status 1.
ERROR: 请查看日志信息

conan install --requires=‘bingo_cases/[>=1.0.0]@openubmc/stable’ -u --deployer-folder=/tmp/tmp_3q1_99i -of /tmp/tmp_3q1_99i -d direct_deploy
conan install --requires=‘bmcgo_cases/[>=1.0.0]@openubmc/stable’ -u --deployer-folder=/tmp/tmpvw4s0iys -of /tmp/tmpvw4s0iys -d direct_deploy
2026-08-06 10:45:01,687 - INFO -

2026-08-06 10:45:01,687 - INFO - :magnifying_glass_tilted_left: 开始统一错误分析
2026-08-06 10:45:01,687 - INFO - ============================================================
2026-08-06 10:45:01,699 - INFO - :bar_chart: 统一分析完成!
2026-08-06 10:45:01,699 - INFO - 分析文件数量: 31 个
2026-08-06 10:45:01,699 - INFO - 日志条目总数: 186 条
2026-08-06 10:45:01,699 - INFO - 日志文件案例: 1 个
2026-08-06 10:45:01,699 - INFO - 命令失败案例: 0 个
2026-08-06 10:45:01,699 - INFO - 总案例: 1 个
2026-08-06 10:45:01,699 - INFO -

2026-08-06 10:45:01,699 - INFO - :clipboard: 详细错误分析
2026-08-06 10:45:01,699 - INFO - ============================================================
2026-08-06 10:45:01,699 - INFO - :file_folder: 案例 1: bingo命令错误或产品与平台版本不匹配
2026-08-06 10:45:01,699 - INFO - ──────────────────────────────────────────────────
2026-08-06 10:45:01,699 - INFO - :one_o_clock: 发生时间: 未知时间
2026-08-06 10:45:01,699 - INFO - :round_pushpin: 来源: 日志文件
2026-08-06 10:45:01,700 - INFO - :page_facing_up: 文件: /root/.bmcgo_log/bingo.log
2026-08-06 10:45:01,700 - INFO - :memo: 问题描述: bingo test命令缺少 -jit选项,或manifest版本没有配套(例如 25.09版本的manifest需要配套25.09的bmc_sdk)
2026-08-06 10:45:01,700 - INFO - :page_facing_up: 相关输出:
2026-08-06 10:45:01,700 - INFO - KeyError: ‘pwd’
2026-08-06 10:45:01,700 - INFO - :light_bulb: 解决方案: 请检查bingo命令拼接以及manifest和sdk是否配套。
2026-08-06 10:45:01,700 - INFO - ──────────────────────────────────────────────────
WARN: 自助解决文档:https://ibmc.openx.huawei.com/#/docs/software_engineering/faq


  1. A-Z ↩︎

  2. A-Z ↩︎

  3. A-Z ↩︎

  4. A-Z ↩︎

答案内容由AI生成,仅供参考:
```text


[details="点击此处查看详细分析解答"]
根据您提供的日志和报错信息分析,`bmcgo build -jit` 执行失败的根本原因综合来看集中在 **bingo命令/版本与产品平台(manifest + bmc_sdk)不配套**,同时日志中也暴露了多处配置文件校验错误,这些错误叠加导致了最终的 `KeyError: 'pwd'` 构建中断。以下是基于上下文的详细解析与解决建议。

---

## 一、核心根因:bingo版本 / 命令与平台环境不匹配

在日志的末尾,错误分析系统自动归纳为:

> **问题描述**:bingo test命令缺少 `-jit` 选项,或 manifest 版本没有配套(例如 25.09 版本的 manifest 需要配套 25.09 的 bmc_sdk)  
> **解决方案**:请检查 bingo 命令拼接以及 manifest 和 sdk 是否配套。

虽然您执行的是 `bmcgo build -jit`(并非 `bingo test`),但构建工具内部可能调用了与 `bingo test` 类似的代码生成流程,而当前环境中的 bingo 版本未能正确识别或传递 `-jit` 参数,导致后续步骤异常。这类问题在上下文中已有同类案例记录:

- **Document Chunk 1** 中记载了类似场景:  
  “对增加的组件进行编译时,报错 KeyError: 'pwd' … 拉取最新的主干 manifest,执行 `bingo build -t install_sdk` … 完全更新了所有版本,还是不行。另外这个 manifest 和 bmc_sdk 有没有个稳定相关联的关系呀?”

  说明 **manifest 版本与 bmc_sdk 必须严格对应**(例如 2509 的 manifest 必须配合 2509 的 SDK),否则会诱发依赖解析或环境变量缺失,从而出现 `KeyError: 'pwd'`。

- **Search Result 1** 指出:  
  “未卸载老版本的情况下,安装了不同版本的 bingo 编译包,导致 bingo 命令编译依然使用的比较老的 bingo 版本,最终导致编译失败。”

  这提示若环境中有多个 bingo 版本混装,需要 **卸载旧版后重新安装最新版的 bingo**。

- **Knowledge Graph** 中的实体 `environment mismatch` 明确描述:  
  “Incorrect BMC SDK version or missing SDK leads to environment mismatch, causing Conan to enter source build mode.”

  您的日志中正显示了 Conan 进入 source build 模式(`libsoc_adapter/...: Forced build from source`),随后在 `source()` 方法内抛出 `KeyError: 'pwd'`,这符合版本不配套导致的环境错乱特征。

---

## 二、次要但必须修正的配置错误

日志前半段还暴露了大量 **MDS Schema / CSR Schema 校验失败**,这些错误虽然未直接导致 `KeyError: 'pwd'`,但会使构建流程在前期就处于不合法状态,可能加剧后续问题。需要逐项修改:

### 1. `mds/service.json` 校验失败

‘version’ is a required property
On instance[‘codegen_policy’]: {‘Version’: 15}

- **原因**:`codegen_policy` 对象中必须包含属性 `version`(全小写),但配置中写成了大写的 `Version`。  
- **修正**:将 `“Version”: 15` 改为 `“version”: 15` 或 `“version”: “>=15”`(参考知识图谱中对该字段的描述)。

### 2. `mds/model.json` 校验失败

Unevaluated properties are not allowed (‘readOnly’ was unexpected)

- **原因**:在 `SensorCategory` 的 `Value` 属性中使用了 `readOnly`,但该字段在当前 schema 的 `unevaluatedProperties: false` 限制下不被允许。  
- **修正**:移除 `readOnly`,或确认 schema 定义中是否允许此关键字(若需要只读属性,可能需要更新 schema 版本或使用其他方式标记)。

### 3. `mds/ipmi.json` 校验失败

Additional properties are not allowed (‘maxLength’, ‘minLength’ were unexpected)

- **原因**:在 `SetVncPassword` 命令的请求字段中使用了 `maxLength` 和 `minLength`,但当前 schema 只允许 `data`, `baseType`, `len`, `value`, `customizedRule` 这些属性。  
- **修正**:删除 `maxLength` 和 `minLength`,或改用 `len` 等方式表达长度约束。

### 4. CSR 文件(`platform_cust.sr`, `14100513_Sensor_0_cust.sr`)校验失败

1.0 is not of type ‘string’
3.0 is not of type ‘string’

- **原因**:`FormatVersion` 字段预期为字符串类型,但配置中写成了数字字面量。  
- **修正**:将 `FormatVersion` 的值加上引号改为字符串,如 `“1.0”`、`“3.0”`。

---

## 三、综合解决方案

结合上下文信息,建议按以下顺序排查修复:

1. **统一并清洗构建环境**  
   - 卸载当前环境中的所有旧版 bingo/bmcgo(参考 [Search Result 1]:`pip uninstall` 或 `dpkg -P`)。  
   - 下载并安装 **与当前 manifest 版本完全对应的 bmc_sdk**(例如若 manifest 来自 25.09 分支,则使用 25.09 的 SDK)。  
   - 重新执行初始化步骤:`bingo build -t install_sdk`(可参考 Document Chunk 1)。

2. **校验并修正配置文件**  
   按照上述第二节的修正项,逐一修改:
   - `mds/service.json`:`version` 字段大小写  
   - `mds/model.json`:移除不该出现的属性  
   - `mds/ipmi.json`:移除不支持的属性  
   - `sr/*.sr`:将数字格式的 `FormatVersion` 改为字符串

3. **检查 bingo 命令参数**  
   - 确保您使用的 `bmcgo build -jit` 在当前 bingo 版本中是被支持的。可以执行 `bingo --help` 查看可用选项(参考 [Document Chunk 3])。  
   - 若 bingo 版本过旧,可能缺少 `-jit` 支持,请升级到推荐版本(如对应 manifest 的配套版本)。

4. **重试构建**  
   清理缓存(`conan remove "*" -s` 谨慎使用)后,在定制仓组件目录下重新执行 `bmcgo build -jit`。若问题仍存在,请检查 `bmcgo/config` 中的 Conan 版本设置是否与组件要求一致(知识图谱提示 `bmcgo/config` 控制 Conan 版本)。

---

## 四、关键证据引用

- **错误分析结论**(直接来自您的日志): “bingo test命令缺少 -jit选项,或manifest版本没有配套”  
- **Document Chunk 1**:manifest 与 bmc_sdk 需要配套,否则出现 `KeyError: 'pwd'`  
- **Knowledge Graph - environment mismatch**:SDK 版本不正确导致 Conan 进入 source build 模式  
- **Search Result 1**:bingo 版本混乱需卸载重装  
- **Knowledge Graph - KeyError.Pwd**:运行时错误,常由环境缺失引起

按照上述步骤操作后,构建应当可以顺利通过。若仍有疑问,建议查看 `bingo.log` 中更详细的错误上下文,或参考官方 FQA 文档:<https://ibmc.openx.huawei.com/#/docs/software_engineering/faq>(该链接出现在您的日志中)。
[/details]

可以通过bmcgo build -h查看可选项。
-jit参数用于bmcgo test ,用于修改enable_luajit的options

bmcgo build 命令报错,这里是sdk版本的问题吗

目前bingo构建已采用整包方案。建议拉取manifest main最新分支,根据readme指导重新进行环境初始化即可