| === frankban|afk is now known as frankban | ||
| wgrant | cjwatson: https://oops.canonical.com/oops/?oopsid=OOPS-4a0aaf3e8e9d686dd25943a55533b842 and https://oops.canonical.com/oops/?oopsid=OOPS-144400735e2b864ade9a821b80988e40 look like regressions from the target picker work. Possibly easier for you to grab them since you have context, but otherwise I'll have a look. | 09:58 |
|---|---|---|
| cjwatson | wgrant: The latter is bug 1628091, the former is new. Will look, thanks. | 10:54 |
| mup | Bug #1628091: oops when loading bug <Launchpad itself:New> <https://launchpad.net/bugs/1628091> | 10:54 |
| === frankban is now known as frankban|afk | ||
| mkayaalp | I'm running a local launchpad.dev. When building a livefs, it always gets stuck at BuildStatus.UPLOADING | 17:55 |
| mkayaalp | Should I be starting process-upload script manually? | 17:56 |
| cjwatson | mkayaalp: Yes, that won't run unless you do so. | 19:30 |
| mkayaalp | The soyuz docs mention some cron job that launches the process-upload | 20:38 |
| mkayaalp | Where would that be | 20:39 |
| mkayaalp | I don't see anything related under cronscripts | 20:39 |
| mkayaalp | I can run it: scripts/process-upload.py --builds /var/tmp/builddmaster | 20:40 |
| mkayaalp | But it exits when it's done processing all under incoming | 20:41 |
| mkayaalp | So, in production does the ubuntu-cdimage wait until the cron job starts the process-upload? | 20:43 |
| cjwatson | mkayaalp: The production cron job is: | 20:59 |
| cjwatson | * * * * * /srv/launchpad.net/codelines/current/scripts/process-upload.py -C buildd --builds /srv/launchpad.net/builddmaster/ -q --log-file=DEBUG:/srv/launchpad.net/production-logs/process-build-uploads.log | 20:59 |
| cjwatson | (obviously path-dependent) | 20:59 |
| cjwatson | mkayaalp: And yes, it will exit when it's finished processing what's in incoming; it's a cron job, not a daemon | 21:00 |
| cjwatson | mkayaalp: ubuntu-cdimage waits until the build's buildstate attribute on the webservice API reaches "Successfully built", which happens when the upload from the builder is processed. | 21:01 |
| cjwatson | mkayaalp: See lib/cdimage/livefs.py:run_live_builds in lp:ubuntu-cdimage | 21:01 |
| cjwatson | mkayaalp: (You must use -C buildd; processing builder uploads without that isn't going to work, since the default upload policy only accepts sourceful uploads and requires a signature.) | 21:03 |
| mkayaalp | cjwatson: thanks a lot | 21:08 |
| wgrant | mkayaalp: Are you familar with https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally? It's more oriented towards binary package builds, but many of the same pieces apply. | 21:11 |
| mkayaalp | wgrant: I am running soyuz locally too | 21:12 |
| mkayaalp | wgrant: That's what gets the build into the UPLOADING state after building it | 21:16 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!