Build cache doesn't seem to work

Ionel Cristian Mărieș's Avatar

Ionel Cristian Mărieș

09 Apr, 2015 10:55 AM


I'm using a build cache on c:\users\appveyor\pip\wheels but it seems that it's always empty.

I have this in the conf:

build: off
  - C:\Users\appveyor\pip\wheels -> tox.ini
  fast_finish: true
environment: matrix: ... long list of slow stuff here ... init: - "echo %CTX%" - "set" - ps: "ls C:\Python*" install: - ps: New-Item -Force -ItemType directory -Path "c:/Users/appveyor/pip/wheels" - ps: Copy-Item -Path "./ci/pip.ini" -Destination "c:/Users/appveyor/pip/pip.ini" -Force - ps: Invoke-WebRequest "" -OutFile "c:\" - ps: Invoke-WebRequest "" -OutFile "c:\" - "c:\python27\python c:\ setuptools wheel" - "c:\python27\Scripts\pip wheel tox virtualenv cookiecutter bumpversion" - "c:\python27\Scripts\pip install -I -U tox virtualenv cookiecutter" test_script: - git config --global "[email blocked]" - git config --global "Your Name" - powershell ci\test.ps1 $Env:ENV

The pip wheel tox virtualenv cookiecutter bumpversion always build the wheels so it must mean that c:/Users/appveyor/pip/wheels is empty.

Any idea what I'm doing wrong?

  1. 1 Posted by Ionel Cristian ... on 09 Apr, 2015 11:00 AM

    Ionel Cristian Mărieș's Avatar
  2. Support Staff 2 Posted by Feodor Fitsner on 09 Apr, 2015 04:54 PM

    Feodor Fitsner's Avatar

    Yeah, that's strange. So, it's just that particular job?

  3. 3 Posted by Ionel Cristian ... on 09 Apr, 2015 04:55 PM

    Ionel Cristian Mărieș's Avatar

    Hey, they all have the same problem.

    -- Ionel Cristian Mărieș,

  4. 4 Posted by Ionel Cristian ... on 09 Apr, 2015 06:06 PM

    Ionel Cristian Mărieș's Avatar

    I've added some debugging info here:

    You can see that the path doesn't exist. Any ideas what to do to make it

    The previous build said it saved the wheels:

    This indicates that the wheels were placed there:

    -- Ionel Cristian Mărieș,

  5. Support Staff 5 Posted by Feodor Fitsner on 09 Apr, 2015 06:36 PM

    Feodor Fitsner's Avatar

    The build next to it says the cache was restored:

    The explanation is why the cache is not restored on some builds/jobs is that cache is stored in the same Azure region where build worker is running. For better reliability AppVeyor can create build workers in 3 regions (West US, Central US and East US). When provisioning time or the number of "unhealthy" build workers is increasing AppVeyor switches to a different region and there is no cache for that project yet (or it's outdated).

  6. 6 Posted by Ionel Cristian ... on 09 Apr, 2015 06:38 PM

    Ionel Cristian Mărieș's Avatar

    I think this is most likely the change that makes it work:

    Maybe a bug after all? :-)

    -- Ionel Cristian Mărieș,

  7. Support Staff 7 Posted by Feodor Fitsner on 09 Apr, 2015 08:12 PM

    Feodor Fitsner's Avatar

    Well, it just makes it tracking C:\Users\appveyor\pip\wheels for any changes to decide when the cache is invalidated.

  8. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac