Skip to content
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

CI | Rearrenge the CI job dependency #636

Open
Xynnn007 opened this issue Dec 18, 2024 · 1 comment
Open

CI | Rearrenge the CI job dependency #636

Xynnn007 opened this issue Dec 18, 2024 · 1 comment

Comments

@Xynnn007
Copy link
Member

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.

  1. Only rust suites tests are triggered once a PR is made
  2. 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.

@fitzthum
Copy link
Member

We might also try the non-tee/sample tests before running the hw-specific ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants