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
  • mjsunit
  • regress
  • regress-1172-bis.js
Find file
BlameHistoryPermalink
  • ager@chromium.org's avatar
    Fix a number of tests that incorrectly used assertUnreachable. · a01b45df
    ager@chromium.org authored May 31, 2011
    Our testing infrastructure uses exceptions to indicate
    errors. assertUnreachable therefore throws an exception to indicate
    that it was reached. Therefore, it cannot be used to check that an
    exception was thrown using the pattern:
    
    try {
      shouldThrow();
      assertUnreachable();
    } catch(e) {
    }
    
    Such a test will always pass because assertUnreachable will throw an
    exception if shouldThrow does not.
    
    R=ricow@chromium.org
    
    Review URL: http://codereview.chromium.org/7053035
    
    git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8117 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
    a01b45df
regress-1172-bis.js 1.84 KB
EditWeb IDE

Replace regress-1172-bis.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.