Well if it's for build and correctness reasons, ma...
# core
s
Well if it's for build and correctness reasons, maybe we can swap the tests to run before cppcheck.. and leave that as the last one. This way you can simply check on Azure the status of the job and you know early if you need to fix and retry. If this is not the use case, what specific use case you have in mind?