Test Parallel CI Jobs

[akarki2005]

Proposed Changes

This PR is to test running parallel jobs during the Update/Resolve Dependencies step within the CI config. Previously, this step was completed using one process, however taking advantage of parallelism has the potential to significantly reduce worst-case CI build time complexity, provided that doing so does not cause out-of-memory issues.

Note: Because this PR removes the dependency caching step to test different n values for parallel job builds, it is not intended to actually be merged in yet. Once testing is complete, the dependency caching step will be re-added.

Type of Change

(Write an X or a brief description next to the type or types that best describe your changes.)

Type	Applies?
🚨 Breaking change (fix or feature that would cause existing functionality to change)
✨ New feature (non-breaking change that adds functionality)
🐛 Bug fix (non-breaking change that fixes an issue)
🎨 User interface change (change to user interface; provide screenshots)
♻️ Refactoring (internal change to codebase, without changing functionality)
🚦 Test update (change that only adds or modifies tests)
📦 Dependency update (change that updates a dependency)
🔧 Internal (change that only affects developers or continuous integration)	X

Checklist

(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)

Before opening your pull request:

• I have performed a self-review of my changes.
  • Check that all changed files included in this pull request are intentional changes.
  • Check that all changes are relevant to the purpose of this pull request, as described above.
• [N/A] I have added tests for my changes, if applicable.
  • This is required for all bug fixes and new features.
• [N/A] I have updated the project documentation, if applicable.
  • This is required for new features.
• [N/A] If this is my first contribution, I have added myself to the list of contributors.
• [N/A] I have updated the project Changelog (this is required for all changes).

After opening your pull request:

• I have verified that the CircleCI checks have passed.
• I have requested a review from a project maintainer.

Questions and Comments

(Include any questions or comments you have regarding your changes.)

[coveralls]

Pull Request Test Coverage Report for Build 16bb2883-05d8-464b-816d-10cdb6d8f893

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 55.118%

---

Totals
Change from base Build c018e228-3ab9-4c76-bfc5-889c25b5f99e:	0.0%
Covered Lines:	2217
Relevant Lines:	3948

---

💛 - Coveralls

[akarki2005]

Hi @david-yz-liu , I've used this PR to conduct testing for running parallel jobs during the dependency resolution / build step. I documented my findings internally and will be sharing them in tomorrow's presentation. Overall, I found that running 4 jobs in parallel worked with no issues, and meaningfully reduced build time on a cache miss. With that being said, I'll close this PR since my previous merged PR (#1625) already set the -j flag to 4.