Builder Linux FYI Release (Intel HD 630) Build 4964
Results:
Failure webgl2_conformance_gl_passthrough_tests on Intel GPU on Linux on Ubuntu
Trigger Info:
Project | chromium |
Revision | 5823b44aa85c3e803530cc77e9bd7429d523c575 |
Got Revision | 5823b44aa85c3e803530cc77e9bd7429d523c575 |
Execution:
- Source: Task 3f40735381878b10
- Bot: swarm1078-c4
Steps and Logfiles:
Show:-
( 106751 days 23 hrs ) Failed to fetch step information from LogDogLog stream has no annotation entries
- - no logs -
Build Properties:
Name | Value | Source |
---|
Blamelist:
- Peter Kasting (pkastingohnoyoudont@chromium.org)
- Cheng-Yu Lee (cyleeohnoyoudont@chromium.org)
- Findit (findit-for-meohnoyoudont@appspot.gserviceaccount.com)
- Peter Kasting (pkastingohnoyoudont@chromium.org)
Timing:
Create | Saturday, 11-Aug-18 06:17:17 UTC |
Start | Saturday, 11-Aug-18 06:17:52 UTC |
End | Saturday, 11-Aug-18 07:19:58 UTC |
Pending | 34 secs |
Execution | 1 hrs 2 mins |
All Changes:
-
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
-
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
-
Revert "Add vector of intervals range checking to Time Restrictions policy"
Changed by Findit - findit-for-meohnoyoudont@appspot.gserviceaccount.com Changed at Saturday, 11-Aug-18 05:19:12 UTC Repository https://chromium.googlesource.com/chromium/src Branch Revision 3a30357690bfd391e2ddab461c6bd48e2c8a5580 Comments
Revert "Add vector of intervals range checking to Time Restrictions policy" This reverts commit b3392d988ae23dc52d9b386af47dc6a53a2d22c8. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 582403 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2IzMzkyZDk4OGFlMjNkYzUyZDliMzg2YWY0N2RjNmE1M2EyZDIyYzgM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/28575 Sample Failed Step: unit_tests Original change's description: > Add vector of intervals range checking to Time Restrictions policy > > * Add function GetEndOfCurrent interval to obtain the last end of the > interval which contains the current time. > * Add function MaterializeIntervalsToLocalTimezone, which materializes > the given intervals to the current local timezone. > * Add function TimeIsInsideCrosSettingsIntervals, which checks if the > current time is inside the intervals set in cros settings. It then > returns the localized string of the end of the interval that contains > the current time. > > BUG=chromium:852860 > TEST=added unittests > > Change-Id: Ife32e31c8a929827fd14ab9f108c49eacb9c32c3 > Reviewed-on: https://chromium-review.googlesource.com/1132676 > Reviewed-by: Maksim Ivanov <emaxx@chromium.org> > Commit-Queue: Maksim Ivanov <emaxx@chromium.org> > Cr-Commit-Position: refs/heads/master@{#582403} No-Presubmit: true No-Tree-Checks: true No-Try: true BUG=chromium:852860 Change-Id: I1663fc559003d938270da4b8fd7e85719b8e9e01 Reviewed-on: https://chromium-review.googlesource.com/1172003 Cr-Commit-Position: refs/heads/master@{#582430}
Changed files
- chrome/browser/chromeos/BUILD.gn
- chrome/browser/chromeos/policy/device_auto_update_time_restrictions_utils.cc
- chrome/browser/chromeos/policy/device_auto_update_time_restrictions_utils.h
- chrome/browser/chromeos/policy/device_auto_update_time_restrictions_utils_unittest.cc
- chrome/browser/chromeos/policy/weekly_time/time_utils.cc
- chrome/browser/chromeos/policy/weekly_time/time_utils.h
- chrome/browser/chromeos/policy/weekly_time/time_utils_unittest.cc
- chrome/browser/chromeos/policy/weekly_time/weekly_time.h
- chrome/browser/chromeos/policy/weekly_time/weekly_time_interval.h
-
Revert "Remove unnecessary tab key press from Focus_AdvanceFocus test"
Changed by Peter Kasting - pkastingohnoyoudont@chromium.org Changed at Saturday, 11-Aug-18 05:15:47 UTC Repository https://chromium.googlesource.com/chromium/src Branch Revision 6df1590559bd965c71b181b4d948e0ea3318189a Comments
Revert "Remove unnecessary tab key press from Focus_AdvanceFocus test" This reverts commit 5eeadd143332f6fc6c26af924d8a38d5f49b06a2. Reason for revert: Seems to have caused failures on mac_cocoa_rel, see e.g. https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8938549477439492256/+/steps/interactive_ui_tests/0/logs/WebViewFocusInteractiveTest.Focus_AdvanceFocus/0 Original change's description: > Remove unnecessary tab key press from Focus_AdvanceFocus test > > The associated bug which required this extra tab is fixed. > > Bug: 147644 > Change-Id: Ied21533accc82613053e119aa2c5c64fc9de8343 > Reviewed-on: https://chromium-review.googlesource.com/1170986 > Reviewed-by: Ehsan Karamad <ekaramad@chromium.org> > Commit-Queue: Kevin McNee <mcnee@chromium.org> > Cr-Commit-Position: refs/heads/master@{#582240} TBR=ekaramad@chromium.org,mcnee@chromium.org Change-Id: I6c84e6950d7f74ae5b15eec084a536115e635ceb No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 147644 Reviewed-on: https://chromium-review.googlesource.com/1172002 Reviewed-by: Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#582429}
Changed files
- chrome/browser/apps/guest_view/web_view_interactive_browsertest.cc