Pat Brisbin

It does. And I would expect it to because `GNUPGPHOME` is set in my shell environment and nothing is clearing it (like `sudo` does when invoked via `update-aurto`).

> So I'm not sure if there are standard ways to do this. I _think_ there's a way to have it not be a root timer; the whole thing could...

> I guess I'm more interested in configurable env vars in general rather than just this one. Yeah, I hear you. I was just saying that (FWIW, IMHO) seems like...

Hi there- unfortunately, this issue makes this Action pretty unusable for us since the check run output is the only place our test suite failures are visible and when they...

Hmm, I can't say that I do. A lot of Actions add annotations to the Job's check where they're run, but they do it by outputting messages with a problem-matcher...

Awesome! > due to the check still being running at the time of updating the result, it won't keep the failure state for example Let me make sure I understand......

Wow, well that's super annoying. I wonder why that is :thinking:

I might be grasping at straws, but in your PR, it looks like the [Update](https://github.com/mikepenz/action-junit-report/pull/421/files#diff-4fab5baaca5c14d2de62d8d2fceef376ddddcc8e9509d86cfa5643f51b89ce3dR94) sets `{ output.conclusion }` while the [Create](https://github.com/mikepenz/action-junit-report/pull/421/files#diff-4fab5baaca5c14d2de62d8d2fceef376ddddcc8e9509d86cfa5643f51b89ce3dR109) sets `{ conclusion, output.* }`. Is it possible...

Ha, not unexpected in hindsight. I would say that when doing the update path you don't want `conclusion` at all -- you aren't intending to _conclude_ it right?

I wonder if the test's conclusion/output is somehow taking over as the "important one". So your annotations remain, but they get subdued in the UI once the test completes? Either...