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

snapshots and logs are too large #339

Open
KaiyiLiu1234 opened this issue Nov 19, 2024 · 4 comments
Open

snapshots and logs are too large #339

KaiyiLiu1234 opened this issue Nov 19, 2024 · 4 comments
Assignees

Comments

@KaiyiLiu1234
Copy link
Collaborator

Snapshots and logs are too large to upload to metal ci repo. We should compress them prior to upload.

@KaiyiLiu1234 KaiyiLiu1234 self-assigned this Nov 19, 2024
@SamYuan1990
Copy link
Collaborator

are those log snapshots and logs are necessary, is there any parts we can ignore or just need for debug usage?
so that we can reduce the size of log and snapshots?

@rootfs
Copy link
Contributor

rootfs commented Nov 20, 2024

per meeting 11/19: use github artifact to store the prometheus database snapshot, instead of merging to the repo. The artifact limit is 2GB

@SamYuan1990
Copy link
Collaborator

it seems folder with path docs/validation/* takes about 8MB for each day, and same for other path as daily-validation, etc. or as an estimate, we need 10MB for a single round of validation, we can have 200 sample keep on github artifact.
Took a month for 30 day, about 6 sample per day.

@rootfs, @KaiyiLiu1234, let's figure out a mapping, as
folder, github action file, and naming conventions on artifact to make this issue more specific.
and in which case, we need keep the result as a github commit and push back to the repo?

@SamYuan1990
Copy link
Collaborator

.github/workflows/equinix_metal_model_server_action_flow.yml
.github/workflows/equinix_metal_flow.yml
.github/workflows/validator_compose.yml
util/validation_regression_check.py

and markdown files may impact.

SamYuan1990 added a commit that referenced this issue Nov 20, 2024
SamYuan1990 added a commit that referenced this issue Nov 22, 2024
[CI]: using artifacts to keep result, a part of #339
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants