Mesa (staging/20.3): appveyor: disable for now

[GitLab Mirror]

Module: Mesa
Branch: staging/20.3
Commit: 45f5e8d45590b3167e2d86c150c4c979dbd5c8ce
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=45f5e8d45590b3167e2d86c150c4c979dbd5c8ce

Author: Dylan Baker <dylan.c.baker at intel.com>
Date:   Wed Nov 25 11:54:03 2020 -0800

appveyor: disable for now

It's borken ATM in general (not just on 20.3), and we want to kep the CI
green. Once it's fixed we'll turn it back on.

---

 appveyor.yml | 71 ------------------------------------------------------------
 1 file changed, 71 deletions(-)

diff --git a/appveyor.yml b/appveyor.yml
deleted file mode 100644
index f66689ea4bb..00000000000
--- a/appveyor.yml
+++ /dev/null
@@ -1,71 +0,0 @@
-# http://www.appveyor.com/docs/appveyor-yml
-#
-# To setup AppVeyor for your own personal repositories do the following:
-# - Sign up
-# - Add a new project
-# - Select Git and fill in the Git clone URL
-# - Setup a Git hook as explained in
-#   https://github.com/appveyor/webhooks#installing-git-hook
-# - Check 'Settings > General > Skip branches without appveyor.yml'
-# - Check 'Settings > General > Rolling builds'
-# - Setup the global or project notifications to your liking
-#
-# Note that kicking (or restarting) a build via the web UI will not work, as it
-# will fail to find appveyor.yml .  The Git hook is the most practical way to
-# kick a build.
-#
-# See also:
-# - http://help.appveyor.com/discussions/problems/2209-node-grunt-build-specify-a-project-or-solution-file-the-directory-does-not-contain-a-project-or-solution-file
-# - http://help.appveyor.com/discussions/questions/1184-build-config-vs-appveyoryaml
-
-version: '{build}'
-
-branches:
-  except:
-  - /^travis.*$/
-
-# Don't download the full Mesa history to speed up cloning.  However the clone
-# depth must not be too small, otherwise builds might fail when lots of patches
-# are committed in succession, because the desired commit is not found on the
-# truncated history.
-#
-# See also:
-# - https://www.appveyor.com/blog/2014/06/04/shallow-clone-for-git-repositories
-clone_depth: 100
-
-# https://www.appveyor.com/docs/build-cache/
-cache:
-- '%LOCALAPPDATA%\pip\Cache -> appveyor.yml'
-- win_flex_bison-2.5.15.zip
-- llvm-5.0.1-msvc2017-mtd.7z
-- subprojects\packagecache -> subprojects\*.wrap
-
-os: Visual Studio 2019
-
-init:
-# Appveyor defaults core.autocrlf to input instead of the default (true), but
-# that can hide problems processing CRLF text on Windows
-- git config --global core.autocrlf true
-
-environment:
-  Path: C:\Python38-x64;C:\Python38-x64\Scripts;%Path%
-  WINFLEXBISON_VERSION: 2.5.15
-  LLVM_ARCHIVE: llvm-5.0.1-msvc2017-mtd.7z
-  matrix:
-  - compiler: msvc
-    buildsystem: scons
-
-install:
-- cmd: .appveyor\appveyor_msvc.bat install
-
-build_script:
-- cmd: .appveyor\appveyor_msvc.bat build_script
-
-test_script:
-- cmd: .appveyor\appveyor_msvc.bat test_script
-
-# It's possible to setup notification here, as described in
-# http://www.appveyor.com/docs/notifications#appveyor-yml-configuration , but
-# doing so would cause the notification settings to be replicated across all
-# repos, which is most likely undesired.  So it's better to rely on the
-# Appveyor global/project notification settings.