lang-nno-x-ext-apertium
Last build: 22 days ago
Total Builds1
Last build 22 days ago
Success Rate100%
1 passed, 0 failed
Visibility public
Repository access
Recent Builds
1h 14m 43s
time-days-ago
1h 19m 5s
time-days-ago
1h 24m 0s
time-days-ago
1h 27m 36s
time-days-ago
1h 18m 49s
time-days-ago
34m 6s
time-days-ago
1h 39m 29s
time-days-ago
45m 54s
time-days-ago
46m 4s
time-days-ago
1h 7m 19s
time-days-ago
46m 15s
time-days-ago
1h 7m 45s
time-days-ago
docs: remove committed badge/test data (generated per build now)
docs/badgedata/, docs/testlogs/*.md, docs/typosreport/report*.json and the
legacy docs/report.json are regenerated on every main build and force-pushed
to the generated/docs-data branch, which the README badges and the /testlogs/
and /typosreport/ pages now read live over raw.githubusercontent.com. The
tracked copies go stale on every commit and add nothing; .gitignore (rev 335)
already keeps them out.
Kept: docs/testlogs/index.html and docs/typosreport/{bundle,global,index}.*
(page and viewer shells, not data).
54m 57s
time-days-ago
1h 8m 19s
time-days-ago
14s
time-days-ago
43m 58s
time-days-ago
1h 13m 44s
time-days-ago
Override lexicon.hfst build via GT_LEXICON_HFST_DEPS/_RECIPE, not a second rule
The shared src-morphology-dir-include.am / lexc-include.am (from
giella-core) define their own ".generated/lexicon.hfst:" rule, built via
hfst-lexc straight from GT_LEXC_ROOT/GT_LEXC_SRCS. Since automake keeps
both definitions in the generated Makefile and plain "last definition
wins", our own same-named rule here -- built from the Apertium subtree's
automorf.att.gz via hfst-substitute -- was silently losing every time:
only an "overriding recipe" warning, no error, so it went unnoticed.
lexicon.hfst has apparently been built from the near-empty root.lexc
fallback instead of the actual Apertium-derived lexicon.
giella-core >= 1.14.0 lets a language override this without a duplicate
rule definition: GT_LEXICON_HFST_DEPS/_RECIPE are read by the one, single
rule definition in lexc-include.am, set with `?=` there so a value set
here (in the normal "Local processing" section, same place this rule
already lived) is picked up instead of the generic default -- no need to
place anything after the includes, no more silent override race.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
54m 14s
time-days-ago
Merge commit '51ba41cfd9b5d481661c0d8e82d96776a472e7f6'
Inneheld oppdateringar frå Apertium frå dei siste to åra.
47s
time-days-ago
45m 42s
time-days-ago