[issue44288] unittest: _is_relevant_tb_level() fails because tb.tb_frame.f_globals=None

STINNER Victor added the comment: I mark this issue as a duplicate of bpo-2. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Globals (and presumably builtins) are cleared premuturely in FrameObject ___

[issue44288] unittest: _is_relevant_tb_level() fails because tb.tb_frame.f_globals=None

STINNER Victor added the comment: Is it possible that bpo-2 is a duplicate of this issue? Is it already fixed by GH-26768, commit ba2f32a983a08c4f64c23c187432e38908639c12? -- ___ Python tracker

[issue44288] unittest: _is_relevant_tb_level() fails because tb.tb_frame.f_globals=None

STINNER Victor added the comment: Oops, I wanted to ping Mark Shannon, not Mark Dickinson. -- nosy: +Mark.Shannon -mark.dickinson ___ Python tracker ___

[issue44288] unittest: _is_relevant_tb_level() fails because tb.tb_frame.f_globals=None

New submission from STINNER Victor : Sometimes, when a test fails in the main branch, unittest fails with the following error: ... File "C:\vstinner\python\main\lib\unittest\result.py", line 205, in _is_relevant_tb_level return '__unittest' in tb.tb_frame.f_globals TypeError: argument