Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

e2e: RescheduleE2ETest/TestDefaultReschedule is failing #19076

Closed
shoenig opened this issue Nov 13, 2023 · 0 comments · Fixed by #19105
Closed

e2e: RescheduleE2ETest/TestDefaultReschedule is failing #19076

shoenig opened this issue Nov 13, 2023 · 0 comments · Fixed by #19105
Assignees
@tgross
Labels
theme/e2e type/bug
Milestone
1.7.0

Comments

@shoenig
Copy link
Member

shoenig commented Nov 13, 2023

https://github.com/hashicorp/nomad-e2e/actions/runs/6845894866/job/18611827943

=== RUN   TestE2E/Rescheduling/*rescheduling.RescheduleE2ETest/TestDefaultReschedule
    rescheduling.go:101: 
        	Error Trace:	/home/runner/actions-runner/_work/nomad-e2e/nomad-e2e/nomad/e2e/rescheduling/rescheduling.go:101
        	Error:      	Received unexpected error:
        	            	alloc status check failed: got []string{"failed", "pending", "pending", "failed"}
        	            	allocs: []map[string]string{
        	            	    {"Created":"2023-11-13T05:55:36Z", "Desired":"run", "Eval ID":"38db7112-b05a-326f-c59d-b5667f9162ed", "ID":"76f97e53-9e34-ac58-04f9-1cf70cd0cac3", "Modified":"2023-11-13T05:55:38Z", "Node ID":"b12ca997-c368-5805-044c-9272109752fc", "Node Name":"ip-172-31-95-44", "Status":"failed", "Task Group":"t", "Version":"0"},
        	            	    {"Created":"2023-11-13T05:55:06Z", "Desired":"run", "Eval ID":"d753dbba-54a0-ada5-b4d2-aa3d124fcf1d", "ID":"206bbee8-64c1-c724-7a13-ed836d76edec", "Modified":"2023-11-13T05:55:06Z", "Node ID":"2741b635-1ae5-7fe4-ce68-1a9f71de0eff", "Node Name":"ip-172-31-89-138", "Status":"pending", "Task Group":"t", "Version":"0"},
        	            	    {"Created":"2023-11-13T05:55:06Z", "Desired":"run", "Eval ID":"d753dbba-54a0-ada5-b4d2-aa3d124fcf1d", "ID":"2ef04887-c59f-d470-6c20-d0ce42608c44", "Modified":"2023-11-13T05:55:06Z", "Node ID":"2f61b196-f370-1a63-9f88-002745842f65", "Node Name":"ip-172-31-94-250", "Status":"pending", "Task Group":"t", "Version":"0"},
        	            	    {"Created":"2023-11-13T05:55:06Z", "Desired":"stop", "Eval ID":"d753dbba-54a0-ada5-b4d2-aa3d124fcf1d", "ID":"f4e94c4c-5b17-7405-ea04-40fd826433c1", "Modified":"2023-11-13T05:55:36Z", "Node ID":"26e14626-b4bd-5962-4fdb-5e402a44bea2", "Node Name":"ip-172-31-88-206", "Status":"failed", "Task Group":"t", "Version":"0"},
        	            	}
        	Test:       	TestE2E/Rescheduling/*rescheduling.RescheduleE2ETest/TestDefaultReschedule
        	Messages:   	should have exactly 3 failed allocs
@shoenig shoenig added this to the 1.7.0 milestone Nov 13, 2023
@tgross tgross mentioned this issue Nov 13, 2023
Closed
@tgross tgross self-assigned this Nov 15, 2023
@tgross tgross mentioned this issue Nov 16, 2023
Merged
tgross added a commit that referenced this issue Nov 16, 2023
@tgross
e2e: fix and modernize rescheduling test (#19105)
da61d27 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of #17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: #19076
This was referenced Nov 16, 2023
Merged
Merged
tgross added a commit that referenced this issue Nov 16, 2023
@tgross
e2e: fix and modernize rescheduling test (#19105)
a3b5de0 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of #17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: #19076
tgross added a commit that referenced this issue Nov 16, 2023
@tgross
e2e: fix and modernize rescheduling test (#19105)
820480c 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of #17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: #19076
tgross added a commit that referenced this issue Nov 16, 2023
@hc-github-team-nomad-core @tgross
e2e: fix and modernize rescheduling test (#19105) (#19107)
f2ade2e 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of #17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: #19076

Co-authored-by: Tim Gross <tgross@hashicorp.com>
tgross added a commit that referenced this issue Nov 16, 2023
@hc-github-team-nomad-core @tgross
e2e: fix and modernize rescheduling test (#19105) (#19106)
6f21977 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of #17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: #19076

Co-authored-by: Tim Gross <tgross@hashicorp.com>
nvanthao pushed a commit to nvanthao/nomad that referenced this issue Mar 1, 2024
@tgross @nvanthao
e2e: fix and modernize rescheduling test (hashicorp#19105)
79309a5 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of hashicorp#17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: hashicorp#19076
nvanthao pushed a commit to nvanthao/nomad that referenced this issue Mar 1, 2024
@tgross @nvanthao
e2e: fix and modernize rescheduling test (hashicorp#19105)
0da8ff0 
The E2E test suite for rescheduling had a few bugs:
* Using the command line to stop a job with a failing deployment returns a non-zero exit
  code, which would cause an otherwise passing test to fail.
* Two of the input jobs were actually invalid but were only correctly detected
  as such because of hashicorp#17342

This changeset also updates the whole test suite to move it off the v1
"framework". A few test assertions are also de-flaked.

Fixes: hashicorp#19076
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tgross tgross

Labels
theme/e2e type/bug
Projects
None yet
Milestone
1.7.0
Development

Successfully merging a pull request may close this issue.

e2e: fix and modernize rescheduling test hashicorp/nomad
2 participants
@shoenig @tgross