Skip to content

deps: V8: backport 2d5017a0fc02#34272

Closed
bcoe wants to merge 1 commit intonodejs:masterfrom
bcoe:v8-10628
Closed

deps: V8: backport 2d5017a0fc02#34272
bcoe wants to merge 1 commit intonodejs:masterfrom
bcoe:v8-10628

Conversation

@bcoe
Copy link
Contributor

@bcoe bcoe commented Jul 9, 2020 •
edited
Loading

Original commit message:

[coverage] remove the last continuation range before synthetic return

Rather than only removing the continuation range for the last return
statement prior to a synthetic return statement, remove the
continuation tracking for whatever statement occurs prior to the
synthetic return.

Bug: v8:10628
Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
Commit-Queue: Benjamin Coe <[email protected]>
Reviewed-by: Toon Verwaest <[email protected]>
Reviewed-by: Jakob Gruber <[email protected]>
Reviewed-by: Sigurd Schneider <[email protected]>
Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Refs: bcoe/c8#229

deps: V8: backport 2d5017a0fc02
aa0a843 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a
@bcoe bcoe requested review from Trott and devsnek July 9, 2020 04:24
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. v8 engine Issues and PRs related to the V8 dependency. labels Jul 9, 2020
@Trott
Copy link
Member

Trott commented Jul 9, 2020

@nodejs/v8-update

@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Jul 9, 2020 •
edited by bcoe
Loading

CI: https://ci.nodejs.org/job/node-test-pull-request/32267/ ✅
v8: https://ci.nodejs.org/job/node-test-commit-v8-linux/3232/ ✅

@bcoe bcoe added fast-track PRs that do not need to wait for 72 hours to land. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Jul 9, 2020
@bcoe
Copy link
Contributor Author

bcoe commented Jul 9, 2020

@devsnek @Trott should I be concerned about these GitHub action flakes I'm seeing? they appear to be unrelated.

@devsnek
Copy link
Member

devsnek commented Jul 9, 2020

@bcoe that's pretty normal. as long as our jenkins ci passes you're fine.

@bcoe
Copy link
Contributor Author

bcoe commented Jul 9, 2020

@bcoe that's pretty normal. as long as our jenkins ci passes you're fine.

@devsnek the OSS project I've been working on this summer to track flaky tests is coming along really well 😄 I can't wait to plug this dashboard into Node.

@bcoe
Copy link
Contributor Author

bcoe commented Jul 9, 2020

requesting we fast track this change, assuming v8 tests pass.

CC: @devsnek, @gengjiawen, @jasnell

bcoe pushed a commit that referenced this pull request Jul 9, 2020
deps: V8: backport 2d5017a0fc02
1198aeb 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

PR-URL: #34272
Refs: bcoe/c8#229
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Gus Caplan <[email protected]>
@bcoe
Copy link
Contributor Author

bcoe commented Jul 9, 2020

Landed in 1198aeb

@bcoe bcoe closed this Jul 9, 2020
targos pushed a commit to targos/node that referenced this pull request Jul 13, 2020
@targos
deps: V8: backport 2d5017a0fc02
b5fee75 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

PR-URL: nodejs#34272
Refs: bcoe/c8#229
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Gus Caplan <[email protected]>
targos pushed a commit that referenced this pull request Jul 13, 2020
@targos
deps: V8: backport 2d5017a0fc02
61c618d 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

PR-URL: #34272
Refs: bcoe/c8#229
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Gus Caplan <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jul 14, 2020
Closed
@MylesBorins
Copy link
Contributor

MylesBorins commented Jul 14, 2020

This doesn't make any changes to the version of V8 currently on 14.x, my guess is that this applies to 8.4. should likely be backported with #34356

@targos
Copy link
Member

targos commented Jul 14, 2020

This change is already included in #34356

MylesBorins pushed a commit that referenced this pull request Jul 14, 2020
@MylesBorins
deps: V8: backport 2d5017a0fc02
8eecac5 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

PR-URL: #34272
Refs: bcoe/c8#229
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Gus Caplan <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jul 14, 2020
Merged
MylesBorins pushed a commit that referenced this pull request Jul 16, 2020
@MylesBorins
deps: V8: backport 2d5017a0fc02
601ed8e 
Original commit message:

    [coverage] remove the last continuation range before synthetic return

    Rather than only removing the continuation range for the last return
    statement prior to a synthetic return statement, remove the
    continuation tracking for whatever statement occurs prior to the
    synthetic return.

    Bug: v8:10628
    Change-Id: Ieb8e393479c9811cf1b9756840bbfdbe7f44a1b8
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2280585
    Commit-Queue: Benjamin Coe <[email protected]>
    Reviewed-by: Toon Verwaest <[email protected]>
    Reviewed-by: Jakob Gruber <[email protected]>
    Reviewed-by: Sigurd Schneider <[email protected]>
    Cr-Commit-Position: refs/heads/master@{#68719}

Refs: v8/v8@2d5017a

PR-URL: #34272
Refs: bcoe/c8#229
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Gus Caplan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jasnell jasnell jasnell approved these changes

@gengjiawen gengjiawen gengjiawen approved these changes

@Trott Trott Awaiting requested review from Trott

+1 more reviewer

@devsnek devsnek devsnek approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. build Issues and PRs related to build files or the CI. fast-track PRs that do not need to wait for 72 hours to land. v8 engine Issues and PRs related to the V8 dependency.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

9 participants

@bcoe @Trott @nodejs-github-bot @devsnek @MylesBorins @targos @jasnell @gengjiawen @codebytere

Comments