Re: Updated installation images for Debian Ports 2019-11-22
On Sat, Nov 30, 2019 at 01:59:36PM +1300, Michael Cree wrote: > (...) It passes more often than not and > only fails occasionally. I see that there is a patch in the > debian/patches directory to avoid a race condition in this test. > But I don't know guile so don't understand the code. There are a few of the "guile" tests that have some timing aspects where sometimes you "win" the race, and other times you "lose". In an earlier private message, I indicated one such test where I had to lengthen the sleep intervals before following actions were taken (because my system is so slow relative to modern hardware). If I didn't mention the specific test, it had to do with making sure the "guild" compiler would clean up after itself if interrupted. On the PWS, it was taking a few more seconds for the interrupt to be received and processed than the test originally allowed. You wouldn't have seen or experienced that particular problem on any of the "buildd" systems. --Bob
Re: Updated installation images for Debian Ports 2019-11-22
On Sat, Nov 30, 2019 at 12:10:28PM +1300, Michael Cree wrote:
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
> arguments: ((system-error "fport_write" "~A" ("Broken pipe") (32)))
>
> Bob: how did you get past this test or did it pass on your build?
It passed on mine. I didn't save the build log for the 2.0 build,
but here's the relevant section of the 2.2 build log:
(...)
make check-TESTS
make[4]: Entering directory '/opt/downloads/work/guile-2.2/guile-2.2-2.2.6+1'
Testing /opt/downloads/work/guile-2.2/guile-2.2-2.2.6+1/meta/guile ...
with GUILE_LOAD_PATH=/opt/downloads/work/guile-2.2/guile-2.2-2.2.6+1/test-suite
Running 00-initial-env.test
Running 00-repl-server.test
Running 00-socket.test
Running alist.test
(...)
--Bob
Re: Updated installation images for Debian Ports 2019-11-22
On Sat, Nov 30, 2019 at 12:10:28PM +1300, Michael Cree wrote:
> On Wed, Nov 27, 2019 at 02:15:30PM +0100, John Paul Adrian Glaubitz wrote:
> I've done a test on an XP1000 (UP) and it got past the failure seen
> on the buildds but errored out in one of 4 or so tests in the
> test suite.
>
> Relevant line in log:
>
> ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
> arguments: ((system-error "fport_write" "~A" ("Broken pipe") (32)))
I've worked out how to run the test manually. Just run:
./check-guile 00-repl-server.test
in the guile build directory. It passes more often than not and
only fails occasionally. I see that there is a patch in the
debian/patches directory to avoid a race condition in this test.
But I don't know guile so don't understand the code.
I could try building again and hope we get a successful build soon...
Cheers,
Michael.
Re: Updated installation images for Debian Ports 2019-11-22
On Wed, Nov 27, 2019 at 02:15:30PM +0100, John Paul Adrian Glaubitz wrote:
> On 11/26/19 4:49 AM, Michael Cree wrote:
> > Taking it that you did use up to date toolchain then that is rather
> > interesting that guile-2.0 built for you. I ran a test rebuild a
> > week or two ago and it failed.
> >
> > Maybe I should try again, but if it fails for me again that would
> > raise issues of:
> >
> > - UP versus SMP since I test built on an SMP system.
> >
> > - sbuild environment.
> >
> > I will set a test rebuild going again soon and report back.
>
> If it's indeed an issue of UMP vs SMP again like we have for openjdk-8, we
> can just blacklist guile-2.0 and guile-2.2 on electro and imago and have
> it built on tsunami only which is a UMP machine.
I've done a test on an XP1000 (UP) and it got past the failure seen
on the buildds but errored out in one of 4 or so tests in the
test suite.
Relevant line in log:
ERROR: 00-repl-server.test: repl-server: HTTP inter-protocol attack -
arguments: ((system-error "fport_write" "~A" ("Broken pipe") (32)))
Bob: how did you get past this test or did it pass on your build?
Cheers,
Michael.
a home-made install CDROM with QLOGIC firmware [was : Re: Updated installation images for Debian Ports 2019-11-22]
Hi, I wonder if the (untested) simple recipe below would work. It would confirm that the missing QLOGIC firmware was indeed the culprit. I hope it will help ! Regards, JH Chatenet # download firmware-qlogic apt-get download firmware-qlogic # become root (to preserve rights) su - # install genisoimage (if not already) apt-get install genisoimage # mount the CD image mkdir my-mount-point && mount -o ro,loop debian-10.0-alpha-NETINST-1.iso my-mount-point # extract the initramfs mkdir my_workdir1 && cd my_workdir1 zcat ../my-mount-point/boot/initrd.gz | cpio -idv # add some firmwares dpkg --fsys-tarfile ../firmware-qlogic_20190717-2_all.deb \ | tar -xvf - ./lib/firmware/qlogic/1040.bin \ ./lib/firmware/qlogic/1280.bin \ ./lib/firmware/qlogic/12160.bin # rebuild the initramfs find . | sort | cpio --create -H newc | gzip -v9 > ../initrd.gz cd .. # rebuild the cdrom image mkdir my_workdir2 (cd my-mount-point && tar -cf - .) | (cd my_workdir2 && tar -xvf -) umount my-mount-point rm my_workdir2/boot/initrd.gz cp -a initrd.gz my_workdir2/boot/ genisoimage -o debian-10.0-alpha-NETINST-1-fw.iso -r -J -joliet-long \ -cache-inodes -l -alpha-boot boot/bootlx \ -V 'Debian 10.0 alpha w fw' my_workdir2
