Hi Ben
I don't know if this is on you radar or not, but here goes.
I have noticed that quite a few of the KDevelop unittests are failing on
the Windows CI.
Running the tests locally they work fine.
If I look at the output of the failing tests it is similar to that pasted
below.
Searching
On Wed, Aug 22, 2018 at 2:36 AM Morten Volden wrote:
>
> Hi Ben
Hi Morten,
>
> I don't know if this is on you radar or not, but here goes.
>
> I have noticed that quite a few of the KDevelop unittests are failing on the
> Windows CI.
>
> Running the tests locally they work fine.
>
> If I look
Hi all,
Final call for objections or queries for this change - i'll be looking
to roll this out this weekend.
Note: Plasma and KDevelop, i'm not subscribed to your lists so please
ensure i'm in CC for any responses.
Cheers,
Ben
On Tue, 14 Aug 2018, 17:09 Christoph Feck, wrote:
> On 14.08.2018 15:03, Ben Cooksley wrote:
> > Currently CI jobs are all created within a flat namespace, meaning
> > that it is quite difficult to view the overall status of an individual
> > project. Additionally, it creates the issue that the
On 14.08.2018 15:03, Ben Cooksley wrote:
Currently CI jobs are all created within a flat namespace, meaning
that it is quite difficult to view the overall status of an individual
project. Additionally, it creates the issue that the main default view
can take a significant amount of time to load.
On mardi 14 août 2018 15:03:42 CEST Ben Cooksley wrote:
> Hi all,
>
> Currently CI jobs are all created within a flat namespace, meaning
> that it is quite difficult to view the overall status of an individual
> project. Additionally, it creates the issue that the main default view
> can take a
Hi all,
Currently CI jobs are all created within a flat namespace, meaning
that it is quite difficult to view the overall status of an individual
project. Additionally, it creates the issue that the main default view
can take a significant amount of time to load.
To resolve this we intend to
