1. 04 Jul, 2021 1 commit
  2. 10 Apr, 2021 1 commit
  3. 10 Mar, 2021 3 commits
  4. 08 Mar, 2021 6 commits
  5. 07 Mar, 2021 5 commits
  6. 02 Mar, 2021 1 commit
  7. 01 Mar, 2021 6 commits
  8. 28 Feb, 2021 5 commits
    • Michael Pyne's avatar
      module: Move phase init into Module to ensure consistency in effect. · 13720f7e
      Michael Pyne authored
      Although the test suite now passes, manually running kdesrc-build -p
      on my local install was showing that some modules were still being
      pulled into the test phase when run-tests was disabled.
      
      Poking into that showed that this is mostly because I had re-introduced
      some alternate ways of managing Module lifetime and phase setup despite
      trying to centralize this into ModuleResolver.
      
      So move the phase init code into ksb::Module where it belongs, and
      ensure that the phase init is actually run through all the paths where a
      ksb::Module can be created, once the options have been loaded.
      
      Modules derived from ksb::ModuleSet are already handled with
      ksb::ModuleSet::_initializeNewModule. The only other spot to create a
      bare ksb::Module is in the rc-file reading code, so a call was added
      there. Finally, ksb::BuildContext is itself a pseudo ksb::Module, but we
      already had a function call that we could adapt to that task once the
      options have been loaded.
      13720f7e
    • Michael Pyne's avatar
    • Michael Pyne's avatar
      test: Refuse metadata download under test. · 357b8f8a
      Michael Pyne authored
      This permits us to expand the build-environment test a bit farther
      (generating a workload object from modulesFromSelectors, which will pull
      down the KDE project metadata which has overrides for even pretend mode)
      
      And *this* brings us down to one TODO test from three.
      357b8f8a
    • Michael Pyne's avatar
    • Michael Pyne's avatar
      test: Ensure unexpectedly passing TODO tests are not marked TODO. · ad2064ee
      Michael Pyne authored
      There are some specific tests known to fail, called from a loop. For
      simplicity I had only used a single TODO handler in the loop but this
      had the effect of masking potential failures from tests which have
      always passed. Make the test suite a bit more strict by removing the
      TODO marker from these.
      ad2064ee
  9. 24 Feb, 2021 2 commits
  10. 23 Feb, 2021 1 commit
  11. 18 Feb, 2021 1 commit
  12. 17 Feb, 2021 2 commits
  13. 16 Feb, 2021 3 commits
  14. 15 Feb, 2021 3 commits