You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "pnowojski (via GitHub)" <gi...@apache.org> on 2023/02/03 08:17:18 UTC
[GitHub] [flink-benchmarks] pnowojski commented on pull request #63: [FLINK-27571][benchmark] Recognize 'less is better' benchmarks in regression detection script
pnowojski commented on PR #63:
URL: https://github.com/apache/flink-benchmarks/pull/63#issuecomment-1415315092
Have you noted that since a couple of weeks, codespeed is reporting regression/improvement colors incorrectly? http://codespeed.dak8s.net:8000/changes/ today for example 18% improvement in the sortedOneInput is reported as a regression. Does it have something to do with the lessisbetter changes? Do you know if something has changed in this area? I'm not sure, but I vaguely remember that there might have been a bug in the codespeed, that if even one benchmark is marked as "lessisbetter", all benchmarks will be treated this way.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org