search

IBT-FMI / gebuilder

Gentoo System and Image Builder
GNU General Public License v3.0
11 stars 0 forks source link

Debugging failed initialization #4

Closed TheChymera closed 6 years ago

TheChymera commented 6 years ago

Other than scrolling up a few more hundred lines, this is about as much as I can reasonably find out about why a SAMRI.gentoo image cannot be built:

d/src/blas/level3/kernel'                                                [151/1905]
make[4]: *** [Makefile:162: dlib] Error 2                                          
make[4]: Leaving directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_share
d/src/blas/level3/kernel'                                                          
make[3]: *** [Makefile:94: dkern] Error 2                                          
make[3]: Leaving directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_share
d/src/blas/level3'                                                                 
make[2]: *** [Makefile:92: IBuildLibs] Error 2                                     
make[2]: Leaving directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_share
d/bin'                                                                             
   DONE  STAGE 5-1-0 at 19:33                                                      

ATLAS install complete.  Examine                                                   
ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details.                              
make[1]: Leaving directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_share
d'                                                                                 
make clean                                                                         
make[1]: Entering directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_shar
ed'                                                                                
rm -f *.o x* config?.out *core*                                                    make[1]: Leaving directory '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_shar$
d'                                                                                 
make: *** No rule to make target 'liblapack.a', needed by 'libclapack.a'.  Stop.
 * ERROR: sci-libs/atlas-3.10.2::gentoo failed (compile phase):
 *   emake failed                                                                  
 *                                                           
 * If you need support, post the output of `emerge --info '=sci-libs/atlas-3.10.2:$
gentoo'`,                                                                         
 * the complete build log and the output of `emerge -pqv '=sci-libs/atlas-3.10.2::$
entoo'`.                                                                            * The complete build log is located at '/var/tmp/portage/sci-libs/atlas-3.10.2/te$
p/build.log'. 
 * The ebuild environment file is located at '/var/tmp/portage/sci-libs/atlas-3.10$
2/temp/environment'.                  
 * Working directory: '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_shared/li$
'                                                                                   * S: '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS'                          
 * Messages for package media-fonts/liberation-fonts-2.00.1-r1:                     * The following fontconfig configuration files have been installed:               
 *                                                                                 
 *   60-liberation.conf
 *                                         
 * Use `eselect fontconfig` to enable/disable them.                                
 * Messages for package media-fonts/stix-fonts-1.1.1:                    
 * The following fontconfig configuration files have been installed:
 *                                                                                 
 *   61-stix.conf                                                        
 *                                  
 * Use `eselect fontconfig` to enable/disable them.                                
 * Messages for package sci-libs/atlas-3.10.2:                            
 * ERROR: sci-libs/atlas-3.10.2::gentoo failed (compile phase):                    
 *   emake failed                                                                  
 *       
 * If you need support, post the output of `emerge --info '=sci-libs/atlas-3.10.2:$
gentoo'`,                                                                          
 * the complete build log and the output of `emerge -pqv '=sci-libs/atlas-3.10.2::$
entoo'`.                                                                           
 * The complete build log is located at '/var/tmp/portage/sci-libs/atlas-3.10.2/te$
p/build.log'.                                                                      
 * The ebuild environment file is located at '/var/tmp/portage/sci-libs/atlas-3.10$
2/temp/environment'.                                                               
 * Working directory: '/var/tmp/portage/sci-libs/atlas-3.10.2/work/ATLAS_shared/li$
'

Ideally I would like to:

Doeme commented 6 years ago

Does the stemgentoo get deleted if the build fails? IIrc it should be preserved, so you can just look at the build log file?

Other than that, there should be logs in the directory described here: https://github.com/IBT-FMI/gebuilder/blob/master/gebuilder/config/generic.conf, i.e. in roots/stemgentoo/logs/initialize/

TheChymera commented 6 years ago

But that's just for stemgentoo itself (as well it should be, given the path). SAMRI.gentoo fails with the aforementioned numpy build, whereas StereotaXYZ.gentoo for some reason manages to build numpy, but fails at scikits_learn. Still:

builder ~/NeuroGentooProject/BuildServer/roots/stemgentoo # ag scikits_learn logs/initialize
logs/initialize/30-emerge_sync.sh.chroot.log
116902:metadata/md5-cache/sci-libs/scikits_learn-0.17
116903:metadata/md5-cache/sci-libs/scikits_learn-0.17.1
116904:metadata/md5-cache/sci-libs/scikits_learn-0.18.1
116905:metadata/md5-cache/sci-libs/scikits_learn-0.18.2
116906:metadata/md5-cache/sci-libs/scikits_learn-0.18.2-r1
116907:metadata/md5-cache/sci-libs/scikits_learn-0.19.0
144439:sci-libs/scikits_learn/
144440:sci-libs/scikits_learn/Manifest
144441:sci-libs/scikits_learn/metadata.xml
144442:sci-libs/scikits_learn/scikits_learn-0.17.1.ebuild
144443:sci-libs/scikits_learn/scikits_learn-0.17.ebuild
144444:sci-libs/scikits_learn/scikits_learn-0.18.1.ebuild
144445:sci-libs/scikits_learn/scikits_learn-0.18.2-r1.ebuild
144446:sci-libs/scikits_learn/scikits_learn-0.18.2.ebuild
144447:sci-libs/scikits_learn/scikits_learn-0.19.0.ebuild
144448:sci-libs/scikits_learn/files/
144449:sci-libs/scikits_learn/files/scikits_learn-0.14.1-system-cblas.patch
144450:sci-libs/scikits_learn/files/scikits_learn-0.17.1-system-cblas.patch
144451:sci-libs/scikits_learn/files/scikits_learn-0.18.1-system-cblas.patch
builder ~/NeuroGentooProject/BuildServer/roots/stemgentoo # ag numpy logs/initialize
logs/initialize/30-emerge_sync.sh.chroot.log
28599:dev-libs/boost-numpy/
28600:dev-libs/boost-numpy/Manifest
28601:dev-libs/boost-numpy/boost-numpy-9999.ebuild
28602:dev-libs/boost-numpy/metadata.xml
42981:dev-python/astroscrappy/files/astroscrappy-1.0.3-numpy-fix-tests.patch
46794:dev-python/numpy/
46795:dev-python/numpy/Manifest
46796:dev-python/numpy/metadata.xml
46797:dev-python/numpy/numpy-1.10.4.ebuild
46798:dev-python/numpy/numpy-1.13.3.ebuild
46799:dev-python/numpy/numpy-1.8.2.ebuild
46800:dev-python/numpy/numpy-1.9.2.ebuild
46801:dev-python/numpy/numpy-9999.ebuild
46802:dev-python/numpy/files/
46803:dev-python/numpy/files/numpy-1.10.2-no-hardcode-blas.patch
46804:dev-python/numpy/files/numpy-1.12.1-no-hardcode-blas.patch
46805:dev-python/numpy/files/numpy-1.8.0-no-hardcode-blas.patch
46806:dev-python/numpy/files/numpy-1.9.2-no-hardcode-blas.patch
46807:dev-python/numpydoc/
46808:dev-python/numpydoc/Manifest
46809:dev-python/numpydoc/metadata.xml
46810:dev-python/numpydoc/numpydoc-0.6.0.ebuild
46811:dev-python/numpydoc/numpydoc-0.7.0.ebuild
47972:dev-python/pyfits/files/02-numpy-deprecation-warning.patch
48446:dev-python/pyplusplus/files/pyplusplus-1.0.0_p20131206-numpy.patch
49883:dev-python/root_numpy/
49884:dev-python/root_numpy/Manifest
49885:dev-python/root_numpy/metadata.xml
49886:dev-python/root_numpy/root_numpy-3.2.0.ebuild
49887:dev-python/root_numpy/root_numpy-3.3.0.ebuild
49888:dev-python/root_numpy/root_numpy-3.3.1.ebuild
49889:dev-python/root_numpy/root_numpy-4.4.0.ebuild
50570:dev-python/statsmodels/files/statsmodels-0.6.1-numpy-1.10.patch
74673:media-gfx/openvdb/files/openvdb-3.2.0-numpy-fix.patch
80349:media-radio/wspr/files/wspr-3.01-numpy.patch
95465:metadata/md5-cache/dev-libs/boost-numpy-9999
101220:metadata/md5-cache/dev-python/numpy-1.10.4
101221:metadata/md5-cache/dev-python/numpy-1.13.3
101222:metadata/md5-cache/dev-python/numpy-1.8.2
101223:metadata/md5-cache/dev-python/numpy-1.9.2
101224:metadata/md5-cache/dev-python/numpy-9999
101225:metadata/md5-cache/dev-python/numpydoc-0.6.0
101226:metadata/md5-cache/dev-python/numpydoc-0.7.0
102188:metadata/md5-cache/dev-python/root_numpy-3.2.0
102189:metadata/md5-cache/dev-python/root_numpy-3.3.0
102190:metadata/md5-cache/dev-python/root_numpy-3.3.1
102191:metadata/md5-cache/dev-python/root_numpy-4.4.0

I assume a similar logs dir is created for each .gentoo root, but is deleted when the initialization fails - right?

Doeme commented 6 years ago

Yes, indeed. Maybe it would be best to just delete roots//root and not roots/

But cleaning failed builds can be disabled here: https://github.com/IBT-FMI/gebuilder/blob/b94200df3bb9825b253e906a414e3d970ebe439b/gebuilder/config/generic.conf#L3

TheChymera commented 6 years ago

It definitely makes sense to not delete the logs.

Perhaps we should also provide a convenience wrapper for chrooting into a failed root? It's tedious to always mount all the devices and easy to forget to then also reload the profile manually...

TheChymera commented 6 years ago

I'd say this is pretty much solved