| commit | 40c044166b68dc836f6d7f5fa45b33d492bcfec1 | |
| author | jyasskin <jyasskin@chromium.org> | |
| Mon, 10 Aug 2015 22:13:32 +0000 (10 15:13 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Mon, 10 Aug 2015 22:14:01 +0000 (10 22:14 +0000) | ||
| tree | 5cda79cae8d77644546c95262d9c224302a56660 | treesnapshot (tar.gz zip) |
| parent | b507eab539043b2af797c31820abc3066769240e | commitdiff |
Speculatively exclude SmartSessionRestoreMRUTest.CorrectLoadingOrder on DrMemory.
Even though SmartSessionRestoreMRUTest.PRE_CorrectLoadingOrder is excluded, it's
still running, and I'm theorizing that it's because exclusions don't work well
for PRE tests.
This started turning the bot red in
http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%20%28DrMemory%20full%29%20%285%29/builds/3805,
but it was failing and yellow before then.
TBR=oshima@chromium.org,georgesak@chromium.org
BUG=504885
Review URL: https://codereview.chromium.org/1273293004
Cr-Commit-Position: refs/heads/master@{#342709}
Even though SmartSessionRestoreMRUTest.PRE_CorrectLoadingOrder is excluded, it's
still running, and I'm theorizing that it's because exclusions don't work well
for PRE tests.
This started turning the bot red in
http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Browser%20%28DrMemory%20full%29%20%285%29/builds/3805,
but it was failing and yellow before then.
TBR=oshima@chromium.org,georgesak@chromium.org
BUG=504885
Review URL: https://codereview.chromium.org/1273293004
Cr-Commit-Position: refs/heads/master@{#342709}
| tools/valgrind/gtest_exclude/browser_tests.gtest-drmemory.txt | diffblobblamehistory |