Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On Friday, May 01, 2015 12:56:26 AM Friedrich W. H. Kossebau wrote: > Hi Scarlett, > > Am Mittwoch, 29. April 2015, 23:26:14 schrieb Friedrich W. H. Kossebau: > > Am Dienstag, 21. April 2015, 13:45:06 schrieb Scarlett Clark: > > > I know this is an external depend, but I have no experience with it. > > > Can maybe a calligra dev take a look, as they need it. > > > VC > > > https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linu > > > x, > > > co mpiler=gcc/2/console > > > > Please build only the 0.7.4 release of vc, tagged with "0.7.4". So not > > "master" or anything else. That would be for any builds of vc, in any > > group > > (vc does not use qt anyway). AFAIK only Calligra uses vc right now, and in > > all branches Calligra needs vc 0.7(.4). > > See you changed that meanwhile, looks good WRT vc (and also the Calligra > master build), thanks :) > > But then there is still the following bummer: > > > With that said: > > > Calligra: (probably vc) > > > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra > > > %2 > > > 0c alligra-2.9%20stable-qt4/10/ > > > > Yes, given so far no vc build completed, this seems to fail when trying to > > get a built version of vc. Should work better once there is one :) > > > > Though there seems also another problem: commits to the "calligra/2.9" > > branch are not triggering any builds of the qt4 stable build: > > https://build.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligr > > a-> 2.9%20stable-qt4/ > > > > That was not a problem in the old CI, but so far noone can tell what is > > wrong now. Commits to the "frameworks" and "master" branches seem to > > properly trigger builds of the respective build setups. Perhaps you might > > have an idea? > > Anything where we could help with to solve this? The calligra/2.9 branch is > actually the hot branch these weeks still, main work is done there > (especially the awesome Krita one), so not having CI as a reference up and > working for this branch is a loss at the moment :) (see, CI is important to > us :) so we appreciate your work even more) > > Cheers > Friedrich 18:08:53 Started by an SCM change I am happy to report this fixed itself by a manual trigger. Must have had corruption the old workspace. I will do the same for the other qt4 branch. Scarlett signature.asc Description: This is a digitally signed message part.
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On Fri, May 1, 2015 at 12:12 PM, Scarlett Clark wrote: > On Friday, May 01, 2015 12:56:26 AM Friedrich W. H. Kossebau wrote: >> Hi Scarlett, >> >> Am Mittwoch, 29. April 2015, 23:26:14 schrieb Friedrich W. H. Kossebau: >> > Am Dienstag, 21. April 2015, 13:45:06 schrieb Scarlett Clark: >> > > I know this is an external depend, but I have no experience with it. >> > > Can maybe a calligra dev take a look, as they need it. >> > > VC >> > > https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linu >> > > x, >> > > co mpiler=gcc/2/console >> > >> > Please build only the 0.7.4 release of vc, tagged with "0.7.4". So not >> > "master" or anything else. That would be for any builds of vc, in any >> > group >> > (vc does not use qt anyway). AFAIK only Calligra uses vc right now, and > in >> > all branches Calligra needs vc 0.7(.4). >> >> See you changed that meanwhile, looks good WRT vc (and also the > Calligra >> master build), thanks :) >> >> But then there is still the following bummer: >> > > With that said: >> > > Calligra: (probably vc) >> > > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra >> > > %2 >> > > 0c alligra-2.9%20stable-qt4/10/ >> > >> > Yes, given so far no vc build completed, this seems to fail when trying to >> > get a built version of vc. Should work better once there is one :) >> > >> > Though there seems also another problem: commits to the "calligra/2.9" >> > branch are not triggering any builds of the qt4 stable build: >> > https://build.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligr >> > a-> 2.9%20stable-qt4/ >> > >> > That was not a problem in the old CI, but so far noone can tell what is >> > wrong now. Commits to the "frameworks" and "master" branches seem to >> > properly trigger builds of the respective build setups. Perhaps you might >> > have an idea? >> >> Anything where we could help with to solve this? The calligra/2.9 branch > is >> actually the hot branch these weeks still, main work is done there >> (especially the awesome Krita one), so not having CI as a reference up and >> working for this branch is a loss at the moment :) (see, CI is important to >> us :) so we appreciate your work even more) >> >> Cheers >> Friedrich > Ahh, I see I think maybe git hooks are missing? Ben can you look into this or > point me the way? The git hooks are in place, and as far as I can tell are working properly. Jenkins however is failing to detect the change as can be seen in the Git Polling log. Perhaps the workspaces for all calligra/2.9 builds needs to be removed from the build nodes? Or possibly could the removal be the cause of this? Alternatively, it might be the / in the branch name causing the problem. > Thanks! > Scarlett Cheers, Ben
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On Friday, May 01, 2015 12:56:26 AM Friedrich W. H. Kossebau wrote: > Hi Scarlett, > > Am Mittwoch, 29. April 2015, 23:26:14 schrieb Friedrich W. H. Kossebau: > > Am Dienstag, 21. April 2015, 13:45:06 schrieb Scarlett Clark: > > > I know this is an external depend, but I have no experience with it. > > > Can maybe a calligra dev take a look, as they need it. > > > VC > > > https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linu > > > x, > > > co mpiler=gcc/2/console > > > > Please build only the 0.7.4 release of vc, tagged with "0.7.4". So not > > "master" or anything else. That would be for any builds of vc, in any > > group > > (vc does not use qt anyway). AFAIK only Calligra uses vc right now, and in > > all branches Calligra needs vc 0.7(.4). > > See you changed that meanwhile, looks good WRT vc (and also the Calligra > master build), thanks :) > > But then there is still the following bummer: > > > With that said: > > > Calligra: (probably vc) > > > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra > > > %2 > > > 0c alligra-2.9%20stable-qt4/10/ > > > > Yes, given so far no vc build completed, this seems to fail when trying to > > get a built version of vc. Should work better once there is one :) > > > > Though there seems also another problem: commits to the "calligra/2.9" > > branch are not triggering any builds of the qt4 stable build: > > https://build.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligr > > a-> 2.9%20stable-qt4/ > > > > That was not a problem in the old CI, but so far noone can tell what is > > wrong now. Commits to the "frameworks" and "master" branches seem to > > properly trigger builds of the respective build setups. Perhaps you might > > have an idea? > > Anything where we could help with to solve this? The calligra/2.9 branch is > actually the hot branch these weeks still, main work is done there > (especially the awesome Krita one), so not having CI as a reference up and > working for this branch is a loss at the moment :) (see, CI is important to > us :) so we appreciate your work even more) > > Cheers > Friedrich Ahh, I see I think maybe git hooks are missing? Ben can you look into this or point me the way? Thanks! Scarlett signature.asc Description: This is a digitally signed message part.
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
Hi Scarlett, Am Mittwoch, 29. April 2015, 23:26:14 schrieb Friedrich W. H. Kossebau: > Am Dienstag, 21. April 2015, 13:45:06 schrieb Scarlett Clark: > > I know this is an external depend, but I have no experience with it. > > Can maybe a calligra dev take a look, as they need it. > > VC > > https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linux, > > co mpiler=gcc/2/console > > Please build only the 0.7.4 release of vc, tagged with "0.7.4". So not > "master" or anything else. That would be for any builds of vc, in any group > (vc does not use qt anyway). AFAIK only Calligra uses vc right now, and in > all branches Calligra needs vc 0.7(.4). See you changed that meanwhile, looks good WRT vc (and also the Calligra master build), thanks :) But then there is still the following bummer: > > With that said: > > Calligra: (probably vc) > > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra%2 > > 0c alligra-2.9%20stable-qt4/10/ > > Yes, given so far no vc build completed, this seems to fail when trying to > get a built version of vc. Should work better once there is one :) > > Though there seems also another problem: commits to the "calligra/2.9" > branch are not triggering any builds of the qt4 stable build: > https://build.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligra-> > 2.9%20stable-qt4/ > > That was not a problem in the old CI, but so far noone can tell what is > wrong now. Commits to the "frameworks" and "master" branches seem to > properly trigger builds of the respective build setups. Perhaps you might > have an idea? Anything where we could help with to solve this? The calligra/2.9 branch is actually the hot branch these weeks still, main work is done there (especially the awesome Krita one), so not having CI as a reference up and working for this branch is a loss at the moment :) (see, CI is important to us :) so we appreciate your work even more) Cheers Friedrich
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
Hi Scarlett, great work with the update of the KDE CI, thank you for caring for that side of development :) 2 things where you asked for more help: Am Dienstag, 21. April 2015, 13:45:06 schrieb Scarlett Clark: > I know this is an external depend, but I have no experience with it. > Can maybe a calligra dev take a look, as they need it. > VC > https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linux,co > mpiler=gcc/2/console Please build only the 0.7.4 release of vc, tagged with "0.7.4". So not "master" or anything else. That would be for any builds of vc, in any group (vc does not use qt anyway). AFAIK only Calligra uses vc right now, and in all branches Calligra needs vc 0.7(.4). > With that said: > Calligra: (probably vc) > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra%20c > alligra-2.9%20stable-qt4/10/ Yes, given so far no vc build completed, this seems to fail when trying to get a built version of vc. Should work better once there is one :) Though there seems also another problem: commits to the "calligra/2.9" branch are not triggering any builds of the qt4 stable build: https://build.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligra-2.9%20stable-qt4/ That was not a problem in the old CI, but so far noone can tell what is wrong now. Commits to the "frameworks" and "master" branches seem to properly trigger builds of the respective build setups. Perhaps you might have an idea? Cheers Friedrich
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On 04/21/2015 03:08 PM, Albert Astals Cid wrote: El Dimarts, 21 d'abril de 2015, a les 23:42:36, Milian Wolff va escriure: On Tuesday 21 April 2015 13:45:06 Scarlett Clark wrote: kdev-crossfire: https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLA TF ORM=Linux,compiler=gcc/11/ kdev-php-formatter: https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4 /P LATFORM=Linux,compiler=gcc/10/console kdev-xtest: https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest %2 0master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console All of the above are unmaintained and should not run through CI until someone spends time on fixing their issues. They are all in playground as well. kdev-css: https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Lin ux ,compiler=gcc/5/console This one was easy and I fixed it. But in general, I don't think that adding all playground projects to the CI is a good idea, as many things in there are just historic artifacts. What we need is someone with some time to apply the life cycle policy and move those historic artifacts to unmaintained :) Cheers, Albert I have removed them from my job list, they probably should go through the above process pointed out by Albert. Scarlett Bye
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
El Dimarts, 21 d'abril de 2015, a les 23:42:36, Milian Wolff va escriure: > On Tuesday 21 April 2015 13:45:06 Scarlett Clark wrote: > > kdev-crossfire: > > https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLA > > TF ORM=Linux,compiler=gcc/11/ > > > > kdev-php-formatter: > > https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4 > > /P LATFORM=Linux,compiler=gcc/10/console > > > > kdev-xtest: > > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest > > %2 0master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console > > All of the above are unmaintained and should not run through CI until > someone spends time on fixing their issues. They are all in playground as > well. > > kdev-css: > > https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Lin > > ux ,compiler=gcc/5/console > > This one was easy and I fixed it. > > But in general, I don't think that adding all playground projects to the CI > is a good idea, as many things in there are just historic artifacts. What we need is someone with some time to apply the life cycle policy and move those historic artifacts to unmaintained :) Cheers, Albert > > Bye signature.asc Description: This is a digitally signed message part.
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On 04/21/2015 02:42 PM, Milian Wolff wrote: On Tuesday 21 April 2015 13:45:06 Scarlett Clark wrote: kdev-crossfire: https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLATF ORM=Linux,compiler=gcc/11/ kdev-php-formatter: https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4/P LATFORM=Linux,compiler=gcc/10/console kdev-xtest: https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest%2 0master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console All of the above are unmaintained and should not run through CI until someone spends time on fixing their issues. They are all in playground as well. kdev-css: https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Linux ,compiler=gcc/5/console This one was easy and I fixed it. But in general, I don't think that adding all playground projects to the CI is a good idea, as many things in there are just historic artifacts. Bye Hi, thanks for fixing that. I do not make the call on what goes in the CI. Everything kde-build-metadata/logical-module-structure will land in CI. Thanks, Scarlett
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On Tuesday 21 April 2015 13:45:06 Scarlett Clark wrote: > kdev-crossfire: > https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLATF > ORM=Linux,compiler=gcc/11/ > > kdev-php-formatter: > https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4/P > LATFORM=Linux,compiler=gcc/10/console > > kdev-xtest: > https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest%2 > 0master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console All of the above are unmaintained and should not run through CI until someone spends time on fixing their issues. They are all in playground as well. > kdev-css: > https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Linux > ,compiler=gcc/5/console This one was easy and I fixed it. But in general, I don't think that adding all playground projects to the CI is a good idea, as many things in there are just historic artifacts. Bye -- Milian Wolff m...@milianw.de http://milianw.de signature.asc Description: This is a digitally signed message part.
Re: branchGroup stable-qt4 Compile failures. Need dev assistance please.
On Tue, Apr 21, 2015 at 10:45 PM, Scarlett Clark wrote: > kaccount-integration: > > https://build-sandbox.kde.org/job/kaccounts-integration%20stable%20stable-qt4/PLATFORM=Linux,compiler=gcc/19/console There is no kaccounts-integration kde4/qt4 version and should not be. I've removed it from kde-build-metadata, please discard this job. Cheers -- Martin Klapetek | KDE Developer
branchGroup stable-qt4 Compile failures. Need dev assistance please.
I know this is an external depend, but I have no experience with it. Can maybe a calligra dev take a look, as they need it. VC https://build-sandbox.kde.org/job/vc%20master%20stable-qt4/PLATFORM=Linux,compiler=gcc/2/console With that said: Calligra: (probably vc) https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/calligra%20calligra-2.9%20stable-qt4/10/ k3b: Found Kcddb: but fails on include file: https://build-sandbox.kde.org/job/k3b%202.0%20stable-qt4/PLATFORM=Linux,compiler=gcc/14/console kamoso: https://build-sandbox.kde.org/job/kamoso%202.1%20stable-qt4/PLATFORM=Linux,compiler=gcc/12/console kdeconnect-kde: fails to find qjson header. I brought it in as a dep but I don't think it actually looks for it because it still fails (and not listed in the configure section). https://build-sandbox.kde.org/job/kdeconnect-kde%20kde4%20stable-qt4/PLATFORM=Linux,compiler=gcc/13/console kdenlive: Please tell me the correct qt4 branches. The ones in LMS were kf5 builds. kaccount-integration: https://build-sandbox.kde.org/job/kaccounts-integration%20stable%20stable-qt4/PLATFORM=Linux,compiler=gcc/19/console kdepim: can't find the supplied grantlee https://build-sandbox.kde.org/job/kdepim%20KDE-4.14%20stable-qt4/PLATFORM=Linux,compiler=gcc/12/console kdev-crossfire: https://build-sandbox.kde.org/job/kdev-crossfire%20master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/ kdev-css: https://build-sandbox.kde.org/job/kdev-css%201.7%20stable-qt4/PLATFORM=Linux,compiler=gcc/5/console kdev-php-formatter: https://build-sandbox.kde.org/job/kdev-php-formatter%20master%20stable-qt4/PLATFORM=Linux,compiler=gcc/10/console kdev-xtest: https://build-sandbox.kde.org/view/branchGroup%20stable-qt4/job/kdev-xtest%20master%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console kstars: https://build-sandbox.kde.org/job/kstars%20Applications-14.12%20stable-qt4/PLATFORM=Linux,compiler=gcc/11/console Thanks, Scarlett signature.asc Description: This is a digitally signed message part.
