1

每获取 Fuchsia 源代码：

~$ echo $PATH
/media/cwh/32GB/swdev/fuchsia/.jiri_root/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
~$ cd /media/cwh/32GB/swdev/
/media/cwh/32GB/swdev$ curl -s "https://fuchsia.googlesource.com/fuchsia/+/master/scripts/bootstrap?format=TEXT" | base64 --decode | bash
cipd bootstrapped to path:"/media/cwh/32GB/swdev/fuchsia/.jiri_root/bin/cipd"
Please add /media/cwh/32GB/swdev/fuchsia/.jiri_root/bin to your PATH
[22:15:04.404] Updating all projects
PROGRESS: Fetching CIPD packages
[22:38:10.385] Jiri hooks are not run due to fatal errors when updating projects or packages
[23:01:03.457] Jiri hooks are not run due to fatal errors when updating projects or packages
ERROR: context deadline exceeded

我在 Jiri hooks 消息之前没有看到任何“致命错误”。

什么是“更新项目或包时由于致命错误而未运行 Jiri 挂钩”？

4

2 回答 2

3

jiri help update表示有两个默认超时：

-fetch-packages-timeout=30
-hook-timeout=5

jiri使用增加的超时直接调用，然后重复原始命令。

cd fuchsia; jiri update -fetch-packages-timeout=90 -hook-timeout=60; cd ..
curl -s "https://fuchsia.googlesource.com/fuchsia/+/master/scripts bootstrap?format=TEXT" | base64 --decode | bash
于 2020-03-08T20:55:04.670 回答
2

就我而言，是 cipd 未能获取一些预构建的工件。只需通过运行登录

cipd auth-login

然后再次运行紫红色引导脚本。

于 2020-12-19T05:26:08.510 回答