Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Wrongful re-compilation and inconsistent caching behaviors #47

Open
0xSidius opened this issue Jun 30, 2022 · 4 comments
Open

Wrongful re-compilation and inconsistent caching behaviors #47

0xSidius opened this issue Jun 30, 2022 · 4 comments
Labels

Comments

@0xSidius
Copy link

Ape will not always see contracts that need re-compilation upon changes, this was noticed both in standalone compilation mode (single command) and also as part of ape-starknet flow for running tests, furthermore, during the latter Ape will output that relevant contracts are being re-compiled however test behavior remains unchanged until the .pytest_cache folder is deleted (signaling that Ape either A) did not correctly re-compile all contracts that needed to B) is still loading the old artifacts for running the test)

@ca11ab1e
Copy link
Contributor

FTR I also reported several issues related to contracts (re)compilation here: ApeWorX/ape#822.

@antazoey
Copy link
Member

How are you compiling + making changes the source code? Are the sources being changed mid test?

@0xLaplace
Copy link

How are you compiling + making changes the source code? Are the sources being changed mid test?

nope, no changes during test run ofc

as for compilation 👇
image

@0xSidius 0xSidius changed the title Wrongful re-compilation and inconsistent pytest caching behaviors Wrongful re-compilation and inconsistent caching behaviors Jul 15, 2022
@antazoey
Copy link
Member

antazoey commented Aug 9, 2022

if there is any easy way to help reproduce this, it would be much appreciated!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants