This ticket is a duplicate of https://pagure.io/taskotron/libtaskotron/issue/206

I've started playing with this on dev, will keep an eye on it to see if the results are what we're looking for. It looks like we might be able to get rid of the log clean step as well if this works

I've got the config change deployed to dev and it appears to be working well (outside of what happened when I tried to use "Follow"). Any thoughts on whether we want to push this out to stg/prod and remove the "store log" step?

after using correct syntax for following logfiles, it seems to be working this time. I'm wondering if we want to start setting up logging to have multiple levels - like autotest does/did (taskotron.log is INFO, taskotron-debug.log is DEBUG) and have them both attached to the buildstep

This doesn't seem to be working well. I randomly clicked on a few results and found following problems:

• Empty taskotron.log, e.g. https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/1323 , even though step 5 shows that the log was not empty.
• Missing lines in taskotron.log, e.g. https://taskotron.fedoraproject.org/taskmaster/builders/x86_64/builds/1325 . If you compare it to step 5 output, you'll see that initial lines are omitted.

Tim, have you enabled the "follow logfiles" feature? It might be the source of the problem. We can try to disable it (we don't need it at the moment, we prune the logs every time) and continue observing.

! In #350#9, @kparal wrote:
Tim, have you enabled the "follow logfiles" feature? It might be the source of the problem. We can try to disable it (we don't need it at the moment, we prune the logs every time) and continue observing.

Yeah, I was hoping to get rid of the log pruning step by using "follow logfiles" but will turn it off to see if that helps

I've removed the follow option from buildmaster configuration and deployed that new config to dev, stg and prod

This has been in production for a while now, I think that the ticket can be closed