aws / aws/amazon-sagemaker-examples

title_of_your_product-Algorithm.ipynb failed CI

Open
#2,288 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
11k
Forks
7k
Avg merge
8h 29m
Merged PRs (30d)
8

Description

Link to the notebook:
https://github.com/aws/amazon-sagemaker-examples/blob/master/aws_marketplace/curating_aws_marketplace_listing_and_sample_notebook/Algorithm/Sample_Notebook_Template/title_of_your_product-Algorithm.ipynb

Error:

---------------------------------------------------------------------------
Exception encountered at "In [6]":
---------------------------------------------------------------------------
FileNotFoundError Traceback (most recent call last)
in
----> 1 training_data=sagemaker_session.upload_data(test_dataset, bucket=bucket, key_prefix='')
2 test_data=sagemaker_session.upload_data(test_dataset, bucket=bucket, key_prefix='')

/opt/conda/lib/python3.7/site-packages/sagemaker/session.py in upload_data(self, path, bucket, key_prefix, extra_args)
225
226 for local_path, s3_key in files:
--> 227 s3.Object(bucket, s3_key).upload_file(local_path, ExtraArgs=extra_args)
228
229 s3_uri = "s3://{}/{}".format(bucket, key_prefix)

/opt/conda/lib/python3.7/sit

[...]

FileNotFoundError: [Errno 2] No such file or directory: 'data/test/'

Contributor guide

Open the contributing guide

Research direction

Open aws_marketplace/curating_aws_marketplace_listing_and_sample_notebook/Algorithm/Sample_Notebook_Template/title_of_your_product-Algorithm.ipynb and begin with cell In [6], where the CI traceback occurs. Trace how test_dataset and the data/test/ path are supplied, then verify that the notebook completes CI without a FileNotFoundError.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, jupyter-notebook, python
Domain
ci-cd, machine-learning
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.