New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839411 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 839470
Owner: ----
Closed: May 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

system_health.common_desktop/browse:social:twitter_infinite_scroll in system_health.common_desktop very flaky on chromium.perf/Win 7 Nvidia GPU Perf

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, May 3 2018

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of sullivan@google.com

Builders failed on: 
- Win 7 Nvidia GPU Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Win%207%20Nvidia%20GPU%20Perf

Flakiness dashboard link: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=system_health.common_desktop&builder=chromium.perf%3AWin%207%20Nvidia%20GPU%20Perf

This seems to have gotten flaky around r552198:r554629. Kicking off a bisect.

Sample log:
https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FWin_7_Nvidia_GPU_Perf%2F2330%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.common_desktop_on_NVIDIA_GPU_on_Windows_on_Windows-2008ServerR2-SP1%2F0%2Fstdout
(WARNING) 2018-05-03 02:52:47,313 artifact_results.AddArtifact:128  Moving artifact file 'c:\\b\\s\\w\\itluwen9\\tmplgpwqx.png' to 'c:\\b\\s\\w\\itluwen9\\tmpuyjqajtelemetry\\artifacts'
Traceback (most recent call last):
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\story_runner.py", line 123, in _RunStoryAndProcessErrorIfNeeded
    state.RunStory(results)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\page\shared_page_state.py", line 311, in RunStory
    self._current_page.Run(self)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\page\__init__.py", line 95, in Run
    self.RunPageInteractions(action_runner)
  File "c:\b\s\w\ir\tools\perf\page_sets\system_health\system_health_story.py", line 106, in RunPageInteractions
    self._DidLoadDocument(action_runner)
  File "c:\b\s\w\ir\tools\perf\page_sets\system_health\browsing_stories.py", line 833, in _DidLoadDocument
    self._Scroll(action_runner, self.SCROLL_DISTANCE, self.SCROLL_STEP)
  File "c:\b\s\w\ir\tools\perf\page_sets\system_health\browsing_stories.py", line 857, in _Scroll
    last_scroll_height=last_scroll_height)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 261, in WaitForJavaScriptCondition
    return self._tab.WaitForJavaScriptCondition(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\browser\web_contents.py", line 239, in WaitForJavaScriptCondition
    return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py", line 302, in WaitForJavaScriptCondition
    e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 60s for IsJavaScriptExpressionTrue.
Console output:
(INFO) 2018-05-03 02:52:47,315 chrome_tracing_agent.RecordClockSyncMarker:183  Chrome version: 3419
(ERROR) 2018-05-03 02:52:50,782 tracing_controller_backend.CollectAgentTraceData:314  Error when deleting c:\b\s\w\itluwen9\tmpz3ngwh, will try again at exit.
Traceback (most recent call last):
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py", line 310, in CollectAgentTraceData
    os.remove(self._trace_log)
 
Cc: charliea@chromium.org nednguyen@chromium.org
Cc-ing benchmark owners.
Also failing on Intel GPU Perf.
Project Member

Comment 4 by bugdroid1@chromium.org, May 3 2018

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

commit b9111cee711e277c1f55654937510e20f4134926
Author: Annie Sullivan <sullivan@chromium.org>
Date: Thu May 03 15:19:40 2018

Disable flaky browse:social:twitter_infinite_scroll on Win

NOTRY=true
TBR=nednguyen@google.com

Bug:  839411 
Change-Id: I659bb4ca9a7cac243e6ccc294d383ce71776f84d
Reviewed-on: https://chromium-review.googlesource.com/1042527
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555735}
[modify] https://crrev.com/b9111cee711e277c1f55654937510e20f4134926/tools/perf/expectations.config

Cc: lukasza@chromium.org
+lukasza: bisect hasn't finished yet, but it's down to 10 CLs with the --site-per-process CL in the range, and this looks very similar to bug 839470.
Mergedinto: 839470
Status: Duplicate (was: Available)
Thanks for the heads-up.  It seems to be a dupe of the twitter_infinite_scroll being investigated in issue 839470.
Cc: kbr@chromium.org rdevlin....@chromium.org alex...@chromium.org pastarmovj@chromium.org isherman@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12fa764bc40000

Make --site-per-process the default on ToT via fieldtrial_testing_config by lukasza@chromium.org
https://chromium.googlesource.com/chromium/src/+/fb1ccf02ee8ca79e1404abfd3a3a7d540b7d2dbd

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 8 by kbr@chromium.org, May 5 2018

Cc: -kbr@chromium.org
📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/14a882a8640000
Still failing most of the time.
😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14e13c06e40000

Buildbucket says the build completed successfully, but Pinpoint can't find the isolate hash.

Sign in to add a comment