Add runtime error option
Release notes
Option to throw runtime error when error messages or too many warning messages are printed.
Details
To throw a runtime error at the end of the job in case error messages were seen the flag --snowflakeThresh <threshold> can be specified. The maximum number of WARNING messages allowed to not throw an error is given by <threshold>.
TQLibrary now holds an instance of itself and not a pointer to an instance of itself.
Merge request reports
Activity
added suggestion + label
mentioned in merge request !434 (closed)
added 1 commit
- f5577119 - Remove feature from TQPathManager. Not a big deal, but fixes CI.
added 1 commit
- e92bf1a8 - Tiny change in TQPathManager to reset it to previous version.
There are two different types of outputs in TQMessageStream. There is
MessageTypeandInfoType. Message is the usual "WARNING: ..." and so on. Info is what you see at the end of a line, i.e.OK,WARN,FAIL.For now, only messages are checked and infos are ignored. Therefore, the CI is not sensitive to missing samples. Should we also implement this, @bejaeger, or leave it at that?
Edited by Konstantin Lehmannadded 1 commit
- 6301d769 - Change the path manager after all. It should now be safe against non-existing...
Hi @kolehman, I think this would round up this whole implementation, but I don't see it as a must have. Especially speaking of the CI, I don't really see cases where a new commit could introduce subtle errors related to missing samples, so that we don't need to have the CI always check up on that. If you agree, I'm fine with merging this.
Edited by Benjamin Paul Jaegermentioned in commit 8bd6fc5e