You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That should be reproducible in any definition, but find a reproducer attached.
The global setting of APPVEYOR_SAVE_CACHE_ON_ERROR does not work, the (expected) local export didn't work either.
A failing build does trigger the artifacts, but not the caching.
The main issue in this environment is that it is ultra slow, with the brew part taking over one hour, so the idea was to split it (manually installing the dependencies) and update the cache with multiple iterations - to get to the real build (which takes 10-20 minutes with all testing).
Apart from the issue that the cache - even with this setting - is only updated on finished builds: isn't there a command to tell appveyor to "update the cache now"? This would solve the issue (and even allow me to put this in several places for the initial cache building).
version: 3.3-dev.{build}-macosimage:
- macOS
- macOS-Montereyenvironment:
HOMEBREW_NO_INSTALL_CLEANUP: 1HOMEBREW_CACHE: /Users/appveyor/projects/brew_cacheHOMEBREW_CURLRC: 1APPVEYOR_SAVE_CACHE_ON_ERROR: truematrix:
- CONFIGURE_FLAGS: --with-curses=ncurses
- CC: gcc-9
- CC: gcc-11install:
- sh: >- # MacOS worker setup for appveyor script export COMPlus_EnableDiagnostics=0 echo "installing missing/outdated packages" mkdir -p $HOMEBREW_CACHE if test "$APPVEYOR_BUILD_WORKER_IMAGE" = "macOS-Monterey"; then brew update && brew upgrade fi brew install pkg-config jq if test "$CC" != ""; then brew install gmp cjson fi brew install berkeley-db if test "x$CC" = "x"; then CC=gcc # disabled to making the build fail # else # brew install $(echo $CC | tr - @) fi # work around bugs in this environment export TMPDIR=$PREFIX/tmp ./autogen.sh installcache:
- $HOMEBREW_CACHEbuild_script:
- sh: "export APPVEYOR_SAVE_CACHE_ON_ERROR=true\n\nconfigure $CONFIGURE_FLAGS\n\nmake check"artifacts:
- path: tests/testsuite.logname: testsuite results
- path: config.logname: configuration for this buildon_failure:
- sh: >- appveyor PushArtifact config.logon_finish:
- sh: >- appveyor PushArtifact tests/testsuite.log
The text was updated successfully, but these errors were encountered:
That should be reproducible in any definition, but find a reproducer attached.
The global setting of
APPVEYOR_SAVE_CACHE_ON_ERROR
does not work, the (expected) local export didn't work either.A failing build does trigger the artifacts, but not the caching.
The main issue in this environment is that it is ultra slow, with the
brew
part taking over one hour, so the idea was to split it (manually installing the dependencies) and update the cache with multiple iterations - to get to the real build (which takes 10-20 minutes with all testing).Apart from the issue that the cache - even with this setting - is only updated on finished builds: isn't there a command to tell appveyor to "update the cache now"? This would solve the issue (and even allow me to put this in several places for the initial cache building).
The text was updated successfully, but these errors were encountered: