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
Now all our CI tests will be triggered at a same time once a PR is made. This is somehow a huge cost of resource given that we now only have limited instances like IBM SE. A typical scene is when we find some bugs with rust lint, we will go back to fix regardless of the outcome of e2e tests.
We'd better add some dependency relationship between the tests, e.g.
Only rust suites tests are triggered once a PR is made
Only after a good successful rust suites test is passed, e2e/docker build tests can be triggered
This would help use to avoid needless e2e tests to occupy much computation power.
The text was updated successfully, but these errors were encountered:
Now all our CI tests will be triggered at a same time once a PR is made. This is somehow a huge cost of resource given that we now only have limited instances like IBM SE. A typical scene is when we find some bugs with rust lint, we will go back to fix regardless of the outcome of e2e tests.
We'd better add some dependency relationship between the tests, e.g.
This would help use to avoid needless e2e tests to occupy much computation power.
The text was updated successfully, but these errors were encountered: