automl / automl/GenericWrapper4AC

Identification of MemoryOut

Open
#9 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
10
Forks
6
PR merge metrics
No merged PRs in 30d

Description

It is unfortunately not trivial to catch memory-outs using the runsolver. if the algorithm hits the hard limit (twice as much as the user-specified soft limit) before the runsolver recognized the violation of the soft limit, the algorithm will die in a hard way and the runsolver will not be aware of it.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.