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
LPS-138663 Delete reads metrics for documents #2183
Conversation
To conserve resources, the PR Tester does not automatically run for every pull. If your code changes were already tested in another pull, reference that pull in this pull so the test results can be analyzed. If your pull was never tested, comment "ci:test" to run the PR Tester for this pull. |
ci:test:sf |
ci:test:relevant |
Hey @CarlosBrichete !! Could you tests if with the changes in this PR https://issues.liferay.com/browse/LPS-138663 is no longer reproducible? Thanks!!! |
✔️ ci:test:sf - 1 out of 1 jobs passed in 2 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-138663 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#120 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-tango#2183 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#416 |
✔️ ci:test:stable - 21 out of 25 jobs passed✔️ ci:test:relevant - 24 out of 28 jobs passed in 1 hour 29 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: 92c72dd04b76a0c36f8ad77efeaf18728ebdf1c6 ci:test:stable - 21 out of 25 jobs PASSED4 Failed Jobs:
21 Successful Jobs:
ci:test:relevant - 23 out of 28 jobs PASSED5 Failed Jobs:
23 Successful Jobs:
For more details click here.This pull contains no unique failures.Failures in common with acceptance upstream results at 92c72dd:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#183 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-tango#2183 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - liferay-tango > liferay-tango - PR#2183 - 2022-02-07[01:35:54] Testray Importer:publish-testray-report#418 |
LGTM |
LGTM 👍 |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites: |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#113135 |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPS-138663 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#3518 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-tango#2183 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#2124 |
✔️ ci:test:stable - 22 out of 25 jobs passed✔️ ci:test:relevant - 25 out of 28 jobs passed in 1 hour 59 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: 76e0dd421b1d463a7563b2fc53f2cae786d7701f ci:test:stable - 22 out of 25 jobs PASSED3 Failed Jobs:22 Successful Jobs:
ci:test:relevant - 24 out of 28 jobs PASSED4 Failed Jobs:24 Successful Jobs:
For more details click here.This pull contains no unique failures.Failures in common with acceptance upstream results at 76e0dd4:
|
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#113147 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#193 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-tango#2183 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - liferay-tango > liferay-tango - PR#2183 - 2022-02-07[08:54:40] Testray Importer:publish-testray-report#448 |
Motivation
Documents should not include reads metrics in the content performance panel
Link to story or ticket
Proposed Solution
Don't fill the read metrics for Documents in the Content Performance Panel
Steps to Verify:
Screencaps: