KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 1515 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/1515/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Sat, 16 Apr 2022 01:42:07 + Build duration: 17 min and counting JUnit Tests Name: projectroot Failed: 3 test(s), Passed: 58 test(s), Skipped: 0 test(s), Total: 61 test(s)Failed: projectroot.autotests.applicationlauncherjob_servicetestFailed: projectroot.autotests.commandlauncherjob_servicetestFailed: projectroot.autotests.kiocore_krecentdocumenttestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
KDE CI: Frameworks » syntax-highlighting » kf5-qt5 SUSEQt5.15 - Build # 562 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/syntax-highlighting/job/kf5-qt5%20SUSEQt5.15/562/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Fri, 15 Apr 2022 14:52:38 +
Build duration:
9 hr 16 min and counting
CONSOLE OUTPUT
Started by an SCM changeStarted by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeStill waiting to schedule taskWaiting for next available executor on ‘SUSEQt5.15’Running on Docker Swarm-3cef9fb20280 in /home/jenkins/workspace/Frameworks/syntax-highlighting/kf5-qt5 SUSEQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] checkout[2022-04-16T00:08:52.402Z] The recommended git tool is: NONE[2022-04-16T00:08:53.498Z] No credentials specified[2022-04-16T00:08:53.501Z] Cloning the remote Git repository[2022-04-16T00:08:53.519Z] Cloning repository https://invent.kde.org/frameworks/syntax-highlighting.git[2022-04-16T00:08:53.707Z] ERROR: Error cloning remote repo 'origin'[2022-04-16T00:08:53.707Z] hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://invent.kde.org/frameworks/syntax-highlighting.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:[2022-04-16T00:08:53.707Z] stdout: [2022-04-16T00:08:53.707Z] stderr: remote: GitLab is not responding[2022-04-16T00:08:53.707Z] fatal: unable to access 'https://invent.kde.org/frameworks/syntax-highlighting.git/': The requested URL returned error: 502[2022-04-16T00:08:53.707Z] [2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2450)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2051)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:573)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:802)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)[2022-04-16T00:08:53.707Z] at hudson.remoting.UserRequest.perform(UserRequest.java:211)[2022-04-16T00:08:53.707Z] at hudson.remoting.UserRequest.perform(UserRequest.java:54)[2022-04-16T00:08:53.707Z] at hudson.remoting.Request$2.run(Request.java:375)[2022-04-16T00:08:53.707Z] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73)[2022-04-16T00:08:53.707Z] at java.util.concurrent.FutureTask.run(FutureTask.java:264)[2022-04-16T00:08:53.707Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)[2022-04-16T00:08:53.707Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)[2022-04-16T00:08:53.707Z] at java.lang.Thread.run(Thread.java:829)[2022-04-16T00:08:53.707Z] Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Docker Swarm-3cef9fb20280[2022-04-16T00:08:53.707Z] at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1800)[2022-04-16T00:08:53.707Z] at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)[2022-04-16T00:08:53.707Z] at hudson.remoting.Channel.call(Channel.java:1001)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)[2022-04-16T00:08:53.707Z] at sun.reflect.GeneratedMethodAccessor388.invoke(Unknown Source)[2022-04-16T00:08:53.707Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[2022-04-16T00:08:53.707Z] at java.lang.reflect.Method.invoke(Method.java:498)[2022-04-16T00:08:53.707Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)[2022-04-16T00:08:53.707Z] at com.sun.proxy.$Proxy95.execute(Unknown Source)[2022-04-16T00:08:53.707Z] at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1224)[2022-04-16T00:08:53.707Z] at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)[2022-04-16T00:08:53.708Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125)[2022-04-16T00:08:53.708Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)[2022-04-16T00:08:53.708Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)[2022-04-16T00:08:53.708Z] at
KDE CI: Frameworks » kwayland » kf5-qt5 SUSEQt5.15 - Build # 180 - Failure!
BUILD FAILURE
Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20SUSEQt5.15/180/
Project:
kf5-qt5 SUSEQt5.15
Date of build:
Fri, 15 Apr 2022 14:36:02 +
Build duration:
9 hr 32 min and counting
CONSOLE OUTPUT
Started by an SCM changeRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] nodeStill waiting to schedule taskWaiting for next available executor on ‘SUSEQt5.15’Running on Docker Swarm-9637180f3a3e in /home/jenkins/workspace/Frameworks/kwayland/kf5-qt5 SUSEQt5.15[Pipeline] {[Pipeline] timestamps[Pipeline] {[Pipeline] catchError[Pipeline] {[Pipeline] stage[Pipeline] { (Checkout Sources)[Pipeline] checkout[2022-04-16T00:08:35.452Z] The recommended git tool is: NONE[2022-04-16T00:08:36.505Z] No credentials specified[2022-04-16T00:08:36.507Z] Cloning the remote Git repository[2022-04-16T00:08:36.627Z] ERROR: Error cloning remote repo 'origin'[2022-04-16T00:08:36.627Z] hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://invent.kde.org/frameworks/kwayland.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:[2022-04-16T00:08:36.627Z] stdout: [2022-04-16T00:08:36.627Z] stderr: fatal: unable to access 'https://invent.kde.org/frameworks/kwayland.git/': The requested URL returned error: 503[2022-04-16T00:08:36.627Z] [2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2450)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2051)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:573)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:802)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)[2022-04-16T00:08:36.627Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)[2022-04-16T00:08:36.627Z] at hudson.remoting.UserRequest.perform(UserRequest.java:211)[2022-04-16T00:08:36.627Z] at hudson.remoting.UserRequest.perform(UserRequest.java:54)[2022-04-16T00:08:36.627Z] at hudson.remoting.Request$2.run(Request.java:375)[2022-04-16T00:08:36.628Z] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73)[2022-04-16T00:08:36.628Z] at java.util.concurrent.FutureTask.run(FutureTask.java:264)[2022-04-16T00:08:36.628Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)[2022-04-16T00:08:36.628Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)[2022-04-16T00:08:36.628Z] at java.lang.Thread.run(Thread.java:829)[2022-04-16T00:08:36.628Z] Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Docker Swarm-9637180f3a3e[2022-04-16T00:08:36.628Z] at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1800)[2022-04-16T00:08:36.628Z] at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)[2022-04-16T00:08:36.628Z] at hudson.remoting.Channel.call(Channel.java:1001)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)[2022-04-16T00:08:36.628Z] at sun.reflect.GeneratedMethodAccessor388.invoke(Unknown Source)[2022-04-16T00:08:36.628Z] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[2022-04-16T00:08:36.628Z] at java.lang.reflect.Method.invoke(Method.java:498)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)[2022-04-16T00:08:36.628Z] at com.sun.proxy.$Proxy95.execute(Unknown Source)[2022-04-16T00:08:36.628Z] at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1224)[2022-04-16T00:08:36.628Z] at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)[2022-04-16T00:08:36.628Z] at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)[2022-04-16T00:08:36.628Z] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[2022-04-16T00:08:36.628Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[2022-04-16T00:08:36.628Z] at
KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 164 - Still Unstable!
BUILD UNSTABLE Build URL https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/164/ Project: kf5-qt5 FreeBSDQt5.15 Date of build: Fri, 15 Apr 2022 14:36:02 + Build duration: 4 min 21 sec and counting JUnit Tests Name: projectroot.autotests Failed: 15 test(s), Passed: 31 test(s), Skipped: 0 test(s), Total: 46 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testIdleFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testTextInputFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandSeatFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay
Re: The KIPI fate
On Fri, Apr 15, 2022 at 12:22 PM Albert Astals Cid wrote: > > In December KIPI support was removed from gwenview and spectacle with this > commit message > > > > Drop KIPI support > > KIPI offers export functionality for various external services > > However it has been abandoned from its original authors and receives no > real development any more > > A lot, if not all of its providers are defunct and it severly lacks UI > polish > > Gwenview already has integration with Purpose which offers a similar > (albeit theoretically reduced) functionality with a much more polished > experience > > > I disagreed loudly on IRC, because we: > > * If we had to remove things that "receives no real development" we would > remove more than half of KDE Gear, remember again, no new features doesn't > mean that the software is not maintained. > > * "A lot, if not all of its providers are defunct" that's just simply not > true since upon removal i went and tested various of the providers. I don't know the background but to me it sounds like there's functionality overlap between kipi and purpose and to that end if one receives development and the other is only getting kept alive as part of Gear maintenance then I see why the argument for removal was made. Specifically having two things cover the same use case seems a bit silly. I mean, competing is all good and fine, but maybe not in the same application ;) Whether or not some or even most of the providers still work only plays a minor role there, if they work the code could just be salvaged and moved into purpose given interest from someone. Seeing as this has not happened I'm somewhat leaning to read it as nobody cares enough, proofing the original point about non-development. My 2 cents anyway. > * "severly lacks UI polish" *SO WHAT* I like to think the quality of our products matter. If something looks unpolished it reflects badly on us and the product. That in particular also applies when we have 300 exporters but the one the user wanted to use isn't working. One bad apple spoils the bunch, as it were. > * "integration with Purpose" useless unless Purpose starts supporting all > the providers that KIPI used to support. Unsurprisingly, Purpose has not > gained any new plugin support since December > > This means that for the KDE Gear 22.04 release both gwenview and spectacle > will have less features for our users for no real reason, it's not even that > the code removed has hard to maintain in those two applications, it was not > more than 500 lines of code in isolated classes. > > Personally I would really like to revert those changes, but if not, I would > like a wider confirmation that we have decided we don't care about our users > that were potentially using those features (we have no way of knowning if 3 > or 3 million) and if that's the case just archive libkipi and kipi-plugins on > invent.kde.org so we can stop releasing and translating them. After all is said and done, this close to release I would leave things as they are TBH. If lots of users complain we can still pull a revert in a patch release, and then expand Purpose's feature set so we can drop kipi in 22.08. If not enough people complain, I'm +1 on archival for 22.08. (all with my limited understanding of kipi and purpose mind you) Going off on a tangent: I think you are hitting on a very important point. No matter what happens with kipi here, we should add userfeedback support for features that we'd like to remove and get a sense of the users the removal impacts. Right now we have no metrics, so all we are left with is removing stuff and see how many people complain and possibly backpedaling after the fact. That is not ideal. HS
The KIPI fate
In December KIPI support was removed from gwenview and spectacle with this commit message Drop KIPI support KIPI offers export functionality for various external services However it has been abandoned from its original authors and receives no real development any more A lot, if not all of its providers are defunct and it severly lacks UI polish Gwenview already has integration with Purpose which offers a similar (albeit theoretically reduced) functionality with a much more polished experience I disagreed loudly on IRC, because we: * If we had to remove things that "receives no real development" we would remove more than half of KDE Gear, remember again, no new features doesn't mean that the software is not maintained. * "A lot, if not all of its providers are defunct" that's just simply not true since upon removal i went and tested various of the providers. * "severly lacks UI polish" *SO WHAT* * "integration with Purpose" useless unless Purpose starts supporting all the providers that KIPI used to support. Unsurprisingly, Purpose has not gained any new plugin support since December This means that for the KDE Gear 22.04 release both gwenview and spectacle will have less features for our users for no real reason, it's not even that the code removed has hard to maintain in those two applications, it was not more than 500 lines of code in isolated classes. Personally I would really like to revert those changes, but if not, I would like a wider confirmation that we have decided we don't care about our users that were potentially using those features (we have no way of knowning if 3 or 3 million) and if that's the case just archive libkipi and kipi-plugins on invent.kde.org so we can stop releasing and translating them. Cheers, Albert
WikiToLearn status (specially regarding translation)
Hi folks, One of the translators today asked me about https://websvn.kde.org/trunk/l10n-kf5/templates/messages/wikitolearn-translation/ Is this something we should encourage people to translate? As far as I remember both the extraction and merging of those translations was pretty manual and looking at https://invent.kde.org/wikitolearn?sort=latest_activity_desc it doesn't seem there's much going on. Should we remove those files or are they actually being used? Cheers, Albert P.S: If answering from the wikitolearn list please CC me, I'm not subscribed
