This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
CI Check against tensorflow
include guard
#204
Merged
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.
Before submitting a pull request (PR), please read the contributing guide.
Description
What is this PR
Why is this PR needed?
Tests the include-guard that denies use of the tools when
tensorflow
is not available.What does this PR do?
Adds a short check to make sure that the
tensorflow
include guard is behaving itself onubuntu
andmacOS
.pip install -e .
should successfully fetchtensorflow
and allow import.tensorflow
is not installed, importing the module should fail. Conditions for this test are achieved by having pip uninstalltensorflow
.References
How has this PR been tested?
Locally running the commands produces the outcomes that are checked against.
New workflow has been introduced to check the results are as expected on CI.
Is this a breaking change?
No
Does this PR require an update to the documentation?
Checklist: