Thanks Pino, that explains it (nearly). I guess there is some magic to
extract autotests from Perl t/ dirs, but that is none of my business.
I still don't understand why it was only triggered on 26, but I guess
again that this has to do with dependencies in testing.
Anyway, it is a pain if one
In data domenica 27 dicembre 2020 11:03:52 CET, Norbert Preining ha scritto:
> Hi Graham,
>
> > If you are referring to the 'Test in progress' status for
> > systray-mdstat/1.1.0-1, then I think you just need to wait. Debian
> > CI's Pending Jobs page [1], shows it was requested on:
> >
Hi Graham,
> If you are referring to the 'Test in progress' status for
> systray-mdstat/1.1.0-1, then I think you just need to wait. Debian
> CI's Pending Jobs page [1], shows it was requested on:
> 2020-12-26 09:10:46 UTC | 23 hour(s) ago
Ok, then I don't get it:
* plasma-workspace does not
Hi Norbert
On Sun, 27 Dec 2020 at 09:39, Norbert Preining wrote:
> we are currently trying to get KDE/Plasma into testing, but it seems
> that the remaining pieces are stuck due to plasma-workspace not
> transitioning, which in turn is due to a stuck autotest on armhf
>
Dear Release Team,
we are currently trying to get KDE/Plasma into testing, but it seems
that the remaining pieces are stuck due to plasma-workspace not
transitioning, which in turn is due to a stuck autotest on armhf
https://qa.debian.org/excuses.php?package=plasma-workspace
>From my inspection
5 matches
Mail list logo
