Closed clackary closed 9 months ago
Thanks for the report - It's basically a regression after https://github.com/ordo-one/package-benchmark/pull/166 was merged, it was partially addressed for check/update/compare operations in https://github.com/ordo-one/package-benchmark/pull/211 - but for the simple iterative use case attached here it won't fail.
I believe it should though, so will make a fix such that any error is always propagated up (but as desired by #166 the rest of the benchmarks will still be run, I believe it was one of your colleagues that asked for that :-) ).
Will be fixed in related PR #231, also see https://github.com/apple/swift-package-manager/issues/7380 which disallows disambiguation between regressions/improvements unfortunately.
Thanks @hassila!
We had some benchmarking jobs in CI happily succeeding, but after looking at the logs, it was immediately evident that some benchmark cases were crashing. CI was receiving its zero exit code from the benchmark plugin, even after logging non-zero exit codes somewhere down the line.
I was able to reproduce this behavior in a blank package with the following benchmark case...
Running benchmark plugin does log error messages, but returns 0. Also noting there's a message with
error code [5]
, but I'm not sure where that comes from.Running benchmark executable directly returns non-zero exit code.
I would have expected benchmark plugin to surface some kind of non-zero exit code to indicate a failure. Is this behavior intended?