Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L lalsuite
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 114
    • Issues 114
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 37
    • Merge requests 37
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • lscsoft
  • lalsuite
  • Merge requests
  • !1929

lal*/conda/meta.yaml.in.in: run install-python.sh with same script_env as build.sh

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Karl Wette requested to merge ANU-CGA/lalsuite:conda-fix-script-env into master Aug 01, 2022
  • Overview 3
  • Commits 1
  • Pipelines 0
  • Changes 27

Description

Fixes lal*/conda/meta.yaml.in.in by adding the same script_env (containing CI_COMMIT_TAG, CI_PIPELINE_SOURCE, and GITLAB_CI) to each install-*.sh script, the same as for the build.sh scripts.

Both scripts need these variables set to decide on which flags to pass to ./configure. In particular, setting -UNDEBUG inconsistently can lead to segfaults (#573 (closed)) because the LAL memory functions are not consistently enabled/disabled.

conda-build raises an error for unset variables in script_env for install-*.sh: ValueError: env var 'CI_COMMIT_TAG' specified in script_env, but is not set This may be a bug as the same error isn't raised for build.sh.

To ensure CI_COMMIT_TAG is passed to all scripts, need to make sure CI_COMMIT_TAG is set before calling conda-build, then in scripts only test whether CI_COMMIT_TAG is null, not whether it is unused.

API Changes and Justification

Backwards Compatible Changes

  • This change does not modify any class/function/struct/type definitions in a public C header file or any Python class/function definitions
  • This change adds new classes/functions/structs/types to a public C header file or Python module

Backwards Incompatible Changes

  • This change modifies an existing class/function/struct/type definition in a public C header file or Python module
  • This change removes an existing class/function/struct/type from a public C header file or Python module

Review Status

Closes #573 (closed) as being the immediate cause of the segfault (but see #573 (comment 576406))

Edited Aug 01, 2022 by Karl Wette
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: conda-fix-script-env