-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A0-3499: Archive logs in case of e2e failure (#1492)
# Description * Enable RUST_LOG=debug in e2e. * dump all logs from docker-compose and archive them in a tarball, but only for failed e2e * Upload this tarball to GH artifacts Considerations: Log growth is around 200 MB per node per 1 hour so given that some nightly tests run 1 hour and there are max 10 nodes, we have 2GB per test, which is affordable as GH runners have a quota of 14 GB, and our self-hosted runners have at least that much. Also, compressed logs should be around 100 MBs max, so for the case of GH artifacts quota, we should be good. For public repos, we don’t pay anything for this quota anyway. There's some trickery when calling e2e client docker, as there's no way to enforce timeout on step level in GH composite actions, so I needed to do a workaround to apply custom timeout mechanism when calling e2e client in docker. ## Type of change Please delete options that are not relevant. - New feature (non-breaking change which adds functionality) ## Testing * success case - no logs uploaded https://github.com/Cardinal-Cryptography/aleph-node/actions/runs/6889159800/job/18740144103 * a genuine timeouts in one e2e tests https://github.com/Cardinal-Cryptography/aleph-node/actions/runs/6904198011 .See that at the bottom there's tgz attached from failed e2e case
- Loading branch information
1 parent
fdcc4f8
commit 94b811e
Showing
6 changed files
with
89 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.