-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow failure: Run Example Code Tests #13885
Comments
There are 38 failing example programs as of the most recent run:
I'm going to take a quick pass through to try to bring as many of these back to passing as I can, if they are quick. |
Examples I was able to fix (see # )
Problem: .NET 7 specced
Problem: .NET 9 specced
Problem: missing file
Problem: Missing comma causing syntax error
Problem: Two syntax errors (unused import, unused variable)
Problem: Misc minor bugs: no package name, class doesn't match filename, wrong type (DeploymentArgs vs DeploymentSpecArgs)
Problem: Missing required configuration variables |
The ones I was not able to quick-fix (need some additional input from the authors @toriancrane , @dirien):
Problem: All failing due to the same underlying error:
Resolution: TBD ask original author(s)
Problem: Insufficient permissions on IAM role/account
Resolution: TBD ask original author(s)
Problem: Null object?
Resolution: TBD ask original author(s)
Problem: Missing chart?
Resolution: TBD ask original author(s)
Problem: Missing chart?
Resolution: TBD ask original author(s)
Problem: Missing chart?
Resolution: TBD ask original author(s)
Problem: Incorrect type for opts?
Resolution: TBD ask original author(s)
Problem: Missing resource?
Resolution: TBD ask original author(s)
Problem: unreachable cluster?
Resolution: TBD ask original author(s) |
Hi @thoward, Fixed the errors with this PR #13914 The examples:
All need a local Kubernetes cluster to work with. We could run a |
@dirien i recently added support for using a |
Workflow Failure
Run Example Code Tests has failed. See the list of failures below:
2025-01-27T10:08:12.000Z
2025-01-31T08:07:34.000Z
2025-02-01T08:06:43.000Z
2025-02-02T08:07:04.000Z
2025-02-03T08:08:21.000Z
2025-02-04T08:08:09.000Z
2025-02-05T10:14:41.000Z
2025-02-06T10:15:58.000Z
2025-02-07T10:15:01.000Z
2025-02-08T10:12:30.000Z
2025-02-09T10:10:05.000Z
2025-02-10T10:12:28.000Z
2025-02-11T10:17:00.000Z
2025-02-12T10:10:54.000Z
The text was updated successfully, but these errors were encountered: