On 7/17/20 1:39 AM, Steve Langasek wrote:
> On Thu, Jul 16, 2020 at 06:24:11PM +0200, Matthias Klose wrote:
>
>> the new update_excuses hides the information for successful autopkg tests
>> which makes the page more compact. I dislike that when searching for
>> failed autopkg tests which failed
On Thu, Jul 16, 2020 at 06:24:11PM +0200, Matthias Klose wrote:
> the new update_excuses hides the information for successful autopkg tests
> which makes the page more compact. I dislike that when searching for
> failed autopkg tests which failed for some triggers, but succeeded with
> others.
On 6/16/20 7:07 PM, Iain Lane wrote:
> Over the last few weeks, I've been working on rebasing our extensive
> delta to proposed-migration. It's now at a state where it's ready for
> others to take a look at. Please check out the output from a dry-run
> (being re-run hourly from cron)
>
>
>
On Thu, Jul 02, 2020 at 04:53:48PM +0100, Iain Lane wrote:
> Just looking into that, but it will delay the rollout into next week.
All done, this is now live. Do let me know if anything looks wrong.
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer
On Tue, Jun 30, 2020 at 10:20:18AM +0100, Iain Lane wrote:
> I'm thinking that I'll make the cut over on Thursday UK time, so
> please have a look at the output before then and check your
> .yaml-parsing scripts against the new output (location changed since
> my initial post; it's now .xz
On Tue, Jun 16, 2020 at 06:07:09PM +0100, Iain Lane wrote:
> Over the last few weeks, I've been working on rebasing our extensive
> delta to proposed-migration. It's now at a state where it's ready for
> others to take a look at. Please check out the output from a dry-run
> (being re-run hourly
Hey Iain, thanks for the work!
Le 16/06/2020 à 19:07, Iain Lane a écrit :
> If you can see anything that's *wrong* in the output linked above,
> please let me know. If you run any scripts which parse the yaml, please
> try them against
>
>
>
On Tue, Jun 16, 2020 at 07:49:18PM +0100, Iain Lane wrote:
> I could maybe make a diff of subsets of the yaml, if that would be
> helpful. Perhaps even just a diff of the candidates, and then people
> can manually go back and inspect why something does or does not
> migrate when it didn't/did
On Wed, Jun 17, 2020 at 12:15:29AM +0100, Dimitri John Ledkov wrote:
> On Tue, 16 Jun 2020 at 19:23, Steve Langasek
> wrote:
> > Personally, my desire to manually review proposed-migration output is low :)
> > Is it possible to get diffs between the old and new output, over a few
> >
Hi Iain,
Personally, my desire to manually review proposed-migration output is low :)
Is it possible to get diffs between the old and new output, over a few
iterations, that we could review in order to identify any behavior changes?
On Tue, Jun 16, 2020 at 06:07:09PM +0100, Iain Lane wrote:
>
10 matches
Mail list logo
