Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • juerg/cache-query-job-benchmark
  • bst-1 protected
  • juerg/cache-query-job
  • tristan/fix-recursive-artifact-pull
  • nanonyme/remove-fix-python-timestamps
  • tristan/shell-artifacts
  • bschubert/update-coverage
  • juerg/remote-cache
  • nanonyme/subprocess-devnull
  • tristan/artifact-extensions
  • tpollard/custom-platform-properties
  • juerg/buildbox
  • chandan/update-reqs
  • chandan/moar-runners
  • tpollard/optional-sandbox-properties
  • nanonyme/fix-tests
  • bschubert/standardize-source-tests
  • nanonyme/warn-nofile
  • abderrahim/stage-artifact-scriptelement
  • 1.6.1
  • 1.6.0
  • 1.93.5
  • 1.5.1
  • 1.93.4
  • bst-1.4-branchpoint protected
  • 1.5.0
  • 1.4.3
  • 1.93.3
  • 1.93.2
  • 1.4.2
  • 1.93.1
  • 1.93.0
  • 1.91.3
  • 1.91.2
  • 1.91.1
  • 1.91.0
  • bst-1-branchpoint protected
  • 1.4.1
  • 1.4.0
40 results

buildstream

  • Clone with SSH
  • Clone with HTTPS
  • Chandan Singh's avatar
    Chandan Singh authored
    Starting from `pytest` version 4.1.0, `Node.get_marker()` has been
    removed, and hence our tests break when running with newer versions of
    `pytest`. It was deprecated since a while back but it has recently been
    removed completely. Use `get_closest_marker()` as a replacement that is
    suggested in the changelog, and seems to work fine for our use case.
    
    See https://github.com/pytest-dev/pytest/pull/4564 for more context on
    the upstream issue.
    
    One way of verifying this change is that this should fix the recently
    added `tests-fedora-update-deps` job, that was failing before due to
    this issue.
    
    (cherry picked from commit c91784ab)
    aa983200
    History
    Name Last commit Last update