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

Fix coverage report. #35927

Closed
belimawr opened this issue Jun 27, 2023 · 1 comment · Fixed by #36000
Closed

Fix coverage report. #35927

belimawr opened this issue Jun 27, 2023 · 1 comment · Fixed by #36000
Assignees
Labels
bug Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@belimawr
Copy link
Contributor

Currently the coverage reports are not working.
To run unit tests with coverage report for Filebeat:

cd filebeat
TEST_COVERAGE=true mage GoUnitTest

You'll see the following error:

cover: can't read "github.com/elastic/beats/v7/filebeat/input/syslog/rfc3164_parser.rl": open /home/tiago/devel/beats/filebeat/input/syslog/rfc3164_parser.rl: no such file or directory
Error: failed to write HTML code coverage report: running "go tool cover -html=build/TEST-go-unit.cov -o build/TEST-go-unit.html" failed with exit code 1

The problem seems to be caused by some files in the syslog input (like filebeat/input/syslog/rfc3164_parser.go) that contain annotations to some .rl files, those annotations look like this:

//line parser/rfc3164_parser.rl:28

Those files are autogenerated.

@belimawr belimawr added bug Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jun 27, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@cmacknz cmacknz mentioned this issue Jul 24, 2023
1 task
@AndersonQ AndersonQ self-assigned this Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants