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.

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

ci: run nightly CI with logs #259

Closed
ClementWalter opened this issue Dec 12, 2024 · 1 comment · Fixed by #262
Closed

ci: run nightly CI with logs #259

ClementWalter opened this issue Dec 12, 2024 · 1 comment · Fixed by #262
Assignees

Comments

@ClementWalter
Copy link
Member

Why

When the nightly CI fails, there is no log to actually reproduce the failing example, see for example
https://github.com/kkrt-labs/keth/actions/runs/12287505621/job/34289650881

What

Change the log level to debug

How

Run pytest with -s --hypothesis-verbosity=debug

@ClementWalter ClementWalter added this to the EELS migration milestone Dec 12, 2024
@ClementWalter ClementWalter moved this to Todo in Keth Dec 12, 2024
@obatirou obatirou moved this from Todo to In progress in Keth Dec 12, 2024
@obatirou
Copy link
Contributor

obatirou commented Dec 12, 2024

Seems related to too much log pytest-dev/pytest-xdist#1138
Passing --hypothesis-verbosity=debug will only increase it and it is not manageable (in local for a few tests, this is illisible).

Reproducing the 1500 runs in local shows that the function load_packed_bytes that cause the exeception is using a lot of memory (20go in under 2min) not sure why.
Maybe because there was a pack_calldata call function on possibly enormous input and hypothesis cache the data?

Anyway, load_packed_bytes is not relevant in Keth as it was part of the account of Kakarot.
Will remove this function.

@github-project-automation github-project-automation bot moved this from In progress to Done in Keth Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants