<https://github.com/Eventual-Inc/Daft/actions/runs...
# daft-deva
Andrew Gazelka
11/20/2024, 12:45 AMhttps://github.com/Eventual-Inc/Daft/actions/runs/11922977327/job/33230361817?pr=3308 any idea why all these things failing related to SQL?
Andrew Gazelka
11/20/2024, 12:45 AMimage.png
Andrew Gazelka
11/20/2024, 12:50 AM@Sammy Sidhu according to @Kevin Wang like this issue would be avoided if we had a merge queue. Do you have any thoughts on this?
👍 1
c
Cory Grinstead
11/20/2024, 12:54 AMdid you merge main? there was a bad commit that made it into main. a merge from main should fix
s
Sammy Sidhu
11/20/2024, 1:17 AMMerge queues are pretty painful at a startup IMO. You could potentially have to wait hours to get your commit in for a quick change
❓ 1
a
Andrew Gazelka
11/20/2024, 1:17 AMkinda confused @Sammy Sidhu how you would have to wait hours? my understand of merge queues is if there is only one pending merge it will take the same time
Andrew Gazelka
11/20/2024, 1:18 AMit is only if you have like 5 pending merges that that will happen
Andrew Gazelka
11/20/2024, 1:18 AMs
Sammy Sidhu
11/20/2024, 1:20 AMlike the case from yesterday:
a
Andrew Gazelka
11/20/2024, 1:20 AMohhh dependabot...
Andrew Gazelka
11/20/2024, 1:20 AMyea
Andrew Gazelka
11/20/2024, 1:20 AM😭
Andrew Gazelka
11/20/2024, 1:20 AMforgot about those tbh
c
Cory Grinstead
11/20/2024, 2:05 AMi think merge queues are also especially difficult when your CI pipelines take 20-30 minutes. I think if we had like 2-3 minute pipelines, then it wouldn't really matter if 10 PR's were in front of you. It would only be like 30 minutes max. But at 30 minute CI pipelines, thats like 4-5 hours.