For when the customer is syncing their job attachments, either while syncing the inputs, or the outputs, we need to make sure that the sync works as expected.
In particular, the functionalities that:
If an input file is not found, but the customer specified that all input paths should exist, we should fail the job submission, as this indicates that the customer likely forgot to save an input file
If there are no output files found in the output directory, the job should still pass. This path should not have any regressions in the line
What was the solution? (How)
Add two tests that test these functionalities
Also added a lot more typing to the tests file
What is the impact of this change?
Better code coverage of the current features in worker-agent.
How was this change tested?
# Linux
source .e2e_linux_infra.sh
hatch run linux-e2e-test
hatch run cross-os-e2e-test
Windows
source .e2e_windows_infra.sh
hatch run windows-e2e-test
hatch run cross-os-e2e-test
### Was this change documented?
No
### Is this a breaking change?
No
----
*By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.*
What was the problem/requirement? (What/Why)
For when the customer is syncing their job attachments, either while syncing the inputs, or the outputs, we need to make sure that the sync works as expected.
In particular, the functionalities that:
What was the solution? (How)
What is the impact of this change?
Better code coverage of the current features in worker-agent.
How was this change tested?
Windows
source .e2e_windows_infra.sh hatch run windows-e2e-test hatch run cross-os-e2e-test