On Saturday, March 21, 2020 1:41:14 AM EDT Scott Kitterman wrote:
> On Wednesday, March 18, 2020 6:32:22 PM EDT Scott Kitterman wrote:
> > I'm currently reviewing some of the autopkgtest regressions that are
> > currently blocking python3-defaults with python3.8 as the default python3
> > from migr
On Wednesday, March 18, 2020 6:32:22 PM EDT Scott Kitterman wrote:
> I'm currently reviewing some of the autopkgtest regressions that are
> currently blocking python3-defaults with python3.8 as the default python3
> from migrating.
>
> With the current state of the environment being used for autop
On Thu, 19 Mar 2020 at 09:27:35 -0400, Scott Kitterman wrote:
> The fact that these tests are failing right now makes them relatively easy to
> find, but even if they weren't failing, I still think testing against
> installed
> versions is wrong. Tests should have an intentional scope, not act
On Thursday, March 19, 2020 6:40:00 AM EDT Simon McVittie wrote:
> On Wed, 18 Mar 2020 at 18:32:22 -0400, Scott Kitterman wrote:
> > We want the tests to run against all versions, but the way to do that is
> > to
> > have your test depend on python3-all (to make sure that all supported
> > versions
On Wed, 18 Mar 2020 at 18:32:22 -0400, Scott Kitterman wrote:
> We want the tests to run against all versions, but the way to do that is to
> have your test depend on python3-all (to make sure that all supported
> versions
> are installed) and then use the -s flag for py3versions vice -i. So (i
Hi all
On 18-03-2020 23:32, Scott Kitterman wrote:
> I'm currently reviewing some of the autopkgtest regressions that are
> currently
> blocking python3-defaults with python3.8 as the default python3 from
> migrating.
Thanks Scott for helping here (all help is welcome). I thought it might
be u
6 matches
Mail list logo
