Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.
1
In plain terms. Should we merge our three test-machine setups into one? This is a call for both you and Fede. Our AWS credits ran out Oct 4, so the bill is real now: test machines cost about $390 of $436 a day. Each setup hears every code change today. Merging them saves about $8 a day. Just muting one kind of change saves about $2.50 a day, needs a check with the vendor first, and is Fede's call too since it is a GitHub app setting. The standby-machine question is on hold: 002 is first merging 28,300 tiny jobs a day into one per run (about $17 a day), then re-measuring.
The full question, as raised
Three RunsOn stacks each receive every GitHub event. Per 002's report this is a joint architecture call for Fede and Gera, not Gera alone. Running ONE stack instead of three saves ~$8/day; merely dropping the workflow_run event saves ~$2.5/day, and someone must first confirm RunsOn does not depend on that event. The subscription is a GitHub App setting (third-party config) so the event change needs Fede regardless. Pool size (6 running + 20 stopped is from an earlier review, not a fresh read) is deferred until the tiny-job merge lands under the standing grant.
Why, and what was tried
The session raising this recommends: Merge the three into one That is where the $8/day is; dropping one event saves only about $2.50 and needs a vendor check first. Tried first, unsuccessfully: Trinity's 002 lane audited the AWS bill read-only (Oct 1-4); report on Fede's Mac at ~/agents/002/reports/waste-aws-ci-bill-2026-10-05.md. Report calls this a Fede+Gera architecture decision, so this raise needs both. Prior raises b91258581/b91258837 withdrawn for wrong numbers / missing Fede. 002 fixes the $5.26/day disk add-on now; the $3.2/day duplicate CloudWatch logs need a note to RunsOn (Fede's call, outbound). Do NOT put runners behind a NAT gateway: 20-30 TB/day of free downloads would cost $900-1,350/day.
e12b0ddc is parked on this.
Answered and withdrawn (2)
b91258581 Should we trim two kinds of wasted test-machine spend? Our AWS credits ran out Oct 4, so the bill is now real money: test machines cost about $390 a day. An audit found two waste items that need your call: three machine setups all hearing every change, and too many standby machines. Pick an answer for each. — withdrawn
b91258837 Should we merge our three test-machine setups into one? Our AWS credits ran out Oct 4, so the bill is real now: test machines cost about $390 of $436 a day. Each setup hears every code change today. Merging them saves about $8 a day. Just muting one kind of change saves about $2.50 a day, needs a check with the vendor first, and is Fede's call too since it is a GitHub app setting. The standby-machine question is on hold: 002 is first merging 28,300 tiny jobs a day into one per run (about $17 a day), then re-measuring. — withdrawn