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
When running the test suite, if the AWS_PROFILE version is set to something locally reasonable, some tests fail.
I'd like to suggest going through the list of supported variables and unsetting all of them as part of a global test setup step - to ensure more repeatable builds. It also seems possible that this problem may cause local test success for developers where tests should really fail, as well as the reverse, which is the symptom I've encountered.
Thanks for reaching out. From the linked discussion you shared it looks like this is the test that is failing. If there are any other details you want to share here please let us know. Otherwise, per discussion with the team this looks like a reasonable ask.
Describe the issue
When running the test suite, if the
AWS_PROFILE
version is set to something locally reasonable, some tests fail.I'd like to suggest going through the list of supported variables and unsetting all of them as part of a global test setup step - to ensure more repeatable builds. It also seems possible that this problem may cause local test success for developers where tests should really fail, as well as the reverse, which is the symptom I've encountered.
Additional Information/Context
This came up on the AUR - you can see the discussion on the AWS CLI project there.
CLI version used
2.15.40
Environment details (OS name and version, etc.)
Arch GNU/Linux, current, installed using AUR package (kernel 6.8.7)
The text was updated successfully, but these errors were encountered: