Skip to content
  1. Jun 06, 2013
  2. Jun 05, 2013
  3. May 29, 2013
  4. May 17, 2013
    • Ashok Thirumurthi's avatar
      Fix xpasses on the gcc buildbots using compiler versions to qualify the xfail. · c97a6083
      Ashok Thirumurthi authored
      - Note that this is not correct, as the failure is associated with build options of libc.so, however it's failing on a Debian buildbot that uses gcc 4.6.2 (and the real goal is a complete backtrace even with -fomit-frame-pointer).
      
      - Adds helpers to lldbtest.py to check the expectedCompiler and expectedVersion, with an eventual goal of reducing the number of test decorators.
      --- Currently allows a comparison operator and a compiler version to be specified.
      --- Can be extended to support ranges of compiler versions.
      
      llvm-svn: 182155
      c97a6083
    • Ashok Thirumurthi's avatar
      Adds a test case for bugzilla #15671 patterned after TestInferiorCrashing.py. · b4e5134f
      Ashok Thirumurthi authored
      - On Linux, the partial back-trace after an assert can cause the basic test to fail as discussed on lldb-dev.
      - Uses SBFrame to walk up the stack to the assert site and tests expression evaluation of locals, globals and arguments.
      
      Thanks to Daniel for review and testing on OS/X.
      
      llvm-svn: 182115
      b4e5134f
  5. May 15, 2013
  6. May 14, 2013
  7. May 07, 2013
  8. May 06, 2013
  9. May 02, 2013
  10. Mar 15, 2013
    • Matt Kopec's avatar
      Add icc support to the test suite · 0de53f06
      Matt Kopec authored
      -adds icc to the lit of compilers to run the tests
      -adds icc test decorators
      -skip TestAnonymous.py for icc
      
      Patch by Ashok Thirumurthi.
      
      llvm-svn: 177174
      0de53f06
  11. Mar 06, 2013
  12. Feb 28, 2013
  13. Feb 27, 2013
  14. Feb 23, 2013
  15. Feb 22, 2013
  16. Feb 19, 2013
    • Daniel Malea's avatar
      Minor test runner improvemenst · 249287af
      Daniel Malea authored
      - rework the way SBDebugger.SetAsync() is used to avoid side effects (reset original value at TearDownHook)
      - refactor expectedFailureClang (and add expectedFailureGcc decorator)
      - mark TestChangeValueAPI.py as expectedFailureGcc due to PR-15039
      
      llvm-svn: 175523
      249287af
  17. Feb 15, 2013
  18. Jan 25, 2013
  19. Nov 27, 2012
  20. Nov 26, 2012
    • Daniel Malea's avatar
      Fix for TestSharedLib.py (on Linux) · 179ff298
      Daniel Malea authored
      - use lldb 'settings' command to help testcase find shared library
      - pull up dyldPath variable from TestLoadUnload.py to fixture base class (applicable in multiple cases)
      
      llvm-svn: 168612
      179ff298
  21. Nov 23, 2012
    • Daniel Malea's avatar
      Update test status on Linux · 93aec0f9
      Daniel Malea authored
      - add decorators @expectedFailLinux and @skipOnLinux
      - skip/mark xfail cases due to open bugzillas # 14323, 14416, 14423, 14424, 14425, 14426
      
      Patch by Ashok Thirumurthi!
      
      llvm-svn: 168529
      93aec0f9
  22. Oct 24, 2012
  23. Oct 23, 2012
  24. Oct 16, 2012
  25. Sep 22, 2012
  26. Sep 21, 2012
    • Enrico Granata's avatar
      Initial commit of a new testsuite feature: test categories. · 165f8af8
      Enrico Granata authored
      This feature allows us to group test cases into logical groups (categories), and to only run a subset of test cases based on these categories.
      
      Each test-case can have a new method getCategories(self): which returns a list of strings that are the categories to which the test case belongs.
      If a test-case does not provide its own categories, we will look for categories in the class that contains the test case.
      If that fails too, the default implementation looks for a .category file, which contains a comma separated list of strings.
      The test suite will recurse look for .categories up until the top level directory (which we guarantee will have an empty .category file).
      
      The driver dotest.py has a new --category <foo> option, which can be repeated, and specifies which categories of tests you want to run.
      (example: ./dotest.py --category objc --category expression)
      
      All tests that do not belong to any specified category will be skipped. Other filtering options still exist and should not interfere with category filtering.
      A few tests have been categorized. Feel free to categorize others, and to suggest new categories that we could want to use.
      
      All categories need to be validly defined in dotest.py, or the test suite will refuse to run when you use them as arguments to --category.
      
      In the end, failures will be reported on a per-category basis, as well as in the usual format.
      
      This is the very first stage of this feature. Feel free to chime in with ideas for improvements!
      
      llvm-svn: 164403
      165f8af8
  27. Aug 01, 2012
  28. Jun 20, 2012
  29. May 16, 2012
  30. Apr 19, 2012
Loading