Parsing tatt's report file
When running tatt generated *-useflags.sh
, if something failed, we always register it as just failed. But it could be some other reason, and not just "fail".
-
Create a new template for tatt for generating nearly JSON
report file. -
When the job is done, parse this file, and "investigate" why it failed. -
Report on IRC the fail reason. -
Add the bug number to DB, so it won't be scanned but also not as failure. NOTE: maybe reporting as fail in DB is also good?
This is a preparation work for auto fetching failure reports and opening bugs for them.
Edited by Arthur Zamarin