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.

Sign up for GitHub

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

Jump to bottom

Packaging tests should not load full container logs in memory #100220

Open
williamrandolph opened this issue Oct 3, 2023 · 2 comments
Open

Packaging tests should not load full container logs in memory #100220

williamrandolph opened this issue Oct 3, 2023 · 2 comments
Labels
:Core/Infra/Core Core issues without another label :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Core/Infra Meta label for core/infra team Team:Delivery Meta label for Delivery team >test Issues or PRs that are addressing/adding tests

Comments

@williamrandolph
Copy link
Contributor

In #99508, a docker test failed because the container's log output exceeded the limit we set. We've bumped the limit as a short-term fix, but a better fix would be to stream through container logs and avoid gathering all logs in memory.
@williamrandolph williamrandolph added >test Issues or PRs that are addressing/adding tests :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts :Core/Infra/Core Core issues without another label labels Oct 3, 2023
@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team Team:Delivery Meta label for Delivery team labels Oct 3, 2023
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@rjernst rjernst changed the title DockerTests should not load full container logs in memory Packaging tests should not load full container logs in memory Oct 3, 2023
@mark-vieira mark-vieira added the >test-failure Triaged test failures from CI label Oct 9, 2023
@mark-vieira mark-vieira added low-risk An open issue or test failure that is a low risk to future releases and removed blocker >test-failure Triaged test failures from CI low-risk An open issue or test failure that is a low risk to future releases labels Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Core/Infra/Core Core issues without another label :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts Team:Core/Infra Meta label for core/infra team Team:Delivery Meta label for Delivery team >test Issues or PRs that are addressing/adding tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@williamrandolph @mark-vieira @elasticsearchmachine