Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Donnerstag, 13. November 2014, Steven Chamberlain wrote: I think we're missing some data from the end of the serial.log; probably due to some buffering, and qemu being sent SIGKILL. Please consider this change to use SIGINT for up to 10 seconds, then SIGKILL only if it's still running after that: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=894584fca2 66789c8f40b4c0cad60b7909385523 did you make this never returns false? The script will immidiatly end in that case, iirc... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, Holger Levsen wrote: On Donnerstag, 13. November 2014, Steven Chamberlain wrote: Please consider this change to use SIGINT for up to 10 seconds, then SIGKILL only if it's still running after that: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=894584fca266789c8f40b4c0cad60b7909385523 did you make this never returns false? The script will immidiatly end in that case, iirc... Are you thinking of -e (exit on error)? g-i-installation.sh doesn't seem to run in that mode, actually it ignores some failing commands already during cleanup steps. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141114120218.gc26...@squeeze.pyro.eu.org
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Freitag, 14. November 2014, Steven Chamberlain wrote: Are you thinking of -e (exit on error)? yes g-i-installation.sh doesn't seem to run in that mode, actually it ignores some failing commands already during cleanup steps. yes, but during cleanup +e is explicitly set, I think. Oh, well, I suppose I should either merge and see how it fails or read the code myself before merging... ;-) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Holger Levsen wrote: g-i-installation.sh doesn't seem to run in that mode, actually it ignores some failing commands already during cleanup steps. yes, but during cleanup +e is explicitly set, I think. Aha yes it does set +e inside that function. But code before and after it does ignore + have to handle fatal errors itself. The code I added shouldn't return false, except maybe a race between 'ps' and 'kill' (if the process goes away in that time); but seems unlikely with the 'sleep 1' after each iteration. Oh, well, I suppose I should either merge and see how it fails or read the code myself before merging... ;-) Well, you were right; I didn't think to check for a set +e in the script, only looked for something like that at the top of the script and assumed it was safe to return false anywhere. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141114123321.gg26...@squeeze.pyro.eu.org
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Freitag, 14. November 2014, Steven Chamberlain wrote: Aha yes it does set +e inside that function. But code before and after it does ignore + have to handle fatal errors itself. The code I added shouldn't return false, except maybe a race between 'ps' and 'kill' (if the process goes away in that time); but seems unlikely with the 'sleep 1' after each iteration. ok, cool, thanks for checking! +merged+pushed+deployed+job triggered :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Holger, Holger Levsen wrote: I don't understand why getting the preseed file then fails... https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/433/screenshot/full After I started at the error message long enough, it finally hit me, and it's kind of amusing. If you could please fix my silly mistake: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=b463b29fdcf5ec4104a2df624690aac8f23481a1 Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141114131949.ge26...@squeeze.pyro.eu.org
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi Steven, On Freitag, 14. November 2014, Steven Chamberlain wrote: After I started at the error message long enough, it finally hit me, and it's kind of amusing. If you could please fix my silly mistake: hehe, I know that feeling... :-) merged + triggered etc.. - thanks! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Mittwoch, 12. November 2014, Samuel Thibault wrote: Maybe hurd also could redirect syslog there to help debug the issue you're seeing. Indeed. actually, all installs can probably benefit from this :) There is: console=com0, it'd only redirect the kernel messages though (which can however be useful to get the out of the vga console output, and in a safe place) [...] Yes, it'd be com0 for GNU/Hurd. patches, please. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, On Mittwoch, 12. November 2014, Steven Chamberlain wrote: Holger Levsen wrote: in the video there is no IP address to be seen. em0 gets a link, but thats all. Later 'network autoconfiguration succeeded', so DHCP probably worked; the IP address isn't usually mentioned within the GUI installer, but the d-i syslog will probably explain what the problem is. ok, cool. Okay I've tried to log serial console output as an artifact, if you could pull again please: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=adc905d26d 93381495a47ece2259207009f0da5e merged+pushed, thanks. Will trigger new builds once jenkins.d.n is up again, there are currently some disturbances in the cloud... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Hi, https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/432/artifact/results/serial.log is there now and it shows how the right IP is received. I don't understand why getting the preseed file then fails... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Holger Levsen wrote: https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_kfreebsd/432/artifact/results/serial.log is there now and it shows how the right IP is received. I don't understand why getting the preseed file then fails... I think we're missing some data from the end of the serial.log; probably due to some buffering, and qemu being sent SIGKILL. Please consider this change to use SIGINT for up to 10 seconds, then SIGKILL only if it's still running after that: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=894584fca266789c8f40b4c0cad60b7909385523 Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141113134537.ge23...@squeeze.pyro.eu.org
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Holger Levsen wrote: in the video there is no IP address to be seen. em0 gets a link, but thats all. Later 'network autoconfiguration succeeded', so DHCP probably worked; the IP address isn't usually mentioned within the GUI installer, but the d-i syslog will probably explain what the problem is. -serial file, to write those separately as an artifact whatever you prefer really. I tend to somewhat prefer the latter... optionally output that at the end of the job... Okay I've tried to log serial console output as an artifact, if you could pull again please: https://git.steven.hosting.pyro.eu.org/jenkins.debian.net.git/?h=adc905d26d93381495a47ece2259207009f0da5e Maybe hurd also could redirect syslog there to help debug the issue you're seeing. Unless there's a convenient kernel parameter to send console messages there, you could always use preseed/early_command to modify inittab like I did here: https://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/commit/?id=f85e9c3f8dcc4283120e77794a150daad930da46 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141112192613.ga19...@squeeze.pyro.eu.org
Re: jenkins kfreebsd jobs (Re: Plan B for kfreebsd)
Steven Chamberlain, le Wed 12 Nov 2014 19:26:14 +, a écrit : Maybe hurd also could redirect syslog there to help debug the issue you're seeing. Indeed. Unless there's a convenient kernel parameter to send console messages there, There is: console=com0, it'd only redirect the kernel messages though (which can however be useful to get the out of the vga console output, and in a safe place) you could always use preseed/early_command to modify inittab like I did here: https://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/commit/?id=f85e9c3f8dcc4283120e77794a150daad930da46 Yes, it'd be com0 for GNU/Hurd. Samuel -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141112220600.gj3...@type.youpi.perso.aquilenet.fr
