Add CI pipeline - #199
Conversation
|
This PR is still under testing. I'll merge it once testing is complete. |
|
Currently, whenever a PR is opened or updated, all 25 tests run via make test, which takes over 30 minutes. In addition to the long wait times, it also incurs costs based on usage. To make this process more efficient, I'd like to propose splitting the test suite into smaller units so that CI only runs tests related to the specific code being modified |
|
Thanks! #208 is ready for review. It already targets the cicd-add-ci-pipeline branch, so it can be merged here for testing. |
|
Got it, I'll review it. Feel free to tag me for review when you work on CI/CD stuff! |
Yaxuan-w
left a comment
Yaxuan-w
left a comment
There was a problem hiding this comment.
Lgtm. Will merge after ci finishing
|
Observed review from Yaxuan-w+40227173 (@Yaxuan-w) |
|
Right now, we need to open the GCP console (see attached photo) for detailed Grate test results. I'll check if I can display the results directly on the PR page instead. 
|
@Uk-jake can you post this in a new issue then we can submit this feature in the follow up pr? |
|
Observed dismissal of prior approval #199 (review) issued by Yaxuan-w+40227173 (@Yaxuan-w) |
|
Observed review from Yaxuan-w+40227173 (@Yaxuan-w) |
|
Observed review from vidyalakshmir+5592993 (@vidyalakshmir) |
|
I have set up the Type2 weekly test pipeline as proposed in the issue. This pipeline runs every Friday at 7:00 AM, and the results are recorded on the GitHub Releases page. On the release page, we can check the test summary, branch, commit, and base image digest. With this setup, test logs(I need to fix the access problem) will be saved each week automatically so we can easily track weekly progress. |
Run the grates test on every PR to main and every push to main.
Currently, this pipeline only runs grate test (make test) on lind-wasm-dev upon each trigger and outputs the results.
Please let me know if any additional features are needed.
Related