John McCabe-Dansted wrote:
> I understand that even the threaded export bugs have
> started hitting users.
yes you never know which bug turns into a 'real' one. the c-t c-t c-t...
report or iconv one didn't help to fix but once we gained the idea from others
it was good to have backtraces in hand
> If you want, you can send me your presentation some time, and I can
> give you some feedback and/or we can do some brainstorming about it.
I now have a draft presentation:
http://www.csse.uwa.edu.au/~john/drafts/LCA_Da11-diag.pdf
On Thu, Dec 30, 2010 at 9:27 PM, Vincent van Ravesteijn wrote:
>
> the machine also produces bugs which would not occur to the normal user. then
> you have new kind of problem - you dont want to close the bug, since it really
> crashes, on the other hand, there is no manpower or willingness to fix all
> weird corner cases. then you need to screw your brain and u
John McCabe-Dansted wrote:
> - Keytest can automatically add bisection information etc.
i would say that this is the fundamental feature, because you have commit in
your hand and can give it to the responsible person.
> - Keytest can provide bug reports in trunk when the code is fresh and
> bef
Hi, I've been offered a spot to present keytest at LinuxConf 2011.
There has been previous discussion of monkey testing as a
cost-effective way of finding bugs. I was thinking of presenting an
argument that keytest generated bugs reports can also be of higher
quality than typical user generated bug
