Home | Search | chromium - Builders
Login

Builder Mac ASAN Release Build 14817 Apple OSX

Results:

Success

Trigger Info:

Projectchromium
Revision5823b44aa85c3e803530cc77e9bd7429d523c575
Got Revision5823b44aa85c3e803530cc77e9bd7429d523c575

Execution:

Steps and Logfiles:

Show:
  1. ( 0 ) Failed to fetch step information from LogDog
    Log stream has no annotation entries

Build Properties:

NameValueSource

Blamelist:

  1. Peter Kasting (pkastingohnoyoudont@chromium.org)
  2. Cheng-Yu Lee (cyleeohnoyoudont@chromium.org)

Timing:

Create Saturday, 11-Aug-18 05:55:37 UTC
Start Saturday, 11-Aug-18 05:55:41 UTC
End Saturday, 11-Aug-18 07:27:16 UTC
Pending 3 secs
Execution 1 hrs 31 mins

All Changes:

  1. Revert "Change the history state throttle interval from 60 to 120 Hz."

    Changed by Peter Kasting - pkastingohnoyoudont@chromium.org
    Changed at Saturday, 11-Aug-18 05:51:46 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision 5823b44aa85c3e803530cc77e9bd7429d523c575

    Comments

    Revert "Change the history state throttle interval from 60 to 120 Hz."
    
    This reverts commit 8e4127dd506c501cd3f51d91dc22a3dfa8f5f1ca.
    
    Reason for revert: Part 1 of trying to revert the history throttling changes, to see if https://bugs.chromium.org/p/chromium/issues/detail?id=870861 improves.
    
    Original change's description:
    > Change the history state throttle interval from 60 to 120 Hz.
    > 
    > This is a bit more lenient and may enable some callers, including a flaky test,
    > to get (more of) what they need. The test's root problem seems to be data races
    > (see issue 847326), however.
    > 
    > Bug: 870861
    > Change-Id: I249e9f06fa9a9a9f3b74e53cf2ef3f34b0c2371c
    > Reviewed-on: https://chromium-review.googlesource.com/1171825
    > Reviewed-by: Daniel Cheng <dcheng@chromium.org>
    > Commit-Queue: Chris Palmer <palmer@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#582415}
    
    TBR=palmer@chromium.org,dcheng@chromium.org,kinuko@chromium.org
    
    Change-Id: I9fb7b5b0f8ebff8b6d6c5a772745cfd2c10ef51a
    No-Presubmit: true
    No-Tree-Checks: true
    No-Try: true
    Bug: 870861
    Reviewed-on: https://chromium-review.googlesource.com/1171708
    Reviewed-by: Peter Kasting <pkasting@chromium.org>
    Commit-Queue: Peter Kasting <pkasting@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#582432}

    Changed files

    • third_party/blink/renderer/core/frame/history.cc
  2. Setting oom_score_adj directly is faster and doesn't have to involve debugd when ARC++ is disabled.

    Changed by Cheng-Yu Lee - cyleeohnoyoudont@chromium.org
    Changed at Saturday, 11-Aug-18 05:32:37 UTC
    Repository https://chromium.googlesource.com/chromium/src
    Branch
    Revision acd58b3ac64ab2e422a2c365bc995cb02ab23470

    Comments

    Setting oom_score_adj directly is faster and doesn't have to involve debugd when ARC++ is disabled.
    
    Bug: 868249
    Change-Id: Ie99e4c4ac7738c369a9b54bf2621a2c16dc8bc1d
    Reviewed-on: https://chromium-review.googlesource.com/1168222
    Reviewed-by: Cheng-Yu Lee <cylee@chromium.org>
    Reviewed-by: Gabriel Charette <gab@chromium.org>
    Commit-Queue: Cheng-Yu Lee <cylee@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#582431}

    Changed files

    • base/process/memory_linux.cc
    • base/threading/thread_restrictions.h
    • chrome/browser/resource_coordinator/tab_manager_delegate_chromeos.cc