ASV py3.6 environment fails to install (numba/numpy conflict)

Describe the bug In asv.conf, the virsion of numba is conflictde with the virsion of numpy,so when run this code asv check,there is a bug.

To Reproduce Steps to reproduce the behavior:

1. Validate and build environments (may take a couple minutes to run): asv check
2. See error

Expected behavior modify the asv.conf

Screenshots

Versions:

• pvlib.__version__:
• pandas.__version__:
• python:conda python 3.9

Additional context And i change the virsion 0.36.1 of numba to the virsion 0.40.0 of numba ,it works.

[kanderso-nrel]

the result of each benchmark is just one commit result

Yep, each dot in the line chart corresponds to the results of a single commit on the pvlib master branch. Just running asv check won’t actually store any benchmark results like asv run ... does.

the process of the benchmarks is too long

Yeah, the benchmarks are a bit slow 😦 it’s a few minutes just to benchmark a single commit, so running benchmarks for a long history of commits does take quite a bit of time. Maybe we can improve that.

Anyway, this issue seems similar to https://github.com/pvlib-benchmarker/pvlib-benchmarks/issues/1. The linux server we use to run the nightly benchmarks isn’t affected by this problem, so maybe the incompatibility is related to the OS. In any case I agree that we should update the configuration file so that the instructions work on a typical PC. While I agree it makes sense to stop benchmarking on python 3.6 eventually, I don’t mind keeping it around as long as we’re still running the unit tests on 3.6. So maybe for now we should just increase the numba version and leave the python version update for later.

[roger-lcc]

Thanks! @kanderso-nrel @Naman-Priyadarshi