合并受阻
Hi hefq343, 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: sig-ebpf, and any of the maintainers: @wonleing , @MrRlu , @nlgwcy , @bitcoffee , @supercharge , @LemmyHuang , @huyd12 , @weiyj_lk , @QingweiXu , @happyseeker
当前仓库存在以下 保护分支 ：
| Protected Branch | Version | Release |
|---|---|---|
| master | 0.19.1 | 2 |
| openEuler-20.03-LTS-SP4 | 0.11.3 | 1 |
| openEuler-22.03-LTS-SP1 | 0.14.1 | 4 |
| openEuler-22.03-LTS-SP3 | 0.14.1 | 4 |
| * openEuler-22.03-LTS-SP4 | 0.14.1 | 4 |
| openEuler-24.03-LTS | 0.19.1 | 1 |
| openEuler-24.03-LTS-Next | 0.19.1 | 1 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支（创建同步 PR）：
a) 如果当前 PR 是 Open 状态，同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged，将立即执行同步操作
注意：
- /sync 命令可以指定同步到多个分支，仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确，可通过向同步 PR 的源分支提交轻量级 PR 完善，或使用 /close 命令关闭
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/bpftrace/64/console
x86_64架构构建及构建后检查：multiarch/src-openeuler/x86-64/bpftrace/64/console
aarch64架构构建及构建后检查：multiarch/src-openeuler/aarch64/bpftrace/62/console
| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #64 | |
| check_package_license | :bug:WARNING | ||
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_consistency | :white_check_mark:SUCCESS | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| x86_64 | check_build | :white_check_mark:SUCCESS | #64 |
| check_install | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :x:FAILED | #62 |
@hefq343
门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报，您可以评论/ci_mistake 64进行误报标记，64表示本次构建号
也可带上误报的门禁检查项以及误报类型（ci、obs、infra），比如/ci_mistake 64 obs check_build check_install表示的是check_build和check_install存在误报，误报类型为obs
若想取消误报标记，可以评论/ci_unmistake 64取消
也可在评论后加上一段文字描述，但请另起一行
/ci
/retest
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/bpftrace/65/console
aarch64架构构建及构建后检查：multiarch/src-openeuler/aarch64/bpftrace/63/console
x86_64架构构建及构建后检查：multiarch/src-openeuler/x86-64/bpftrace/65/console
| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #65 | |
| check_package_license | :bug:WARNING | ||
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_consistency | :white_check_mark:SUCCESS | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :white_check_mark:SUCCESS | #63 |
| check_install | :white_check_mark:SUCCESS | ||
| x86_64 | check_build | :white_check_mark:SUCCESS | #65 |
| check_install | :white_check_mark:SUCCESS | ||
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | :white_check_mark:SUCCESS | #65 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_cmd | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | bpftrace | :x:FAILED | ||
| rpm_symbol | :white_check_mark:SUCCESS | |||
| compare_package(aarch64) | add_rpms | :white_check_mark:SUCCESS | #63 | |
| delete_rpms | :white_check_mark:SUCCESS | |||
| rpm_cmd | :white_check_mark:SUCCESS | |||
| rpm_files | :white_check_mark:SUCCESS | |||
| rpm_provides | :white_check_mark:SUCCESS | |||
| rpm_requires | bpftrace | :x:FAILED | ||
| rpm_symbol | :white_check_mark:SUCCESS |
@hefq343
门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报，您可以评论/ci_mistake 65进行误报标记，65表示本次构建号
也可带上误报的门禁检查项以及误报类型（ci、obs、infra），比如/ci_mistake 65 obs check_build check_install表示的是check_build和check_install存在误报，误报类型为obs
若想取消误报标记，可以评论/ci_unmistake 65取消
也可在评论后加上一段文字描述，但请另起一行
门禁 failed 看下
门禁 failed 看下
难道不是ci_successful吗？
@peng_zou rpm_requires bpftrace FAILED
@peng_zou rpm_requires bpftrace FAILED
@LemmyHuang 单个子项FAILED不影响整体ci_successful的结果，这种也需要看吗？
看了下日志，整体编译成功了，没有看到报错的地方，不知道这个子项是因为什么失败
@peng_zou rpm_requires bpftrace FAILED
依赖变更，忽略
@peng_zou rpm_requires bpftrace FAILED
另外，建议下次增加pr描述信息
1、bugfix最好有issue，记录问题场景和现象。
2、如果是社区修复方案，附上链接。
/lgtm
/approve
approved was added to this pull request by: LemmyHuang. 👋
NOTE: If this pull request is not merged while all conditions are met, comment "/check-pr" to try again. 😄
/check-pr
@peng_zou, this pr is not mergeable and the reasons are below:
PR does not have these lables: lgtm
lgtm: A label mandatory for merging a pull request. The repository collaborators can comment '/lgtm' to add the label. The creator of a pull request can comment '/lgtm cancel' to remove the label, but cannot run the '/lgtm' command to add the label.
approved: A label mandatory for merging a pull request. The repository collaborators can comment '/approve' to add the label and comment '/approve cancel' to remove the label.
openeuler-cla/yes: A label mandatory for merging a pull request. The author of each commit of a pull request must sign the Contributor License Agreement (CLA). Otherwise, the pull request will fail to be merged. After signing the CLA, the author can comment '/check-cla' to check the CLA status again.
wait_confirm: A label for confirming pull request merging. A pull request with this label cannot be automatically merged. This label is added because members (including maintainers, committers, and repository administrators) are to be added to sig-info.yaml in the pull request. To remove the label, all members to be added must comment '/lgtm' in the pull request.
@peng_zou rpm_requires bpftrace FAILED
好的！多谢
/check-pr
@hefq343, this pr is not mergeable and the reasons are below:
PR does not have these lables: lgtm
lgtm: A label mandatory for merging a pull request. The repository collaborators can comment '/lgtm' to add the label. The creator of a pull request can comment '/lgtm cancel' to remove the label, but cannot run the '/lgtm' command to add the label.
approved: A label mandatory for merging a pull request. The repository collaborators can comment '/approve' to add the label and comment '/approve cancel' to remove the label.
openeuler-cla/yes: A label mandatory for merging a pull request. The author of each commit of a pull request must sign the Contributor License Agreement (CLA). Otherwise, the pull request will fail to be merged. After signing the CLA, the author can comment '/check-cla' to check the CLA status again.
wait_confirm: A label for confirming pull request merging. A pull request with this label cannot be automatically merged. This label is added because members (including maintainers, committers, and repository administrators) are to be added to sig-info.yaml in the pull request. To remove the label, all members to be added must comment '/lgtm' in the pull request.
/lgtm
@LemmyHuang 您好！好像要重新审视以下，输入/lgtm添加lgtm标签，这一次没有检测到，有劳了
@LemmyHuang 您好！好像要重新审视以下，输入/lgtm添加lgtm标签，这一次没有检测到，有劳了
@LemmyHuang 您好！好像要重新审视一下，输入/lgtm添加lgtm标签
@peng_zou 这个修改是修复了什么问题？
建议增加pr描述信息
1、bugfix最好有issue，记录问题场景和现象。
2、如果是社区修复方案，附上链接。
Fix cannot convert bfd* to bfd_architecture