[Fedora-spins] Re: Unterstanding F24 Spin build failures

[Christian Dersch]

Hi all,

today without changes in spin-kickstarts there are more builds
completed, but some of them still failing. Does anybody know what is
going on there? I'd like to get Astronomy Spin working again, but as
other Spins (Cinnamon, Design, Games, Security and SoaS) are failing too
and the other KDE based spins build fine. First I thought it could be a
space issue, but as there were Spins failing yesterday which build today
without any changes (and the error was the same, squashfs.img creation
failed, for all of them), I doubt that this is the reason.

Greetings,
Christian


On 03/20/2016 12:51 PM, Christian Dersch wrote:
>  Hi all,
>
>  I had a look at build status of F24 live builds, most of them are
>  failing
>  http://koji.fedoraproject.org/koji/tasks?state=all&view=tree&meth...
>  media&order=-id
>
>  Does anybody know why so many builds started to fail some days ago?
>  Today all builds except Workstation, MATE and KDE failed. Astronomy
>  maintained by me is based on KDE and just adds additional packages,
>  installation of packages works fine according to mock_output.log but
>  creation of squashfs image fails. For example Xfce and Design show
>  exactly the same error message:
>
>  2016-03-20 10:40:20,738: Error in atexit._run_exitfuncs:
>  2016-03-20 10:40:20,739: Traceback (most recent call last):
>  2016-03-20 10:40:20,739: File "/usr/sbin/anaconda", line 80, in
>  exitHandler
>  2016-03-20 10:40:20,739: anaconda.storage.umountFilesystems(swapoff=Fals
>  e)
>  2016-03-20 10:40:20,739: File
>  "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 1410, in
>  umountFilesystems
>  2016-03-20 10:40:20,740: self.fsset.umountFilesystems(swapoff=swapoff)
>  2016-03-20 10:40:20,740: File
>  "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 655, in
>  umountFilesystems
>  2016-03-20 10:40:20,740: device.format.teardown()
>  2016-03-20 10:40:20,740: File
>  "/usr/lib/python3.5/site-packages/blivet/formats/__init__.py", line
>  526, in teardown
>  2016-03-20 10:40:20,740: self._teardown(**kwargs)
>  2016-03-20 10:40:20,740: File
>  "/usr/lib/python3.5/site-packages/blivet/formats/fs.py", line 698, in
>  _teardown
>  2016-03-20 10:40:20,741: raise FSError("umount of %s failed (%d)" %
>  (mountpoint, rc))
>  2016-03-20 10:40:20,741: blivet.errors.FSError: umount of
>  /mnt/sysimage/dev/shm failed (32)
>  2016-03-20 10:41:26,703: Shutting down log processing
>  2016-03-20 10:41:28,384: Disk Image install successful
>  2016-03-20 10:41:28,433: working dir is /var/tmp/lmc-work-fkf96tt7
>  2016-03-20 10:41:29,895: Problem zeroing free blocks of
>  /tmp/lmc/lmc-disk-xv0m8u29.img
>  2016-03-20 10:41:29,895: squashfs.img creation failed
>
>  So, why are most builds failing while a small collection (Workstation,
>  MATE and KDE) builds just fine?
>
>  Greetings,
>  Christian
>  _______________________________________________ > spins mailing list >
> spins(a)lists.fedoraproject.org >
http://lists.fedoraproject.org/admin/lists/[e-mail]