Assigned
Status Update
Comments
ap...@google.com <ap...@google.com> #2
[Details redacted due to bug visibility]
Change-Id: I1dc2e6f496a559bb02e5c3e110477f32a1467999
https://chrome-internal-review.googlesource.com/7293973
Change-Id: I1dc2e6f496a559bb02e5c3e110477f32a1467999
ap...@google.com <ap...@google.com> #3
Project: chromium/src
Branch: main
commit a816fd8edd715d781b50f3155c56905cf36f4907
Author: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Date: Wed May 15 23:29:07 2024
Roll clank/internal/apps from 4ea0ed5c9b07 to 3e4a02712b8d (1 revision)
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/4ea0ed5c9b07..3e4a02712b8d
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll
Please CC chrome-brapp-engprod@google.com,davidjm@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Bug: chromium:338979594,chromium:340938898,chromium:340940207,chromium:340940885,chromium:40232150
Tbr: davidjm@google.com
No-Try: true
Change-Id: I4763beba8fbbe66015558cea0da80c40cf8921f8
Reviewed-on:https://chromium-review.googlesource.com/c/chromium/src/+/5542692
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1301652}
M DEPS
M clank
https://chromium-review.googlesource.com/5542692
Branch: main
commit a816fd8edd715d781b50f3155c56905cf36f4907
Author: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Date: Wed May 15 23:29:07 2024
Roll clank/internal/apps from 4ea0ed5c9b07 to 3e4a02712b8d (1 revision)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
Please CC chrome-brapp-engprod@google.com,davidjm@google.com on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
Documentation for the AutoRoller is here:
Bug: chromium:338979594,chromium:340938898,chromium:340940207,chromium:340940885,chromium:40232150
Tbr: davidjm@google.com
No-Try: true
Change-Id: I4763beba8fbbe66015558cea0da80c40cf8921f8
Reviewed-on:
Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#1301652}
M DEPS
M clank
ya...@chromium.org <ya...@chromium.org> #4
[Navigation triage] Hi rnanjappan@, I don't think the navigation component is the component for this bug. The navigation component is for navigations in the browser, like opening URLs, clicking links, executing javascript. I tried to look at 339271455 for more context but don't have access. If you think this is the right component, can you please provide more context? Thanks.
pe...@google.com <pe...@google.com> #5
The issue's primary component must be in the Component Tags, so re-adding it. To change the primary component, use the edit button at the top of the issue, just above the title.
pe...@google.com <pe...@google.com> #6
The issue's primary component must be in the Component Tags, so re-adding it. To change the primary component, use the edit button at the top of the issue, just above the title.
tw...@google.com <tw...@google.com> #7
Looks like this test is 10+ years old, not sure there's a clear Clank Eng owner.
Charles, do you mind taking an initial look at what might be going wrong here? Test was added to a disabled filter, so not urgent.
Charles, do you mind taking an initial look at what might be going wrong here? Test was added to a disabled filter, so not urgent.
cr...@chromium.org <cr...@chromium.org> #8
[Navigation Triage] I'll put this back in the Navigation component since the test is navigation-related.
cl...@google.com <cl...@google.com> #9
Will take a look! :)
Description
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:87)
at org.junit.Assert.assertTrue(Assert.java:42)
at org.junit.Assert.assertTrue(Assert.java:53)
at org.chromium.chrome.browser.NavigateTest.testWindowOpenUrlSpoof(NavigateTest.java:703)