Azure
feat: container insights release 3.1.22 and win-3.1.22
What type of PR is this? /kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Requirements:
- [ ] uses conventional commit messages
- [ ] includes documentation
- [ ] adds unit tests
- [ ] tested upgrade from previous version
Special notes for your reviewer:
Release note:
none
Pull Request Test Coverage Report for Build 9684881063
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9674880013: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
Pull Request Test Coverage Report for Build 9693279254
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9693263400: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
Pull Request Test Coverage Report for Build 9707765244
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9707744418: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
@cameronmeissner Linux pipelines failed due to capacity issue in eastus. Could you please take a look?
@junjiezhang1997 we are working on changing the Packer build azure location outside of the affected eastus, until this is completed, the pipeline tests will be flaky
@cameronmeissner Linux pipelines failed due to capacity issue in eastus. Could you please take a look?
@junjiezhang1997 we are working on changing the Packer build azure location outside of the affected eastus, until this is completed, the pipeline tests will be flaky
@djsly Could we bypass these flaky tests now since they are required to merge the PR?
Pull Request Test Coverage Report for Build 9736838560
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9718319384: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
Pull Request Test Coverage Report for Build 9753638971
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9753173800: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
Pull Request Test Coverage Report for Build 9769388684
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9765241504: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
any reason we're still waiting to merge?
there is no reason to wait if all the PR gates passed. enabled auto-merge and hopefully, this time this should get merged.
Pull Request Test Coverage Report for Build 9812852058
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9811870560: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |
💛 - Coveralls
Pull Request Test Coverage Report for Build 9851633670
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 70.486%
| Totals | |
|---|---|
| Change from base Build 9849658700: | 0.0% |
| Covered Lines: | 2627 |
| Relevant Lines: | 3727 |