Closed qbarrand closed 5 years ago
In fact maybe caching or something can improve the AppVeyor speed. choco is quite slow. See also https://github.com/appveyor/ci/issues/3009 and https://github.com/appveyor/ci/issues/3058
See the choco caching for AppVeyor https://www.appveyor.com/docs/build-cache/
Will cache choco packages using
cache:
- C:\ProgramData\chocolatey\lib -> appveyor.yml
However the build time itself is already rather short, the problem is that jobs are queued for ages :disappointed:
@qbarrand actually we can try to setup Azure Pipelines. They are damn fast:
There's also Travis, although windows builds are rather slow and I somehow cannot make the matrix work.
You can add Azure Pipelines YAML file, I enabled it for the repository
@XVilka Do we really want yet another CI? It works in Travis for Windows + gcc https://travis-ci.org/radareorg/r2pm/jobs/575841184
@XVilka Could we remove .builds/openbsd.yml
? I think it's the only CI that fails now.
Azure is faster, so we eventually can add installability checks and more tests. For the OpenBSD - let it fail for now, we'll see if it's possible to fix somehow, maybe complain to Go or OpenBSD developers
Seems AppVeyor clang build also failing by the way
Merging #40 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #40 +/- ##
=======================================
Coverage 25.86% 25.86%
=======================================
Files 2 2
Lines 116 116
=======================================
Hits 30 30
Misses 83 83
Partials 3 3
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 2319b71...77dcfa7. Read the comment docs.
Can you setup
CC=gcc
for AppVeyor too while you are on it?