WIP: add build debugging

[eisber]

trying to debug a build issue

[eisber]

/azp run

[github-actions]

Hey @eisber 👋!
Thank you so much for contributing to our repository 🙌.
Someone from SynapseML Team will be reviewing this pull request soon.

We use semantic commit messages to streamline the release process.
Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix.
This helps us to create release messages and credit you for your hard work!

Examples of commit messages with semantic prefixes:

• fix: Fix LightGBM crashes with empty partitions
• feat: Make HTTP on Spark back-offs configurable
• docs: Update Spark Serving usage
• build: Add codecov support
• perf: improve LightGBM memory usage
• refactor: make python code generation rely on classes
• style: Remove nulls from CNTKModel
• test: Add test coverage for CNTKModel

To test your commit locally, please follow our guild on building from source.
Check out the developer guide for additional guidance on testing your change.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov-commenter]

Codecov Report

Merging #1914 (e5ae2a5) into master (469445b) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1914      +/-   ##
==========================================
- Coverage   86.80%   86.72%   -0.08%     
==========================================
  Files         301      301              
  Lines       15621    15621              
  Branches      821      821              
==========================================
- Hits        13560    13548      -12     
- Misses       2061     2073      +12     

see 3 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[eisber]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[eisber]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).