logParser throw error if release used is not AthGeneration
Recently a jO with AthGenerationExternals
was used and this was not caught in logParser or any other test.
Should add the test and throw an error.
Recently a jO with AthGenerationExternals
was used and this was not caught in logParser or any other test.
Should add the test and throw an error.
changed milestone to %S1.2020
added High priority logParser labels
changed weight to 2
@ewelina I think it would be better to catch this in the transform (instead of logParser which is run very late) and throw so that we don't waste CPU, what do you think?
Also the same goes for using black-listed caches, we could throw from the transform and if we need it for testing we could run perhaps with a --ignoreBlackList
flag or similar.
Hi @sargyrop yes, I think it makes sense to check this on the transform level. Cheers, ewelinA
OK great, I keep this open then until it's implemented there and then we close it.
assigned to @ewelina
removed logParser label
mentioned in merge request !271 (merged)
closed via merge request !271 (merged)