Airspeed Velocity Set Up

[trexfeathers]

This pull request enables testing with Airspeed Velocity 🐦

Any user with an ASV install can run the suite of tests held within lib/iris/tests/benchmarking using the shell command asv run, while in the root directory. See the ASV documentation linked above for more details on what the software can do.

Points for future discussion:

• What tests should be included in the suite?
• What will be the standard arguments for asv run, and how should we store these?
  • Documentation?
  • A small text file that could be referenced in the building of scripts?

[trexfeathers]

Covers some of #3495

[bjlittle]

@trexfeathers Do we need to add the asv package to the requirements/test.txt to make it a dependency?

[bjlittle]

@trexfeathers This is awesome, so looking forward to getting asv up and running - it's an invaluable contribution to iris.

Just a couple of review actions to service, but otherwise looks good to me 👍

[bjlittle]

@trexfeathers Perhaps not in this PR, but we should also provide documentation for the iris developer on how to use asv etc

[trexfeathers]

@trexfeathers Do we need to add the asv package to the requirements/test.txt to make it a dependency?

@bjlittle nice catch. The existing automated tests would not break without this, but it's still clearer to have asv as a dependency, so I've added it 😊

[trexfeathers]

@trexfeathers Perhaps not in this PR, but we should also provide documentation for the iris developer on how to use asv etc

@bjlittle 100% with you, once we have an agreed way of using ASV that we can document. I'm particularly interested in standardising the asv run arguments in some way.

[bjlittle]

@bjlittle 100% with you, once we have an agreed way of using ASV that we can document. I'm particularly interested in standardising the asv run arguments in some way.

Nice. How do we capture this intent moving forwards? An issue? Elsewhere? Or have you got that covered? 😉

[trexfeathers]

@bjlittle 100% with you, once we have an agreed way of using ASV that we can document. I'm particularly interested in standardising the asv run arguments in some way.

Nice. How do we capture this intent moving forwards? An issue? Elsewhere? Or have you got that covered? 😉

I'm not intending to map out next steps until I have finished experimenting with local routine testing schedules as this will inform further discussion.

[bjlittle]

@trexfeathers asv cleared for take-off runway iris 🎉