当您有机会时，能否帮助提供一些澄清和日志，因为我们无法访问：

1. 我们看到黄金镜像没有被收割，您能提供从这行代码生成的茧状日志吗？ log.fine('This change\'s destination, ${pr.base!.ref}, does not run Skia Gold checks, skipping.');
2. 看起来您遇到了超出收割问题的问题，因为测试不得不被禁用。这是您遇到的问题吗？ https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac%20Production%20Engine%20Drone/12733/infra ?为什么在那里有一个GOLDCTL问题，但在Update .engine-release.version engine#53148上没有？您能否澄清是什么问题导致您不得不回滚测试，因为未能收割黄金镜像不应该阻止您的工作流程吗？

当您有机会时，您能帮忙提供一些澄清和日志吗？因为我们无法访问：

1. 我们看到黄金镜像没有被收割，您能提供从这行代码生成的茧状日志吗：log.fine('This change\'s destination, ${pr.base!.ref}, does not run Skia Gold checks, skipping.');

我在谷歌云存储桶中看到的路径声称是一个空的noop.txt文件。我的猜测是我们没有写入日志文件，或者我们写入了错误的路径。

1. 看起来您遇到了超出收割问题的问题，因为测试不得不被禁用。这是您遇到的问题吗：https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac%20Production%20Engine%20Drone/12733/infra?

为什么在Update .engine-release.version engine#53148上没有GOLDCTL问题？

我不知道。

您能澄清一下是什么问题导致您不得不回滚测试吗？因为无法收割黄金镜像不应该阻止您的工作流程吗？

是的，我回滚了测试，因为run_tests.py引发了RuntimeError: The GOLDCTL environment variable is not set,导致步骤失败，从而整个构建失败，因此构建引擎的工件从未上传，也无法滚动到框架。

当您有机会时，能否帮助提供一些澄清和日志记录，因为我们无法访问：

1. 我们看到金色图像没有被收获，您能提供从这行代码生成的茧状日志吗？
   在谷歌云存储桶中，我看到的路径声称是一个空的noop.txt文件。我的猜测是我们没有写入日志文件，或者我们写入了错误的路径。
   我理解错了，我看错了不同类型的日志。

以下是神殿日志：

350: {
logMessage: "Last known Gold status for flutter/engine#53148 was with sha: , status: , description: "
severity: "DEBUG"
time: "2024-05-31T17:18:11.270Z"
}
351: {
logMessage: "This change's destination, flutter-3.23-candidate.0, does not run Skia Gold checks, skipping."
severity: "DEBUG"
time: "2024-05-31T17:18:11.271Z"
}

matanlurey flutter/cocoon#3761修复了收割问题。你能链接到设置GOLDCTL的机器人指令吗？我找不到你前几天给我链接的东西。我们可以向chris展示，希望他知道放在哪里。

matanlurey flutter/cocoon#3761修复了收割问题。你能链接到设置GOLDCTL的机器人指令吗？我找不到你前几天给我链接的东西。我们可以向chris展示这一点，希望他知道该放在哪里。
https://github.com/flutter/engine/tree/main/testing/skia_gold_client#configuring-ci

@christopherfujino 你知道如何调和Matan列出的上述获取GOLDCTL设置的步骤以及如何设置发布机器人吗？添加那个依赖项应该可以做到。我不确定发布机器人的正确位置在哪里，或者它们是否以相同的方式工作。如果你能指出正确的方向，我们可以尝试一下。

@christopherfujino do you know how to reconcile the steps Matan listed above for getting GOLDCTL set and how to setup the release bots? Adding that dependency should be doing it. I'm not sure where the right place to put that would be for the release bots though or if they even work the same. If you point us in the right direction we can try it out.
Off the top of my head, I can see that we do have goldctl specified as a dependency in .ci.yaml: https://github.com/flutter/engine/blob/flutter-3.18-candidate.18/.ci.yaml#L364

• However*, if you notice, that target is using the engine_v2/engine_v2 recipe--meanwhile, in the build that failed the test, it ran with the engine_v2/builder recipe: https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac%20Production%20Engine%20Drone/12733/infra .

I do see that it has goldctl listed as a dependency in the input properties. However, I don't see a step that explicitly installed goldctl via cipd (which I would expect to see).
In this recipe, we do call api.flutter_deps.required_deps(env, env_prefixes, test_deps) , which I would expect to install, via cipd, everything listed in the dependencies hash map of the build input properties: https://flutter.googlesource.com/recipes/+/refs/heads/flutter-3.23-candidate.0/recipes/engine_v2/builder.py#138
I would start tracing around that code, and comparing it with the build steps. I would first verify whether or not we actually installed in goldctl. If we did, then I would check why we didn't set the GOLDCTL env var that we wrap the test invocation with (you can see the env vars here: https://logs.chromium.org/logs/dart-internal/buildbucket/cr-buildbucket/8746400829535528113/+/u/test:_Impeller-golden_for_host_release/execution_details ).