You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is a default glexec validation from glideinWMS side and it seems to be running according CMS frontend configuration.
As far as I understood, it runs if GLEXEC_BIN attribute in the factory entry is set.
Do we need to duplicate this test? Do we need some information from this test to be reported to ES?
Default glideinWMS glexec setup script runs after custom scripts. So I can't get result of it.
I need to find other way as I want to avoid duplicating tests.
I can add singularity validation script to PSST or just take value from HAS_SINGULARITY.
Activity
roksys commentedon Jun 27, 2017
Currently there is a default glexec validation from glideinWMS side and it seems to be running according CMS frontend configuration.
As far as I understood, it runs if GLEXEC_BIN attribute in the factory entry is set.
Do we need to duplicate this test? Do we need some information from this test to be reported to ES?
bbockelm commentedon Jul 3, 2017
Knowing whether there is functioning isolation is pretty important.
Is it possible to just get the result from the Singularity / glexec test and advertise it in ES?
roksys commentedon Jul 5, 2017
Default glideinWMS glexec setup script runs after custom scripts. So I can't get result of it.
I need to find other way as I want to avoid duplicating tests.
I can add singularity validation script to PSST or just take value from
HAS_SINGULARITY.bbockelm commentedon Jul 5, 2017
Let's just take the value from
HAS_SINGULARITY- we can addglexectest support later.roksys commentedon Jul 7, 2017
plot - singularity vs no singularity