googlefonts / googlefonts/fontc
Update CI to run fea-rs tests against more recent fonttools/python
- Dominant language
- Rust
- Stars
- 193
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 65
Description
In fact ideally we can just run the same version of python and feaLib that we use for ttx_diff, and that will give us a chance to catch any upstream changes that cause our output to deviate.
> we seem to have multiple inconsistent python-version in this file. Can we use the same one? Do we have to be so specific or can we say e.g. 3.13 and leave .x to setup?
_Originally posted by @rsheeter in https://github.com/googlefonts/fontc/pull/1804#discussion_r2603576024_
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test path is named. Start in the CI configuration by comparing the fea-rs test job with the ttx_diff job and their Python and feaLib versions; done means fea-rs tests run with the aligned, more recent versions and continue to pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100