"Failed to run dartdoc" shows empty output

[Komposten]

My package public_suffix has lost 10 points because dartdoc failed to run in the latest analysis. When I check the score page it says "Running dartdoc failed with the following output" but no output is provided:

[sethloco]

I had the same issue (es_compression) which seemed to happen around the time of the recent pub.dev outage. Of course, this is just a guess.

However, I did a small update to pub.dev just a moment ago and it seems to be fixed

[Komposten]

Yeah, it probably fixes itself when the analysis is run again so I'm not too worried about that. It's just that the output probably should say something (whether it is actual dartdoc output or that the request to run the command failed or whatever). 🙂

[sethloco]

Your absolutely right...empty error output indicates there is probably some room to improve:)

[tiloc]

Same thing here for my just published package "faiadashu". No indication of a general outage. Also happens to colleagues of mine on a regular basis with their packages. I assumed it was because their package is huge (>10k files), but mine is very compact and it still happens.

[isoos]

In case of faiadashu the log has an indication that no content was detected in the output: https://pub.dev/documentation/faiadashu/latest/log.txt

Not sure why that would be, the package looks fine otherwise, I'll investigate a bit more.

[isoos]

Further investigation revealed that we have a few edge cases where we don't expose the fact that the process was timed out.
I agree, package:faiadashu seems to be small, and dartdoc seems to run much longer on it than similarly sized packages. We've started to collect some metrics over all the pub.dev packages, maybe it will expose a pattern there...