Skip to content

unstable mock calls between Python versions #21

@ynikitenko

Description

@ynikitenko

It has persisted for a long time that with each new Python version the mock calls were changing (with unessential calls that don't change the final result).
It was suggested to fix it here. That is why I'm copying the code from Lena.

It was recently reported on AUR:

assert mocker_print.mock_calls == [


call.write('In repository myhost'), call.write('\n'),
call.write('No commits found'), call.write('\n')
]
E       AssertionError: assert [call.fileno(...l.write('\n')] == [call.write('...l.write('\n')]
E
E         At index 0 diff: call.fileno() != call.write('In repository myhost')
E         Left contains 388 more items, first extra item: call.fileno()
E         Use -v to get more diff


/home/simona/.cache/yay/yarsync/src/yarsync-0.3/tests/test_status.py:75: AssertionError

Time to finally fix that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions