forked from chromium/chromium
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run debug builds of ozone_demo #5
Comments
EwanRoycroft
added
bug
Something isn't working
ozone
Specific to the Ozone implementation
labels
Jul 1, 2020
Terminal log above says "permission denied" for
Even though the directory exists:
|
Adding |
EwanRoycroft
pushed a commit
that referenced
this issue
Oct 6, 2020
This reverts commit 525a4a2. Reason for revert: Fixed missing @EnD Original change's description: > Revert "[ios] Reduce pointer boilerplate in Credential Provider" > > This reverts commit ca2e472. > > Reason for revert: breaks compile, see https://ci.chromium.org/p/chromium/builders/ci/ios-simulator-noncq/4247? > > Original change's description: > > [ios] Reduce pointer boilerplate in Credential Provider > > > > crrev.com/c/2199891 introduces a reusable class for pointer > > interactions for non-button views. This class internally handles > > all the delegate callbacks. So usage is simplified to a single line. > > > > This CL should have no impact/change on the UI. > > > > Bug: 1073961 > > Change-Id: I28904804916d0c112f73fe6e372bea6aede504d0 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199727 > > Reviewed-by: Javier Ernesto Flores Robles <javierrobles@chromium.org> > > Commit-Queue: edchin <edchin@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#768924} > > TBR=edchin@chromium.org,javierrobles@chromium.org > > Change-Id: Ib4e9c99203d3dbb673d49f302b342d2055561b3d > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 1073961 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203138 > Reviewed-by: Dana Fried <dfried@google.com> > Commit-Queue: Dana Fried <dfried@google.com> > Cr-Commit-Position: refs/heads/master@{#768987} TBR=edchin@chromium.org,javierrobles@chromium.org,dfried@google.com # Not skipping CQ checks because this is a reland. TBR=javierrobles@chromium.org (cherry picked from commit 1e0897d) Bug: 1073961 Change-Id: I8534dd58ff1f7ba9f2ad2567bea894ed200b8597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2202687 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by: edchin <edchin@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#769056} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203837 Reviewed-by: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/branch-heads/4147@{#5} Cr-Branched-From: 1630782-refs/heads/master@{#768962}
EwanRoycroft
pushed a commit
that referenced
this issue
Oct 26, 2020
This reverts commit 27e795c. Reason for revert: Sorry for another revert, but this is still causing flake. See https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome/9353 . Specifically: ../../content/public/test/browser_test_base.cc:702: Failure Failed RunLoop::Run() timed out. Stack trace: #0 0x56324b6c5e50 base::internal::Invoker<>::Run() #1 0x56324b623b4f base::(anonymous namespace)::OnRunLoopTimeout() #2 0x56324b6249e3 base::internal::Invoker<>::RunOnce() #3 0x5632492266ab base::internal::CancelableCallbackImpl<>::ForwardOnce<>() #4 0x56324b63bc46 base::TaskAnnotator::RunTask() #5 0x56324b64c845 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() chromium#6 0x56324b64c588 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() #7 0x56324b69fb29 base::MessagePumpLibevent::Run() #8 0x56324b64cf9a base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #9 0x56324b62363e base::RunLoop::Run() #10 0x5632483f1f23 chromeos::EduCoexistenceLoginBrowserTest::WaitForScreenExit() #11 0x563248402206 chromeos::ParentalHandoffScreenBrowserTest_RegularUserLogin_Test::RunTestOnMainThread() #12 0x56324bae8dd1 content::BrowserTestBase::ProxyRunTestOnMainThreadLoop() #13 0x56324b6fff04 ChromeBrowserMainParts::PreMainMessageLoopRunImpl() #14 0x56324b6ff3b9 ChromeBrowserMainParts::PreMainMessageLoopRun() #15 0x563248bf574e chromeos::ChromeBrowserMainPartsChromeos::PreMainMessageLoopRun() #16 0x563249bdf3b0 content::BrowserMainLoop::PreMainMessageLoopRun() #17 0x563249f3668a content::StartupTaskRunner::RunAllTasksNow() #18 0x563249bde45b content::BrowserMainLoop::CreateStartupTasks() #19 0x563249be0bba content::BrowserMainRunnerImpl::Initialize() #20 0x563249bdcbd2 content::BrowserMain() #21 0x56324b198740 content::RunBrowserProcessMain() #22 0x56324b1995d1 content::ContentMainRunnerImpl::RunServiceManager() #23 0x56324b199234 content::ContentMainRunnerImpl::Run() #24 0x56324a5c8687 content::RunContentProcess() #25 0x56324a5c8c16 content::ContentMain() #26 0x56324bae8a00 content::BrowserTestBase::SetUp() #27 0x56324b5d8620 InProcessBrowserTest::SetUp() Original change's description: > Reland "Adds parental handoff login screen in oobe." > > This is a reland of dca1afe > > This is an interesting failure point due to the difference between > official builds and non official builds. In official builds, the > Sync Consent screen is shown and it will not exit until we interact > with it. The waiters timeout waiting for the Parental Handoff Screen > to be shown. > > Original change's description: > > > Adds parental handoff login screen in oobe. > > > > The description and mock can be seen in the comments in the bug report. > > > > Bug: 1134567 > > Change-Id: I2ecd7c72629dc96dfbc054f747c6cb2508210709 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2466618 > > Commit-Queue: Yilkal Abe <yilkal@chromium.org> > > Reviewed-by: Aga Wronska <agawronska@chromium.org> > > Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org> > > Reviewed-by: Jesse Doherty <jwd@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#819158} > > Bug: 1134567 > Change-Id: Id4d8c15363579799da14a3f3ed0a285e61dde5d6 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2489756 > Commit-Queue: Yilkal Abe <yilkal@chromium.org> > Reviewed-by: Aga Wronska <agawronska@chromium.org> > Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org> > Reviewed-by: Jesse Doherty <jwd@chromium.org> > Cr-Commit-Position: refs/heads/master@{#820388} TBR=jwd@chromium.org,rsorokin@chromium.org,agawronska@chromium.org,yilkal@chromium.org Change-Id: I6febf7f06a0d5d7a072be1e50aaa9cc2a4d3c217 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1134567 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2495423 Reviewed-by: Scott Violet <sky@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#820489}
EwanRoycroft
pushed a commit
that referenced
this issue
Nov 2, 2020
Separating the branch configuration by file has been rather unwieldy and would only get worse when it is necessary to maintain a 3rd subset of builders for LTS. This puts the information about what branches the LUCI resources are applicable to with the resource. (cherry picked from commit b29b9a2) Bug: 1119446 Change-Id: I1c8622b7084fd332ae16fcdc9afe5d6e30dc1811 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2365915 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Erik Staab <estaab@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#800627} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2369254 Reviewed-by: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/branch-heads/4240@{#5} Cr-Branched-From: f297677-refs/heads/master@{#800218}
EwanRoycroft
pushed a commit
that referenced
this issue
Mar 3, 2021
TBR=bindusuvarna@chromium.org Change-Id: I8341ba6e630a07d3b70118fe7c01bb2b89deaee7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633742 Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4389@{#5} Cr-Branched-From: 9251c5d-refs/heads/master@{#843830}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Debug builds of the
ozone_demo
target will exit after a few seconds, reportingCheck failed: IsGpuFenceSupported()
.More information
ozone_demo
Steps to reproduce
Make a debug build of
ozone_demo
for the Ozone-GBM platform and run on the RPi 4.GN arguments
(Ignoring any additional codec args.)
Command
Terminal output
The text was updated successfully, but these errors were encountered: