Conda-forge.github.io: Feedstocks still using macOS builds on Travis-CI

Created on 7 Jan 2021  Â·  7Comments  Â·  Source: conda-forge/conda-forge.github.io

This is from November 20 to January 6.

  • [ ] conda-forge / gdb-feedstock
  • [x] conda-forge / lastools-feedstock
  • [x] conda-forge / pulsewaves-feedstock
  • [x] conda-forge / cxxopts-feedstock
  • [ ] conda-forge / gmsh-feedstock
  • [x] conda-forge / ocaml-feedstock
  • [x] conda-forge / udunits2-feedstock
  • [x] conda-forge / sfepy-feedstock
  • [x] conda-forge / nspr-feedstock

we should move away from travis-CI for macOS builds and use it only for ppc64le.

cc @conda-forge/core, @conda-forge/gdb, @conda-forge/lastools, @conda-forge/pulsewaves @conda-forge/cxxopts, @conda-forge/gmsh, @conda-forge/ocaml, @conda-forge/udunits2, @conda-forge/sfepy, @conda-forge/nspr.

A simple rerender should switch to azure for macos

Most helpful comment

This happened last month for ocaml during https://github.com/conda-forge/ocaml-feedstock/pull/22, we have .azure-pipelines/azure-pipelines-osx.yml replacing .travis.yml

All 7 comments

regarding GDB, we need macOS 10.13 unfortunately, because GDB hangs about half the time on 10.14+ (see https://github.com/conda-forge/gdb-feedstock/tree/master/recipe). So I'm not sure what can be done.. apart from just removing the test on macOS.

AFAICT nspr is only using Travis CI for ppc64le builds, but please let me know if I'm missing something

This happened last month for ocaml during https://github.com/conda-forge/ocaml-feedstock/pull/22, we have .azure-pipelines/azure-pipelines-osx.yml replacing .travis.yml

I think conda-forge / udunits2-feedstock was fixed in the mean-time as
part of a version upgrade.

On 06/01/2021 18:24, Isuru Fernando wrote:

This is from the November 20.

conda-forge / gdb-feedstock
conda-forge / lastools-feedstock
conda-forge / pulsewaves-feedstock
conda-forge / cxxopts-feedstock
conda-forge / gmsh-feedstock
conda-forge / ocaml-feedstock
conda-forge / udunits2-feedstock
conda-forge / sfepy-feedstock
conda-forge / nspr-feedstock

we should move away from travis-CI for macOS builds and use it only for
ppc64le.

cc @conda-forge/core https://github.com/orgs/conda-forge/teams/core,
@conda-forge/gdb https://github.com/orgs/conda-forge/teams/gdb,
@conda-forge/lastools
https://github.com/orgs/conda-forge/teams/lastools,
@conda-forge/pulsewaves
https://github.com/orgs/conda-forge/teams/pulsewaves
@conda-forge/cxxopts
https://github.com/orgs/conda-forge/teams/cxxopts, @conda-forge/gmsh
https://github.com/orgs/conda-forge/teams/gmsh, @conda-forge/ocaml
https://github.com/orgs/conda-forge/teams/ocaml, @conda-forge/udunits2
https://github.com/orgs/conda-forge/teams/udunits2, @conda-forge/sfepy
https://github.com/orgs/conda-forge/teams/sfepy, @conda-forge/nspr
https://github.com/orgs/conda-forge/teams/nspr.

A simple rerender should switch to azure for macos

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
https://github.com/conda-forge/conda-forge.github.io/issues/1237, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJBQFPPQTIDT6N7T3TXNLTSYT5KBANCNFSM4VYH27PQ.

sfepy was fixed in PR ( https://github.com/conda-forge/sfepy-feedstock/pull/32 )

gmsh seems to need a specific macOS SDK. Not entirely sure the history there. Maybe this can be moved to Azure with a little work? Started this with PR ( https://github.com/conda-forge/gmsh-feedstock/pull/38 ), but may need help from others to complete this.

gmsh and gdb are legitimate uses of travis. Thanks everyone for the help in fixing this issue.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

westurner picture westurner  Â·  3Comments

basnijholt picture basnijholt  Â·  4Comments

dharhas picture dharhas  Â·  3Comments

peterjc picture peterjc  Â·  4Comments

prachi237 picture prachi237  Â·  4Comments