You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this unit test we check that the template verison job status is canceled but we do not assert that the error is nil when in fact we timed out cancelling the job. Seems related to the low value (25ms) of ForceCancelInterval in coderdtest.NewProvisionerDaemon.
This tripped us up when in #3061, so filing a follow-up issue for this.
EDIT: see also coderd/TestPatchCancelWorkspaceBuild
The text was updated successfully, but these errors were encountered:
Two coderd unit tests (TestPatchCancelTemplateVersion/Success and TestPatchCancelWorkspaceBuild) implied erroneously that the job was canceled successfully.
This is not the case, as these unit tests do not include a Provision_Complete response in the input to the
echo provisioner. Now explicitly checking the job error and bumping the force cancel interval to be longer.
Fixes#3083.
In this unit test we check that the template verison job status is canceled but we do not assert that the error is nil when in fact we timed out cancelling the job. Seems related to the low value (25ms) of
ForceCancelInterval
incoderdtest.NewProvisionerDaemon
.This tripped us up when in #3061, so filing a follow-up issue for this.
EDIT: see also
coderd/TestPatchCancelWorkspaceBuild
The text was updated successfully, but these errors were encountered: