You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this in #377 today, where I've pulled in a new version of taskgraph to pick up a helper function, but had the test task fail with an error that indicated an older version was being used.
In order to ensure that we always test with what we run on our infrastructure, we may want to consider moving Taskcluster unit testing to a separate target/task, and using the requirements from requirements.txt instead of poetry.lock.
The text was updated successfully, but these errors were encountered:
I noticed this in #377 today, where I've pulled in a new version of taskgraph to pick up a helper function, but had the
test
task fail with an error that indicated an older version was being used.Whenever
taskgraph
runs in CI, we use the version from https://github.com/mozilla/firefox-translations-training/blob/main/taskcluster/requirements.txt. When we run unit tests, we use whatever is in https://github.com/mozilla/firefox-translations-training/blob/main/poetry.lock.In order to ensure that we always test with what we run on our infrastructure, we may want to consider moving Taskcluster unit testing to a separate target/task, and using the requirements from
requirements.txt
instead ofpoetry.lock
.The text was updated successfully, but these errors were encountered: