-
Notifications
You must be signed in to change notification settings - Fork 212
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: optimise integration test #4113
Conversation
9673a4c
to
831d209
Compare
4268eeb
to
15cae21
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well played
77843b7
to
831d209
Compare
Thanks. Unfortunately, the problem appears to be in the length of the Would you please have another look? I don't want to assume you have no comments. :) |
Yes, the SOLO_MAX_DEBUG_LENGTH thing looks good too. I already saw it; I guess I neglected to say so. |
- Update to node 16 and Debian bullseye (with fallback to node 14 for older incompatible SDKs) - Handle some older SDK versions which output lockdown sniffing to stdout instead of stderr - Rewrote the config argv parsing logic, to make it behave slightly more sanely - Fixed some deadlock issues, e.g. adding some timeouts on task ready (see #40) or slog streams not closing properly - Capture client storage and slog file (should help track some transient seg faults in the solo) - Automatically capture the state of the client and chain if an error occurs (see #39) - Background the compression of the state directories after snapshotting them (overlayfs supports CoW). Closes #39 - Avoid resetting the whole `agoric-servers` project in `local-chain` tests. Removes loadgen project `git` dependency. - Elide long lines from the chain or solo output (improves github actions perf, see Agoric/agoric-sdk#4113)
Description
Speed up the integration test CI by not printing out a whole endo bundle (the Github Actions don't handle that very well).
Before
After
Conclusion
48 minutes down to 13 minutes.
Security Considerations
Documentation Considerations
Testing Considerations