Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

GHA build logs have 56K lines of junk #61

Open
2 tasks
ARMmaster17 opened this issue Feb 4, 2022 · 0 comments
Open
2 tasks

GHA build logs have 56K lines of junk #61

ARMmaster17 opened this issue Feb 4, 2022 · 0 comments
Labels
bug Something isn't working DevOps Changes are expected to be made to IaaS manifests or low-level Java configuration bindings.
Milestone

Comments

@ARMmaster17
Copy link
Member

For some reason, Selenium is writing every byte that goes through the sandboxed Chrome instance to the console, which besides being 100% unnecessary, makes it difficult to find log entries that matter. Additionally, most of the Spring startup log entries can be hidden.

  • Remove Selenium log output from GHA logs. Only output should come directly from JUnit test suites.
  • Get rid of some of the startup logging from Spring that we generally don't need.
@ARMmaster17 ARMmaster17 added bug Something isn't working DevOps Changes are expected to be made to IaaS manifests or low-level Java configuration bindings. labels Feb 4, 2022
@ARMmaster17 ARMmaster17 added this to the Sprint 1 milestone Feb 4, 2022
@ARMmaster17 ARMmaster17 moved this to Committed in Kanban Board Feb 4, 2022
@ARMmaster17 ARMmaster17 modified the milestones: Sprint 1, Sprint 2 Feb 15, 2022
@ARMmaster17 ARMmaster17 modified the milestones: Sprint 2, Sprint 3 Mar 14, 2022
@ARMmaster17 ARMmaster17 modified the milestones: Sprint 3, Sprint 4 Apr 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working DevOps Changes are expected to be made to IaaS manifests or low-level Java configuration bindings.
Projects
Status: Committed
Development

No branches or pull requests

1 participant