Repository navigation
Various fixes for long-running tests - #8680
Conversation
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8680 +/- ##
==========================================
- Coverage 55.95% 55.94% -0.01%
==========================================
Files 604 604
Lines 41466 41466
==========================================
- Hits 23203 23199 -4
- Misses 16492 16495 +3
- Partials 1771 1772 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
kachawla
left a comment
There was a problem hiding this comment.
Have we spent time investigating it before marking it skipped? If we are skipping the test, can you make sure that a task to unskip it is created and assigned as well?
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Test_TerraformRecipe_KubernetesPostgres|
|
||
| # Delete all test namespaces. | ||
| echo "delete all test namespaces" | ||
| namespaces=$(kubectl get namespace | |
There was a problem hiding this comment.
IMO this system is too complicated. Instead I think it's better to specify the namespaces we want to keep and delete everything else. Looks like there's already been some discussion about this: #7966
| name: aksClusterName | ||
| location: location | ||
| kubernetesVersion: '1.28.5' | ||
| kubernetesVersion: '1.31.5' |
There was a problem hiding this comment.
I was unable to run this bicep deployment locally because of the outdated kubernetes version. This should make sure that next time we create a long-running test cluster we won't hit this issue.
There was a problem hiding this comment.
Is a better option to query for the latest version and use that? I'm concerned about this becoming stale and having to think about updating this manually
There was a problem hiding this comment.
I created #8901 to track version numbers for tools and platforms.
There was a problem hiding this comment.
+1 for @nicolejms' suggestion. @willdavsmith we don't know when this bicep will be used next time to recreate the LRT cluster again, so making this update might not be very useful since it’s likely that this version will be outdated by the time it’s needed. Any thoughts on how you can make it fetch the latest version instead of hardcoding?
@willdavsmith, @kachawla, the skipped test referenced in this comment was reverted. Is this PR ready to approve? |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
I wasn't aware that this PR was entirely repurposed for something else. @willdavsmith - please respond to PR comments for heads up on such changes. @brooke-hamilton - I won't be able to get to this PR today, but if it looks good then feel free to go ahead. The changes I had requested were on an older version of the PR, so you can dismiss that. |
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Description
Type of change
Fixes: #issue_number
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: