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

LPD-40116 on this case the friendlyURLPosition should match with the one with # because can be mixed #6030

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

AliciaGarciaGarcia
Copy link
Collaborator

LPD-40116 Importation fails when on a web content with 2 links with ONE of the on trash

What is this trying to solve?

https://liferay.atlassian.net/browse/LPD-40116

On some cases, the importation and exportation fails, it happens when the links are mixed AND the old one, the one inserted with the UUID, the file is on the trash.

How am I fixing it?

As the filters can be mixed we should check the exact characteres to find.

How can you verify that it works?

Run the included automated tests.

Commits

  • LPD-40116 add test to test the behavior on the importation and exportation when the links are mixed AND the old one, the one inserted with the UUID is on the trash.
  • LPD-40116 on this case the friendlyURLPosition should match with the one with # because can be mixed

@liferay-continuous-integration
Copy link
Collaborator

CI is automatically triggering the following test suites:

  •     ci:test:sf

@AliciaGarciaGarcia
Copy link
Collaborator Author

ci:test:content-management

@AliciaGarciaGarcia
Copy link
Collaborator Author

ci:help

@liferay-continuous-integration
Copy link
Collaborator

Available CI commands:

ci:close

    Close the pull request.

ci:forward[:force]

    Test the pull request and forward the pull request to brianchandotcom if the required test suites pass for ci:forward or complete for ci:forward:force.

ci:merge[:force]

    Merge in the changes from the subrepo. All tests must pass before this command will successfully run. Optionally use the force flag to bypass failed tests.

ci:reevaluate:[buildID]

    Reevaluate the pull request result from a generated build ID.

ci:reopen

    Reopen the pull request.

ci:report:[testrayBuildID]

    Generates a report of test results categorized into unique and nonunique test failures based on the Testray Analysis Tool.

ci:stop[:suite]

    Stop all currrently running tests. Optionally specify the name of the test suite.

ci:test[:suite]:dryrun

    Generate the job summary of the specified test suite based on the pull request changes. This command will not test the pull request.

ci:test[:suite][:SHA|nocompile|norebase|gist-SHA]

    Test the pull request. Optionally specify the name of the test suite and/or optionally specify the upstream SHA to test against or use "nocompile" to test with a prebuilt bundle or use "norebase" to test without rebasing.

Available test suites:
  •     ci:test:acceptance - Test acceptance tests.
  •     ci:test:acceptance-ce - No description is available.
  •     ci:test:acceptance-dxp - No description is available.
  •     ci:test:acceptance-functional - Test acceptance functional tests.
  •     ci:test:acceptance-functional-db-partition - Test acceptance functional tests with Database Partitioning.
  •     ci:test:acceptance-release - Compile a release bundle and execute acceptance tests.
  •     ci:test:accessibility - Test all accessibility tests.
  •     ci:test:accessibility-menu - Test all accessibility menu tests.
  •     ci:test:account - Test Account tests.
  •     ci:test:analytics-cloud - Test Analytics Cloud tests.
  •     ci:test:analytics-cloud-acceptance - No description is available.
  •     ci:test:analytics-cloud-integration - No description is available.
  •     ci:test:analytics-cloud-quarantine - No description is available.
  •     ci:test:analytics-cloud-release - No description is available.
  •     ci:test:analytics-cloud-upstream - No description is available.
  •     ci:test:api-builder - All tests for API Builder component.
  •     ci:test:api-builder-functional - Functional tests for API Builder component.
  •     ci:test:app-servers - Test Deployments on App Servers.
  •     ci:test:auto-tagging - Test Auto Tagging tests.
  •     ci:test:backend - Test backend tests.
  •     ci:test:backend-hypersonic - Test backend tests on Hypersonic.
  •     ci:test:blade - Test Blade samples tests.
  •     ci:test:blogs - Test Blogs tests.
  •     ci:test:bundle - Saves a compiled tomcat bundle.
  •     ci:test:bundles - No description is available.
  •     ci:test:calendar - Test Calendar tests.
  •     ci:test:clay - Test Clay component tests.
  •     ci:test:click-to-chat - Test Click to Chat tests.
  •     ci:test:clustering - Test clustering tests.
  •     ci:test:comment - Test Comment tests.
  •     ci:test:commerce - Test only Commerce tests.
  •     ci:test:commerce-database - Test only Commerce Database tests.
  •     ci:test:commerce-es7-remote - Test only Commerce tests with the latest compatible remote Elasticsearch 7 version.
  •     ci:test:commerce-es8-remote - Test only Commerce tests with the latest compatible remote Elasticsearch 8 version.
  •     ci:test:commerce-functional - Test only Commerce functional tests.
  •     ci:test:commerce-integration - Test only Commerce integration tests.
  •     ci:test:commerce-opensearch2 - Test only Commerce tests with the latest compatible OpenSearch 2 version.
  •     ci:test:commerce-upgrade - No description is available.
  •     ci:test:configuration-framework - Test Configuration Framework component tests.
  •     ci:test:content-management - Test Content Management tests.
  •     ci:test:content-management-playwright - Test Content Management playwright tests.
  •     ci:test:content-page-review - Test Content Page Review (comments) tests.
  •     ci:test:continuous-integration - Test Continuous Integration tests.
  •     ci:test:cookies - Test Cookie Preferences tests.
  •     ci:test:core-functional - Test Core Infra Functional tests
  •     ci:test:customer-solutions - Test all Customer Solutions team tests.
  •     ci:test:data-engine - Test Data Engine functional tests.
  •     ci:test:data-engine-db-partition - Test Data Engine functional tests with Database Partitioning.
  •     ci:test:data-integration - Test only Data Integration tests.
  •     ci:test:data-integration-functional - Test only functional Data Integration tests.
  •     ci:test:db-partition - Test Database Partitioning functional tests.
  •     ci:test:depot - Test Depot tests.
  •     ci:test:dev-tools - Test Dev Tools tests.
  •     ci:test:digital-signature - Test Digital Signature tests.
  •     ci:test:dl-store - Test Document Library Store tests.
  •     ci:test:document - Test Document and Media tests.
  •     ci:test:document-antivirus - Test Antivirus against DM.
  •     ci:test:drools - Test Drools tests.
  •     ci:test:dummy - No description is available.
  •     ci:test:environments - Test environment acceptance functional tests on all available environment stacks.
  •     ci:test:export-import - Test exportimport tests.
  •     ci:test:forms - Test forms tests.
  •     ci:test:forms-db-partition - Test forms functional tests with Database Partitioning.
  •     ci:test:forms-functional - Test only functional forms tests.
  •     ci:test:frontend - Test all Frontend Infra team tests.
  •     ci:test:frontend-client-extensions - Test frontend client extensions tests.
  •     ci:test:frontend-data-set - Test frontend data set tests.
  •     ci:test:frontend-dev-exp - Test frontend developer experience tests.
  •     ci:test:frontend-ui - Test frontend ui tests.
  •     ci:test:frontend-walkthrough - Test frontend walkthrough tests.
  •     ci:test:gauntlet - Test upstream tests.
  •     ci:test:gauntlet-bucket - Test a subset of upstream tests.
  •     ci:test:gradle-plugins - Test Gradle Plugins tests.
  •     ci:test:headless - Test all headless team tests.
  •     ci:test:headless-acceptance - Test headless team acceptance tests considering Headless and REST Builder.
  •     ci:test:headless-functional - Headless team functional API tests.
  •     ci:test:headless-playwright - Headless team playwright tests.
  •     ci:test:headless-staging - Test Staging components tests.
  •     ci:test:headless-staging-custom-db - Test Staging components tests with a custom database.
  •     ci:test:hotel - Test all Source Formatter unit tests related to upgrade
  •     ci:test:item-selector - Test item selector tests.
  •     ci:test:jdk11 - Test acceptance,smoke,and upgrade functional tests against JDK11.
  •     ci:test:jdk21 - Test acceptance tests against JDK21.
  •     ci:test:jdk21-functional - No description is available.
  •     ci:test:jdk21-integration - No description is available.
  •     ci:test:jdk21-unit - No description is available.
  •     ci:test:jsf - Test Liferay Faces tests.
  •     ci:test:kaleo-forms - Test Kaleo Forms admin tests.
  •     ci:test:knowledge-base - No description is available.
  •     ci:test:ldap - Test LDAP tests.
  •     ci:test:license - Compile a release bundle and execute tests for licensing.
  •     ci:test:license-cluster - Compile a release bundle and execute tests for cluster licensing on 32GB slaves.
  •     ci:test:liferay-osb-site-initializer - No description is available.
  •     ci:test:liferay-sample-workspace - No description is available.
  •     ci:test:liferay-site-initializer - No description is available.
  •     ci:test:lpkg - Test LPKG tests.
  •     ci:test:message-boards - No description is available.
  •     ci:test:mfa - Test Multi Factor Authentication tests.
  •     ci:test:navigation-framework - Test Navigation Framework tests.
  •     ci:test:notifications - Test Notifications tests.
  •     ci:test:oauth2 - Test OAuth 2 tests.
  •     ci:test:object - Test Object tests.
  •     ci:test:object-as - Test object tests with different application servers.
  •     ci:test:object-db - Test object tests with different databases.
  •     ci:test:object-db-integration - Test only Object integration tests with different databases.
  •     ci:test:object-db-partition - Test object functional tests with Database Partitioning.
  •     ci:test:object-functional - Test only Object functional tests
  •     ci:test:object-lxc - Test Object tests with Liferay Experience Cloud configurations.
  •     ci:test:oidc - Test OpenID Connect tests.
  •     ci:test:onedrive - Test OneDrive tests.
  •     ci:test:page-management - Test all Page Management team tests.
  •     ci:test:page-management-playwright - Test Page Management team playwright tests.
  •     ci:test:password-policies - Test Password Policies tests.
  •     ci:test:platform-experience - Test Platform Experience team tests.
  •     ci:test:platform-experience-acceptance - Test Platform Experience team acceptance tests.
  •     ci:test:platform-experience-accessibility - Test Platform Experience team accessibility framework tests.
  •     ci:test:platform-experience-db-partition - No description is available.
  •     ci:test:playwright - Test all playwright tests.
  •     ci:test:portal-context-path - No description is available.
  •     ci:test:portal-proxy-path - No description is available.
  •     ci:test:portlet-deployment - Test deployment of all demo portlet plugins.
  •     ci:test:poshi - No description is available.
  •     ci:test:poshi-gauntlet - No description is available.
  •     ci:test:project-templates - Test project-templates tests.
  •     ci:test:publications - Test publications tests.
  •     ci:test:publications-as - Test publications tests with different application servers.
  •     ci:test:publications-db - Test publications tests with different databases.
  •     ci:test:publications-db-partition - Test publications functional tests with Database Partitioning.
  •     ci:test:publications-lxc - Test publications tests with Liferay Experience Cloud configurations.
  •     ci:test:questions - No description is available.
  •     ci:test:redirect - No description is available.
  •     ci:test:relevant - Test relevant changes only.
  •     ci:test:reports - Test Reports tests.
  •     ci:test:roles - Test Roles tests.
  •     ci:test:saml - Test SAML tests.
  •     ci:test:scim - Test SCIM tests.
  •     ci:test:search - Test search tests with the Elasticsearch 7 search engine.
  •     ci:test:search-as - Test search tests with the Elasticsearch 7 search engine on different application servers.
  •     ci:test:search-db - Test search tests with the Elasticsearch 7 search engine on different databases.
  •     ci:test:search-db-partition - Test search functional tests with Database Partitioning.
  •     ci:test:search-es8-as - Test search tests with the Elasticsearch 8 search engine on different application servers.
  •     ci:test:search-es8-db - Test search tests with the Elasticsearch 8 search engine on different databases.
  •     ci:test:search-es8-remote - Test only search tests with the latest compatible remote Elasticsearch 8 version.
  •     ci:test:search-es8-remote-minimum - Test search tests with the minimum compatible remote Elasticsearch 8 version.
  •     ci:test:search-lxc - Test search tests with the Elasticsearch 7 search engine and Liferay Experience Cloud configurations.
  •     ci:test:search-opensearch2 - Test only search tests with the latest compatible OpenSearch 2 version.
  •     ci:test:search-opensearch2-as - Test search tests with the OpenSearch 2 search engine on different application servers.
  •     ci:test:search-opensearch2-db - Test search tests with the OpenSearch 2 search engine on different databases.
  •     ci:test:search-remote - Test only search tests with the latest compatible remote Elasticsearch 7 version.
  •     ci:test:search-remote-minimum - Test search tests with the minimum compatible remote Elasticsearch 7 version.
  •     ci:test:search-solr - Test search tests with the Solr 8 search engine.
  •     ci:test:search-solr-as - Test search tests with the Solr 8 search engine on different application servers.
  •     ci:test:search-solr-db - Test search tests with the Solr 8 search engine on different databases.
  •     ci:test:security - Test security tests.
  •     ci:test:service-builder - Test Service Builder tests.
  •     ci:test:setup-wizard - Test Setup Wizard tests.
  •     ci:test:sf - Test source formatter.
  •     ci:test:sharing - Test Asset Sharing tests.
  •     ci:test:site-management - Test Site Management tests.
  •     ci:test:site-template - Test Site Template tests.
  •     ci:test:smoke - Run smoke test with all available configurations in PortalSmoke.testcase
  •     ci:test:stable - No description is available.
  •     ci:test:startup - Test Portal startup.
  •     ci:test:sybase - Test functional and integration tests on Sybase database.
  •     ci:test:system - Test functional and integration tests for System Management (Virtual Instances,System Settings,Instance Settings)
  •     ci:test:tck - Test TCK tests.
  •     ci:test:themes - No description is available.
  •     ci:test:translation - Test Translation Management tests.
  •     ci:test:um - Test User Management tests.
  •     ci:test:um-db-partition - No description is available.
  •     ci:test:upgrade - Test upgrades against tomcat app server and all supported databases.
  •     ci:test:upgrade-all - Test upgrades from all components against all app servers and databases.
  •     ci:test:upgrade-app-servers - Test upgrades against all app servers.
  •     ci:test:upgrade-client - Test upgrade client.
  •     ci:test:upgrade-performance - Test large database for upgrade performance regressions.
  •     ci:test:upstream-dxp - No description is available.
  •     ci:test:upstream-functional - Test upstream functional tests.
  •     ci:test:upstream-functional-db-partition - Test upstream functional tests with Database Partitioning.
  •     ci:test:users - Test Users and Organizations tests.
  •     ci:test:usm - No description is available.
  •     ci:test:usm-db-partition - No description is available.
  •     ci:test:usm-environments - No description is available.
  •     ci:test:usm-upgrade - No description is available.
  •     ci:test:vulcan-acceptance - Test headless team acceptance tests considering Vulcan and Commerce.
  •     ci:test:wiki - Test wiki tests.
  •     ci:test:workflow - Test Workflow tests.
  •     ci:test:workflow-db-partition - Test Workflow functional tests with Database Partitioning.
  •     ci:test:workflow-es7-remote - Test Workflow tests with the latest compatible remote Elasticsearch 7 version.
  •     ci:test:workflow-es8-remote - Test Workflow tests with the latest compatible remote Elasticsearch 8 version.
  •     ci:test:workflow-opensearch2 - No description is available.
  •     ci:test:workspaces - No description is available.

For more details, see CI GitHub Commands

@AliciaGarciaGarcia
Copy link
Collaborator Author

ci:test:export-import

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: 449fa8fd0fbf5b9bbae254fdd8b549332370371e

Sender Branch:

Branch Name: LPD-40116
Branch GIT ID: 7964a7b6ac3a61b3b7e0ddd92fe79e3c3994ffe5

1 out of 1jobs PASSED
1 Successful Jobs:
For more details click here.

@liferay-continuous-integration
Copy link
Collaborator

@liferay-continuous-integration
Copy link
Collaborator

✔️ ci:test:export-import - 52 out of 52 jobs passed in 56 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: 449fa8fd0fbf5b9bbae254fdd8b549332370371e

Upstream Comparison:

Branch GIT ID: 75cdfe67b3f03ae0eaaddbcb91187877e279f954
Jenkins Build URL: EE Development Acceptance (master) - 943 - 2024-10-23[07:21:16]

ci:test:export-import - 52 out of 52 jobs PASSED
52 Successful Jobs:
For more details click here.

@liferay-continuous-integration
Copy link
Collaborator

❌ ci:test:content-management - 922 out of 1001 jobs passed in 2 hours 17 minutes

Click here for more details.

Base Branch:

Branch Name: master
Branch GIT ID: 449fa8fd0fbf5b9bbae254fdd8b549332370371e

