1 |
On 1 November 2014 00:18, Rich Freeman <rich0@g.o> wrote: |
2 |
> So, if there is a better way, I'm all ears for constructive |
3 |
> suggestions. By constructive I mean that somebody who comes up with a |
4 |
> script that automatically retrieves build logs and attaches them to |
5 |
> bugs is being more helpful than somebody who says that somebody else |
6 |
> should come up with such a script, and so on. That doesn't mean that |
7 |
> we can't talk about solutions before we build them - only that it |
8 |
> isn't helpful when we basically demand that others build them for us. |
9 |
|
10 |
Let me try to be clear (once again) of what the problem is. Even just |
11 |
spending time rewriting this irks me because I have written, repeated, |
12 |
re-explained, described the problem a number of times, between bugs, |
13 |
this ML and my blog ( https://blog.flameeyes.eu/tag/tinderbox ). |
14 |
|
15 |
The problem with "it's trivial to do that in python so just do it" is |
16 |
that first of all Python is not my language of choice, so the whole |
17 |
infrastructure is currently not written in Python at all. And all the |
18 |
people, including Luca, who promised they can convert it to Python in |
19 |
no time, never delivered. Beside the point that, if it's so trivial |
20 |
for somebody, I would expect it'll take them less time to provide me |
21 |
with the tool, rather than complain about it. |
22 |
|
23 |
Another suggestion that happens fairly often is "oh just do it after |
24 |
opening the bug with a script", and the answer is -> no way. Because |
25 |
right now it's all self contained in a browser for good reasons: I |
26 |
open these bugs when I'm at work waiting for a meeting, at home |
27 |
waiting to sleep, or while watching TV. I do it from laptops and |
28 |
tablets, and if I have to start copy-pasting things between browser |
29 |
and console to run a script, I'd rather just leave things broken |
30 |
because it *is* too much work by the amount of bugs I open. And it's |
31 |
not something I can do on a tablet or at work. Which would mean that |
32 |
not only it'll take me more time , and I would also have less time |
33 |
available. Not a good deal. |
34 |
|
35 |
Since the bugs are opened through a pre-filled form template, it's not |
36 |
easy for anything else to know what the bug is to attach logs to. One |
37 |
alternative would be to have the app that I use to show me the logs |
38 |
file the bug entirely for me. Unfortunately that means I'll have to |
39 |
figure out how to secure the app, as right now, being just a |
40 |
display-only thing, it's completely open to the Internet. And I'm sure |
41 |
Infra would rather not have a tool open to the internet that can open |
42 |
bugs with logs of many MBs attached. It will also slightly lower the |
43 |
quality of bugs because either it needs to build its own form to fill |
44 |
in for summary and blocking bugs, or it'll just go with the two |
45 |
summaries I know for sure how to get from the log ("fails to build", |
46 |
"fails tests"), so no more "foo[doc] fails to build" or "foo fails to |
47 |
build with ncurses[tinfo]". |
48 |
|
49 |
But let's reason a moment on the no-linked-logs policy: as Rich |
50 |
pointed out already, the policy is there for a reason and that reason |
51 |
is that we don't want people to submit bugs with pastebins or home |
52 |
server logs because they are bound to go away. I link logs to Amazon, |
53 |
which I pay for. Mike says it's unreasonable to expect me to pay |
54 |
Amazon for them forever... I pay $1/mo for storing viewing an adding |
55 |
the logs. And even that turned out to be actually an excess as I was |
56 |
paying between $.12 and $.20 for storing EBS snapshots from long ago |
57 |
that I never ended up removing. It's not even a rounding error at this |
58 |
point. |
59 |
|
60 |
|
61 |
Diego Elio Pettenò — Flameeyes |
62 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |