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-132714 Upgrade ckeditor to v4.16.0-liferay.2 #1098
Conversation
**Changes in this version** [Full changelog](liferay/liferay-ckeditor@v4.16.0-liferay.1...v4.16.0-liferay.2) ### 🔧 Bug fixes - fix: remove unneeded styles ([\#176](liferay/liferay-ckeditor#176)) - fix: update @clayui/css to latest and add more icons ([\#175](liferay/liferay-ckeditor#175)) - fix: add null check ([\#168](liferay/liferay-ckeditor#168))
CI is automatically triggering the following test suites:
|
✔️ 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-132714 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#4780 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-frontend#1098 Testray Routine:EE Pull Request Testray Importer:publish-testray-report#1001 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#6029 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-frontend#1098 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - markocikos > liferay-frontend - PR#1098 - 2021-05-24[08:30:56] Testray Importer:publish-testray-report#1062 |
Hi @markocikos, The change in |
It's Ok for my part, we agreed on committing it here, not going to send anything :) |
@nhpatt ah ok, no worries then - sorry for the confusion. |
@john-co @manoelcyreno can you please take a look the failure, it looks unrelated. The failing test looks wrong. I don't think we should be checking for |
@nkkwon could you take a look and analyze the failure? |
Just started reviewing :) |
Analysis Details LocalFile.PortalSmokeUpgrade#ViewPortalSmokeArchive621021 - It looks like it's a flaky issue, has the same error occur in a recent acceptance run and looks like some other PR are being affected by it |
cc/ @vicnate5 see flaky PortalSmokeUpgrade#ViewPortalSmokeArchive621021 reported above. |
ci:test:relevant |
Trying relevant again so hopefully it passes and ready by morning. If not, ok to manually forward if test failure doesn't look related. |
Jenkins Build:test-portal-acceptance-pullrequest(master)#6049 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-frontend#1098 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - markocikos > liferay-frontend - PR#1098 - 2021-05-25[18:58:58] Testray Importer:publish-testray-report#1120 |
I'm a bit worried about forwarding manually, since we are updating a lot of dependencies in this PR. First CI fail was very early on, and second one was aborted build. I'll try forwarding one more time. |
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: |
I can split updating the package.json in another PR if it fails again. |
All required test suite(s) passed. |
Pull request has been successfully forwarded to brianchandotcom#102400 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#630 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-frontend#1098 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - markocikos > liferay-frontend - PR#1098 - 2021-05-26[07:18:35] Testray Importer:publish-testray-report#1076 |
JIRA ticket: https://issues.liferay.com/browse/LPS-132714
@julien @jonmak08
In addition to ckeditor version increase, we are running
yarn
onmodules
in 159bb48.Changelog:
🔧 Bug fixes