bloomberg/pytest-memray

Issues

• It would be nice to have a `json` output option so one could use this to track memory consumption over time via github-action-benchmark

  #126 opened 15 days ago by mmcdermott
  0

• pytest-memray breaks anyio

  #119 opened 2 months ago by godlygeek
  6

• option to count only memory used in current thread / limit_memory("10MB", current_thread_only=True),

  #111 opened 5 months ago by ecerulm
  2

• Cannot get report for all tests

  #46 opened 5 months ago by deepix
  3

• Documentation is slightly ambiguous about meaning of @pytest.mark.limit_memory()

  #115 opened 6 months ago by itamarst
  2

• Running pytest with --most-allocations throws an ZeroDivisionError: float divmod()

  #93 opened 7 months ago by juliannguyen4
  0

• Exception thrown while trying to calculate ``math.log(0)``

  #102 opened 7 months ago by gnufede
  1

• A CLI interface for looping over test body

  #104 opened 7 months ago by ckutlu
  2

• Getting different results for @pytest.mark.limit_memory on macOS

  #109 opened 7 months ago by ecerulm
  5

• Generate single output for all test cases

  #98 opened a year ago by jay0129
  6

• compare memory usage between pytest runs

  #7 opened a year ago by djarecka
  2

• <root> shows high memory usage, but the flamegraph shows just a little portion of it

  #97 opened a year ago by rdbisme
  1

• Marker for fail a leaking test

  #45 opened a year ago by tonybaloney
  6

• Support --follow-fork

  #89 opened a year ago by luochen1990
  1

• Test with the oldest version of pytest and Memray we support in CI

  #80 opened a year ago by godlygeek
  12

• Add new options to the docs

  #64 opened a year ago by pablogsal
  0

• Support flag `--trace-python-allocators` when running the memray pytest plugin

  #78 opened a year ago by godiedelrio
  2

• Add support for unittests (via pytest)

  #6 opened a year ago by ChaoticRoman
  8

• Clarify that the reported allocations are at the high water mark

  #8 opened a year ago by godlygeek
  1

• Long test names can be problematic

  #68 opened a year ago by pablogsal
  9

• Disable the caplog fixture by default

  #29 opened 2 years ago by gaborbernat
  0

• limit_memory for parametrized tests

  #33 opened 2 years ago by gaborbernat
  3

• Changelog links lead to 404

  #66 opened 2 years ago by pquentin
  1

• `pytest-memray` raises `pytest.PytestReturnNotNoneWarning` warnings

  #60 opened 2 years ago by WilliamJamieson
  4

• Enable @pytest.mark.limit_memory without having to specify --memray

  #49 opened 2 years ago by pquentin
  2

• incompatible with flaky (as used in urllib3)

  #53 opened 2 years ago by graingert
  3

• Empty report when running with pytest-xdist

  #2 opened 2 years ago by orsinium
  6

• Enable more reporters as pytest options

  #39 opened 2 years ago by thomasfinstad
  1

• Allow specifying the run id via CLI (and print it in report)

  #28 opened 2 years ago by gaborbernat
  0

• Documentation and pypi landing page states incorrect minimal Python version

  #27 opened 2 years ago by ChaoticRoman
  1

• Ability to persist the binary dump post test run

  #10 opened 2 years ago by gaborbernat
  0

• Release wheel file

  #9 opened 2 years ago by gaborbernat
  3

• --memray causes built-in junit-xml results writer to fail

  #3 opened 2 years ago by petr-tik
  8