Use AutoDoc to extract examples - #167
Conversation
|
@fingolfin Why "use AutoDoc to extract examples"? That might be fine for new packages, but for one that has been around for a long time and has tests and manual files in parallel (but not identical) it seems unnecessary. Is it optional? If so, how to get rid of it? |
I thought that PR #164 and #165 make it clear that it is necessary: humans make mistake, and are bad at keeping two different data sources in sync. They drift. As has happened here: this package had several outright broken examples in the manuals, that were not caught, because the tests did not carry the broken examples or carried variants without the breakage.
Of course it is optional: this is why xmod is not using it right now. But I think that's a mistake, for the reason explained above; and it is also very visible if you look into the failure logs. That said: I don't mind if you prefer to close this PR, as long as you merge the other PRs, so that at least those issues in the xmod documentation are fixed. If you prefer to keep the remaining issues unfixed, that's fine by me :-) |
d4da34f to
d804a0b
Compare
|
You have convinced me. 164,165,166 are now merged. Now trying to implement 167 locally, so I have added to makedoc.g the extract_examples := rec( subdir := "tst/manual" ) but, when I run makedoc.g, the tests xmodn.tst are not created. Is there something else to be added? |
d804a0b to
9ef1321
Compare
|
@cdwensley Hmm, hard to say without seeing your file. Did you add it in the right place? Which GAP version are you using? If you have and use the In the meantime, here are the first few errors, copied and paste from the CI logs here, with some comments by me interspersed: These two fail because the info level is not high enough (it probably is 0 but should be 1). These actually worked before I modified a test in one of the PRs by me you just merged: that test increased the info level to 1 but then "forgot" to decrease it again -- which is bad for this test, but it was necessary to fix a bunch of other tests. Two solutions come to mind (I am sure there are more)
The output of Some possible solutions:
This looks like it might be cause by some algorithms (in GAP?) now producing slightly different output. No idea what is going on here, that sounds like a genuine problem only you can figure out. Then after this, there are a ton of errors that are due to |
This contains PRs #164, #165, #166 and also will still produce errors. I recommend merging the other three PRs first, then this can be rebased, and further fixes be made.