ci: debug: what happens when we take out explicit caching and only sp… #9

	name: CI

	on: [push, pull_request]

	env:
	# Used to differentiate from other slices of the cache for other workflow runs, and to forcefully bust the cache when renamed
	CACHE_KEY_BASE: ci@v1

	jobs:
	setup:
	name: Setup
	runs-on: ubuntu-latest
	steps:
	- name: Checkout repository
	uses: actions/checkout@v5

	- name: Set up Deno
	id: deno-install-and-cache
	uses: denoland/setup-deno@v2
	with:
	deno-version: 2.x
	cache-hash: ${{ runner.os }}-${{ env.CACHE_KEY_BASE }}-${{ hashFiles('deno.lock') }}

	# - name: Set up Deno dependencies cache
	# id: deno-deps-cache
	# uses: actions/cache@v3
	# with:
	# path: \|
	# ~/.deno
	# ~/.cache/deno
	# key: ${{ env.CACHE_KEY_BASE }}-${{ hashFiles('deno.lock') }}
	# restore-keys: ${{ env.CACHE_KEY_BASE }}

	- name: Install dependencies
	id: deno-deps-install
	run: deno install

	test:
	name: Test
	needs: [setup]
	runs-on: ubuntu-latest
	steps:
	- name: Checkout repository
	uses: actions/checkout@v5

	# Now the Deno cache should be warmed up, so this should be much faster
	- name: Set up Deno
	id: deno-install-and-cache
	uses: denoland/setup-deno@v2
	with:
	deno-version: 2.x
	cache: true

	# - name: Set up Deno dependencies cache
	# id: deno-deps-cache
	# uses: actions/cache@v3
	# with:
	# path: \|
	# ~/.deno
	# ~/.cache/deno
	# key: ${{ env.CACHE_KEY_BASE }}-${{ hashFiles('deno.lock') }}
	# restore-keys: ${{ env.CACHE_KEY_BASE }}

	- name: Install dependencies
	id: deno-deps-install
	run: deno install

	- name: Test
	run: deno test --allow-read

Provide feedback