Pull Request已成功合入, 合并人@
(感谢 Funda Wang 的贡献)Hi fundawang, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Computing, and any of the maintainers: @liqingqing_1229 , @wangbin224 , @SuperSix173 , @juyin , @yang_yanchao , any of the committers: @liqingqing_1229 , @wswsamao , @wangbin224 , @SuperSix173 , @juyin , @yang_yanchao


当前仓库存在以下 保护分支 :
| Protected Branch | Version | Release |
|---|---|---|
| Multi-Version_OpenStack-Antelope_openEuler-24.03-LTS | 1.9.3 | 1 |
| Multi-Version_OpenStack-Antelope_openEuler-24.03-LTS-Next | 1.9.3 | 1 |
| Multi-Version_OpenStack-Antelope_openEuler-24.03-LTS-SP1 | 1.9.3 | 1 |
| Multi-Version_OpenStack-Antelope_openEuler-24.03-LTS-SP2 | 1.9.3 | 1 |
| Multi-Version_OpenStack-Wallaby_openEuler-22.03-LTS-Next | 1.6.2 | 1 |
| Multi-Version_OpenStack-Wallaby_openEuler-24.03-LTS | 1.9.3 | 1 |
| Multi-Version_OpenStack-Wallaby_openEuler-24.03-LTS-Next | 1.9.3 | 1 |
| Multi-Version_OpenStack-Wallaby_openEuler-24.03-LTS-SP1 | 1.9.3 | 1 |
| Multi-Version_OpenStack-Wallaby_openEuler-24.03-LTS-SP2 | 1.9.3 | 1 |
| * master | 1.15.3 | 1 |
| openEuler-20.03-LTS-SP4 | 1.2.2 | 5 |
| openEuler-22.03-LTS-SP3 | 1.6.2 | 3 |
| openEuler-22.03-LTS-SP4 | 1.6.2 | 3 |
| openEuler-24.03-LTS | 1.12.0 | 2 |
| openEuler-24.03-LTS-Next | 1.12.0 | 2 |
| openEuler-24.03-LTS-SP1 | 1.12.0 | 2 |
| openEuler-24.03-LTS-SP2 | 1.12.0 | 2 |
| openEuler-25.03 | 1.12.0 | 2 |
| openEuler-25.09 | 1.15.3 | 1 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支(创建同步 PR):
a) 如果当前 PR 是 Open 状态,同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged,将立即执行同步操作
注意:
- /sync 命令可以指定同步到多个分支,仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确,可通过向同步 PR 的源分支提交轻量级 PR 完善,或使用 /close 命令关闭


门禁正在运行, 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决,可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/scipy/130/console


x86_64架构构建及构建后检查:multiarch/src-openeuler/x86-64/scipy/119/console


aarch64架构构建及构建后检查:multiarch/src-openeuler/aarch64/scipy/119/console


| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :bug:WARNING | #130 | |
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_repo_in_maintain | :white_check_mark:SUCCESS | ||
| check_consistency | :white_check_mark:SUCCESS | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :white_check_mark:SUCCESS | #119 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :white_check_mark:SUCCESS | ||
| x86_64 | check_build | :white_check_mark:SUCCESS | #119 |
| check_install | :white_check_mark:SUCCESS | ||
| check_license | :white_check_mark:SUCCESS | ||


如下为接口变更检查结果,目标分支为master,请PR提交者check差异信息
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | :white_check_mark:SUCCESS | #119 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_abi | :white_check_mark:SUCCESS | |||
| rpm_config | python3-scipy | :x:FAILED | ||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_header | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | python3-scipy | :x:FAILED | ||
| rpm_requires | python3-scipy | :x:FAILED | ||
| rpm_symbol | :white_check_mark:SUCCESS | |||
| compare_package(aarch64) | add_rpms | :white_check_mark:SUCCESS | #119 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_abi | :white_check_mark:SUCCESS | |||
| rpm_config | python3-scipy | :x:FAILED | ||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_header | :white_check_mark:SUCCESS | |||
| rpm_lib | :white_check_mark:SUCCESS | |||
| rpm_provides | python3-scipy | :x:FAILED | ||
| rpm_requires | python3-scipy | :x:FAILED | ||
| rpm_symbol | :white_check_mark:SUCCESS |


@fundawang


门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报,您可以评论/ci_mistake 130进行误报标记,130表示本次构建号
也可带上误报的门禁检查项以及误报类型(ci、obs、infra),比如/ci_mistake 130 obs check_build check_install表示的是check_build和check_install存在误报,误报类型为obs
若想取消误报标记,可以评论/ci_unmistake 130取消
也可在评论后加上一段文字描述,但请另起一行


/sync openEuler-25.09


In response to this:
/sync openEuler-25.09
@fundawang
一旦当前 PR 被合入,以下同步操作将会执行:
| Branch | Status |
|---|---|
| openEuler-25.09 | 当前 PR 合并后,将创建同步 PR |


/lgtm
/approve


lgtm was added to this pull request by: liqingqing_1229. 👋
NOTE: If this pull request is not merged while all conditions are met, comment "/check-pr" to try again. 😄


approved was added to this pull request by: liqingqing_1229. 👋
NOTE: If this pull request is not merged while all conditions are met, comment "/check-pr" to try again. 😄


In response to this:
/sync openEuler-25.09
@openeuler-ci-bot
同步操作执行结果:
| Branch | Status | Pull Request |
|---|---|---|
| openEuler-25.09 | 同步失败:请手动创建 PR 进行同步,我们会继续完善分支之间同步操作,尽量避免同步失败的情况 |


In response to this:
/sync openEuler-25.09
@openeuler-ci-bot
同步操作执行结果:
| Branch | Status | Pull Request |
|---|---|---|
| openEuler-25.09 | 同步失败:请手动创建 PR 进行同步,我们会继续完善分支之间同步操作,尽量避免同步失败的情况 |


/sync openEuler-25.09


In response to this:
/sync openEuler-25.09
@fundawang
同步操作执行结果:
| Branch | Status | Pull Request |
|---|---|---|
| openEuler-25.09 | 创建同步 PR | https://gitee.com/src-openeuler/scipy/pulls/68 |


@fundawang 指定 rpath 是上游包要求的必要行为吗


@fundawang 指定 rpath 是上游包要求的必要行为吗
是的,你看一下本 PR 中提到的 A-Tune 的构建问题。


https://gitee.com/src-openeuler/A-Tune/issues/ICORY9?from=project-issue