Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(114)

Issue 1646803002: Revert of DevTools: remove V8ScriptRunner use from InjectedScript*. (Closed)

Created:
4 years, 10 months ago by Noel Gordon
Modified:
4 years, 10 months ago
CC:
chromium-reviews, caseq+blink_chromium.org, lushnikov+blink_chromium.org, pfeldman+blink_chromium.org, apavlov+blink_chromium.org, devtools-reviews_chromium.org, blink-reviews, blink-reviews-bindings_chromium.org, sergeyv+blink_chromium.org, kozyatinskiy+blink_chromium.org, pilgrim_google
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Revert of DevTools: remove V8ScriptRunner use from InjectedScript*. (patchset #2 id:20001 of https://codereview.chromium.org/1641933002/ ) Reason for revert: http/tests/inspector/resource-tree/resource-tree-non-unique-url.html started failing https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%2032/bui... Reverting to see if we can get that test to pass again. Original issue's description: > DevTools: remove V8ScriptRunner use from InjectedScript*. > > BUG=580337 > > Committed: https://crrev.com/ec279b9d63c3a96d237495967faba97be76597eb > Cr-Commit-Position: refs/heads/master@{#372020} TBR=dgozman@chromium.org,jochen@chromium.org,pfeldman@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=580337 Committed: https://crrev.com/718abf542ea95a35036331f3c78caf21959155dc Cr-Commit-Position: refs/heads/master@{#372034}

Patch Set 1 #

Messages

Total messages: 16 (4 generated)
Noel Gordon
Created Revert of DevTools: remove V8ScriptRunner use from InjectedScript*.
4 years, 10 months ago (2016-01-28 06:37:05 UTC) #1
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1646803002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1646803002/1
4 years, 10 months ago (2016-01-28 06:37:36 UTC) #2
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 10 months ago (2016-01-28 06:38:35 UTC) #4
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/718abf542ea95a35036331f3c78caf21959155dc Cr-Commit-Position: refs/heads/master@{#372034}
4 years, 10 months ago (2016-01-28 06:39:48 UTC) #7
Noel Gordon
On 2016/01/28 06:38:35, commit-bot: I haz the power wrote: > Committed patchset #1 (id:1) https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%2032/builds/44900 ...
4 years, 10 months ago (2016-01-28 06:42:32 UTC) #8
pfeldman
A revert of this CL (patchset #1 id:1) has been created in https://codereview.chromium.org/1645663004/ by pfeldman@chromium.org. ...
4 years, 10 months ago (2016-01-28 15:42:23 UTC) #9
Noel Gordon
On 2016/01/28 15:42:23, pfeldman wrote: > A revert of this CL (patchset #1 id:1) has ...
4 years, 10 months ago (2016-01-28 15:49:22 UTC) #10
pfeldman
> You should maybe consider fixing the test. I was referring to the "Workflows" section ...
4 years, 10 months ago (2016-01-28 15:52:33 UTC) #11
pfeldman
Yep, here it is: https://code.google.com/p/chromium/issues/detail?id=575766
4 years, 10 months ago (2016-01-28 15:56:55 UTC) #12
Noel Gordon
On 2016/01/28 15:56:55, pfeldman wrote: > Yep, here it is: https://code.google.com/p/chromium/issues/detail?id=575766 IC, an Oilpan problem ...
4 years, 10 months ago (2016-01-28 16:15:48 UTC) #13
pfeldman
On 2016/01/28 16:15:48, noel gordon wrote: > On 2016/01/28 15:56:55, pfeldman wrote: > > Yep, ...
4 years, 10 months ago (2016-01-28 16:34:49 UTC) #15
Noel Gordon
4 years, 10 months ago (2016-01-28 17:12:35 UTC) #16
Message was sent while issue was closed.
On 2016/01/28 16:34:49, pfeldman wrote:
> On 2016/01/28 16:15:48, noel gordon wrote:
> > On 2016/01/28 15:56:55, pfeldman wrote:
> > > Yep, here it is:
https://code.google.com/p/chromium/issues/detail?id=575766
> > 
> > IC, an Oilpan problem ... since Jan 8th! 
> > 
> 
> Could you explain you tone please?

What I meant was, I thought a new expectation might have been submitted sometime
during Jan 8th till today to handle the flake.  

Looked to be recent issue to me, didn't find the bug reference you found.

> The issue was filed against Oilpan (non-tree-closer bots) on Jan 8th. Oilpan
> owners were aware of the issue, but decided to enable Oilpan on trunk this
> Monday. Given the scale of Oilpan change, breakages like this are expected and
> as per haraken's update they are going full speed through the issues.

Yes I have been cc-ing haraken on any thing I thought was Oilpan related.

First time I've had to garden the tree with Oilpan on.
 
> Gardener's responsibility is to follow the documented workflow and I cited
what
> you should have done from that doc.

Yes, what to do for Oilpan failures had going old skool and adding them
OilpanExpectations.

That didn't work, of course, but haraken@ mentioned were to put them now.

> > In other news we are red again:
> > 
>
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%2032/bui...
>  
> And the reason is that you did a wrong thing - it is clear that randon revert
> does not fix the flake and the doc suggests what you should have done to
resolve
> it.

I mentioned in the revert log "Reverting to see if we can get that test to pass
again", aka speculative.  And I revert-revert those if I find a revert does not
fix things.  You beat to me to it, but apparently I was looking in the wrong
place :/

> > pilgrim@ is the gardener, so perhaps we can add a new expectation for Oilpan
> for
> > this test.
> 
> I did that first thing in the morning, so he would no' need to.

Thanks for that.

Powered by Google App Engine
This is Rietveld 408576698