1. 01 May, 2018 5 commits
  2. 20 Apr, 2018 1 commit
  3. 05 Feb, 2018 1 commit
  4. 19 Dec, 2017 2 commits
  5. 16 Dec, 2017 1 commit
  6. 20 Nov, 2017 1 commit
  7. 13 Nov, 2017 1 commit
  8. 21 Jul, 2017 4 commits
  9. 25 May, 2017 1 commit
  10. 18 May, 2017 1 commit
  11. 19 Jan, 2017 1 commit
  12. 10 Nov, 2016 9 commits
  13. 08 Nov, 2016 1 commit
  14. 04 Nov, 2016 1 commit
  15. 26 Oct, 2016 2 commits
  16. 24 Oct, 2016 2 commits
    • Dylan Baker's avatar
      framework/backends/json: Don't convert to TestrunResult while updating · 12012814
      Dylan Baker authored
      This changes the way updates are done in the backend, instead of
      converting to a TestrunResult immediately, all of the transformations
      are done to the JSON data in it's rawest form, ie, as dicts and lists,
      and then transform to a TestrunResult (and children) after that.
      
      This makes the loading code more robust and simpler, since it's
      decoupled from the representation, making the transformations easier to
      test and manage.
      
      Part of this change is fixing the .to_json and .from_dict methods, many
      of which "worked" because their shortcomings were papered over by using
      json.load with a custom decoder. This patch fixes them to actually work
      correctly. Despite my best attempts I couldn't decouple this work for
      this patch because of the close coupling of the JSON loading code and
      the class representations.
      
      There are a number of fixups to the tests in this patch, since a number
      of issues were being covered by the TestrunResult.to_json() method
      filling it missing values.
      Signed-off-by: 's avatarDylan Baker <dylanx.c.baker@intel.com>
      12012814
    • Dylan Baker's avatar
      framework: Drop support for JSON formats < 7 · ef57fdd7
      Dylan Baker authored
      Most of these are pretty old at this point (over a year), and it seems
      unlikely anyone still has results in those formats. The biggest problem
      with them is that some of them (especially the early ones) are complex
      transformations with a lot of validation needed, and some of the middle
      ones rely on the class representations to do the transformations, which
      is what this series is trying to change, since the tight coupling makes
      changes to the schema difficult, or nearly impossible in other cases.
      
      If there is compelling reason I could push support back a bit more, but
      I really want to drop some of the versions we support since it
      simplifies the code considerably.
      
      This also drops support for the older "main" file, and only supports
      results.json and results.json.<compression>
      Signed-off-by: 's avatarDylan Baker <dylanx.c.baker@intel.com>
      ef57fdd7
  17. 07 Oct, 2016 4 commits
  18. 05 Oct, 2016 1 commit
  19. 16 Sep, 2016 1 commit