Missatge de Xavi Ivars <xavi.iv...@gmail.com> del dia dv., 10 de des. 2021 a les 21:05:
> Actually, this has helped me already to identify two issues: > apertium-spa-cat and apertium-fra tests (using apertium-regtest) are broken. > > I'm pretty sure the contributors to those packages don't really know how > regtest works, and what needs to be done to fix those tests. > I am working on apertium-fra. Hopefully tomorrow it will be solved Hèctor > > Missatge de Xavi Ivars <xavi.iv...@gmail.com> del dia dv., 10 de des. > 2021 a les 18:53: > >> While playing this morning with some fixes on Apertium Apy, I added a >> Github Action to make sure tests were running and code coverage stats were >> pushed to Coveralls.io, and I really liked how Github Actions work. >> >> To better test the possibilities Github Actions gives us, I setup the >> same scripts we already had in TravisCI (not working now) on Github >> Actions, for apertium-spa, apertium-cat and apertium-spa-cat. >> >> And I found it's way more powerful, and we can do pretty cool things. >> >> This is what I've setup: >> >> *Apertium Github Actions repository [1]* >> >> This repository contains reusable workflows and actions, that can be >> referenced by other repository specific workflows. >> >> There are currently 2 workflows already implemented, one for monolingual >> [2] and another one for bilingual [3] modules. >> >> *Apertium Github repository [4] * >> >> This repository already existed, and was used to define Apertium's >> profile in Github. I've added there "workflow templates", what makes it >> extremely easy to setup a reusable workflows into an existing module. >> >> As an example, this is what would be required to setup the monolingual >> workflow in apertium-fra: >> >> 1. Go to actions tab >> 2. (In case workflows already exist) click on create new workflow >> 3. Scroll down, and select the appropriate workflow. In case of >> apertium-fra, it would be the monolingual >> >> [image: image.png] >> 4. In case of bilingual replace xxx-yyy, xxx and yyy with the language >> codes of your bilingual module, and the monolinguals. >> 5. DONE! Tests are integrated! >> >> >> >> References: >> [1] https://github.com/apertium/github-actions/tree/master >> [2] >> https://github.com/apertium/github-actions/tree/master#monolingual-buildyml >> [3] >> https://github.com/apertium/github-actions/tree/master#bilingual-buildyml >> [4] https://github.com/apertium/.github >> -- >> < Xavi Ivars > >> < http://xavi.ivars.me > >> > > > -- > < Xavi Ivars > > < http://xavi.ivars.me > > _______________________________________________ > Apertium-stuff mailing list > Apertium-stuff@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/apertium-stuff >
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
