[many ports] Update existing KF5 frameworks to 5.75#13467
[many ports] Update existing KF5 frameworks to 5.75#13467vicroms merged 75 commits intomicrosoft:masterfrom
Conversation
kf5crash - make x11 patch exclusive to linux - enable win/macOS builds kf5syntaxhighlighting - fix building on non-Win by removing the cli tool from all platforms
|
My apologies, I pushed a new kf5auth port by mistake. |
This reverts commit 8703c24.
|
@NancyLi1013 FYI, I reverted the new kf5auth I accidentally added |
This reverts commit f1ac3db.
|
There is also another new port Edit: I noticed that you have removed just now. Please ignore this comment. |
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
|
LGTM now. Thanks for your PR. |
ras0219-msft
left a comment
There was a problem hiding this comment.
LGTM other than one question
|
@ras0219 @NancyLi1013 similarly to what I reported under PR #13469, I see that all the modified ports in this PR were also labeled as CASCADE by the CI run, which to my understanding implies they were skipped due to a missing/failing dependency. In this case it looks that for some reason |
|
Your understanding is right. The build results are related with those dependencies. |
|
@NancyLi1013 so I just run those builds locally on my Windows VM after learning they aren't actually being tested by the CI and I already had some failures. I don't believe I can consciously push this PR into the master unless we can actually have your CI to properly test all the supported triplets – I don't have the means to do so locally. @ras0219-msft I see that the ecm was excluded as part of this change of yours. May we know wat was wrong with ecm? The pull request doesn't mention anything specific about it. |
|
Hi @wrobelda I'm so sorry for updates many times, I reviewed this PR again and gave some extra suggestions. Please address them if you're free. LGTM now except for these review suggestions. The only problem is the failure on Linux, which is not related with the changes in this PR, but we still recommend to merge this PR after all CI checks passed. So we need to wait for the PR #15808 merged. |
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
Co-authored-by: NancyLi1013 <46708020+NancyLi1013@users.noreply.github.com>
Absolutely, nothing to apologize for! I totally understand we're held to high standards here and I appreciate your continuous feedback. All suggestions were addressed. |
|
There is nothing need to be done on your sides now, Let's wait for the PR #15808 merged. |
|
@NancyLi1013 it looks like #15808 has stalled. Is there anything else that can be done to obtain an unobstructed Linux CI/CD run and have this merged? |
|
Sorry, there is nothing to do except for waiting it merged. Unless the errors on Linux will disappear. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Will be fixed by another PR #16954 |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
LGTM now, thanks for your hard work and patience @wrobelda. |
Describe the pull request
Which triplets are supported/not supported? Have you updated the CI baseline?
No change in triplets supported.
Does your PR follow the maintainer guide?
Yes