Skip to content

Parametrize test_benchmarks.py test by criterion benchmarks #4832

Open
@roypat

Description

@roypat

Currently, test_benchmarks.py contains a single test that runs all criterion benchmarks. With increasing number of benchmarks, we thus increase the duration of this test, and need to adjust its timeout. Instead, we want to parameterize the test by the list of criterion benchmarks we have in the repository. This means introducing a fixture that yields the benchmarks listed by cargo bench --all -- --list individually. Then the test itself would only run the benchmark it is provided. This should also make it easier to see which benchmarks are failing.

Originally posted by @pb8o in #4830 (comment)

Activity

added
Good first issueIndicates a good issue for first-time contributors
Priority: LowIndicates that an issue or pull request should be resolved behind issues or pull requests labelled `
Status: ParkedIndicates that an issues or pull request will be revisited later
on Oct 9, 2024
MacOS

MacOS commented on Oct 18, 2024

@MacOS

If someone has not done it yet, I would take it over.

bchalios

bchalios commented on Oct 30, 2024

@bchalios
Contributor

Hey @MacOS, please start working on it if you want.

cm-iwata

cm-iwata commented on Dec 21, 2024

@cm-iwata
Contributor

@MacOS
CC: @bchalios

Are you still working on this?
If you are busy, may I handle it instead you?

linked a pull request that will close this issue on Dec 30, 2024
MacOS

MacOS commented on Jan 3, 2025

@MacOS

I would submit something next week, however, I am not mad if you do it.

gjkeller

gjkeller commented on Apr 10, 2025

@gjkeller

@MacOS @cm-iwata @bchalios

I wanted to check and see if this issue was still being worked on. If not, would I be able to work on it?

cm-iwata

cm-iwata commented on Apr 10, 2025

@cm-iwata
Contributor

@gjkeller
I'm waiting for a pull request review...

gjkeller

gjkeller commented on Apr 11, 2025

@gjkeller

@cm-iwata
No worries! I was unsure of if it was complete due to the failing tests, but seems like the failure was only due to timeouts and network errors. Good luck with getting your PR merged!

roypat

roypat commented on Apr 23, 2025

@roypat
ContributorAuthor

@gjkeller I'm waiting for a pull request review...

Hi, sorry, I thought the latest update on the PR was that you were looking into why the CI was failing. Did you need help with anything? :o

cm-iwata

cm-iwata commented on Apr 27, 2025

@cm-iwata
Contributor

@roypat
I have made some adjustments, so could you please re-run the CI and review it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good first issueIndicates a good issue for first-time contributorsPriority: LowIndicates that an issue or pull request should be resolved behind issues or pull requests labelled `Status: ParkedIndicates that an issues or pull request will be revisited later

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @MacOS@kalyazin@gjkeller@bchalios@cm-iwata

      Issue actions

        Parametrize `test_benchmarks.py` test by criterion benchmarks · Issue #4832 · firecracker-microvm/firecracker