Stream: committers
Topic: R4B - pull request hung
Lloyd McKenzie (Mar 03 2021 at 04:16):
I've got a pull request that ran successfully, but the 'notification' bit has been hung for about 20 minutes (normally takes seconds). https://dev.azure.com/fhir-pipelines/fhir-publisher/_build/results?buildId=2662&view=results. Pull request: https://github.com/HL7/fhir/pull/1142
@Mark Iantorno?
Mark Iantorno (Mar 03 2021 at 13:01):
So, right now there is one build agent for all of the builds for master/R4B. It's an GCP hosted VM (azure cannot do it natively for us, because the build requires too much memory for the free tier to handle).
Mark Iantorno (Mar 03 2021 at 13:02):
What this means is that is there is more than one person doing a merge/build at any given time, there will be a line. You'll have to wait for the build(s) ahead of you to complete before you're will even start.
Mark Iantorno (Mar 03 2021 at 13:02):
Looking now, it seems like it built okay, and you merged, so I'm assuming this was resolved? I just wanted to give you the details.
Lloyd McKenzie (Mar 03 2021 at 14:29):
Thanks Mark. Being in a line sucks, but I understand. And 'free' matters :)
Mark Iantorno (Mar 03 2021 at 14:37):
If this becomes an issue that is preventing work from getting done, we can always spin up another VM to split the load. From what I've seen though, the most people are waiting is 1 position in line (25-30 min)
Mark Iantorno (Mar 03 2021 at 14:37):
Let me know if it becomes an issue though
Last updated: Apr 12 2022 at 19:14 UTC
