-
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
Fix functional test by dispatch trigger #5712
Conversation
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... |
Test Results2 699 tests ±0 2 692 ✔️ ±0 1m 55s ⏱️ -5s Results for commit 88661c7. ± Comparison against base commit dc49de4. This pull request removes 2 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
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 We need to use javascript syntax for github-actions, not bash commands. ## Issue reference <!-- We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation. --> Fixes: #issue_number ## Checklist Please make sure you've completed the relevant tasks for this PR, out of the following list: * [ ] Code compiles correctly * [ ] Adds necessary unit tests for change * [ ] Adds necessary E2E tests for change * [ ] Unit tests passing * [ ] Extended the documentation / Created issue for it ## Auto-generated summary <!-- GitHub Copilot for docs will auto-generate a summary of the PR --> <!-- copilot:all --> ### <samp>🤖 Generated by Copilot at 254cf6f</samp> ### Summary 🛠️🧪🔄 <!-- 1. 🛠️ - This emoji represents fixing or repairing something, which is what the step did by using the latest action and the `fs` module to avoid errors and bugs. 2. 🧪 - This emoji represents testing or experimenting, which is what the functional-test workflow does by running tests on different platforms and browsers. 3. 🔄 - This emoji represents updating or refreshing something, which is what the step did by using the latest version of the action and the `fs` module to ensure compatibility and performance. --> Improved the functional-test workflow for pull requests by using a newer action and a built-in module. This change affects the `.github/workflows/functional-test.yaml` file. > _We are the functional-test warriors_ > _We use the latest `github-script` to fight_ > _We set up the checkout target with `fs`_ > _We test the pull requests in the night_ ### Walkthrough * Simplify the `uses` field of the `Set up checkout target (repository_dispatch)` step to use the major version tag of the `actions/github-script` action ([link](https://github.com/project-radius/radius/pull/5712/files?diff=unified&w=0#diff-c79f364a9293abaaa8595776b74674e24bec6287834e63ab8aa7aec6a42f0dbcL91-R91)) * Fix the environment variable setting for Windows runners by using the `fs` module instead of the `echo` command in the `Set up checkout target (repository_dispatch)` step ([link](https://github.com/project-radius/radius/pull/5712/files?diff=unified&w=0#diff-c79f364a9293abaaa8595776b74674e24bec6287834e63ab8aa7aec6a42f0dbcL97-R103)) * Use the `testPayload` object to get the pull request information for the `repository_dispatch` event in the `Set up checkout target (repository_dispatch)` step ([link](https://github.com/project-radius/radius/pull/5712/files?diff=unified&w=0#diff-c79f364a9293abaaa8595776b74674e24bec6287834e63ab8aa7aec6a42f0dbcL97-R103))
Description
We need to use javascript syntax for github-actions, not bash commands.
Issue reference
Fixes: #issue_number
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
Auto-generated summary
🤖 Generated by Copilot at 254cf6f
Summary
🛠️🧪🔄
Improved the functional-test workflow for pull requests by using a newer action and a built-in module. This change affects the
.github/workflows/functional-test.yaml
file.Walkthrough
uses
field of theSet up checkout target (repository_dispatch)
step to use the major version tag of theactions/github-script
action (link)fs
module instead of theecho
command in theSet up checkout target (repository_dispatch)
step (link)testPayload
object to get the pull request information for therepository_dispatch
event in theSet up checkout target (repository_dispatch)
step (link)