<fossy><stikonas> fossy: for mes libc FILES variable, do we want one file per line? <fossy>what about break at column 80? <stikonas>+ extra line break when parent folder changes <fossy>Ill review again in just a moment <stikonas>fossy: oh, there is a typo in commit message... <stikonas>at least we caught the ones that were happening most frequently <stikonas>yes, and another one is similar with mkdir failure <stikonas>and I think those runs are in QEMU (initramfs) <stikonas>gforce_de1977: can you try inserting sync there? <stikonas>anyway, those errors are infrequent even in gforce_de1977's runs <stikonas>and gforce_de1977 somehow has higher failure rate for intermittent errors <OriansJ`>stikonas[m]: well look at how much RAM you are using stikonas[m] and how much gforce_de1977 is. <OriansJ`>in sufficient memory will reduce RAM caching by the kernel and lead to exposing disk issues. <OriansJ`>especially if the disk IO is choked by a swapfile and applications doing lots of swapping. <OriansJ`>All posix kernels have permission to fail on any system call and applications are expected to check syscall returns for errors but most don't <OriansJ`>So mkdir could have easily gotten an error code and ignored it and happily went on its way to create a bug <OriansJ`>The same for application writes (which are not being retried) <OriansJ`>we could tweak our libc to test that hypothesis and have it write to stderr on a write syscall failure and see if the error message we expect shows up. <Hagfish>that's clever, i've never thought of adding something like that to a libc <OriansJ`>Hagfish: benefits of bootstrapping. no source is immune from being pried open and being played with, so that we can understand how it works. <c4droid>Hi, emm, someone know how to use the bootstrap seeds to build something or write some package definitions? <c4droid>I watched the document, but I still have a little confused <c4droid>I'm current work on make Linux From Scratch to reproducible, using the guix power, but I stucked at using bootstrap seeds build temp toolchain <c4droid>OriansJ`: I watch that, maybe I should make some research for it <c4droid>OriansJ`: Hi, I just take some research, first using mes tool to build guix, then build the lfs cross toolchain, and build the lfs final system, it's that right? <c4droid>mes tool->guix-mesboot->lfs-cross-toolchain(guix-mesboot)->lfs-final-system(guix-mesboot+lfs-cross-toolchain) <gforce_d11977>stikonas: ok, will add a 'sync' after each 'mkdir' too see if it helps. OriansJ: let me first check if a 'sync' helps, if not we can output every write syscall error using stderr ***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
***roptat_ is now known as roptat
***terpri_ is now known as terpri