Re: [gentoo-dev] reduce load of tinderox' bug reprots to bugs.gentoo.org

2020-03-29 Thread Kent Fredric
On Sun, 22 Mar 2020 15:11:23 +0100
"Haelwenn (lanodan) Monnier"  wrote:

> I think it might be better to fix bugzilla to be able to send multiple 
> attachments at once. AWS S3 might be okay for the long term but I've often 
> seen paste services being used and most of them expire in a week/month, so 
> you can easily loose the content before it can be read or fixed and 
> absolutely no hope to have it be readable if it's an old bug that might have 
> appeared again.

Part of my objections to using Bugzilla for this is due to the
attachments frequently being unuseful.

Not that *all* of them are useless, but due to the pattern of
automation, no sentience evaluates if a given log is useful or not, so
there are usually many more to wade through that don't help.

Add to this the whole "bugzilla limits attachment sizes", and the
workaround being "upload compressed versions which are harder to read",
this creates a lot of attachments that can't even be read directly in
your browser (even though they're just text, the size demands
decompression first).

And due to the sizes involved, I worry about the burden it places on
the database to perform this at scale.

IMO, Databases are just not the tool to use for binary data storage. (
Though I suspect perhaps bugzilla has an out-of-database binary file
storage thing? idk ).

It feels like that mistake people make when they commit large binary
assets into git, where they really want something out-of-band more
optimized for it.

And like git, once its submitted, there's no "delete" as far as I know,
... which, given the ratio of useful data vs the size, seems silly.

So the net result is a lot of downsides due to silly limitations in the
choice of platform.

I don't want to discourage automated testing, but I do want to champion
a better platform to store this data (and more importantly, aggregate
this data).

Just so its clear, my dream is a system like CPAN Testers, where
anybody can submit results regardless of who they are, with no quality
requirements on the data submissions, ... without necessitating that
each and every failure be communicated to a bug report.

That way, the 3rd party platform collects information that indicates
where a bug *could* be, and once an actual bug is found in this
information set, the bug is opened, citing the relevant details.



pgpIDnhVOyqAA.pgp
Description: OpenPGP digital signature


Re: [gentoo-dev] reduce load of tinderox' bug reprots to bugs.gentoo.org

2020-03-22 Thread Haelwenn (lanodan) Monnier
[2020-03-22 14:50:25+0100] Toralf Förster:
> I was asked about possible changes of the way how tinderbox detected bugs 
> shall be filed, eg. to reduce the amount of attached files. There were ideas 
> to store eg. logs et al at AWS s3 and use b.g.o. only for the bug report 
> itself.
> 
> I started with the tinderbox being a 1-liner serving my purpose. It grewed up 
> by the needs of other devs. So maybe it is time for changes?
> 
> I do use pybugz to create bugs. Before I do manually check whether it is 
> aalredy reported (yes, this is error prone). Reporting a bug once is my 
> preferred solution. Bercause it is a little bit uncomfortable for me to 
> attach files later manually at individual request.
> 
> I'm open for any opinions / ideas.

I think it might be better to fix bugzilla to be able to send multiple 
attachments at once. AWS S3 might be okay for the long term but I've often seen 
paste services being used and most of them expire in a week/month, so you can 
easily loose the content before it can be read or fixed and absolutely no hope 
to have it be readable if it's an old bug that might have appeared again.



[gentoo-dev] reduce load of tinderox' bug reprots to bugs.gentoo.org

2020-03-22 Thread Toralf Förster
I was asked about possible changes of the way how tinderbox detected bugs shall 
be filed, eg. to reduce the amount of attached files. There were ideas to store 
eg. logs et al at AWS s3 and use b.g.o. only for the bug report itself.

I started with the tinderbox being a 1-liner serving my purpose. It grewed up 
by the needs of other devs. So maybe it is time for changes?

I do use pybugz to create bugs. Before I do manually check whether it is 
aalredy reported (yes, this is error prone). Reporting a bug once is my 
preferred solution. Bercause it is a little bit uncomfortable for me to attach 
files later manually at individual request.

I'm open for any opinions / ideas.

-- 
Toralf
PGP 23217DA7 9B888F45



signature.asc
Description: OpenPGP digital signature