On Saturday 09 May 2015 05:29:17 Scarlett Clark wrote:
> I aborted the stuck job already so it should be moving along.
Looks like many jobs get stuck.
Now it's kdelibs4support, which gets stuck in the OSX CI while running
kdebugtest:
https://build.kde.org/view/Frameworks%20kf5-qt5/job/kdelibs4
On Saturday, May 09, 2015 02:12:15 PM David Faure wrote:
> On Saturday 09 May 2015 04:49:52 Scarlett Clark wrote:
> > On Saturday, May 09, 2015 01:33:05 PM David Faure wrote:
> > > Hello,
> > >
> > > CI seems stuck again.
> > >
> > > I upgraded all version numbers yesterday, which triggered a reb
On Saturday 09 May 2015 04:49:52 Scarlett Clark wrote:
> On Saturday, May 09, 2015 01:33:05 PM David Faure wrote:
> > Hello,
> >
> > CI seems stuck again.
> >
> > I upgraded all version numbers yesterday, which triggered a rebuild of all
> > frameworks (as expected), and today these jobs are stil
On Saturday, May 09, 2015 01:33:05 PM David Faure wrote:
> Hello,
>
> CI seems stuck again.
>
> I upgraded all version numbers yesterday, which triggered a rebuild of all
> frameworks (as expected), and today these jobs are still running or
pending,
> it's like nothing has moved since yesterday
Hello,
CI seems stuck again.
I upgraded all version numbers yesterday, which triggered a rebuild of all
frameworks (as expected), and today these jobs are still running or pending,
it's like nothing has moved since yesterday evening.
See https://build.kde.org/view/Frameworks%20kf5-qt5/
--
Da
Hi Scarlett,
I’ve logged onto my VM as user jenkins, i.e. a GUI session is now available.
So you could run a test-build for a project which failed before on you.
Let me know how it goes.
Greets,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
On Saturday, May 02, 2015 08:36:02 PM David Faure wrote:
> On Saturday 02 May 2015 06:56:06 Scarlett Clark wrote:
> > This will be fixed when the builders free up so I can restart jenkins.
> > XDG*
> > is was not set. So things should improve after restart.
>
> Thanks. Did a restart happen by now
On Saturday 02 May 2015 06:56:06 Scarlett Clark wrote:
> This will be fixed when the builders free up so I can restart jenkins. XDG*
> is was not set. So things should improve after restart.
Thanks. Did a restart happen by now? I tried to kick a new kparts build to see
if it worked better, but .
On Saturday, May 02, 2015 10:20:27 AM David Faure wrote:
> KMainWindow_UnitTest::testDefaultName() Cannot create window: no screens
> available
Yes it is a CI issue. We connect to slaves via SSH and therefore GUI is not
available. I am not a Mac person so this requires the assistance of Mac folks
On Saturday, May 02, 2015 10:00:15 AM David Faure wrote:
> On my checklist before making a KF5 release:
> * Ensure that CI is green.
>
> What a surprise today CI is definitely not green!
> https://build.kde.org/view/Frameworks%20kf5-qt5/
>
> One thing is: Mac OSX was added, so many jobs are
On Saturday 02 May 2015 10:00:15 David Faure wrote:
> Ben, Scarlett: did something change in the setup? Is XDG_DATA_DIRS not
> pointing to the install dir of the framework anymore?
Similarly, shared-mime-info (found via XDG_DATA_DIRS on Linux) isn't found
anymore, breaking at least kparts and kic
On Saturday 02 May 2015 10:00:15 David Faure wrote:
> (*) On the Mac, many tests fail with "Cannot create window: no screens
> available". I think this is because they need a bundle, which can be done
> by adding GUI to the ecm_add_test call, see kxmlgui 9abace028 for an
> example.
Hmm, that's not
12 matches
Mail list logo
