Opt your try pushes into Pernosco

[Andrew Halberstadt]

Hi everyone,

As of now, you can opt-in to Pernosco <https://pernos.co/> analysis on your
try pushes by running:

$ ./mach try fuzzy --pernosco

or:

$ ./mach try chooser --pernosco

For those who are unaware, Pernosco is a debugging service built on top of
rr. It will analyze your try push for failures, attempt to record the
failures
with rr, then e-mail you a link to a live debugging session. Allow a few
hours
after your task has finished for the Pernosco recording to complete.

There are several limitations:

1. It only works with Linux x64 debug tests
2. Failure should be reproducible (otherwise the recording might not
capture it)
3. An @mozilla.com e-mail address is required to log-in to the service
(./mach
try will fail early if you don't have this)
4. Artifact builds are not yet supported (see bug 1598142
<https://bugzilla.mozilla.org/show_bug.cgi?id=1598142>)

Previously we were using a whitelist of developers to control which pushes
were
analyzed. For now this whitelist continues to exist. If you are on it, you
can opt
out of Pernosco by passing in `--no-pernosco`.

Thanks to Kyle Huey for updating the Pernosco infrastructure to support this
flag.

Let me know if you have any questions.
Cheers,
Andrew

[Andrew Halberstadt]

On Mon, Nov 25, 2019 at 1:33 PM Kyle Huey <kh...@pernos.co> wrote:

>
> On Mon, Nov 25, 2019 at 10:16 AM Valentin Gosu <valent...@gmail.com>
> wrote:
>
>> I only have push permissions on my @gmail account, not on my @mozilla.com
>> one.
>> Does this mean I can't trigger a --pernosco try build, or that I need to
>> log with my @moz email in order to use Pernosco?
>>
>
> The latter. To log into Pernosco you need to have your @mozilla.com email
> address listed on your Github account (doesn't have to be public). We can
> whitelist people for whom that poses an issue if necessary.
>

Actually, also the former. I put in a check to prevent pushing without an @
mozilla.com
e-mail to avoid wasting resources and time. It'll currently error out,
though the error is
entirely superficial. Maybe we can change it to a prompt or implement some
kind of
`--force` flag to by-pass it. I filed bug 1599267
<https://bugzilla.mozilla.org/show_bug.cgi?id=1599267>.

For now you can comment this line out:
https://searchfox.org/mozilla-central/rev/0678172d5b5c681061b904c776b668489e3355b0/tools/tryselect/templates.py#144

-Andrew

[Kyle Huey]

On Mon, Nov 25, 2019 at 10:16 AM Valentin Gosu <valent...@gmail.com>
wrote:

> On Mon, 25 Nov 2019 at 18:29, Andrew Halberstadt <ah...@mozilla.com> wrote:
>
>> Hi everyone,
>>
>> As of now, you can opt-in to Pernosco <https://pernos.co/> analysis on
>> your
>> try pushes by running:
>>
>> $ ./mach try fuzzy --pernosco
>>
>> or:
>>
>> $ ./mach try chooser --pernosco
>>
>> For those who are unaware, Pernosco is a debugging service built on top of
>> rr. It will analyze your try push for failures, attempt to record the
>> failures
>> with rr, then e-mail you a link to a live debugging session. Allow a few
>> hours
>> after your task has finished for the Pernosco recording to complete.
>>
>> There are several limitations:
>>
>> 1. It only works with Linux x64 debug tests
>> 2. Failure should be reproducible (otherwise the recording might not
>> capture it)
>> 3. An @mozilla.com e-mail address is required to log-in to the service
>> (./mach
>> try will fail early if you don't have this)
>>
>

> I only have push permissions on my @gmail account, not on my @mozilla.com
> one.
> Does this mean I can't trigger a --pernosco try build, or that I need to
> log with my @moz email in order to use Pernosco?
>

The latter. To log into Pernosco you need to have your @mozilla.com email
address listed on your Github account (doesn't have to be public). We can
whitelist people for whom that poses an issue if necessary.

- Kyle

>
>
>> 4. Artifact builds are not yet supported (see bug 1598142
>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1598142>)
>>
>> Previously we were using a whitelist of developers to control which pushes
>> were
>> analyzed. For now this whitelist continues to exist. If you are on it, you
>> can opt
>> out of Pernosco by passing in `--no-pernosco`.
>>
>> Thanks to Kyle Huey for updating the Pernosco infrastructure to support
>> this
>> flag.
>>
>> Let me know if you have any questions.
>> Cheers,
>> Andrew

>> _______________________________________________
>> dev-platform mailing list
>> dev-pl...@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-platform
>>
>