Right now every time there is a new PoV for a project, the patcher tries to find out the build+test instructions for the project, so that it can later validate the patch. If it finds those instructions, it save them in redis, but if it doesn't, the next time it will try again, and again...
As this operation does not require a PoV at all and it can be done before the project has been even fuzzed, we should split this operation out of the patcher and do this as soon as possible. The patcher can use the test instructions, if present, when they are actually needed in the run_tests step.
Right now every time there is a new PoV for a project, the patcher tries to find out the build+test instructions for the project, so that it can later validate the patch. If it finds those instructions, it save them in redis, but if it doesn't, the next time it will try again, and again...
As this operation does not require a PoV at all and it can be done before the project has been even fuzzed, we should split this operation out of the patcher and do this as soon as possible. The patcher can use the test instructions, if present, when they are actually needed in the
run_testsstep.