Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in / Register
V
V8
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Linshizhi
  • V8
  • Repository

Switch branch/tag
  • v8
  • test
  • message
  • fail
  • async-arrow-invalid-rest.js
Find file
BlameHistoryPermalink
  • Clemens Hammacher's avatar
    Split message tests in failing and non-failing · 913d5ba5
    Clemens Hammacher authored Oct 25, 2017
    This way, we can also check the return code of d8. We currently have a
    bug (6981) which makes failing tests not being detected, even though
    the failure message is (sometimes) being printed.
    After this refactoring, we can write tests for our mjsunit test
    functions.
    
    R=machenbach@chromium.org
    
    Bug: v8:6981
    Change-Id: I0aa0abcb0f9a4f622a1e1d1a4d826da1e6eb4f07
    Reviewed-on: https://chromium-review.googlesource.com/737991Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
    Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#48951}
    913d5ba5
async-arrow-invalid-rest.js 224 Bytes
EditWeb IDE

Replace async-arrow-invalid-rest.js

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.