| === ChanServ changed the topic of #launchpad to: Help contact: jugmac00 (07:00-15:00 UTC) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad | ||
| LocutusOfBorg | hello, please don't forget the s390x stick when possible | 08:32 |
|---|---|---|
| LocutusOfBorg | https://en.wikipedia.org/wiki/King-Size_Homer#/media/File:King-Size_Homer.png | 08:37 |
| LocutusOfBorg | or maybe https://tenor.com/view/computer-drinking-bird-keyboard-the-simpsons-gif-8025433 | 08:38 |
| jugmac00 | LocutusOfBorg: I am currently in a meeting, will have a look later. | 08:45 |
| LocutusOfBorg | thanks! | 08:46 |
| jugmac00 | LocutusOfBorg: I have done a reset of the cleaning builders. Let's wait a couple of minutes whether this did the trick. | 09:32 |
| LocutusOfBorg | thanks! | 09:52 |
| LocutusOfBorg | jugmac00, sadly the stick was probably not enough long to reach the correct button? | 09:53 |
| jugmac00 | LocutusOfBorg: I will talk with the team what would be the next step | 09:55 |
| seb128 | jugmac00, LocutusOfBorg, autopkgtests have the same issue so I would guess it's an IS problem and not a launchpad team one | 09:56 |
| cjwatson | jugmac00: no point, there's already a half-hourly automatic reset job. | 10:01 |
| cjwatson | resetting manually makes no difference to that | 10:02 |
| LocutusOfBorg | so its a bos01 problem? | 10:03 |
| cjwatson | yes | 10:06 |
| LocutusOfBorg | I hope the bits will sort out soon, keep up the good work! | 10:07 |
| jugmac00 | LocutusOfBorg: This is an IS issue, and they are aware of it and investigating. That is all I can say for now. | 11:10 |
| LocutusOfBorg | well, looks like bos02 is crunching s390x jobs, so the situation is at least partially working! | 11:10 |
| mitya57 | Is the Debian importer broken? LP still doesn't have my pymca and python-docutils uploads from 1.5 days ago. | 11:25 |
| LocutusOfBorg | maybe the reason is the bos2 failure above^ | 11:26 |
| jugmac00 | mitya57: yes, it is broken, and we are aware of it, see https://answers.launchpad.net/launchpad/+question/704509 | 11:26 |
| mitya57 | Ok, thanks! | 11:27 |
| LocutusOfBorg | oh noes, the old/new non-free-firmware is causing new troubles? | 11:27 |
| cjwatson | actually a Debian archive bug, just filing it | 11:50 |
| cjwatson | https://bugs.debian.org/1029497 | 11:51 |
| -ubottu:#launchpad- Debian bug 1029497 in ftp.debian.org "ftp.debian.org: weird non-free-firmware/dep11 structure in bookworm" [Normal, Open] | 11:51 | |
| cjwatson | LocutusOfBorg: (it is not possible for a bos02 failure to cause Debian importer issues, for the record) | 11:52 |
| cjwatson | Or a bos01 failure for that matter | 11:53 |
| LocutusOfBorg | oh ok thanks, for sure my brain is failing to remember such things then... | 12:03 |
| kkeithley | not sure if this is the right place (maybe #launchpad-dev instead?) I fired off a few builds on Saturday. Two days later the s390x builds still haven't run. All weekend the status said 'Start in 60 minutes'. Now it says start in 9 minutes. Are the s390x builders just backed up or is there something else going on? Thanks | 12:53 |
| jugmac00 | kkeithley: There are currently issues with bos01 - the bos02 are working, at least some of them. IS is already investigating. | 12:59 |
| === cpaelzer_ is now known as cpaelzer | ||
| cjwatson | bos01 is not perfect but it's looking quite a lot healthier now, so the s390x queue should start draining | 15:25 |
| ginggs | \o/ | 16:04 |
| === jose_ is now known as jose | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
