1. 07 Jul, 2017 1 commit
  2. 23 Jun, 2017 1 commit
    • jgruber's avatar
      [coverage] Expose block coverage through inspector · 1541f422
      jgruber authored
      This piggy-backs on top of existing precise and best-effort coverage to expose
      block coverage through the inspector protocol.
      
      Coverage collection now implicitly reports block-granularity coverage when
      available.  A new 'isBlockCoverage' property on Inspector's FunctionCoverage
      type specifies the granularity of reported coverage.
      
      For now, only count-based block coverage is supported, but binary block
      coverage should follow soon.
      
      Support is still gated behind the --block-coverage flag.
      
      Bug: v8:6000
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      Change-Id: I9c4d64e1d2a098e66178b3a68dcee800de0081af
      Reviewed-on: https://chromium-review.googlesource.com/532975
      Commit-Queue: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: 's avatarAleksey Kozyatinskiy <kozyatinskiy@chromium.org>
      Reviewed-by: 's avatarDmitry Gozman <dgozman@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46157}
      1541f422
  3. 30 May, 2017 1 commit
  4. 23 Mar, 2017 1 commit
    • yangguo's avatar
      [debug] introduce precise binary code coverage. · d71ef941
      yangguo authored
      With precise binary code coverage, the reported count is either 0 or 1.
      We only report 1 the first time we collect coverage data after the
      function has been executed.
      
      Since we do not care about the accurate execution count, we can optimize
      the function once it has been executed once.
      
      Also change best effort coverage to be implicitly binary.
      
      R=caseq@chromium.org, jgruber@chromium.org, pfeldman@chromium.org
      BUG=v8:5808
      
      Review-Url: https://codereview.chromium.org/2766573003
      Cr-Commit-Position: refs/heads/master@{#44074}
      d71ef941
  5. 21 Mar, 2017 1 commit
  6. 10 Mar, 2017 1 commit
  7. 08 Mar, 2017 1 commit
  8. 25 Feb, 2017 1 commit
  9. 16 Nov, 2016 1 commit
  10. 02 Nov, 2016 1 commit
  11. 26 Sep, 2016 1 commit
  12. 21 Sep, 2016 1 commit
  13. 19 Sep, 2016 1 commit
  14. 15 Sep, 2016 1 commit
  15. 09 Sep, 2016 1 commit
  16. 06 Sep, 2016 1 commit
  17. 01 Sep, 2016 1 commit
  18. 31 Aug, 2016 2 commits