QA (public) » openQA Project (public) » openQA Tests (public)

Issues is resolved by creating proper needle with yast_error tag.

ok but I guess there is another problem that the sum of the internal timeouts exceed MAX_JOB_TIME. How about simply scaling MAX_JOB_TIME accordingly?

okurz wrote:

ok but I guess there is another problem that the sum of the internal timeouts exceed MAX_JOB_TIME. How about simply scaling MAX_JOB_TIME accordingly?

I believe that more than 2 hours is too much to be handled as "normal", so we should handle it case by case.

In case you disagree, please, scale the settings for all the test suites, as this problem might appear for any scenario, good luck ;)

the problem is that the sum of the internal timeout is already higher than 2h so bumping the timeout of the complete scenario is just one option, reducing internal timeouts, e.g. in await_install is another one. As "await_install" falls in the domain of QSF-y I think this should be something for your team. This should even help you because it would make review easier when jobs fail in await_install instead of incompleting without proper issue carry over. When you think that you in your team are fine with the incompletes then you can just reject the ticket (or set back to Resolved)

We are not fine with incompletes, but we are not going to fix potential problems which might occur. I've fixed the issue you've reported, thanks for that, so now this case is covered. Once we see another one, we act accordingly. Cheers ;)