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.

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

Fix benchmarks (rendering, site) #901

Merged
merged 1 commit into from
Dec 26, 2019
Merged

Conversation

samford
Copy link
Contributor

@samford samford commented Dec 24, 2019

It turns out that I broke benchmarks in #885 because I was a little heavy-handed in my removal of extern crate statements and attributes. This restores the necessary #![feature(test)] and extern crate test; for these benchmarks to work.

I fixed the RenderContext::new() errors in the rendering benchmark, where six parameters were provided but five were expected.

Past this, the /components/site/benches/load.rs benchmark fails for some reason and simply gives an error: bench failed message. If you have any insight on how to fix this, I can try to tackle it in this PR, otherwise you can take care of it sometime later.

* Restore #![feature(test)] and extern crate test; statements, which
were mistakenly removed as part of the Rust 2018 edition migration.

* Fix rendering benchmark's usage of RenderContext. 6 parameters were
provided when 5 were expected.
@Keats Keats merged commit f5dce64 into getzola:next Dec 26, 2019
@Keats
Copy link
Collaborator

Keats commented Dec 26, 2019

Most of the benches are not actually used at all by anyone I think. I'll have a look and see if some can be removed. Thanks!

@samford samford deleted the fix-benchmarks branch December 26, 2019 14:10
Keats pushed a commit that referenced this pull request Feb 3, 2020
* Restore #![feature(test)] and extern crate test; statements, which
were mistakenly removed as part of the Rust 2018 edition migration.

* Fix rendering benchmark's usage of RenderContext. 6 parameters were
provided when 5 were expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants