Conversation
|
[balbla] |
1 similar comment
|
[balbla] |
|
Detected an outage of following critical component(s):
Due to this issue E2E tests cannot be run. Please keep an eye on the following status pages:
and comment /retest-required once the reported issues are solved |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages:
and comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages:
and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
4 similar comments
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
1 similar comment
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗ Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
4 similar comments
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests will probably fail. Please keep an eye on the following status pages: and add a comment |
|
❗ Detected an outage of the following critical component(s)❗
Due to this issue E2E tests won't run on your PR. Please keep an eye on the following status pages: and add a comment |
| klog.Infof("health check report saved to %s", reportFilePath) | ||
|
|
||
| if viper.GetBool(failIfUnhealthyParamName) { | ||
| // for s := range status.Services.Github.Components { |
There was a problem hiding this comment.
can we remove this if not required?
No description provided.