Open baxpr opened 2 years ago
This was maybe fixed already? Not sure. Anyway I was wrong and the linked PR isn't related
@KarthikMasi does this describe what just happened today? Maybe this is not resolved. Ideally when there is a typo in the yaml like that, other stuff would still run on the project, just not the one spider with the error.
CUTTING_LD4 did not build because of the error in REDCap entry. But the following projects got built on daily_singularity
7TMSlong, ADNI_BFF, Claassen_Crave, CUTTING_EF1, EmotionBrain, JEFFERSON, PRICE_DDK2, REMBRANDT, STEIN, TAYLOR_CAARE
We have 58 dax-settings files in the daily singularity account which means that we should have got more dax build logs right(not just the 10 above)?
P.S The manager logs did end on the "updating" part with the CUTTING_LD4 error.
Only 10 builds launch at a time, so that much makes sense I think.
I'm wondering if the error in the redcap settings stalled all of CUTTING_LD4, or only the specific assessor.
Nothing ran on a project with a bunch of assessors launched (Neg_Val_SCZ starting mid-Dec). The only problem seemed to be a typo in the inputs.xnat.etc variable name in a single one of the instruments. Can dax run the ones that are ok and skip the ones that fail?