-
Notifications
You must be signed in to change notification settings - Fork 48
feat: port taskgraph action from gecko_taskgraph
#645
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
Conversation
0375acd to
688ca43
Compare
taskgraph action from gecko_taskgraphtaskgraph action from gecko_taskgraph
ahal
left a comment
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.
Thanks!
|
Marking this back as a draft as after talking to @hneiva about it, I discovered that there were indeed a few tests in |
The documentation already says `You can generate actions.json locally by running taskgraph actions.` however that command was never ported over from gecko's `./mach taskgraph actions`
To be able to test without relying on actions that are always generated too much, I monkeypatch `registry._load` so it simply doesn't import the modules registering those actions. Adding that test found that parameters should be parsed with `strict=False` to match other CLI actions. The return value isn't strictly necessary but I added it to be consistent with other functions in the CLI.
688ca43 to
49ec488
Compare
|
Ah great, something is leaving the test env dirty.
|
|
Ah yeah, I see taskgraph/test/test_actions_registry.py Line 101 in 5200e65
The modules declaring the actions get imported, the actions registered. Later when the second test runs, it mocks the |
Otherwise a previous test might have imported the actions modules already, making `registry._load` a no-op and failing the test
hneiva
left a comment
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.
LGTM!
The documentation already says
You can generate actions.json locally by running taskgraph actions.however that command was never ported over from gecko's./mach taskgraph actions