Closed abhaasgoyal closed 9 months ago
We could use a subprocess for lquota
/ os.listdir
- but that'd be very specific to Gadi in terms of unit tests,.
Since running an invalid project name on PBS could provide an error, do we still need this at an earlier steps (potentially to make benchcab
more user-friendly? Also, are there other ways to check which groups is a user in
Benchcab should complain if the project is not in the groups of the user, but it isn't that user friendly:
I see, for now it is resolved in validate_environment
, when doing integration tests. A more robust way would be in Unit Tests when we could separate the abstraction of environment in benchcab
Right now, a user can input any value in $PROJECT / project keyword in
config.yaml
. It isn't checked whether the user belongs to a certain group until the job has been submitted to PBS.Reproduce
Run benchcab with the following parameter
Next steps
Add a validation check by checking the groups of a user, and whether
project
lies within the corresponding set