Learn more about these different git repos.
Other Git URLs
The f22 updates-testing atomic compose is failing. There's not too much in the logs:
{{{ DEBUG util.py:495: Executing command: ['/bin/sh', '-c', '/usr/bin/rpm-ostree compose tree --workdir-tmpfs --repo=/srv/fedor a-atomic/22/x86_64/docker-host /tmp/tmpuT3cv5/fedora-atomic.git/treefile.json'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt 100', 'SHELL': '/bin/bash', 'PROMPT_COMMAND': 'printf "\x1b]0;<mock-chroot>\x07<mock-chroot>"', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/builddir', 'HOSTNAME': 'mock'} and shell False DEBUG util.py:417: Previous commit: d5538ace45f71e0d4e089af1cf67211a1f8e01ed3d613250974138fd5e1076e6 DEBUG util.py:417: Downloading metadata: 1% DEBUG util.py:542: Child return code was: -11 }}}
which looks like things are crashing. I cannot find a core.
Nothing I can see off hand has changed in f22 updates-testing since the last working compose. The compose machine hasn't been updated, no new rpm-ostree, hawkey, libhif, etc updates. Nothing related seems to be in the current push.
It would be good if we could gather a core / stacktrace so we could see whats happening.
So, it seems we had been using a side repo for f22 updates-testing composes:
'f22-temprepo': 'file:///mnt/koji/mash/updates/f22-temprepo/',
In this repo was: rpm-ostree-2015.7-6.fc22 f22-updates-testing had: rpm-ostree-2015.7-3.fc22
I have unpushed the one in updates-testing (which has been there a year), re-added the tmp repo so we can get a compose out, then disabled it again. The next push should use the version in f22 updates, so hopefully will work.
The pushes worked, we are all back on track.
Metadata Update from @kevin: - Issue set to the milestone: Fedora 24 Alpha
Login to comment on this ticket.