The Git plugin picks up a change and shows the correct commit and the pipeline is launched. The job is very long running (35-ish hours), being the actual git test suite.
After the poll time expires, and Jenkins relaunches the job again reporting the same commit id - with the previous job from the day before still running. The poll configuration is (H H * * *). There are two executors in our standalone Jenkins environment.
We have been killing the second run.