Upstream Comparison:

Branch GIT ID: 75cdfe67b3f03ae0eaaddbcb91187877e279f954
Jenkins Build URL: EE Development Acceptance (master) - 943 - 2024-10-23[07:21:16]

ci:test:content-management - 922 out of 1001 jobs PASSED

79 Failed Jobs:

922 Successful Jobs:
    For more details click here.

    Failures unique to this pull:

    1. functional-tomcat90-mysql57/19/15
           [exec] * What went wrong:
           [exec] Execution failed for task ':runPoshi'.
           [exec] > There were failing tests. See the report at: file:///opt/dev/projects/github/liferay-portal/portal-web/tests/index.html
           [exec] 
           [exec] * Try:
           [exec] > Run with --scan to get full insights.
           [exec] 
           [exec] BUILD FAILED in 29s
           [exec] 3 actionable tasks: 2 executed, 1 up-to-date
           [exec] 
           [exec] See the profiling report at: file:///opt/dev/projects/github/liferay-portal/portal-web/build/reports/profile/profile-2024-10-23-11-37-39.html
           [exec] A fine-grained performance profile is available: use the --scan option.
           [exec] Result: 1
           [copy] Copying 1 file to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/372829
           [copy] Copying 2 files to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/372829/screenshots
         [delete] Deleting: /opt/dev/projects/github/liferay-portal/null178340855.properties
      

      clean-up-selenium-driver:
      [echo] Executing commands:
      [echo]
      [echo] docker logs cloud-10-0-16-26.lax.liferay.com_chrome > /tmp/jenkins/test-1-1/test-portal-acceptance-pullrequest-downstream(master)/372829/docker-logs/cloud-10-0-16-26.lax.liferay.com_chrome.log
      [echo]
      [echo] https://test-1-32.liferay.com/userContent/jobs/test-portal-acceptance-pullrequest(master)/builds/5400/functional-tomcat90-mysql57/19/15/docker-logs/cloud-10-0-16-26.lax.liferay.com_chrome.log
      [echo] Executing commands:
      [echo] killall chromedriver
      [exec] chromedriver: no process found
      [exec] Result: 1
      [stopwatch] [test.execution.duration: 6:39.939 sec]
      [stopwatch] [run.batch.test.action: 7:22.917 sec]
      [echo] The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:373: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1701: /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1705: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:38: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:50: The following error occurred while executing this line:

    2. functional-tomcat90-mysql57/19/16
           [exec] * What went wrong:
      [exec] Execution failed for task ':runPoshi'.
      [exec] > There were failing tests. See the report at: file:///opt/dev/projects/github/liferay-portal/portal-web/tests/index.html
      [exec]
      [exec] * Try:
      [exec] > Run with --scan to get full insights.
      [exec]
      [exec] BUILD FAILED in 29s
      [exec] Result: 1
      [copy] Copying 1 file to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1006633
      [copy] Copying 2 files to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1006633/screenshots
      [delete] Deleting: /opt/dev/projects/github/liferay-portal/null1011778537.properties

      clean-up-selenium-driver:
      [echo] Executing commands:
      [echo]
      [echo] docker logs test-1-28-17.lax.liferay.com_chrome > /tmp/jenkins/test-1-28/test-portal-acceptance-pullrequest-downstream(master)/1006633/docker-logs/test-1-28-17.lax.liferay.com_chrome.log
      [echo]
      [echo] https://test-1-32.liferay.com/userContent/jobs/test-portal-acceptance-pullrequest(master)/builds/5400/functional-tomcat90-mysql57/19/16/docker-logs/test-1-28-17.lax.liferay.com_chrome.log
      [echo] Executing commands:
      [echo] killall chromedriver
      [exec] chromedriver: no process found
      [exec] Result: 1
      [stopwatch] [test.execution.duration: 4:11.112 sec]
      [stopwatch] [run.batch.test.action: 4:40.510 sec]
      [echo] The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:373: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1701: /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1705: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:38: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:50: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test.xml:16736: Property custom.default.user.password was circularly defined.
      [get] Getting: ${dependencies.url}/archive/test-1-28/test-portal-acceptance-pullrequest-downstream(master)/1006633consoleText
      [get] To: /opt/dev/projects/github/liferay-portal/20241023113512679.txt

    3. functional-tomcat90-mysql57/19/17
           [exec] * What went wrong:
      [exec] Execution failed for task ':runPoshi'.
      [exec] > There were failing tests. See the report at: file:///opt/dev/projects/github/liferay-portal/portal-web/tests/index.html
      [exec]
      [exec] * Try:
      [exec] > Run with --scan to get full insights.
      [exec]
      [exec] BUILD FAILED in 33s
      [exec] Gradle build finished at 2024-10-23 18:41:03.830.
      [exec] 3 actionable tasks: 2 executed, 1 up-to-date
      [exec]
      [exec] See the profiling report at: file:///opt/dev/projects/github/liferay-portal/portal-web/build/reports/profile/profile-2024-10-23-11-40-34.html
      [exec] A fine-grained performance profile is available: use the --scan option.
      [exec] Result: 1
      [copy] Copying 1 file to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/376647
      [copy] Copying 2 files to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/376647/screenshots
      [delete] Deleting: /opt/dev/projects/github/liferay-portal/null663309237.properties

      clean-up-selenium-driver:
      [echo] Executing commands:
      [echo]
      [echo] docker logs cloud-10-0-16-97.lax.liferay.com_chrome > /tmp/jenkins/test-1-5/test-portal-acceptance-pullrequest-downstream(master)/376647/docker-logs/cloud-10-0-16-97.lax.liferay.com_chrome.log
      [echo]
      [echo] https://test-1-32.liferay.com/userContent/jobs/test-portal-acceptance-pullrequest(master)/builds/5400/functional-tomcat90-mysql57/19/17/docker-logs/cloud-10-0-16-97.lax.liferay.com_chrome.log
      [echo] Executing commands:
      [echo] killall chromedriver
      [exec] chromedriver: no process found
      [exec] Result: 1
      [stopwatch] [test.execution.duration: 8:17.499 sec]
      [stopwatch] [run.batch.test.action: 9:07.800 sec]
      [echo] The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:373: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1701: /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1705: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:38: The following error occurred while executing this line:

    4. functional-tomcat90-mysql57/19/18
           [exec] * What went wrong:
      [exec] Execution failed for task ':runPoshi'.
      [exec] > There were failing tests. See the report at: file:///opt/dev/projects/github/liferay-portal/portal-web/tests/index.html
      [exec]
      [exec] * Try:
      [exec] > Run with --scan to get full insights.
      [exec]
      [exec] BUILD FAILED in 26s
      [exec] Result: 1
      [copy] Copying 1 file to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1236883
      [copy] Copying 2 files to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1236883/screenshots
      [delete] Deleting: /opt/dev/projects/github/liferay-portal/null1157013221.properties

      clean-up-selenium-driver:
      [echo] Executing commands:
      [echo]
      [echo] docker logs test-1-37-5.lax.liferay.com_chrome > /tmp/jenkins/test-1-37/test-portal-acceptance-pullrequest-downstream(master)/1236883/docker-logs/test-1-37-5.lax.liferay.com_chrome.log
      [echo]
      [echo] https://test-1-32.liferay.com/userContent/jobs/test-portal-acceptance-pullrequest(master)/builds/5400/functional-tomcat90-mysql57/19/18/docker-logs/test-1-37-5.lax.liferay.com_chrome.log
      [echo] Executing commands:
      [echo] killall chromedriver
      [exec] chromedriver: no process found
      [exec] Result: 1
      [stopwatch] [test.execution.duration: 3:57.399 sec]
      [stopwatch] [run.batch.test.action: 4:27.084 sec]
      [echo] The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:373: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1701: /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1705: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:38: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:50: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test.xml:16736: Property custom.default.user.password was circularly defined.
      [get] Getting: ${dependencies.url}/archive/test-1-37/test-portal-acceptance-pullrequest-downstream(master)/1236883consoleText
      [get] To: /opt/dev/projects/github/liferay-portal/20241023113526966.txt

    5. functional-tomcat90-mysql57/19/19
           [exec] * What went wrong:
      [exec] Execution failed for task ':runPoshi'.
      [exec] > There were failing tests. See the report at: file:///opt/dev/projects/github/liferay-portal/portal-web/tests/index.html
      [exec]
      [exec] * Try:
      [exec] > Run with --scan to get full insights.
      [exec]
      [exec] BUILD FAILED in 29s
      [exec] Gradle build finished at 2024-10-23 18:36:49.241.
      [exec] 3 actionable tasks: 2 executed, 1 up-to-date
      [exec]
      [exec] See the profiling report at: file:///opt/dev/projects/github/liferay-portal/portal-web/build/reports/profile/profile-2024-10-23-11-36-23.html
      [exec] A fine-grained performance profile is available: use the --scan option.
      [exec] Result: 1
      [copy] Copying 1 file to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1009791
      [copy] Copying 2 files to /opt/dev/projects/github/liferay-portal/test-portal-acceptance-pullrequest-downstream(master)/builds/1009791/screenshots
      [delete] Deleting: /opt/dev/projects/github/liferay-portal/null1667401090.properties

      clean-up-selenium-driver:
      [echo] Executing commands:
      [echo]
      [echo] docker logs test-1-29-75.lax.liferay.com_chrome > /tmp/jenkins/test-1-29/test-portal-acceptance-pullrequest-downstream(master)/1009791/docker-logs/test-1-29-75.lax.liferay.com_chrome.log
      [echo]
      [echo] https://test-1-32.liferay.com/userContent/jobs/test-portal-acceptance-pullrequest(master)/builds/5400/functional-tomcat90-mysql57/19/19/docker-logs/test-1-29-75.lax.liferay.com_chrome.log
      [echo] Executing commands:
      [echo] killall chromedriver
      [exec] chromedriver: no process found
      [exec] Result: 1
      [stopwatch] [test.execution.duration: 4:15.200 sec]
      [stopwatch] [run.batch.test.action: 4:45.418 sec]
      [echo] The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:373: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1701: /opt/dev/projects/github/liferay-portal/build-test-batch.xml:1705: The following error occurred while executing this line:
      [echo] /opt/dev/projects/github/liferay-portal/build-test-tomcat.xml:38: The following error occurred while executing this line:

    6. ...

    @liferay-continuous-integration
    Copy link
    Collaborator

    @AliciaGarciaGarcia
    Copy link
    Collaborator Author

    ci:report:50171385

    @liferay-continuous-integration
    Copy link
    Collaborator

    Build completed.

    Testray CSV has been generated successfully for testrayBuildID: 50171385.

    Job Link: generate-testray-csv

    Testray CSV Link: testray-results-50171385.csv

    …ation when the links are mixed AND the old one, the one inserted with the UUID is on the trash.
    @AliciaGarciaGarcia
    Copy link
    Collaborator Author

    ci:test:sf

    @liferay-continuous-integration
    Copy link
    Collaborator

    ✔️ ci:test:sf - 1 out of 1 jobs passed in 4 minutes

    Click here for more details.

    Base Branch:

    Branch Name: master
    Branch GIT ID: ff9815fa7c6e0c17a7e10fd9f56ff6e4d93af28a

    Sender Branch:

    Branch Name: LPD-40116
    Branch GIT ID: 1cbdf86fde45612afdab340ea8695239a5f9a174

    1 out of 1jobs PASSED
    1 Successful Jobs:
    For more details click here.

    @liferay-continuous-integration
    Copy link
    Collaborator

    @AliciaGarciaGarcia
    Copy link
    Collaborator Author

    ci:test:content-management

    @jkappler
    Copy link
    Collaborator

    That's why I was not 100% sure @AliciaGarciaGarcia :P

    @AliciaGarciaGarcia
    Copy link
    Collaborator Author

    That's why I was not 100% sure @AliciaGarciaGarcia :P

    that's me the 100% of the time

    @AliciaGarciaGarcia
    Copy link
    Collaborator Author

    ci:test:relevant

    @liferay-continuous-integration
    Copy link
    Collaborator

    Build started.

    Jenkins is currently running tests in the content-management test suite.

    Base Branch:

    Branch Name: master

    Job Summary:

    Job Link: test-portal-acceptance-pullrequest(master)

    For more details click here.

    @liferay-continuous-integration
    Copy link
    Collaborator

    Build started.

    Jenkins is currently running tests in the relevant test suite.

    Base Branch:

    Branch Name: master

    Job Summary:

    Job Link: test-portal-acceptance-pullrequest(master)

    For more details click here.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    4 participants