You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2022/09/28 11:38:59 UTC

[GitHub] [lucene] mikemccand commented on issue #11827: Release manager should review lucene benchmarks before building release candidates

mikemccand commented on issue #11827:
URL: https://github.com/apache/lucene/issues/11827#issuecomment-1260778045

   > yup. Possibly too if Mike M is bored he could implement an alarming system :) or export the data somehow so we could bolt one on the side?
   
   Actually I rather like the alarm idea.  Maybe we could start with something simple -- more than X% change over Y data points?  Maybe for starters the nightly bench just writes these alarms in (blinking red font, heh) at the [top of the index page](https://home.apache.org/~mikemccand/lucenebench/)?  If it seems like that is not too noisy, maybe we find some stronger way to "notify" us.


-- 
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@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org