Hello! In the aftermath of the recent educational round, there is an apparent weakness in the test-cases of problem A that is leading to a ton of hacks.

This large volume of hacks will be added to the systests tomorrow morning. However, they do not represent distinct weaknesses; odds are that only a tiny fraction of these test-cases is necessary, since they are all targeting the same weakness, and most codes will fail at the first hack.

Doesn't this represent an inefficiency that will be an added burden on the already crowded system tests? I don't know how this could be handled, but perhaps live rejudging of all codes on individual successful hack cases will prevent many unnecessary hacks from being created in the first place? This is not exclusive to this contest, and is a persistent issue in div3's and educationals with long hacking phases that could perhaps be improved to save system test resources.