setup-chrome icon indicating copy to clipboard operation
setup-chrome copied to clipboard

The tool-cache is not working

Open fsvalim opened this issue 1 year ago • 2 comments

Caching is not functioning properly, as each step of the Chromium installation process requires a fresh download instead of utilizing the local version.

image

Part of workflow for reference

      - name: Install Google Chrome
        uses: browser-actions/setup-chrome@v1
        with:
          chrome-version: 120        
          
      - name: Check Google Chrome Version
        run: chrome --version          


      - name: Install Google Chrome
        uses: browser-actions/setup-chrome@v1
        with:
          chrome-version: 120      

      - name: Check Google Chrome Version
        run: chrome --version

fsvalim avatar Mar 21 '24 17:03 fsvalim

Hey, facing this issue on our Isolated GH instance. We need to have the action look for the file locally in the runner and it is not working. It saves the files in the correct location but then it downloads every-time, instead of looking for them.

What we are using: https://docs.github.com/en/[email protected]/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access

joaopedrocg27 avatar Mar 25 '24 10:03 joaopedrocg27

I'm also facing this issue 👀

nunosousa-dev avatar Mar 25 '24 10:03 nunosousa-dev

Thank you for your bug report. The cache with the version in non-server format does not work in tool-cache. This is reported by the following issue: https://github.com/actions/toolkit/issues/709

We are going to fix this issue in the next version.

ueokande avatar May 03 '24 08:05 ueokande

@ueokande I'm afraid this issue still persists. We're using the latest (v2.1.0 as of today) version on the GitHub-hosted runner with:

- name: "Install Chrome"
  uses: "browser-actions/setup-chrome@latest"
  with:
    chrome-version: "120"

And then see this output in GHA logs:

Image

arg avatar Sep 05 '25 05:09 arg

@ueokande I'm afraid this issue still persists. We're using the latest (v2.1.0 as of today) version on the GitHub-hosted runner with:

  • name: "Install Chrome" uses: "browser-actions/setup-chrome@latest" with: chrome-version: "120" And then see this output in GHA logs:

try to use the full version (4 dots)

joaopedrocg27 avatar Sep 05 '25 07:09 joaopedrocg27

try to use the full version (4 dots)

I tried passing full version (120.0.6099.109 in our case), but it doesn't look like the cache works as intended:

Image

This is the second CI run with full version specified, so browser is supposed to be cached already.

arg avatar Sep 06 '25 03:09 arg