Eric said:
> I've never tried do describe that kind of testing because it's not easy to
> tell people without prior experience running the clients what a success/
> failure indication looks like. Of course alarm bells would go off on a
> crash, but the most definite thing I could say otherwise is
Hal Murray :
>
> e...@thyrsus.com said:
> > Alas, the client tools are difficult ebnough to test-jig that I have to
> > hand-test under Python 3 before releases. I have a routine for this and I
> > assume Ian does as well.
>
> How much testing do you do by hand? Is that written down anyplace?
e...@thyrsus.com said:
> Alas, the client tools are difficult ebnough to test-jig that I have to
> hand-test under Python 3 before releases. I have a routine for this and I
> assume Ian does as well.
How much testing do you do by hand? Is that written down anyplace? Should
it be on the relea
Hal Murray via devel :
> >From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort of testing is that? How do I run it on my setup?
A
On Tue, Mar 20, 2018 at 09:03:45PM -0700, Hal Murray via devel wrote:
> What sort of testing is that? How do I run it on my setup?
Our Gitlab CI runs the builds and all of our python tests using python3 (using
the latest python3 from docker) on every build. See
https://gitlab.com/NTPsec/ntpse
Yo Hal!
On Tue, 20 Mar 2018 21:03:45 -0700
Hal Murray via devel wrote:
> From packaging/packaging.txt
>
> > The shebang lines in our Python scripts point to
> > "python". Part of our standard tests check that
> > you can change that to "python3" without breaking
> > anything.
>
> What sort
>From packaging/packaging.txt
> The shebang lines in our Python scripts point to
> "python". Part of our standard tests check that
> you can change that to "python3" without breaking
> anything.
What sort of testing is that? How do I run it on my setup?
--
These are my opinions. I hate spam