CI fails with no output #1

ISSOtm commented 2025年11月16日 22:56:24 +01:00

Example: https://codeberg.org/ISSOtm/eldred.fr/actions/runs/2/jobs/0/attempt/2

The first attempt was in the current configuration, the second one with the DNS records altered to ALIAS grebedoc.dev. The lack of any error output are not giving me much to work off of... what's going on?

Note that, even with the current DNS records, this Works On My MachineTM:

% ~/go/bin/git-pages-cli https://eldred.fr --password $PASSWORD --upload-dir public --server grebedoc.dev
result: no-change
(archive)

Example: https://codeberg.org/ISSOtm/eldred.fr/actions/runs/2/jobs/0/attempt/2 The first attempt was in the current configuration, the second one with the DNS records altered to `ALIAS grebedoc.dev`. The lack of any error output are not giving me much to work off of... what's going on? Note that, even with the current DNS records, this Works On My MachineTM: ```console % ~/go/bin/git-pages-cli https://eldred.fr --password $PASSWORD --upload-dir public --server grebedoc.dev result: no-change (archive) ```

whitequark commented 2025年11月16日 23:01:51 +01:00

OK, this is my fault..-ish.

The behavior is indeed incredibly confusing. Here is where the error ends up:

image

(Please don't ask me how I came to know this. It was not a joyful journey. It's actually a general thing: if you ever see no output from a Forgejo Action, look at the next or final step.)

OK, this is my fault..-ish. The behavior is indeed incredibly confusing. Here is where the error ends up:  (Please don't ask me how I came to know this. It was not a joyful journey. It's actually a general thing: if you ever see no output from a Forgejo Action, look at the next or final step.)

whitequark commented 2025年11月16日 23:03:38 +01:00

As for why this happens: though I'm not aware of any specification or documentation for this, it seems that Forgejo Actions runner will cache action checkouts and then just not update branch references in those cached checkouts, so you end up with a somewhat arbitrary commit that doesn't get updated. Try using https://codeberg.org/git-pages/action@5363f77926c0c1aa61fbe41ea729fe6ca349f8f2.

As for *why* this happens: though I'm not aware of any specification or documentation for this, it seems that Forgejo Actions runner will cache action checkouts and then just not update branch references in those cached checkouts, so you end up with a somewhat arbitrary commit that doesn't get updated. Try using `https://codeberg.org/git-pages/action@5363f77926c0c1aa61fbe41ea729fe6ca349f8f2`.

whitequark commented 2025年11月17日 07:14:24 +01:00

Update: try using https://codeberg.org/git-pages/action@v1.0.0.

Update: try using `https://codeberg.org/git-pages/action@v1.0.0`.

ISSOtm commented 2025年11月17日 08:08:52 +01:00

It worked! Thank you very much ^^

Please don't ask me how I came to know this. It was not a joyful journey.

Relatable, I've been through my own cursed journeys too 🫡

[It worked](https://codeberg.org/ISSOtm/eldred.fr/actions/runs/3/jobs/0/attempt/1)! Thank you very much ^^ > Please don't ask me how I came to know this. It was not a joyful journey. Relatable, I've been through my own cursed journeys too 🫡