You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 the binary result from CI compile(which is used for CI testing later on) is right in the ${{ github.workspace }}/build/pika. Should not and no need to copy from "../../output/pika"
2 in ubuntu and centos of CI, when exec start_master_and_slave.sh, sed will throw "sed: can't read : No such file or directory" although it actually worked. this is due to the script uses the Mac exclusive format {sed -i '' ...} while in ubuntu/centos this should be {sed -i} , without the ''
1 CI 编译出的二进制结果(稍后用于 CI 测试)就在 ${{ github.workspace }}/build/ 中,不应该也不需要从 "../../output/pika" 复制,这个cp命令实际上是失败的,只是正好用于测试的二进制就处于当前目录下,所以后续的CI能顺利运行
2 sed命令在ubuntu和centos中会报错(但实际上还是生效了,完成了参数替换),因为使用的是sed -i '',这种mac写法,在ubuntu/centos上应该使用 sed -i (不带'')
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this a regression?
No
Description
1 the binary result from CI compile(which is used for CI testing later on) is right in the ${{ github.workspace }}/build/pika. Should not and no need to copy from "../../output/pika"
2 in ubuntu and centos of CI, when exec start_master_and_slave.sh, sed will throw "sed: can't read : No such file or directory" although it actually worked. this is due to the script uses the Mac exclusive format {sed -i '' ...} while in ubuntu/centos this should be {sed -i} , without the ''
1 CI 编译出的二进制结果(稍后用于 CI 测试)就在 ${{ github.workspace }}/build/ 中,不应该也不需要从 "../../output/pika" 复制,这个cp命令实际上是失败的,只是正好用于测试的二进制就处于当前目录下,所以后续的CI能顺利运行
2 sed命令在ubuntu和centos中会报错(但实际上还是生效了,完成了参数替换),因为使用的是sed -i '',这种mac写法,在ubuntu/centos上应该使用 sed -i (不带'')
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: