-
Notifications
You must be signed in to change notification settings - Fork 3k
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
{CI} Put the cloud module at the end of the serial execution to avoid affecting other tests. #26824
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
CI |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
The error is caused by performing tenant discovery on mock tenant
My gut feeling tells me this may not be caused by
Can we get the full call stack back? |
I test in this PR, If don't test it with cloud module, ci won't report an error. |
… affecting other tests. (Azure#26824) * Update automation_full_test.py * Update automation_full_test.py * Update automation_full_test.py
Related command
Description
Now the test is to dynamically allocate the modules that need to be tested for each instance.
PR #26785 adds a module graphservices. Due to the adjustment of dynamic allocation, on instance 7, we will test the cloud and acr modules in turn. There is a test test_get_docker_credentials in acr that will fail, and the error is as follows:
The reason is that after the cloud test is completed, some changes have been made and are not restored in tearDown. Since the specific reason is not yet determined, the workaround is to put the cloud module at the end for testing to eliminate the impact.
Test screenshot:
TODO:
Find the root cause of the failure and modify the relevant test code.
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a
: Make some customer-facing breaking change[Component Name 2]
az command b
: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.