On Wed, Feb 16, 2022 at 8:20 AM [email protected] <[email protected]> wrote:
> Trying this out for the first time: > Ran 812 tests in 18.881s > OK (skipped=10) > > What does the "skipped" tell us and which ones are they? > "skipped" tells us that the test called self.skipTest(). The argument to skipTest tells why. Is this test routine what Travis runs? > I'm not sure. > And how will we be able to verify that everything works on the lowest > supported version of Python, since most devs won't be running, say, Python > 3.6? Who will be adding new tests and making sure they work as expected? > I run test-all with python 3.6 from time to time. > I suggest that the output should include the Leo version, branch, > changeset, OS, and date. Then the devs can easily copy and paste it > somewhere useful. > That could be done in a unit test. It might be worth doing. > I'm inclined to think that routine hand-off testing is valuable. If the > current invocation of Travis can't be straightened out, maybe there is > another workflow available? > I am quickly going crazy trying to disable the automatic python 3.6 test. I've revoked various TravisCI permissions, and TravisCI is *still* running tests and failing. I guess it's time for a break :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS0VvUzejXkBudsBcxrb%3DMF0evt1itEtvr0Zq98nc8N54g%40mail.gmail.com.
