-
-
Notifications
You must be signed in to change notification settings - Fork 56.4k
G-API: Make test execution lighter (first attempt) #25060
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
Conversation
- Marked some outliers as `verylong`: - OneVPL barrier test - pure brute force - Stateful test in stream - in fact BG Sub accuracy test clone - Restructured parameters instantiation in Streaming tests to generate less test configurations (54 -> 36)
|
Okey dokey here's first results, before: https://github.com/opencv/opencv/actions/runs/7988786908/job/21814098436 after: https://github.com/opencv/opencv/actions/runs/7988920497/job/21814498159?pr=25060 Nearly the 40% time reduction. I will check how the profile looks after than and move forward. |
asmorkalov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
@asmorkalov we discussed locally with @TolyaTalamanov and he was ok with the Streaming test change; so I believe this one can merged to help the CI (I will continue the work in other PRs) |
G-API: Make test execution lighter (first attempt) opencv#25060 ### Background G-API tests look running longer than tests for the rest of modules (e.g., 5m), and the analysis show that there's several outliers in G-API test suite which take a lot of time but don't improve the testing quality much:  In this PR I will cut the execution time to something reasonable. ### Contents - Marked some outliers as `verylong`: - OneVPL barrier test - pure brute force - Stateful test in stream - in fact BG Sub accuracy test clone - Restructured parameters instantiation in Streaming tests to generate less test configurations (54 -> 36) ### Pull Request Readiness Checklist See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request - [x] I agree to contribute to the project under Apache 2 License. - [x] To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV - [x] The PR is proposed to the proper branch - [x] There is a reference to the original bug report and related work - [x] There is accuracy test, performance test and test data in opencv_extra repository, if applicable Patch to opencv_extra has the same branch name. - [x] The feature is well documented and sample code can be built with the project CMake



Background
G-API tests look running longer than tests for the rest of modules (e.g., 5m), and the analysis show that there's several outliers in G-API test suite which take a lot of time but don't improve the testing quality much:

In this PR I will cut the execution time to something reasonable.
Contents
verylong:Pull Request Readiness Checklist
See details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request
Patch to opencv_extra has the same branch name.