Skip to content

Conversation

@paulhauner
Copy link
Member

Issue Addressed

#2768 (comment)

Proposed Changes

Minimise memory usage in the max transaction size test. I couldn't get it any lower than 3GB (see the comments). If it still fails we can delete the test entirely (or question the rationale of having a 1GB transaction limit..).

Additional Info

This follows from #2800.

@paulhauner
Copy link
Member Author

This still fails CI :( I'm going to just remove the tests. I think that's quite reasonable, I am comfortable that ssz_types length checking is well tested enough elsewhere.

@paulhauner paulhauner changed the title Allocate less memory (3GB) in engine tests (v2) Allocate less memory in engine tests (v2) Nov 15, 2021
@paulhauner paulhauner changed the title Allocate less memory in engine tests (v2) Skip memory intensive engine test (v2) Nov 15, 2021
@paulhauner paulhauner changed the title Skip memory intensive engine test (v2) Skip memory intensive engine test Nov 15, 2021
@paulhauner paulhauner merged commit 2bd4cf6 into sigp:kintsugi Nov 15, 2021
@paulhauner paulhauner mentioned this pull request Nov 15, 2021
paulhauner added a commit that referenced this pull request Nov 28, 2021
* Allocate less memory (3GB) in engine tests

* Run cargo format

* Remove tx too large test

Co-authored-by: Michael Sproul <[email protected]>
paulhauner added a commit that referenced this pull request Nov 28, 2021
* Allocate less memory (3GB) in engine tests

* Run cargo format

* Remove tx too large test

Co-authored-by: Michael Sproul <[email protected]>
paulhauner added a commit that referenced this pull request Dec 2, 2021
* Allocate less memory (3GB) in engine tests

* Run cargo format

* Remove tx too large test

Co-authored-by: Michael Sproul <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants