As a stopgap for fixing the CI jobs we had to remove the usage of status.waitFor in the Docker integration tests. The reason for this is despite fixing how the filesystems were mounted for testing, any file changes inside of the container were not propagated back to the host filesystem. This means we could not check the status for any state change inside the test.
We need to figure out how to properly mount the filesystem between the host and the container filesystem to make sure that changes are propagated between both, and we need to update the test to use status.waitFor.
linear[bot]
commented
4 months ago
Specification
As a stopgap for fixing the CI jobs we had to remove the usage of
status.waitForin the Docker integration tests. The reason for this is despite fixing how the filesystems were mounted for testing, any file changes inside of the container were not propagated back to the host filesystem. This means we could not check the status for any state change inside the test.We need to figure out how to properly mount the filesystem between the host and the container filesystem to make sure that changes are propagated between both, and we need to update the test to use
status.waitFor.Additional context
Tasks