ted. 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.ja...@gmail.com]
>>
.
>
>
>
> -Amanda Brindle
>
>
>
> *From:* Martin Jansa [mailto:martin.ja...@gmail.com]
> *Sent:* Thursday, July 19, 2018 11:38 AM
> *To:* Brindle, Amanda R
> *Cc:* Yocto Project
> *Subject:* Re: [yocto] Error Report Tool Purge
>
>
>
> I'm just curiou
On Thu, Jul 19, 2018 at 11:30 AM Brindle, Amanda R
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
AM
To: Brindle, Amanda R
Cc: Yocto Project
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
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
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
