Prow is a Kubernetes based CI/CD system developed to serve the Kubernetes community. This repository contains Prow source code and Hugo sources for Prow documentation site.
Not sure if this is an expected behaviour, but it looks werid to me?
So I opened this CI build history, and click any error builds. The build log can highlight error lines in color, which is helpful. However, once I clicked the 'Analyzed' button, everything changed, and I can't find a way to revert it. Additionally, this seems to affect the server side as well.
In response to [this](https://github.com/kubernetes-sigs/prow/issues/246#issuecomment-2304780136):
>That's just running an analysis tool, which we're no longer deploying. It was called halogen. https://github.com/kubernetes/test-infra/pull/33353
>
>/close
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
Not sure if this is an expected behaviour, but it looks werid to me?
So I opened this CI build history, and click any error builds. The build log can highlight error lines in color, which is helpful. However, once I clicked the 'Analyzed' button, everything changed, and I can't find a way to revert it. Additionally, this seems to affect the server side as well.