Musters ability to parse log files and pull out warning and error strings is great, but …
I find my self often writting 2 versions of each engine. One that reports errors and warnings correctly, and another that considers error strings to be warnings.
The reason is that we want your dispathcer to reque erroring packets on MOST jobs, but there are times when we want to render a scene that throws up fake error strings. In that case we use the second engine. This seems like needless duplication and I would like the ability to control the requing and handling of errors on a job level.
Any thoughts on how I could do this?
Kind regards,
Tim Murphy
Pipeline Developer
Weta Productions
New Zealand
Tim we already have in the TODO list, warnings and errors overrides on a job basis, should come out on 6.1.0 or later!
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.
We use cookies to ensure that we give you the best experience on our website Cookies are also used to send anonymous browsing data to Google Analytics. We give you the option to Refuse our cookies.