-
Notifications
You must be signed in to change notification settings - Fork 101
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
Restore bicep artifacts before starting tests #8283
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: sk593 <[email protected]>
Unit Tests3 552 tests 3 548 ✅ 5m 21s ⏱️ Results for commit a000290. ♻️ This comment has been updated with latest results. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8283 +/- ##
==========================================
+ Coverage 59.81% 59.83% +0.01%
==========================================
Files 590 590
Lines 39513 39513
==========================================
+ Hits 23636 23642 +6
+ Misses 14116 14112 -4
+ Partials 1761 1759 -2 ☔ View full report in Codecov by Sentry. |
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.
I tested this locally - 🚀 🛰️
Signed-off-by: sk593 <[email protected]>
Signed-off-by: sk593 <[email protected]>
Signed-off-by: sk593 <[email protected]>
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... |
# Restore Radius Bicep types | ||
bicep build ./test/functional-portable/corerp/cloud/resources/testdata/corerp-azure-connection-database-service.bicep | ||
# Restore AWS Bicep types | ||
bicep build ./test/functional-portable/corerp/cloud/resources/testdata/aws-s3-bucket.bicep |
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.
Do the tests need the files generated by these two commands to be able to run successfully? If so, should we add those files to the repository itself?
I think that to be able to run these tests locally, this is also something we need to run. Is that right?
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.
No, they're not needed. They're an output of the build command but we're more interested in the artifacts being restored in this step.
Yes to the second question. The bicep build
command gets run when we deploy bicep templates. bicep build
automatically restores the artifacts which might be why we've been seeing flaky restoration failures. This change is added so the bicep artifacts are restored before the tests start and bicep build
is run
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... |
Signed-off-by: sk593 <[email protected]>
Signed-off-by: sk593 <[email protected]>
Signed-off-by: sk593 <[email protected]>
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
This change restores Bicep artifacts before running any tests. This will avoid any restoration errors while the tests are running as seen in #8184
Type of change
Fixes: #8184
Contributor checklist
Please verify that the PR meets the following requirements, where applicable: