[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Change by Irit Katriel : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.11 -Python 3.8 ___ Python tracker ___ _

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Irit Katriel added the comment: New changeset f3ea249569bbce8417c55d421521bb672c202552 by Irit Katriel in branch '3.9': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688) (GH-31776) https://github.com/python/cpython/commit/f3ea2495

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

miss-islington added the comment: New changeset 26fa25a9a73f0e31bf0f0d94103fa4de38c0a3cc by Miss Islington (bot) in branch '3.10': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688) https://github.com/python/cpython/commit/26fa25a9

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Change by Irit Katriel : -- pull_requests: +29883 pull_request: https://github.com/python/cpython/pull/31776 ___ Python tracker ___

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Irit Katriel added the comment: New changeset 88b7d86a73da9388aa65c96401c2984c8c16f8db by Irit Katriel in branch 'main': bpo-24959: fix unittest.assertRaises bug where traceback entries are dropped from chained exceptions (GH-23688) https://github.com/python/cpython/commit/88b7d86a73da9388aa

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Change by miss-islington : -- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +29882 pull_request: https://github.com/python/cpython/pull/31775 ___ Python tracker _

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Change by David Mandelberg : -- nosy: +dseomn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Change by Irit Katriel : -- keywords: +patch pull_requests: +24039 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/23688 ___ Python tracker

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Irit Katriel added the comment: I think this is the same as issue42247, where I've recently attached a patch that removes __unittest frames from the traceback rather than count them and then set a limit for printing. I could add to that patch what Robert suggests here - to filter the __caus

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Aaron Sokoloski added the comment: I've run into this bug too. Took a while to track down the cause :) -- nosy: +Aaron Sokoloski ___ Python tracker ___ _

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Changes by Robert Collins : -- stage: needs patch -> test needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Robert Collins added the comment: Yes, it is... ish. The frame skipping code occurs when we serialise exceptions, and we pass a limit in. The limit is calculated on the main exception only. If the cause has a longer exception than the limit we calculated, you'd see this behaviour. Probably ne

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Chris Jerdonek added the comment: This is simply a reduced test case to illustrate the issue more clearly. There was more to it in how I was using it in practice. -- ___ Python tracker

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Robert Collins added the comment: Hmm, this is a little surprising, but - why are you raising AssertionError like that - thats what assertRaises is for. -- stage: -> needs patch ___ Python tracker ___

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Changes by Ezio Melotti : -- nosy: +ezio.melotti, michael.foord, rbcollins versions: +Python 3.5, Python 3.6 -Python 3.4 ___ Python tracker ___ __

[issue24959] unittest swallows part of stack trace when raising AssertionError in a TestCase

Chris Jerdonek added the comment: I guess this isn't limited just to the "raise from" syntax. It also occurs if "from exc" is removed from the example above. -- title: unittest swallows part of stack trace using "raise from" with AssertionError -> unittest swallows part of stack trace