Feature #8529

Support notices

Added by Evgeny Novikov over 1 year ago. Updated 7 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Published in build:


Sometimes Core and its components warns about various unpleasant things that don't break the whole verification process of any its part, i.e. there is no corresponding unknown reports. For instance, this is the case when LKVOG filters out large verification objects, VTG doesn't generate verification tasks because of users forget to set rule specifications to be checked and so on. But users are hard to find out corresponding notices since they are located just in component log files.

I suggest to support a new conception, notice, that will be almost the same as unknown but will be generated, showed and assessed separately. Moreover, notices shouldn't be taken into account when comparing verification results.

Most likely, it has sense to introduce new report kind, namely notice, that will be almost the same as unknown. Core and their components can collect notices using, say, commands STDERR or/and by printing all warnings additionally into special notice files. Notice marks should look completely like unknown ones but should be independent from them.

Related issues

Related to Klever - Feature #8664: Refactor relating build commandsRejected2018-01-15

Blocks Klever - Feature #9290: Respect warnings issued by CladeNew2018-09-28


#1 Updated by Evgeny Novikov 7 months ago

  • Related to Feature #8664: Refactor relating build commands added

#2 Updated by Evgeny Novikov 7 months ago

Don't forget to issue notices for failed build command relations (#8664).

#3 Updated by Evgeny Novikov 5 months ago

Also available in: Atom PDF