Re: [jdt-dev] Fwd: [eclipse-jdt/eclipse.jdt.core] Run failed: Publish Un

[Stephan Herrmann <stephan.herrmann@xxxxxxxxx>]

Let's do the forensics:

The workflow file unit-tests.yml 
<https://github.com/eclipse-jdt/eclipse.jdt.core/blob/master/.github/workflows/unit-tests.yml> 
was created on 2023-04-17 and hasn't been changed since.

The first of those (constantly failing) workflows ran on 2023-07-28.

That's when Mickael started to work on ci.yml, first in a PR, then when 
that was merged every commit to master (i.e., every merge of a PR) 
started triggering both these workflows. So unit-tests.yml only became 
effective when ci.yml was added.

Sometimes, the same commit triggers more than one run of the workflow, e.g.:

  #25 
https://github.com/eclipse-jdt/eclipse.jdt.core/actions/runs/6195748998
  #24 
https://github.com/eclipse-jdt/eclipse.jdt.core/actions/runs/6195338053

Wait, when you drill into one of the failures (across several levels) 
than you'll see:

Traceback (most recent call last):
File "/action/publish_test_results.py", line 529, in <module>
settings = get_settings(options, gha)
File "/action/publish_test_results.py", line 389, in get_settings
with open(event, 'rt', encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'artifacts/Event 
File/event.json'

Does anyone know about these things and you to fix or at least silence it?

BTW, Are others receiving those emails, too?


On 18.09.23 23:25, Roland Grunberg wrote:
> On Mon, 2023-09-18 at 21:28 +0200, Stephan Herrmann via jdt-dev wrote:
> > What is a mail like this trying to tell me and where do I get
> > additional
> > information, on what failed and where?
> >
> > Yes, I can recognize the commit ID, which I recently merged, after
> > github signalled all checks are green.
> When I look at
> https://github.com/eclipse-jdt/eclipse.jdt.core/actions/runs/6216200378
> , I see
>
> https://github.com/eclipse-jdt/eclipse.jdt.core/commit/92fba491e94bf1c3dc79f0014aedb3e75896a9ac
>
> as the commit associated with that. When looking at the checks for the
> commit, they all seem to pass, so I'd guess it's not configured to run
> on a pull/push to the repo. Looking at :
>
> https://github.com/eclipse-jdt/eclipse.jdt.core/actions/workflows/unit-tests.yml
> https://github.com/eclipse-jdt/eclipse.jdt.core/blob/master/.github/workflows/unit-tests.yml
>
> it hasn't ever passed so maybe it just hasn't been configured correctly
> or the JDT Core tests aren't publishing something that the job requires
> to properly report the results.