You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Steps to reproduce
Wait for a scheduled test run to fail or inject a failure: https://github.com/radius-project/radius/actions/workflows/long-running-azure.yaml
Observed behavior
Automated GitHub issues for scheduled test runs (both functional and long-running) have not been created for some time: https://github.com/radius-project/radius/issues?q=is%3Aopen+is%3Aissue+label%3Atest-failure. This occurs even though there have been ad-hoc failures:
Long Running Workflow Failures
Functional Test Cloud Failures
Desired behavior
GitHub issues should be created whenever a scheduled test run fails. Example here.
Workaround
Monitor workflows
rad Version
N/A
Operating system
No response
Additional context
No response
Would you like to support us?
AB#13474
The text was updated successfully, but these errors were encountered: