Skip to content

develope "post: report" step of the procedure

Currently, an execution of ci-uprev is practically independent of previous executions. The only thing it does to prior executions is to attach, instead of creating a new item, when an uprev candidate is made (with or without expectations update) or when a problem is found.

So, it should be smarter.

If there is a merge request candidate, it should act over other results of previous executions. So, for example, a new MR candidate can close a previously open issue about the ci-uprev process because now the problem is solved.

When an uprev candidate doesn't need an expectations update, it can (at least say something) is the merge request that needs it. However, be careful because the expectations update can also be because of an "unexpectedpass" that could be seen better than w/o an expectations update.

Wiki about the uprev procedure

Edited by Sergi Blanch Torné
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information