-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fixes transform.ipynb and adds notebook testing #3497
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
fdcb5aa
to
9cefe90
Compare
87976f0
to
aa666ca
Compare
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.
Yes please
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.
Approved, but please add more comments and explanation about the new test.
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. |
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 think we need more information about this, for people who follow in this footsteps and try to modify / augment this in the future.
Something akin to the PR description would be useful.
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.
Oh, I'll add that in then!!! Agreed on instructions - I think we should add something in the Development.MD as well!
Fixes a missing import statement from transform.ipynb, also, adds notebook tests.
The notebook tests run in parallel and each of them in their own virtual env, ensuring that the
pip install
statements work well. This mirrors how the tests are run on devsite pipelines as well. Hopefully we can catch errors faster this way!Follow-up potentials:
I tested treebeard (#3504) github action, and finally settled on rolling my own driver with an executor. For executor I chose papermill as it simply worked just fine with xdist. Though probably I could use treebeard (?) - not sure what the benefit would be for individual notebook execution.
jupyter nbconvert --execute
didn't seem to executepip installs
? But I haven't gone too deep in that direction.Fixes #2711.