(ci) fix integrationtest vectorsearch

[thomasht86]

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

This integration test has been unstable and slooow. 🐌
Some updates to improve stability and speed.

• reuse common environment and run workflows in parallel
• comment out prod deployment (not only skip)
• switch to Python 3.10

PR run here: https://github.com/vespa-engine/pyvespa/actions/runs/11970588855

[esolitos]

I'm not sure why you wouldn't reuse the cache and instead upload it as artifact?

What I would typically in this situation is one of those:

a. Have a "build" job which builds the application and stores an actions/upload-artifact. The dependant jobs only get the built artifact and don't run any install steps.

b. Don't have a build job and simply use actions/cache with restore-keys that can fallback on a "older version" of the caches perfect match fails.

You seem to have mixed up caches and artifact and I don't see the benefit in this approach, unless I am missing something, that is. 😅

[esolitos]

Suggested change

	uses: actions/cache@v3
	uses: actions/cache@v4

[esolitos]

I don't understand why you would use this instead of simply rely on actions/cache for restoring as well?

[esolitos]

Use actions/cache + restore-key instead?

[esolitos]

Also, outdated version:

Suggested change

	- name: Download Python environment
	uses: actions/download-artifact@v3
	with:
	name: python-environment
	path: ~/.cache/pip
	- name: Download Python environment
	uses: actions/download-artifact@v4
	with:
	name: python-environment
	path: ~/.cache/pip

[thomasht86]

Thanks! I will have another look at the cache-action to see if we can skip the artifact upload/download!

[thomasht86]

Ok, so it is 2 different things we ideally would want 2 cache.

1. Pip packages directory. This is now handled automatically by setup-python-action.
2. It would also be nice to cache the generated environment after installing pyvespa from source. This would probably require a more advanced caching, but not so much time to save on this, so leaving that for now.

[esolitos]

👍🏼