Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add continuous benchmarking #6157

Closed
tobiasdiez opened this issue Mar 22, 2020 · 1 comment
Closed

Add continuous benchmarking #6157

tobiasdiez opened this issue Mar 22, 2020 · 1 comment
Labels
dev: build-system dev: performance status: stale Issues marked by a bot as "stale". All issues need to be investigated manually.

Comments

@tobiasdiez
Copy link
Member

tobiasdiez commented Mar 22, 2020 •
edited
Loading

We have a jmh benchmark suit but this is never run and/or checked for performance regressions. Thus it would be good to have a continuous benchmarking solution.

Github action that goes in this direction (but has not yet support for jmh) https://github.com/marketplace/actions/continuous-benchmark https://github.com/bobheadxi/gobenchdata
@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2020

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

@github-actions github-actions bot added the status: stale Issues marked by a bot as "stale". All issues need to be investigated manually. label Dec 8, 2020
koppor pushed a commit that referenced this issue Oct 1, 2022
Squashed 'buildres/csl/csl-styles/' changes from 201e022..7bde3e4
7486037 
7bde3e4 Add style for the Geographical Analysis journal (#6145)
6fa1551 Create taylor-and-francis-chicago-b-author-date.csl (#6232)
eba2e8c Create taylor-and-francis-ama.csl (#6221)
dda9d57 ACS, AMA, Vancouver: Remove hardcoded space after `citation-number` (#6248)
8f5fe92 GitHub Workflows security hardening (#6246)
284bc10 Create angiology.csl (#6122)
eb141cc Update society-of-biblical-literature-fullnote-bibliography.csl (#6157)
dddb459 Rewrite law-citation-manual.csl (#6171) (#6171)
b975c96 Update Cell to numeric-superscript style (#6245)
3a41b08 Create isara-iso-690.csl (#6201)
5a128fe Create Biomembranes.csl (#6200)
da2e0c0 Capitalize-first short titles for legislation ("Statute"). (#6241)
af7f08d Create proceedings-of-the-estonian-academy-of-sciences-author-date.csl (#6209)

git-subtree-dir: buildres/csl/csl-styles
git-subtree-split: 7bde3e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dev: build-system dev: performance status: stale Issues marked by a bot as "stale". All issues need to be investigated manually.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tobiasdiez @ThiloteE