[BUGFIX] Fixing integration test failures.

[alexsherstinsky]

Scope

We have had consistent failures from two tests involving image processing. Through troubleshooting, the cause was determined to be the running out of storage space on the test host Linux machine in GitHub actions. The fixes are:

1. Improve error handling in Carton utilities module.
2. Add GitHub Action steps to clean out unneeded storage space.

Code Pull Requests

Please provide the following:

• a clear explanation of what your code does
• if applicable, a reference to an issue
• a reproducible test for your PR (code, config and data sample)

Documentation Pull Requests

Note that the documentation HTML files are in docs/ while the Markdown sources are in mkdocs/docs.

If you are proposing a modification to the documentation you should change only the Markdown files.

api.md is automatically generated from the docstrings in the code, so if you want to change something in that file, first modify ludwig/api.py docstring, then run mkdocs/code_docs_autogen.py, which will create mkdocs/docs/api.md .

[github-actions]

Unit Test Results

  6 files  ±0    6 suites  ±0   14m 29s ⏱️ ±0s
12 tests ±0    9 ✔️ ±0    3 💤 ±0  0 ❌ ±0 
60 runs  ±0  42 ✔️ ±0  18 💤 ±0  0 ❌ ±0 

Results for commit 9e5b5cd. ± Comparison against base commit e0f112c.

♻️ This comment has been updated with latest results.

[arnavgarg1]

Is the python version bump strictly necessary?

[alexsherstinsky]

@arnavgarg1 It is not; I just felt that testing on the latest -- if all tests pass -- would be better. What do you think?

[arnavgarg1]

Fair enough!

[justinxzhao]

This is a lovely change -- thank you!

[arnavgarg1]

Is it possible to use the logging directory here? Or do we actually need to write to sys stderr when we're raising it through the ValueError anyway?

[alexsherstinsky]

@arnavgarg1 I was thinking of showing these messages on the screen, so that in GitHub log review, we can see exactly what went wrong. We could create a directory, but that might hide the failure error messages. It was very challenging to troubleshoot even this one, because the code is wrapping Rust. Happy to discuss, of course. Thanks!