-
Notifications
You must be signed in to change notification settings - Fork 125
fix: replace git reference injection with wheel artifacts in charm test workflows #2252
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
base: main
Are you sure you want to change the base?
Conversation
…rkflows Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
tonyandrewmeyer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot the pack test can't use the wheels because the packing is done in a sandboxed environment. Please revert the changes to charmcraft-pack.yaml.
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Reverted in d012d43. The charmcraft-pack.yaml workflow now uses the original git reference approach since the packing is done in a sandboxed environment that cannot access local wheel files. |
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
|
@copilot the observability tests are failing: |
Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
|
@copilot two observability tests still fail: This seems to be from an old version of |
... Could you please provide the complete error message? The comment appears to be cut off after "line 5, in". I need to see the full traceback to understand what's failing in the interface_tester module. |
|
@copilot The extra error message is not going to provide any useful information. Plus, you can get it from the GitHub actions. |
… test workflows Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Added debugging steps in 5347bff to show:
This will help identify what versions are actually being installed in the failing test environments. |
|
@copilot we need to see all the dependencies installed in the environment that will run the unit tests, because there seems to be a conflict with an old version of interface-tester. |
…y conflicts Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Enhanced debugging in 08749c2 to show the complete list of all installed packages in the test environments. The workflows now run |
|
@copilot the tests are run with I think you need to do |
…t environments Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
|
@copilot no, you pointed |
…vironment Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Fixed in 2bbca32. Changed to use |
|
@copilot let's work around this by having the observability tests (only, not the other workflows) force a newer version of interface tester. Something like |
…tests Co-authored-by: tonyandrewmeyer <826522+tonyandrewmeyer@users.noreply.github.com>
Added workaround in c5f97df. The observability-charm-tests workflow now forces an upgrade of pytest-interface-tester to version >=3.4 using |
Update charmcraft-pack.yaml to use wheel artifactsReverted - pack runs in sandboxed environmentuv pip freezewithout Python spec to let uv use its managed environmentOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.