Error (failed with exit code 1) in GitHub Action check #3136
-
Observed behaviourAfter pushing the update, the files are not passing the Action check (Fontbakery CI — variable fonts and Fontbakery CI — static fonts)
Expected behaviour(Describe here what you expected to happen, or what you wish was different) Resources and exact process needed to replicateNot sure on that. Here is a link https://github.com/JetBrains/JetBrainsMono/actions |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
When your font project has some problem detected by FontBakery, the tool returns a non-zero error code which is often used by other tools such as the GitHub Actions infrastructure to detect that something went wrong. That's why you get a "broken build" in this case. This is the expected behaviour, it is not a bug. You should look at the GitHub Actions build log to get the full details on what are the problems that FontBakery detected in the latest commit of your font project repo. You will see some FAIL messages (highlighted in red), and maybe also some WARN messages (in yellow). You must address the FAIL ones and should at least consider what the WARN ones tell you. Here's one of those FAILs: As FontBakery development continues, we sometimes add new checks. So the fact that you did not get these messages before can have two different explanations: (1) you may have made changes to your font files that introduced a problem or (2) you may have had these problems already but was unaware of it and now FontBakery introduced a check that detects it. |
Beta Was this translation helpful? Give feedback.
-
You should be able to update these lines of your GitHub Actions workflows to include the exclusions:
The Font Bakery GitHub Action repo + docs are here: https://github.com/f-actions/font-bakery And the GitHub Action documentation is available here: https://docs.github.com/en/free-pro-team@latest/actions I made the first draft of the GH Action workflows on your repository and maintain the fontbakery GH Action. Let me know if you need a hand. |
Beta Was this translation helpful? Give feedback.
When your font project has some problem detected by FontBakery, the tool returns a non-zero error code which is often used by other tools such as the GitHub Actions infrastructure to detect that something went wrong. That's why you get a "broken build" in this case. This is the expected behaviour, it is not a bug.
You should look at the GitHub Actions build log to get the full details on what are the problems that FontBakery detected in the latest commit of your font project repo. You will see some FAIL messages (highlighted in red), and maybe also some WARN messages (in yellow). You must address the FAIL ones and should at least consider what the WARN ones tell you.
Here's one of those FAIL