was on

commit 189c9336236459d0397e2d0bcb4467e4f5f8ca59
Author: Andreas Stenius <andreas.stenius@svenskaspel.se>
Date:   Sun Dec 12 19:38:46 2021 +0100

    Include `shell_source(s)` in `docker_image` build context. (#13761)
    
    Fixes #13756.

this worked fine:

./pants run build-support/bin/changelog.py -- --prior 2.9.0.dev3 --new 2.9.0.dev4

then pulled main, now on

commit 9762ff6b5dc8af8f9f6cf80e1c3b3d76ab3242fb (HEAD -> prep2.9.0.dev4, origin/main, main)
Author: Stu Hood <stuhood@gmail.com>
Date:   Mon Dec 13 09:55:47 2021 -0800

    [jvm] Use `immutable_inputs` to provide the compiletime classpath (#13862)

it seems stuck:

$ ./pants run build-support/bin/changelog.py -- --prior 2.9.0.dev3 --new 2.9.0.dev4
10:22:44.50 [INFO] Filesystem changed during run: retrying `Run` in 500ms...
10:22:47.80 [INFO] Filesystem changed during run: retrying `Run` in 500ms...
10:22:51.74 [INFO] Filesystem changed during run: retrying `Run` in 500ms...
10:22:58.61 [INFO] Filesystem changed during run: retrying `Run` in 500ms...
10:23:03.88 [INFO] Filesystem changed during run: retrying `Run` in 500ms...
10:23:08.81 [INFO] Filesystem changed during run: retrying `Run` in 500ms...

Not blocked for now, so just reporting.

@wide-energy-11069: what is in

.pants.d/pants.log

while it is reporting the filesystem changes?

https://gist.github.com/wisechengyi/12480710604dec4e9c876f3048bec3511 no worries

gist seems to be a broken link

my bad https://gist.github.com/wisechengyi/12480710604dec4e9c876f3048bec351

hm… seems like maybe it’s catching up to a very large branch switch

oh that could make sense. i’ve accidentally switch to ‘master’, which is very far from ‘main’ then switched back.