Add Missing curl
Package to manual-test.yaml
as Dependency
#14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request addresses an issue in our GitHub Actions workflow where the R environment was missing the
curl
package, leading to a failure in the execution ofmanual-test.yaml
.Issue Description
During the execution of our GitHub Actions workflow, particularly in the "Generate data" step within
run-test-list.yaml
, we encountered an error indicating that thecurl
package was not installed. The error message was as follows:This issue was causing the workflow to halt prematurely, preventing the completion of our automated test suite.
Proposed Changes
To resolve this issue, I have added an additional command in the "Install dependencies" step of our
manual-test.yaml
workflow. This command explicitly installs thecurl
package in our R environment, ensuring that all necessary dependencies are available for our scripts.The updated section of the workflow file is as follows:
Impact
With the addition of the
curl
package, our automated testing workflow should now run without encountering the previous error. This will enable us to reliably generate and test data as part of our continuous integration process, ensuring the stability and reliability of our codebase.Testing
After making this change, the workflow should be re-run to verify that the "Generate data" step completes successfully without encountering the previous error. Taking into account the amount of errors we have been seeing in our
*.csv
files, I'm sure we'll get to encounter another errors after this.@infotroph Requesting a review on this pull request.