flake: cli Test_Tasks/delete_task

[mtojek]

Spotted while running a standard CI job:

=== FAIL: cli Test_Tasks/delete_task (0.44s)
    clitest.go:75: invoking command: coder --global-config /var/folders/lf/wbx6llps6z37wkfpk85_942m0000gn/T/Test_Tasksdelete_task1504307573/001 exp task delete funny-nobel233 --yes
    exp_task_test.go:143: 
        	Error Trace:	/Users/runner/work/coder/coder/cli/exp_task_test.go:143
        	Error:      	Received unexpected error:
        	            	running command "coder exp task delete": delete task "naughty-gagarin8-zJ3/funny-nobel233":
        	            	    github.com/coder/coder/v2/cli.(*RootCmd).taskDelete.func1
        	            	        /Users/runner/work/coder/coder/cli/exp_task_delete.go:75
        	            	  - DELETE http://127.0.0.1:50142/api/experimental/tasks/naughty-gagarin8-zJ3/e3e442e4-03f4-4287-9814-4cc170c9034c: unexpected status code 500: Failed to delete task
        	            		Error: sql: no rows in result set
        	Test:       	Test_Tasks/delete_task
    --- FAIL: Test_Tasks/delete_task (0.44s)

[ethanndickson]

Spotted again after the previously merged fix (as indicated by the test case: log lines) : https://github.com/coder/coder/actions/runs/19283967689/job/55140706328

[ethanndickson]

Erroneously closed, reopening

[flake-investigator]

Recurrence observed in main CI today.

• CI run: https://github.com/coder/coder/actions/runs/20065288831
• Failing job: test-go-pg (macos-latest) (run_attempt=1)
• Commit: ce9e7ad90927e0f6d0ab0f212e4a55a21998d42d by Spike Curtis

Error excerpt:

=== FAIL: cli Test_Tasks (16.08s)
    task_test.go:141: 
        Error: running command "coder task delete": delete task "boring-goldstine3-13s/upbeat-buck184":
          - DELETE http://127.0.0.1:50625/api/v2/tasks/boring-goldstine3-13s/07392660-31d4-486b-80b8-83cc238a05f8: unexpected status code 500: Failed to delete task
            Error: sql: no rows in result set

Classification: Flaky test (delete endpoint intermittently returns 500 with "sql: no rows in result set").

Additional checks:

• No data race indicators ("WARNING: DATA RACE") found in logs.
• No panic/OOM signatures observed.

Linking here for tracking; let me know if more log context is helpful.