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

Detect patterns in log files #10914

Closed
omkar-yb opened this issue Dec 20, 2021 · 0 comments
Closed

Detect patterns in log files #10914

omkar-yb opened this issue Dec 20, 2021 · 0 comments
Assignees
@omkar-yb

Comments

@omkar-yb
Copy link
Contributor

Detect patterns in log files and add fail tags when writing out the test_report.json.
@omkar-yb omkar-yb self-assigned this Dec 20, 2021
omkar-yb added a commit that referenced this issue Jan 24, 2022
@omkar-yb
[#10914] Detect and tag failure patterns in test log files
c38761b 
Summary: Detect patterns in log files in a way inspired by the existing function did_test_succeed (which is currently used only for C++ tests). Add "failure tags" in the test report JSON files.

Test Plan:
Jenkins: build platform: centos7, build type: debug
- Ran some unit tests manually and check the output of postprocess_test_result.py manually.
- Added unit tests for set_fail_tag()
- Looking for suggestions on testing with logs from failed tests.

Reviewers: jharveysmith, steve.varnau, mbautin

Reviewed By: mbautin

Subscribers: bogdan, devops

Differential Revision: https://phabricator.dev.yugabyte.com/D14216
omkar-yb added a commit that referenced this issue Jan 25, 2022
@omkar-yb
[#10914] Fix typo in set_fail_tags
434b29f 
Summary: The condition that checked for 'num_failures' was incorrect.

Test Plan: Jenkins: build platform: centos7, build type: debug

Reviewers: steve.varnau, mbautin, jharveysmith

Reviewed By: jharveysmith

Subscribers: devops

Differential Revision: https://phabricator.dev.yugabyte.com/D15011
omkar-yb added a commit that referenced this issue Feb 11, 2022
@omkar-yb
[#10914] Logs: de-duplicate fail tags
41117a3 
Summary:
When grep-ing for a signal, there can be multiple matches.
Filter stdout to get unique, non-empty matches and append a tag for each.

Test Plan:
- Run unit tests with `( . build/venv/bin/activate; export PYTHONPATH=python; ./yb_build.sh --python-tests )`
- Run a test-suite on a local Spark cluster
Jenkins: build platform: centos7, build type: debug

Reviewers: jharveysmith, steve.varnau, mbautin

Reviewed By: mbautin

Subscribers: devops

Differential Revision: https://phabricator.dev.yugabyte.com/D15069
jayant07-yb pushed a commit to jayant07-yb/yugabyte-db that referenced this issue Mar 8, 2022
@omkar-yb
[yugabyte#10914] Logs: de-duplicate fail tags
364bad1 
Summary:
When grep-ing for a signal, there can be multiple matches.
Filter stdout to get unique, non-empty matches and append a tag for each.

Test Plan:
- Run unit tests with `( . build/venv/bin/activate; export PYTHONPATH=python; ./yb_build.sh --python-tests )`
- Run a test-suite on a local Spark cluster
Jenkins: build platform: centos7, build type: debug

Reviewers: jharveysmith, steve.varnau, mbautin

Reviewed By: mbautin

Subscribers: devops

Differential Revision: https://phabricator.dev.yugabyte.com/D15069
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@omkar-yb omkar-yb

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@omkar-yb