本文介绍了下载Fuchsia源码-更新项目或软件包时由于致命错误而无法运行Jiri挂钩的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

每个获取紫红色的源代码:

~$ 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挂钩消息之前,我没有看到任何致命错误".

I do not see any "fatal errors" preceding the Jiri hooks message.

什么是更新项目或程序包时由于致命错误而无法运行Jiri挂钩"?

What is the 'Jiri hooks are not run due to fatal errors when updating projects or packages'?

推荐答案

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

jiri help update indicates there are two default timeouts:

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

直接增加超时时间直接调用jiri,然后重复原始命令.

Invoke jiri directly with increased timeouts then repeat original command.

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

这篇关于下载Fuchsia源码-更新项目或软件包时由于致命错误而无法运行Jiri挂钩的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-20 15:48