合并受阻
Hi shipujin, 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-nodejs, and any of the maintainers: @solarhu , @HuaxinLuGitee , @zhengyuhanghans , @gitee-cmd , @wang--ge , @lyn1001
当前仓库存在以下 保护分支 ：
| Protected Branch | Version | Release |
|---|---|---|
| * master | 8.5.5 | 1.16.15.0.3 |
| openEuler-20.03-LTS | 6.14.4 | 1.10.21.0.7 |
| openEuler-20.03-LTS-Next | 6.14.4 | 1.10.21.0.8%{?dist} |
| openEuler-20.03-LTS-SP1 | 6.14.16 | 1.12.22.11.3 |
| openEuler-20.03-LTS-SP2 | 6.14.16 | 1.12.22.11.1 |
| openEuler-20.03-LTS-SP3 | 6.14.16 | 1.12.22.11.3 |
| openEuler-20.09 | 6.4.1 | 1.10.11.0.1 |
| openEuler-21.03 | 6.14.6 | 1.12.18.4.3%{?dist} |
| openEuler-21.09 | 6.14.16 | 1.12.22.11.1 |
| openEuler-22.03-LTS | 6.14.16 | 1.12.22.11.5 |
| openEuler-22.03-LTS-LoongArch | 6.14.16 | 1.12.22.11.1 |
| openEuler-22.03-LTS-Next | 6.14.16 | 1.12.22.11.4 |
| openEuler-22.03-LTS-SP1 | 6.14.16 | 1.12.22.11.4 |
| openEuler-22.09 | 6.14.16 | 1.12.22.11.3 |
| openEuler-23.03 | 8.5.5 | 1.16.15.0.2 |
评论 /sync <branch1> <branch2> ... 可将当前 PR 修改同步到其它分支（创建同步 PR）：
a) 如果当前 PR 是 Open 状态，同步操作将延迟到 PR 被合并时执行
b) 如果当前 PR 已经 Merged，将立即执行同步操作
注意：
- /sync 命令可以指定同步到多个分支，仅最后一个 /sync 命令生效
- 如果创建的同步 PR 不正确，可通过向同步 PR 的源分支提交轻量级 PR 完善，或使用 /close 命令关闭
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
门禁入口及编码规范检查: multiarch/src-openeuler-ebs/trigger/nodejs, 当前构建号为 16
构建及构建后检查: multiarch/src-openeuler-ebs/x86-64-obs/nodejs, multiarch/src-openeuler-ebs/aarch64-obs/nodejs
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
| Arch Name | Check Items | Rpm Name | Check Result | Build Details |
|---|---|---|---|---|
| compare_package(x86_64) | add_rpms | ✅SUCCESS | #148 | |
| delete_rpms | ✅SUCCESS | |||
| rpm | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | ✅SUCCESS | |||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | npm | ❌FAILED | ||
| rpm_requires | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS | |||
| compare_package(aarch64) | add_rpms | ✅SUCCESS | #148 | |
| delete_rpms | ✅SUCCESS | |||
| rpm | ✅SUCCESS | |||
| rpm_abi | ✅SUCCESS | |||
| rpm_cmd | ✅SUCCESS | |||
| rpm_files | ✅SUCCESS | |||
| rpm_header | ✅SUCCESS | |||
| rpm_lib | ✅SUCCESS | |||
| rpm_provides | npm | ❌FAILED | ||
| rpm_requires | ✅SUCCESS | |||
| rpm_symbol | ✅SUCCESS |
@shipujin
门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报，您可以评论/ci_mistake 149进行误报标记，149表示本次构建号
也可带上误报的门禁检查项以及误报类型（ci、obs、infra），比如/ci_mistake 149 obs check_build check_install表示的是check_build和check_install存在误报，误报类型为obs
若想取消误报标记，可以评论/ci_unmistake 149取消
也可在评论后加上一段文字描述，但请另起一行
/check-cla
CLA Signature Guide
@shipujin1 , thanks for your pull request.
The following commit(s) are not associated with a signed Contributor License Agreement (CLA).
| Commit | Reason |
|---|---|
| 8b34b27a Remove duplicate and disorderly ... | the email used in the commit is not linked to a signed CLA! please verify that it matches the email you used when signing the CLA. |
To sign CLA, click here.
To check if your email is configured correctly, refer to the FAQs.
Once you've signed the CLA or updating your email, please comment /check-cla to revalidate CLA status.
nodejs.spec文件中changelog有重复且日期乱序的记录需要删除，否则会导致“changelog not in descending chronological order”等类似编译报错