conda-forge / numba-feedstock

A conda-smithy repository for numba.
BSD 3-Clause "New" or "Revised" License
0 stars 27 forks source link

0.56.4 lints, try to convice Travis CI to build for ppc64le #109

Open mbargull opened 1 year ago

mbargull commented 1 year ago

Checklist

closes gh-92 fixes gh-102

conda-forge-linter commented 1 year ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

mbargull commented 1 year ago

ppc64le seems to work now with verbose test output and redirecting stderr to stdout (the oddest thing...). (The PYTHONUNBUFFERED=1 might or might not be needed.)

But I'm still leery of those Travis/ppc64le runs, so I'll just restart those a couple of times to see how it behaves.

mbargull commented 1 year ago

BTW: The ppc64le builds took around 30-45 minutes, i.e., the -j --random 0.15 seems to be quite appropriate given the 50 minute limit. The aarch64 builds seem to finish in under 15 minutes for the last few months, i.e., we could maybe try to up the portion of selected tests to something around 0.3 to 0.5 for that platform.

mbargull commented 1 year ago

@conda-forge-admin, please restart ci

mbargull commented 1 year ago

@conda-forge-admin, please restart ci

mbargull commented 1 year ago

@conda-forge-admin, please restart ci

jakirkham commented 1 year ago

Restarted one of the jobs that errored without a log

gmarkall commented 1 year ago

The PPC64le builds that error with no output after 10 minutes all seem to have a hostname in common, *.lxd-ppc64le-travis-ci-production-1-worker1-saopaulo. Examples:

gmarkall commented 1 year ago

The PPC64le builds that error with no output after 10 minutes all seem to have a hostname in common

(Just to be clear this is the ones that don't even appear to start cloning, not the ones that were actually running tests and timing out during the tests as in earlier runs, before https://github.com/conda-forge/numba-feedstock/pull/109#issuecomment-1323809183)

jakirkham commented 1 year ago

FWIW the restarted one passed

Maybe we should follow up with Travis CI on the problematic worker?

Edit: Sent an email to Travis CI with a link to Graham's comment above ( https://github.com/conda-forge/numba-feedstock/pull/109#issuecomment-1324814500 )

Edit 2: Link to issue ( https://support.travis-ci.com/hc/requests/41747 ). Idk if others can view this (guessing not). In any event they say this issue is fixed and we should retry. So restarting on main ( https://app.travis-ci.com/github/conda-forge/numba-feedstock/builds/258052004 )

Edit 3: Restarting failed with the same timeout issue. Asking Travis CI to take another look.