-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for train-vocab
#123
Conversation
I discovered that these artifacts are not actually published right now. The pipeline script wants a prefix, not a directory.
As with the previous `merge-corpus`, this is a pretty straightforward step. It's solely downstream of `merge-corpus`, and takes one parameter from the action input.
# 2) input files | ||
- >- | ||
export BIN=$MOZ_FETCHES_DIR && | ||
$VCS_PATH/pipeline/clean/merge-corpus.sh | ||
artifacts | ||
artifacts/corpus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the /corpus
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is that a directory?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a prefix of the artifacts from the merge-corpus
step. (The spm-train.sh
scripts wants a prefix which it appends some suffixes too.)
$VCS_PATH/pipeline/train/spm-vocab.sh | ||
fetches/corpus.{src_locale}.zst | ||
fetches/corpus.{trg_locale}.zst | ||
artifacts/vocab.spm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not artifacts/<something>/vocab.spm
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could do that, yeah, although it might be a bit annoying for downstream steps (we'd end up with an extra directory in the artifact path). I'm good either way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nah, I see the prefix above is not a directory
This is a much more straightforward pipeline step addition - mostly just the usual pipeline script tweaks and a new kind. The only notable parts are:
merge-corpus
artifacts (whoops)My latest test run in staging can be found at https://firefox-ci-tc.services.mozilla.com/tasks/FxbqwlALQ0uIQaNUkKOL1w.