You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to support all developers so that they can fully focus on their feature & bug fixes. During the entire development life-cycle, many boring work has to be conducted such as tests. Currently, we have supported many automated workflows with Github Actions. However, there are still room for improvement.
Developer's View
From the developer's perspective, the most important is that anything other than writing code can be automated. Currently, many jobs have been automated besides Test Cache which is cache the test based on code coverage to increase test efficiency.
Organizer's view
The organizers must have a clear view of how this project is going. Sometimes, an organizer does not necessarily write code for the project. However, there must be something to report to him/her so that he understands the project is in a healthy status.
The diagrams above shows the different checks that are conducted on a regularly basis. We want to hook these checks with Lark, so as to everyone including the organizers know how the library is performing.
Future Plan
In this section, the tasks that should be conducted are listed and tracked below to give everyone a clear picture of the progress.
ID
Task
Issue Number
1
Adjust the GPU memory threshold for scheduled build and test
Proposal
Overview
We want to support all developers so that they can fully focus on their feature & bug fixes. During the entire development life-cycle, many boring work has to be conducted such as tests. Currently, we have supported many automated workflows with Github Actions. However, there are still room for improvement.
Developer's View
From the developer's perspective, the most important is that anything other than writing code can be automated. Currently, many jobs have been automated besides
Test Cache
which is cache the test based on code coverage to increase test efficiency.Organizer's view
The organizers must have a clear view of how this project is going. Sometimes, an organizer does not necessarily write code for the project. However, there must be something to report to him/her so that he understands the project is in a healthy status.
The diagrams above shows the different checks that are conducted on a regularly basis. We want to hook these checks with Lark, so as to everyone including the organizers know how the library is performing.
Future Plan
In this section, the tasks that should be conducted are listed and tracked below to give everyone a clear picture of the progress.
fail-fast: false
to matrix strategiesYou can view the project progress in https://github.com/orgs/hpcaitech/projects/8
Self-service
The text was updated successfully, but these errors were encountered: