Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.pipelines bob.pipelines
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.pipelinesbob.pipelines
  • Issues
  • #10
Closed
Open
Issue created Apr 17, 2020 by Tiago de Freitas Pereira@tiago.pereiraOwner

Conflicts ad eternum

Hi guys,

I'm facing some problems with our CI and I need some light. It's been a while that I'm having some enigmatic conflicts, check here one example.

https://gitlab.idiap.ch/bob/bob.pipelines/-/jobs/195496/raw

bdt build doesn't work at all on the CI and on my computers. I'm wondering if it's something with Numpy, because of this message at the logs:

Attempting to finalize metadata for bob.pipelines
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done
Adding .* to spec 'numpy 1.16.6' to ensure satisfiability.  Please consider putting {{ var_name }}.* or some relational operator (>/</>=/<=) on this spec in meta.yaml, or if req is also a build req, using {{ pin_compatible() }} jinja2 function instead.  See https://conda.io/docs/user-guide/tasks/build-packages/variants.html#pinning-at-the-variant-level
WARNING conda_build.utils:ensure_valid_spec(1749): Adding .* to spec 'numpy 1.16.6' to ensure satisfiability.  Please consider putting {{ var_name }}.* or some relational operator (>/</>=/<=) on this spec in meta.yaml, or if req is also a build req, using {{ pin_compatible() }} jinja2 function instead.  See https://conda.io/docs/user-guide/tasks/build-packages/variants.html#pinning-at-the-variant-level
INFO:bob.devtools.scripts.build@2020-04-17 09:24:21,641: Building bob.pipelines-0.0.1b0-py37 (build: 12) for linux-64
INFO:bob.devtools.bootstrap@2020-04-17 09:24:21,641: environ["BOB_BUILD_NUMBER"] = 12
/scratch/builds/bob/bob.pipelines/miniconda/lib/python3.7/site-packages/conda_build/environ.py:427: UserWarning: The environment variable 'DOCSERVER' is being passed through with value 'http://www.idiap.ch'.  If you are splitting build and test phases with --no-test, please ensure that this value is also set similarly at test time.
  UserWarning
/scratch/builds/bob/bob.pipelines/miniconda/lib/python3.7/site-packages/conda_build/environ.py:427: UserWarning: The environment variable 'NOSE_EVAL_ATTR' is being passed through with value ''.  If you are splitting build and test phases with --no-test, please ensure that this value is also set similarly at test time.
  UserWarning
BUILD START: ['bob.pipelines-0.0.1b0-py37h9f5372d_12.conda']
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done

However, if I try to install the bob.pipelines setup, everything works fine.

conda install bob-devel==2020.03.30 dask dask-jobqueue bob.extension bob.io.base -c https://www.idiap.ch/software/bob/conda/label/beta/ --dry-run

Can I have some light?

Thanks

ping @andre.anjos @amohammadi

Assignee
Assign to
Time tracking