Skip to content

Commit a5329f1

Browse files
authored
Update how-to-debug-pipelines.md
1 parent 0ea2b37 commit a5329f1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/machine-learning/how-to-debug-pipelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ In this article, you learn how to debug and troubleshoot [machine learning pipel
2424
## Debug and troubleshoot in the Azure Machine Learning SDK
2525
The following sections provide an overview of common pitfalls when building pipelines, and different strategies for debugging your code that's running in a pipeline. Use the following tips when you're having trouble getting a pipeline to run as expected.
2626

27-
### Test scripts locally
27+
### Testing scripts locally
2828

2929
One of the most common failures in a pipeline is that an attached script (data cleansing script, scoring script, etc.) is not running as intended, or contains runtime errors in the remote compute context that are difficult to debug in your workspace in the Azure Machine Learning studio.
3030

@@ -44,7 +44,7 @@ Once you have a script setup to run on your local environment, it is much easier
4444
> Once you can verify that your script is running as expected, a good next step is running the script in a single-step pipeline before
4545
> attempting to run it in a pipeline with multiple steps.
4646
47-
### Debug scripts from remote context
47+
### Debugging scripts from remote context
4848

4949
Testing scripts locally is a great way to debug major code fragments and complex logic before you start building a pipeline, but at some point you will likely need to debug scripts during the actual pipeline run itself, especially when diagnosing behavior that occurs during the interaction between pipeline steps. We recommend liberal use of `print()` statements in your step scripts so that you can see object state and expected values during remote execution, similar to how you would debug JavaScript code.
5050

0 commit comments

Comments
 (0)