imgproc: add 512mb tag for FindContours.accuracy test#25396
Merged
opencv-pushbot merged 1 commit intoopencv:4.xfrom Apr 11, 2024
Merged
imgproc: add 512mb tag for FindContours.accuracy test#25396opencv-pushbot merged 1 commit intoopencv:4.xfrom
opencv-pushbot merged 1 commit intoopencv:4.xfrom
Conversation
opencv-alalek
approved these changes
Apr 11, 2024
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've met issues when running
FindContours.accuracytest (uses old C-API) on a machine with 512Mb memory (RISC-V CanMV K230). While test itself consumes ~400Mb, with the system and other tests' leftovers it often gets killed with OOM error. So I propose to mark this test with512mbtag to allow filtering it out on similar devices.Below is memory consumption on x86_64 machine (GCC 11.4, Release build, with OCL):

Notes:
free -hshows480MiTotal memory on this machine