Run flaky tasks locally?

[Owez]

Hi,

Is there a way to run flaky tasks locally? I get this popup on the cli:

But the link to https://nx.dev/ci/features/flaky-tasks seems to only advertise how to do it on Nx cloud. There should probably be docs on how it can be done locally, or why not if not. --verbose doesn't change the output.

[FrozenPandaz]

Hm, can you be more specific about what you expect to be the behavior locally? I think there's something here. but let's discuss more before to get a clearer idea of the expected behavior.

[Owez]

As an end-user, I'd like details on the details of what the flaky task was.

In my case finding this message, this general alarm for a flaky task did help me eventually find a strange async bug (it was only failing my ci) – but in this case I had to manually comment out tests until I found which one was doing it. Took a few hours 😄

I'd like to see more insight into what test/task is flaky (even if its low-level it helps, like some stacktrace/thread id), and maybe a "hint:" message which could help me resolve it? Linking to the docs are fine too, if they have some detail about it all.

[primeinc]

I always panic when something is intermittent - mine was dumb too, had a double execution of a hook script that would mess with the cache state - sometimes - in one package. I'm assuming if the tool itself knew exactly what caused it, it would happily tell you.

With that, my moltbot's words of wisdom

 Look for the same task running twice through different paths
 (nx dependencies in nx.json vs npm pre-hooks in package.json) 
 because the duplicate execution causes cache inconsistency.