Don't think I am the correct owner here. Have not touched this test.

It turns out that henrika@ just did a reland. The actual author of the test is sebsg@.

sebsg: can you take a look or assign to a better owner?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/49219e95f40800c5b710554712af7a2f31bd26ee

commit 49219e95f40800c5b710554712af7a2f31bd26ee
Author: guidou <guidou@chromium.org>
Date: Wed Jun 01 12:37:55 2016

Disable ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio on Windows due to flakiness.

BUG=616421
TBR=jochen@chromium.org,henrika@chromium.org,pkasting@chromiun.org

Review-Url: https://codereview.chromium.org/2032493002
Cr-Commit-Position: refs/heads/master@{#397113}

[modify] https://crrev.com/49219e95f40800c5b710554712af7a2f31bd26ee/chrome/browser/renderer_host/render_process_host_chrome_browsertest.cc

Thanks, I'll take a look and reassign if necessary.

Note: please make a habit of pasting a typical error log when disabling a test (links to logs quickly lead to 404s):

In this case the typical stdio on failure appears to be:
ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio (run #1):
[ RUN      ] ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio
Some features may not be available.
Some features may not be available.
[6076:3824:0531/190737:WARNING:webmediaplayer_impl.cc(345)] Using MultibufferDataSource
[3248:3876:0531/190737:WARNING:embedded_test_server.cc(193)] Request not handled. Returning 404: /favicon.ico
Some features may not be available.

which is peculiar per lack of crash or failure...?

From the full stdio (weird that the snippets don't match that):

[ RUN      ] ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio

[5972:324:0601/034834:ERROR:resource_bundle.cc(754)] Failed to load e:\b\swarm_slave\work\isolated\run_tmyto\out\Release_x64\chrome_material_100_percent.pak

Some features may not be available.

[0601/034834:ERROR:resource_bundle.cc(754)] Failed to load e:\b\swarm_slave\work\isolated\run_tmyto\out\Release_x64\chrome_material_100_percent.pak

Some features may not be available.

[6532:2828:0601/034835:WARNING:webmediaplayer_impl.cc(345)] Using MultibufferDataSource

[5972:7972:0601/034835:WARNING:embedded_test_server.cc(193)] Request not handled. Returning 404: /favicon.ico

[0601/034835:ERROR:resource_bundle.cc(754)] Failed to load e:\b\swarm_slave\work\isolated\run_tmyto\out\Release_x64\chrome_material_100_percent.pak

Some features may not be available.

[334/506] ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio (TIMED OUT)

A successful run looks like this:

[241/506] ChromeRenderProcessHostBackgroundingTest.ProcessPriorityAfterStoppedAudio (10739 ms)

(though logs are squashed on success so not clear whether same errors/warnings occur but clearly it's a slow test even on success which can explain why it sometimes times out)

It seems like this error: 
[0601/034906:ERROR:resource_bundle.cc(754)] Failed to load e:\b\swarm_slave\work\isolated\run_tmyto\out\Release_x64\chrome_material_100_percent.pak

happens several times during the runs. For example it happens in:
InputImeApiTest.CreateWindowTest
BrowserActionApiTest.BrowserActionOpenPopupOnPopup
PermissionBubbleManagerBrowserTest.KillSwitchNotifications
etc

And when it happens that test fails.

+pkasting for flakes related to missing chrome_material_100_percent.pak

Is the test failure caused by the .pak load failure, or are both symptoms of a shared cause?

I think varkha/tdanderson know more about the resource pak loading.

+estade, could it be related to changes in .isolate files in https://codereview.chromium.org/1991573002/?

might be fixed here: https://codereview.chromium.org/2028103002/

estade@, please correct me if I am wrong, but my understanding is that the error with chrome_material_100_percent is supposed to be harmless. More so, it happens every single time, so it doesn't really explain the flake.

I will land my CL, but I don't think there's any good reason for me to be the owner of this bug.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2f3f36758fba0f3436c4eca1370d1f78b7beb981

commit 2f3f36758fba0f3436c4eca1370d1f78b7beb981
Author: mfomitchev <mfomitchev@chromium.org>
Date: Thu Jun 02 16:03:51 2016

Do not try to load material design paks if not on Mac OS.

This gets rid of (harmless) errors when launching Chrome, which are a little
distracting.

BUG=616421

Review-Url: https://codereview.chromium.org/2028103002
Cr-Commit-Position: refs/heads/master@{#397430}

[modify] https://crrev.com/2f3f36758fba0f3436c4eca1370d1f78b7beb981/ui/base/resource/resource_bundle.cc

@sebsg: can you try to re-enable the tests if we believe this could have fixed it?

my understanding is the same as comment 14: the output lines are harmless.

when a test succeeds, we don't print the output, which is why you don't see these lines normally. only when a test fails do we print the output.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ebca0939c5c1adefb92df85d1a085d1bc6999f5b

commit ebca0939c5c1adefb92df85d1a085d1bc6999f5b
Author: sebsg <sebsg@chromium.org>
Date: Wed Aug 03 13:54:12 2016

I can no longer repro locally.

BUG=616421

Review-Url: https://codereview.chromium.org/2200143002
Cr-Commit-Position: refs/heads/master@{#409505}

[modify] https://crrev.com/ebca0939c5c1adefb92df85d1a085d1bc6999f5b/chrome/browser/renderer_host/render_process_host_chrome_browsertest.cc