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

CI test flow can't analysis coverage for different packages #844

Open
2 of 4 tasks
tkxkd0159 opened this issue Dec 27, 2022 · 0 comments
Open
2 of 4 tasks

CI test flow can't analysis coverage for different packages #844

tkxkd0159 opened this issue Dec 27, 2022 · 0 comments
Labels
A: bug Something isn't working A: CI priority/backlog Possibly useful, but not yet enough support to actually get it done.

Comments

@tkxkd0159
Copy link
Member

tkxkd0159 commented Dec 27, 2022 •
edited
Loading

Summary of Bug

Currently, we list packages inside the lbm-sdk module through go list ./... and separate them to run each test. In this case, the test coverage analysis is limited to the inside of the package because the go test is run on each package. Therefore, we need a patch to modify it.

Version

Steps to Reproduce

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@tkxkd0159 tkxkd0159 added A: bug Something isn't working A: CI labels Dec 27, 2022
@tkxkd0159 tkxkd0159 mentioned this issue Dec 27, 2022
Merged
5 tasks
@tkxkd0159 tkxkd0159 added the priority/backlog Possibly useful, but not yet enough support to actually get it done. label Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A: bug Something isn't working A: CI priority/backlog Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tkxkd0159