Skip to content

CI: publish benchmarks log as artifact #44464

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
Closed
wants to merge 3 commits into from
Closed

CI: publish benchmarks log as artifact #44464

wants to merge 3 commits into from

Conversation

jorisvandenbossche
Copy link
Member

To check the benchmarks timings for #44450

@jreback
Copy link
Contributor

jreback commented Nov 15, 2021

where does this show up?

@jorisvandenbossche
Copy link
Member Author

Well, it doesn't yet show up anywhere, because with the updated asv comment it complains about having no machine information (see failing ci of latest commit), and not directly sure how to fix that.

@jreback jreback added CI Continuous Integration Benchmark Performance (ASV) benchmarks labels Nov 15, 2021
@jorisvandenbossche
Copy link
Member Author

Potentially related upstream issue: airspeed-velocity/asv#944

@jorisvandenbossche jorisvandenbossche mentioned this pull request Nov 15, 2021
Open
@jorisvandenbossche
Copy link
Member Author

So the problem with using asv run instead of asv dev is that it now gives "No information stored about machine 'fv-az186-290'. I know about nothing". Not directly sure how to work-around that (see also airspeed-velocity/asv#944)

@github-actions
Copy link
Contributor

This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this.

@github-actions github-actions bot added the Stale label Dec 17, 2021
@jreback
Copy link
Contributor

jreback commented Jan 16, 2022

still active?

@mroeschke
Copy link
Member

Looks like this currently isn't possible due to airspeed-velocity/asv#944. Once the upstream issue is address then this approach can be continued. Closing for now.

@mroeschke mroeschke closed this Jan 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lithomas1 lithomas1 lithomas1 left review comments

Assignees
No one assigned
Labels
Benchmark Performance (ASV) benchmarks CI Continuous Integration Stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@jorisvandenbossche @jreback @mroeschke @lithomas1