Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pytest 8.0 keeps returning AttributeError: 'CallSpec2' object has no attribute 'funcargs' #11890

Closed
2 of 4 tasks
vanloc1808 opened this issue Jan 30, 2024 · 3 comments
Closed
2 of 4 tasks

pytest 8.0 keeps returning AttributeError: 'CallSpec2' object has no attribute 'funcargs' #11890

vanloc1808 opened this issue Jan 30, 2024 · 3 comments
Labels
status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity

Comments

@vanloc1808
Copy link

vanloc1808 commented Jan 30, 2024 •
edited
Loading

After upgrading to pytest 8.0, I see a lot of tests failed with the error.
I observe that failed tests happen when there is usage of pytest_lazyfixture with pytest 8.0.0.
image

Operating System: Ubuntu 22.04

  • a detailed description of the bug or problem you are having
  • output of pip list from the virtual environment you are using
  • pytest and operating system versions
  • minimal example if possible
@The-Compiler
Copy link
Member

Please show the actual, full error you get.

@The-Compiler The-Compiler added the status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity label Jan 30, 2024
@vanloc1808
Copy link
Author

vanloc1808 commented Jan 30, 2024 •
edited
Loading

Hi @The-Compiler
Here is the error
image
Due to security policies, I cannot reveal the test here.
But one note, I observed that the error happens when using
pytest_lazyfixture.lazy_fixture
Other tests without lazy_fixture are successful

@The-Compiler
Copy link
Member

As you can see in the stacktrace, this is indeed an issue in pytest_lazyfixture.py and not pytest:

@The-Compiler The-Compiler closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2024
@bpkroth bpkroth mentioned this issue Jan 31, 2024
Merged
motus pushed a commit to microsoft/MLOS that referenced this issue Jan 31, 2024
@bpkroth
Workaround pytest version bump incompatibility with pytest-lazy-fixtu…
5287c24 
…res plugin (#656)

See Also:
- TvoroG/pytest-lazy-fixture#65
- pytest-dev/pytest#11890
@hugovk hugovk mentioned this issue Feb 1, 2024
Closed
@cclauss cclauss mentioned this issue Feb 2, 2024
Merged
ANogin added a commit to ANogin/ofrak that referenced this issue Feb 9, 2024
@ANogin
Require pytest<8.0
67ee05e 
This is needed becase of pytest-dev/pytest#11890
TvoroG/pytest-lazy-fixture#65
@ANogin ANogin mentioned this issue Feb 11, 2024
Merged
1 task
@kiendang kiendang mentioned this issue Feb 12, 2024
Merged
EdwardLarson pushed a commit to redballoonsecurity/ofrak that referenced this issue Feb 12, 2024
@ANogin
Use python3.8 in docker images (#416)
5c1cd3b 
* Use python3.8 in docker images

* Require pytest<8.0

This is needed becase of pytest-dev/pytest#11890
TvoroG/pytest-lazy-fixture#65

* Update changelog

* Revert "Update changelog"

This reverts commit 500ee9b.

Making changes before having coffee :(

* Add a note on recommending Python 3.8

* `ofrak_core` also needs `pytest<8.0`
whyitfor added a commit to redballoonsecurity/ofrak that referenced this issue Feb 22, 2024
@ANogin @Edward-Larson
@rbs-alexr @rbs-jacob @paulnoalhyt @whyitfor
Update to angr==9.2.77 (#417)
8fe5083 
* Use python3.8 in docker images

* Require pytest<8.0

This is needed becase of pytest-dev/pytest#11890
TvoroG/pytest-lazy-fixture#65

* Update changelog

* Revert "Update changelog"

This reverts commit 500ee9b.

Making changes before having coffee :(

* Update to latest angr==9.2.89, which also necessitates Python >= 3.8 and capstone==5.0.0.post1

* Apply Edward's attempted fix to angr test failure

* Add a note on recommending Python 3.8

* Add a note on recommending Python 3.8

* Document the requirement of Python 3.8+

* Switch to angr 9.2.77

* `ofrak_core` also needs `pytest<8.0`

* ignore DataWord in test due to angr bug

* add another now missing block

* black linting

* Attempt to fix a capstone error

* Dropping the .altinstr_replacement section from the toolchain (#414)

* Dropping the .altinstr_replacement section from the toolchain

* Updated CHANGELOG

* Set the fallback font to monospace (#422)

* Set the fallback font to monospace

* Update CHANGELOG

* Display strings with numbers primarily as strings (#423)

* Display strings with numbers primarily as strings

* Update CHANGELOG

* Add typing support to ofrak_ghidra package (#421)

* Add typing to ofrak_ghidra package

* Add changelog

---------

Co-authored-by: Paul Noalhyt <[email protected]>

* Increase time limit on `test_comment_content`

* Fix a spurious "no current event loop" test error

* Explain 3.7 vs 3.8 better in the docs

* Cite specific versions of angr in comment

* Update docs/environment-setup.md

* Update docs/getting-started.md

---------

Co-authored-by: Edward Larson <[email protected]>
Co-authored-by: rbs-alexr <[email protected]>
Co-authored-by: Jacob Strieb <[email protected]>
Co-authored-by: Paul Noalhyt <[email protected]>
Co-authored-by: Paul Noalhyt <[email protected]>
Co-authored-by: Wyatt <[email protected]>
@adraismawur adraismawur mentioned this issue Mar 11, 2024
Closed
3 tasks
roll added a commit to okfn/opendataeditor that referenced this issue Apr 9, 2024
@roll
Rebase on pytest-lazy-fixtures
417b957 
pytest-dev/pytest#11890
pdelboca pushed a commit to okfn/opendataeditor that referenced this issue Apr 11, 2024
@roll
Recover development flow (tests/CI); remove lxml dependency (via `p…
6ec7038 
…yquery`) (#312)

* Removed `pyquery` dependency (depends on `lxml`)

* Group python dependencies by functionaly

* Fixed ruff configuration

astral-sh/ruff#9406

* Rebase on `pytest-lazy-fixtures`

pytest-dev/pytest#11890

* Rename `check` to self-explanatory `type`
ANogin added a commit to ANogin/ofrak that referenced this issue May 30, 2024
@ANogin
Use python3.8 in docker images (redballoonsecurity#416)
76d5942 
* Use python3.8 in docker images

* Require pytest<8.0

This is needed becase of pytest-dev/pytest#11890
TvoroG/pytest-lazy-fixture#65

* Update changelog

* Revert "Update changelog"

This reverts commit 500ee9b.

Making changes before having coffee :(

* Add a note on recommending Python 3.8

* `ofrak_core` also needs `pytest<8.0`
ANogin added a commit to ANogin/ofrak that referenced this issue May 30, 2024
@ANogin @Edward-Larson
@rbs-alexr @rbs-jacob @paulnoalhyt @whyitfor
Update to angr==9.2.77 (redballoonsecurity#417)
b805ac1 
* Use python3.8 in docker images

* Require pytest<8.0

This is needed becase of pytest-dev/pytest#11890
TvoroG/pytest-lazy-fixture#65

* Update changelog

* Revert "Update changelog"

This reverts commit 500ee9b.

Making changes before having coffee :(

* Update to latest angr==9.2.89, which also necessitates Python >= 3.8 and capstone==5.0.0.post1

* Apply Edward's attempted fix to angr test failure

* Add a note on recommending Python 3.8

* Add a note on recommending Python 3.8

* Document the requirement of Python 3.8+

* Switch to angr 9.2.77

* `ofrak_core` also needs `pytest<8.0`

* ignore DataWord in test due to angr bug

* add another now missing block

* black linting

* Attempt to fix a capstone error

* Dropping the .altinstr_replacement section from the toolchain (redballoonsecurity#414)

* Dropping the .altinstr_replacement section from the toolchain

* Updated CHANGELOG

* Set the fallback font to monospace (redballoonsecurity#422)

* Set the fallback font to monospace

* Update CHANGELOG

* Display strings with numbers primarily as strings (redballoonsecurity#423)

* Display strings with numbers primarily as strings

* Update CHANGELOG

* Add typing support to ofrak_ghidra package (redballoonsecurity#421)

* Add typing to ofrak_ghidra package

* Add changelog

---------

Co-authored-by: Paul Noalhyt <[email protected]>

* Increase time limit on `test_comment_content`

* Fix a spurious "no current event loop" test error

* Explain 3.7 vs 3.8 better in the docs

* Cite specific versions of angr in comment

* Update docs/environment-setup.md

* Update docs/getting-started.md

---------

Co-authored-by: Edward Larson <[email protected]>
Co-authored-by: rbs-alexr <[email protected]>
Co-authored-by: Jacob Strieb <[email protected]>
Co-authored-by: Paul Noalhyt <[email protected]>
Co-authored-by: Paul Noalhyt <[email protected]>
Co-authored-by: Wyatt <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@The-Compiler @vanloc1808