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? Is this test routine what Travis runs? 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 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. 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? On Wednesday, February 16, 2022 at 8:53:19 AM UTC-5 Edward K. Ream wrote: > Imo, using TravisCI provides no significant testing benefits, slows the > commit process, and creates unnecessary (and confusing) distribution files. > > Instead, devs need only ensure that Leo's test-all command succeeds before > each commit. > > Two recent issues have severely tested my tolerance for TravisCI: > > 1. TravisCI creates leo.exe, which imo should be hidden but somehow got > documented here <https://leoeditor.com/download.html#standalone>. See > #2370 <https://github.com/leo-editor/leo-editor/issues/2370>. > > 2. Within the last several days, TravisCI has suddenly started rejecting > *all* commits, even those based on master, which hasn't changed in over a > month. See #2421 <https://github.com/leo-editor/leo-editor/issues/2421>. > > Folks, I think it's time to do without TravisCI. Your comments, please. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f41ed1e0-4c53-490a-9325-8984236060f1n%40googlegroups.com.
