Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[microTVM] Remove Arduino aot code #8869
[microTVM] Remove Arduino aot code #8869
Changes from all commits
a59f25c
69b01ac
3a36816
2e433f6
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Given these fixtures are only used as part of the tests in this folder, and
conftest
is meant for auto-registration or pytest configuration rather than to hold helpers and utils, could these be either moved fully intoconftest
as fixtures or the underlying function moved into a more suitably named file?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.
The scope fixture of
workspace_dir
varies from test to test (for example, test_arduino_workflowhas it at module scope), and I suspect tests with more complex
workspace_dirsetups will be added in the future. For that reason, I'd prefer to define
workspace_dirindividually in each test, but use the helper function
make_workspace_dir` to avoid code reuse. I've also added a comment to each of these functions to clarify it.That said, if you feel strongly I'm also open to other solutions, like defining multiple kinds of workspace dirs in
conftest
(e.g. amodule_scope_workspace_dir
,per_function_workspace_dir
, etc.).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.
Argh, I feel like I could've been clearer here, my apologies. My suggestion is not to have general functions in
conftest.py
but rather in a different file such as aworkspace.py
to include from the test. This means only pytest-specific things end up inconftest.py
, I have no issue with fixtures local to the test files which then use those functions.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.
Ah, that makes more sense. I like the idea of moving non-pytest code into a
workspace.py
, but I think that might be OOS for this PR. Definitely worth addressing in a follow up though!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.
Agreed, it'd be good to have the move isolated in another PR 👍
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.
i agree with @Mousius sentiment--let's place test_utils in a file called test_utils or similar. can be a follow-up PR.