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
The infra build out problem has now been fixed, which has uncovered failures in the test suites. These all seem to be related to stopping a job:
Failed
=== RUN TestE2E/Namespaces/*namespaces.NamespacesE2ETest/TestNamespacesFiltering
namespaces.go:183:
Error Trace: namespaces.go:183
Error: Received unexpected error:
command nomad [job stop -namespace NamespaceA test-namespace-ac40f329] failed: exit status 1
Output: ==> 2022-02-01T05:36:20Z: Monitoring evaluation "2043867f"
2022-02-01T05:36:20Z: Evaluation triggered by job "test-namespace-ac40f329"
==> 2022-02-01T05:36:21Z: Monitoring evaluation "2043867f"
2022-02-01T05:36:21Z: Evaluation within deployment: "959243a3"
2022-02-01T05:36:21Z: Evaluation status changed: "pending" -> "complete"
==> 2022-02-01T05:36:21Z: Evaluation "2043867f" finished with status "complete"
==> 2022-02-01T05:36:21Z: Monitoring deployment "959243a3"
2022-02-01T05:36:21Z
ID = 959243a3
Job ID = test-namespace-ac40f329
Job Version = 0
Status = cancelled
Description = Cancelled because job is stopped
Deployed
Task Group Desired Placed Healthy Unhealthy Progress Deadline
group 1 1 0 0 2022-02-01T05:46:17Z
Test: TestE2E/Namespaces/*namespaces.NamespacesE2ETest/TestNamespacesFiltering
Messages: could not stop job in namespace
Some investigation has found that #11550 changed the way in which deployment monitoring reports to the CLI, particularly when running job stop. When stopping a job, the deployment becomes cancelled because the job is stopped, and therefore exits with code 1 on the CLI. This will be discussed internally so we can come up with the correct solution.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
The infra build is currently failing:
The text was updated successfully, but these errors were encountered: