verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
vilhalmer has quit [Ping timeout: 255 seconds]
wielaard has quit [Quit: Leaving]
mjw has joined #buildbot
vilhalmer has joined #buildbot
vilhalmer has quit [Quit: :qa!]
vilhalmer has joined #buildbot
razrdog[m] has quit [Ping timeout: 260 seconds]
flx[m] has quit [Ping timeout: 260 seconds]
gonewest818[m] has quit [Ping timeout: 260 seconds]
gonewest818[m] has joined #buildbot
uovobw has quit [Ping timeout: 252 seconds]
uovobw has joined #buildbot
flx[m] has joined #buildbot
razrdog[m] has joined #buildbot
Vesryn has quit [*.net *.split]
dol-sen has quit [*.net *.split]
sknebel has quit [*.net *.split]
abby has quit [*.net *.split]
Vesryn has joined #buildbot
abby has joined #buildbot
sknebel has joined #buildbot
dol-sen has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by markw!~wielaard@gnu.wildebeest.org))]
wielaard has joined #buildbot
vilhalmer has quit [Ping timeout: 252 seconds]
vilhalmer has joined #buildbot
SirScott has joined #buildbot
<SirScott> Newb question: Got an EC2 latent worker configured. In my master.cfg, I have `f = util.BuildFactory(); f.addStep(steps.ShellCommand(command=['df', '-hP'])); f.addStep(steps.ShellCommand(command=['yum', 'install', '-y', 'git']))
<SirScott> When I force the build, the ec2 instance launches and successfully connects and the build steps start running. In the output of the first step, I see 500GB free space on /, which is what I'd expect.
<SirScott> The yum install fails though - stating that 74MB more space is needed on /
<SirScott> Am I missing some core concept? Is there a chroot, or something else going on that would be responsible for this?