We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make adjustment of the following log event:
Activate error: Unable to schedule collection <9391110637957382604> with path main/RecoGroup/RecoCollection)| |--- | --- | --- | --- | --- | --- | --- | --- | --- | ---|
If possible it should reflect why exactly the scheduling of the task/collection is not possible.
The text was updated successfully, but these errors were encountered:
Just to listing one use case, to help identify cases where more info would help:
Activate error: Unable to schedule collection <250212107438957809> with path main/Sinks
In this case a collection in the topology had a groupname requirement for group x, while only y and z groups were submitted.
x
y
z
A hint in the log saying that "no group x exists" would help.
Sorry, something went wrong.
There is another use case for it: https://alice.its.cern.ch/jira/browse/EPN-272 Involves insufficient number of slots.
AnarManafov
No branches or pull requests
Make adjustment of the following log event:
If possible it should reflect why exactly the scheduling of the task/collection is not possible.
The text was updated successfully, but these errors were encountered: