Re: "Getting Traces"

António Fernandes <[email protected]> Thu, 11 Apr 2013 18:25:18 +0100
Newsgroups gmane.comp.gnome.bugsquad
Message-ID <CAJa6SmeORWkM8-BueL+X5ED6Khiq6Xb3R_FrmUuTajyKWK7NiA@mail.gmail.com>
--===============1769353652032118331==
Content-Type: multipart/alternative; boundary=047d7bfd056252eced04da1913e7

--047d7bfd056252eced04da1913e7
Content-Type: text/plain; charset=ISO-8859-1

Answering my own question:

> 3-
> Current instructions ask for reporters to add the traces as an attachment.
> I've noticed that bugzilla recognizes such text files as binary files.
>
> Also, I've seen reports where traces shows up in the description,
> expandable in line, instead of being an ordinary attachment. Example:
> https://bugzilla.gnome.org/show_bug.cgi?id=594425 I don't know how to do
> that, but it looks like something we should instruct reporters to do
> instead.
>

So, I found that all you need to do is paste the trace into the comment and
bugzilla-traceparser [1] will detect it automatically. Submitting traces
like this is preferable because of the features bugzilla-traceparser
provides, so I'll update the instructions in the wiki.

[1] https://launchpad.net/bugzilla-traceparser

--047d7bfd056252eced04da1913e7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">Answ=
ering my own question:<br></div><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">

<div dir=3D"ltr"><div><div><div>3-<br></div><div>Current instructions ask f=
or reporters to add the traces as an attachment. I&#39;ve noticed that bugz=
illa recognizes such text files as binary files.<br>
<br>Also, I&#39;ve seen reports where traces shows up in the description, e=
xpandable in line, instead of being an ordinary attachment. Example: <a hre=
f=3D"https://bugzilla.gnome.org/show_bug.cgi?id=3D594425" target=3D"_blank"=
>https://bugzilla.gnome.org/show_bug.cgi?id=3D594425</a> I don&#39;t know h=
ow to do that, but it looks like something we should instruct reporters to =
do instead.<br>


</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">So, I found that al=
l you need to do is paste the trace into the comment and bugzilla-tracepars=
er [1] will detect it automatically. Submitting traces like this is prefera=
ble because of the features bugzilla-traceparser provides, so I&#39;ll upda=
te the instructions in the wiki.<br>

<br>[1] <a href=3D"https://launchpad.net/bugzilla-traceparser">https://laun=
chpad.net/bugzilla-traceparser</a><br></div></div>

--047d7bfd056252eced04da1913e7--

--===============1769353652032118331==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnome-bugsquad mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-bugsquad

--===============1769353652032118331==--