Pull Request已成功合入, 合并人@openharmony_ci
(感谢 ren_ze_hua 的贡献)感谢提交 Pull Requests!如果您提交的PR已经开发完毕,请评论 "start build" 触发门禁,更多交互操作,请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态,请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.


感谢提交 Pull Requests!如果您提交的PR已经开发完毕,请评论 "start build" 触发门禁,更多交互操作,请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态,请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.


start build


感谢提交 Pull Requests!如果您提交的PR已经开发完毕,请评论 "start build" 触发门禁,更多交互操作,请访问OpenHarmony社区支持命令清单。如果需要调整订阅PR、Issue的变更状态,请访问订阅链接。
Thanks for submitting the pull request. If your Pull Request has already been developed, you can leave a "start build" comment to trigger the gated system. For more commands, please visit OpenHarmony Command List. If you need to change the subscription of a Pull Request or Issue, please visit the link.


首次触发
门禁构建开始,包含静态检查、代码编译和测试【master_inner_build编译, mac-sdk编译, ohos-sdk编译, dayu200测试, hispark_taurus_Linux编译, hispark_taurus_LiteOS编译, hispark_taurus_LiteOS测试, dayu200_xts编译, dayu200_xts_static编译, dayu200-codearts编译, dayu200_tdd编译, dayu200编译, dayu200_xts_acts编译】,预计在60分钟内完成,门禁结果会同步发送到注册邮箱。您可以通过如下链接跟踪门禁进展:http://dcp.openharmony.cn/workbench/cicd/detail/69abd03264650f998b913376/runlist


代码门禁未通过
您可以通过如下链接查看门禁报告:http://dcp.openharmony.cn/workbench/cicd/detail/69abd03264650f998b913376/runlist
静态检查:
| # | check type | result | report |
|---|---|---|---|
| 1 | codeCheck | noPass | >>> |
编译测试:
| # | Device | build result | package |
|---|---|---|---|
| 1 | hispark_taurus_LiteOS | pending | NA |
| 2 | hispark_taurus_Linux | pending | NA |
| 3 | ohos-sdk | pending | NA |
| 4 | dayu200 | pending | NA |
| 5 | dayu200_xts | pending | NA |
| 6 | dayu200_tdd | pending | NA |
| 7 | dayu200_xts_acts | pending | NA |
| 8 | dayu200_xts_static | pending | NA |
| 9 | master_inner_build | pending | NA |
| 10 | dayu200-codearts | pending | NA |
| 11 | mac-sdk | pending | NA |


start build


上次构建已超过12小时,重新全量验证,重置所有关联PR的验证状态
门禁构建开始,包含静态检查、代码编译和测试【dayu200编译, dayu200_xts_acts编译, dayu200-codearts编译, ohos-sdk编译, dayu200_xts_static编译, dayu200_tdd编译, hispark_taurus_Linux编译, dayu200测试, dayu200_xts编译, mac-sdk编译, hispark_taurus_LiteOS测试, hispark_taurus_LiteOS编译, master_inner_build编译】,预计在60分钟内完成,门禁结果会同步发送到注册邮箱。您可以通过如下链接跟踪门禁进展:http://dcp.openharmony.cn/workbench/cicd/detail/69ae878964650f998b44dc56/runlist


代码门禁通过
您可以通过如下链接查看门禁报告:http://dcp.openharmony.cn/workbench/cicd/detail/69ae878964650f998b44dc56/runlist
静态检查:
| # | check type | result | report |
|---|---|---|---|
| 1 | codeCheck | pass | >>> |
编译测试:
| # | Device | build result | test result | package |
|---|---|---|---|---|
| 1 | hispark_taurus_LiteOS | success | success | >>> |
| 2 | hispark_taurus_Linux | success | NA | >>> |
| 3 | ohos-sdk | success | NA | >>> |
| 4 | dayu200 | success | success | >>> |
| 5 | dayu200_xts | success | NA | >>> |
| 6 | dayu200_tdd | success | NA | >>> |
| 7 | dayu200_xts_acts | success | NA | >>> |
| 8 | dayu200_xts_static | success | NA | >>> |
| 9 | master_inner_build | (IGNORE) | NA | >>> |
| 10 | dayu200-codearts | failed(IGNORE)(skip build) | NA | >>> |
| 11 | mac-sdk | success | NA | >>> |


您好,Committer @handyohos @csliutt-private @ringking0 ,请分配检视人员检视该PR,可以通过命令"assign [@someone_id]"分配检视人员,也可以直接评论"assign"分配给自己进行检视。
Hello, Committer @handyohos @csliutt-private @ringking0 . Please assign someone to review the PR. You can assign a reviewer by using the command "assign [@someone_id]", or you can comment "assign" to review the PR by yourself.


相关的Issue
https://gitcode.com/openharmony/build/issues/4416
原因(目的、解决的问题等)
开发者可以基于设备性能选择不同的开启等级
描述(做了什么,变更了什么)
提供了一个build_framework_security_configs_policy配置开关
测试用例(新增、改动、可能影响的功能)
不涉及,使用开关的开发者需自己适配功能特性并完成相关的功能验证
是否需要同步至release(如: monthly_20221018,OpenHarmony-3.2-Beta5 ... )分支?
必须选择一项(在MarkDown模式下用[x]替换[ ]即可勾选对应选项):
理由:
是否需要刷新社区文档?
编译构建社区文档
是否已执行L0用例