-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
Added 'datashield/armadillo-rserver_caravan' and 'datashield/armadillo-rserver_caravan-volcano' #28
base: main
Are you sure you want to change the base?
Conversation
…nd 'armadillo-rserver_edam-terrain', updated 'armadillo-rserver_caravan'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@StuartWheater what test do you expect here? It looks good.
Do you need one of us to locally run it?
I know little about the post "Pull Request" process as I don't have access to the Azure Pipeline results. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approve the config; I noticed build is failing, is that blocking the merge?
I can't access the "details" of the check, so don't know the reason. I suspect it could be exceeding the time limit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@StuartWheater What you could try to do is to increase the timeout in the azure-pipelines.yaml. See: https://github.com/datashield/docker-armadillo-rserver-base/blob/main/azure-pipelines.yml#L9
Yes, the timeout can be extended and number of cpus used by R increased. |
No description provided.