1. 24 Feb, 2020 1 commit
  2. 13 Feb, 2020 1 commit
    • Tom Rini's avatar
      travis/gitlab/azure: Ensure we use python3 always · 26a426a1
      Tom Rini authored
      
      
      When running our tests there are some cases where as part of the Python
      2.7 to Python 3.6 migration we didn't force Python 3.6 to be used as
      everything wasn't yet migrated.  Now that everything is, make sure to
      tell virtualenv to use python3.  In the case of Travis this is best done
      by making the tools test happen after the main tests so that it will
      already have been run in all cases, TEST_PY_TOOLS is a subset of
      TEST_PY_BD.
      Signed-off-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      26a426a1
  3. 07 Feb, 2020 2 commits
  4. 04 Feb, 2020 1 commit
  5. 20 Jan, 2020 1 commit
  6. 10 Jan, 2020 1 commit
  7. 23 Nov, 2019 1 commit
  8. 07 Nov, 2019 1 commit
  9. 01 Nov, 2019 1 commit
  10. 31 Oct, 2019 1 commit
  11. 29 Oct, 2019 1 commit
    • Bin Meng's avatar
      Bring all testings in gitlab and travis CI to Azure Pipelines · bf275222
      Bin Meng authored and Tom Rini's avatar Tom Rini committed
      
      
      This expands current Azure Pipelines Windows host tools build
      testing to cover all the CI testing in gitlab and travis CI.
      
      Note for some unknown reason, the 'container' cannot be used for
      any jobs that have buildman, for buildman does not exit properly
      and hangs the job forever. As a workaround, we manually call
      docker to run the image to perform the CI tasks.
      
      A complete run on Azure Pipelines takes about 2 hours and 10
      minutes.
      Signed-off-by: Bin Meng's avatarBin Meng <bmeng.cn@gmail.com>
      bf275222
  12. 28 Oct, 2019 1 commit