Disable randomized experiments?

[John Williams]

Is there a flag to run Chrome such that experimental features that are enabled for a certain percentage of profiles are always disabled? I had trouble reproducing this issue, but when I created a new profile, I saw the behavior that was originally described, and one of my teammates thinks the difference is that the first profile I used was opted into an experiment that interacts with the bug I was trying to reproduce.

[Alexei Svitkine]

(Re-sending from right email this time.)

On Tue, Sep 18, 2018, 6:25 PM Alexei Svitkine <asvi...@google.com> wrote:

If you start Chrome with a clean user dir, experiments from the server won't apply. So that's the easiest way to test the hypothesis.

(Experiments will apply the next launch since the configs would have been downloaded and persisted to local state for next start up.)

On Tue, Sep 18, 2018, 5:44 PM 'John Williams' via Chromium-dev <chromi...@chromium.org> wrote:

Is there a flag to run Chrome such that experimental features that are enabled for a certain percentage of profiles are always disabled? I had trouble reproducing this issue, but when I created a new profile, I saw the behavior that was originally described, and one of my teammates thinks the difference is that the first profile I used was opted into an experiment that interacts with the bug I was trying to reproduce.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CALaH6DvWsv9nCpxgYGK_9RyJOo67rap%3Dq9B0uDzMrEmLju8mRA%40mail.gmail.com.

[Primiano Tucci]

Also, --no-experiments should achieve that without requiring a new profile IIRC

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAKFU2SANO%3D7bLC35FB4cUUbN_n_xosFouxZSCHU8jVW5%3D%2BMhHA%40mail.gmail.com.

[Alexei Svitkine]

I think that flag only affects about:flags settings that users may have toggled.

[PhistucK]

While I believe you cannot disable field trials altogether, you can at least identify them by going to chrome://net-internals/#capture and clicking on "Stop". The "Active Field Trial Groups" shows their names.

Then, I believe you can disable them one by one (or create a script that takes the names and creates a command line disabling all of them) using some command flag.

(Of course, in case it does not list all of the available (not necessarily enabled) field trials, then some field trial may be added the next time you launch Chrome. Wash, rinse, repeat)

☆PhistucK

On Wed, Sep 19, 2018 at 12:44 AM 'John Williams' via Chromium-dev <chromi...@chromium.org> wrote:

Is there a flag to run Chrome such that experimental features that are enabled for a certain percentage of profiles are always disabled? I had trouble reproducing this issue, but when I created a new profile, I saw the behavior that was originally described, and one of my teammates thinks the difference is that the first profile I used was opted into an experiment that interacts with the bug I was trying to reproduce.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.