Enumerate variables needed by the HTCondor workflow#376
Enumerate variables needed by the HTCondor workflow#376duncanmmacleod wants to merge 3 commits intogwpy:masterfrom
Conversation
instead enumerate the variables we want to propagate from the submit environment
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #376 +/- ##
==========================================
- Coverage 50.27% 49.65% -0.62%
==========================================
Files 60 60
Lines 8677 8824 +147
==========================================
+ Hits 4362 4381 +19
- Misses 4315 4443 +128
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@duncanmmacleod Thanks, do we also need |
I don't see any references to |
@duncanmmacleod the reason I ask is because the code wants to get the conda environment used at the time pages are generated. Like here: https://github.com/gwdetchar/gwdetchar/blob/f79547a178c16b9a6b9626d23d656fb025c10338/gwdetchar/io/html.py#L51. Wouldn't this mean we need |
so that it is available in conda to generate the package list
I have added |
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375
|
I'll close this PR as I'd like to use #429 instead. I hope to be able to remove |
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by gwpy#376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes gwpy#375 # Conflicts: # gwsumm/batch.py
See https://computing.docs.ligo.org/guide/htcondor/environment/?h=getenv#getenv. This PR is inspired by #376, but I wanted to keep the existing code as simple as possible to avoid confusion. Closes #375 Co-authored-by: Evan Goetz <evan.goetz@ligo.org>
This PR closes #375 by replacing the use of
getenv=truewith a hardcoded set of environment variables to pass through from the submit environment.