[yocto] Error Report Tool Purge

[Brindle, Amanda R]

Every time a specific report is visited (with the end of the URL being /Errors/Details/<id>), we are tracking if the referrer is another website, the reporting tool itself, or unknown. If the referrer is another website or unknown, then we won’t delete it.

The purge script does not look at links to whole builds, so as it is right now, those would get deleted. If it’s common to link to whole builds, though, I can add something to the script to save reports from a visited or linked build.

-Amanda Brindle

From: Martin Jansa [mailto:martin.jansa at gmail.com]
Sent: Thursday, July 19, 2018 11:38 AM
To: Brindle, Amanda R <amanda.r.brindle at intel.com>
Cc: Yocto Project <yocto at yoctoproject.org>
Subject: Re: [yocto] Error Report Tool Purge

I'm just curious, how are you tracking which reports were viewed or linked to (and linked from where)? I often use a link to http://errors.yoctoproject.org in the mailing list or the recipes/commit message instead of copy pasting whole build error, because it already shortens the build paths and shows useful additional information about the error.

The links to whole builds on http://errors.yoctoproject.org were also often linked from "bitbake world status" e-mails and wiki like:
https://www.openembedded.org/wiki/Bitbake_World_Status_Rocko
and on many of them nobody clicked yet - should I expect that these will mostly get broken?

Regards



On Thu, Jul 19, 2018 at 8:30 PM Brindle, Amanda R <amanda.r.brindle at intel.com<mailto:amanda.r.brindle at intel.com>> wrote:
Hello,

The Error Reporting Tool’s database (http://errors.yoctoproject.org/Errors/Latest/Autobuilder/)  has grown to a huge size, and this is affecting the performance of the application. We are planning to run a purge to get rid of reports that we don’t need. We will keep reports from the last thirty days, as well as reports that have been viewed or linked to. If you have a specific report that you don’t want purged, please let me know by the end of the month.

Amanda Brindle, Software Engineer
503-264-3970
amanda.r.brindle at intel.com<mailto:amanda.r.brindle at intel.com>

--
_______________________________________________
yocto mailing list
yocto at yoctoproject.org<mailto:yocto at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180719/676c6c17/attachment.html>