search

AICoE / content-pipeline

Other
3 stars 5 forks source link

When To Stop: Optimize Test Runtimes Using AI4CI #72

Closed aakankshaduggal closed 1 year ago

aakankshaduggal commented 2 years ago

Overview Longer running tests are often painful as they can block the CI/CD process for lengthy periods of time. How can we optimize the running time of our tests and prevent bottlenecks in our CI/CD pipeline? By understanding the test failure times, we aim to predict an Optimal Stopping Point for a test/build by training a machine learning model to help developers and managers better allocate the development resources, and ensure efficiency, consistency, and transparency for manual and time-consuming processes.

Speakers @hemajv @aakankshaduggal

What conference(s) are you submitting this proposal to?

62 #23

Project repo link, or other relevant resources https://www.operate-first.cloud/data-science/ai4ci/docs/content.md#optimal-stopping-point-prediction

Link to abstract https://cfp.devconf.info/proposals/40/3711

Was this proposal accepted?

hemajv commented 2 years ago

Submitted to #68

hemajv commented 2 years ago

Accepted in DevConf.US #62

hemajv commented 2 years ago

Submitted to #76

sesheta commented 1 year ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 1 year ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

sesheta commented 1 year ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 1 year ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/content-pipeline/issues/72#issuecomment-1338122343): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.