Skip to content
Snippets Groups Projects
  1. Mar 02, 2020
    • Jeremy Bowman's avatar
      Upgrade edx-lint BOM-1298 (#23227) · 45644a35
      Jeremy Bowman authored
      The last time we tried this upgrade we encountered timeouts on the quality job, which it now appears were due to the worker running pylint common running out of memory and killing the Jenkins process. Switching to a different worker type with double the RAM (8 GB vs. 4 GB) seems to have fixed this; about 5.5 GB was used. Upstream is aware of the high memory usage on large projects, it's apparently due primarily to a cache of parsed modules: https://github.com/PyCQA/pylint/issues/1495 .
      
      Even after disabling some of the new checks that have been added, the new version of pylint found about twice as much to complain about. Just bumping the threshold for now to unblock the Django upgrade, we can try automated utilities like pyupgrade to fix some of these later.
  2. Dec 27, 2019
  3. Jun 05, 2019
  4. May 23, 2019
  5. May 19, 2019
  6. Apr 10, 2019
  7. Feb 21, 2019
  8. Feb 20, 2019
  9. Feb 01, 2019
  10. Dec 17, 2018
  11. Dec 01, 2017
  12. Oct 26, 2017
  13. Jan 27, 2016
  14. Dec 22, 2015
  15. Dec 19, 2015
  16. Nov 03, 2015
  17. Oct 21, 2015
  18. Sep 03, 2015
    • Ned Batchelder's avatar
      Update edx-lint to 0.2.6 · f47a53eb
      Ned Batchelder authored
      This gets us checking for tests inheriting from other tests.  When that
      happens, tests get run more than once, which is pointless.  We have a
      few dozen new warnings due to this new check.
      
      This also disables unused-wildcard-import.  That removes a few hundred
      warnings.
      
      Together, this means we can reduce the pylint limit to 5999. :)
      f47a53eb
  19. Jun 02, 2015
  20. Mar 03, 2015
  21. Feb 06, 2015
    • Calen Pennington's avatar
      Add our custom pylint plugin · b93b5417
      Calen Pennington authored
      So far, it checks:
      
      * Whether setUp is called in TestCase setUp methods.
      * If _("translate me") functions are called with only string literals.
      b93b5417
  22. Feb 05, 2015
  23. Feb 04, 2015
  24. Jan 12, 2015
  25. Jan 08, 2015
  26. Dec 13, 2014
  27. Dec 08, 2014
  28. Nov 26, 2014
  29. Nov 06, 2014
  30. Mar 07, 2014
  31. Feb 10, 2014
  32. Jan 15, 2014
  33. Oct 28, 2013
  34. Sep 27, 2013
    • Calen Pennington's avatar
      Make sure that we have the right set of fields available during xml parsing · f500b722
      Calen Pennington authored
      We had a bug where mixins weren't being applied before `load_from_xml`
      was called. This meant that not all of the fields were being loaded
      correctly. To fix it, we used the mixoligist from the runtime to apply
      the mixins earlier in the process. However, that caused the mixins to be
      applied twice.
      
      The included fixes to xblock resolved the multiply-applied mixins, and
      the fixes to the parsing code make it simpler to understand, and add
      some unit tests of the parsing to boot.
      f500b722
  35. Aug 27, 2013
  36. Aug 19, 2013
  37. Jul 31, 2013
  38. Jul 08, 2013