[00:16] oSoMoN: The tinyjsd removal wants to be a removal + sync blacklist (to prevent it coming back from Debian), right? [11:07] cpaelzer, coreycb: please could you pick up these in your team: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html#ubuntu-server [11:07] seb128, Wimpress: same for desktop: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html#desktop-packages [11:07] jamespage: openstack: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html#ubuntu-openstack [11:08] mdeslaur, sbeattie: and security: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html#ubuntu-security [11:10] apw, sforshee: and kernel: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html#kernel-packages [11:11] doko, what is that rebuilding against? [11:22] doko, yes [11:22] (is that just gcc-10 or somethign else) [11:48] doko: thanks for the heads up - we'll take a look [12:18] doko: we have already started on it [12:19] is that a different link than the one in your mail? [12:19] no, seems to be the same - so yes we already started [12:20] doko: what is the source for your team mapping? [12:21] doko: some openstack bits ended up in ur bucket - e.g. nfs-ganesha [12:21] this mapping looks correct [12:21] hence I'm asking what your script is based on [12:27] doko: I have recently seen "internal compiler error: Segmentation fault" on armhf a few times (groovy) [12:27] doko: is there a known bug around that in progress already? [12:30] could be 1887557 [12:31] apw: see u-d-a, -release [12:33] cpaelzer: I saw only one which succeeded on a retry. package? [12:35] doko: qemu 2/5 armhf builds failed - no build log that shows it currently [12:35] doko: I filed 1890435 to ahve something to dump further insights to [12:36] one ongoing build which might or might not fail at https://launchpad.net/ubuntu/+source/qemu/1:5.0-5ubuntu4/+build/19773244 [12:36] and this issue seems (from 10.000 feet) similar https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1887557 [12:36] Launchpad bug 1887557 in gcc-10 (Ubuntu) "GCC 10 is crashing with an internal compiler error when compiling Mesa" [Undecided,New] [12:38] I attached a failing build log that I still had on disk [12:39] doko, most of the kernel ones look to be genuinly detected double definitions; which i assume is a new fatal warning [12:41] Sounds like the -fno-common change [12:46] cpaelzer: that is focal only, fixed in groovy [12:48] thanks doko [12:48] doko: in that case I'll keep an eye open and report on that bug I filed if I see it happen more often [12:49] or if I get to a reproducible state [12:53] the one I saw for llvm-11 goes away with a rebuild too [14:41] When is Ubuntu going to have Intel Optane support? Trying to install it on my new laptop, no go. Acer A515-55-56HH, no bios options to disable Optane, UEFI mode only, etc. Secure boot is disabled. [15:03] ask intel [15:22] tafb2: hi, we currently do not support RST and we also give instructions to users on how to disable it, if we detect it is on. [15:23] tafb2: the url for instructions is at https://help.ubuntu.com/rst [15:24] tafb2: which effectively asks to diable Optate. [15:24] tafb2: you say you have no option to disable it however =( i'm not sure that's possible to support then. Because Intel Optane support is not available on linux at all. [15:25] tafb2: if not possible from Bios, you should be able to disable it after booting into windows too [15:25] i.e. https://support.cyberpowerpc.com/hc/en-us/articles/360014775073-How-do-I-disable-Intel-Optane- seems to be relevant too [15:32] xnox: neat, never figured you could disable from Windows, I'll give that a try, thanks so much. [15:38] xnox: In installed Intel RST but when I open it and go into settings it says "your system is not Intel Optane ready" lol :( I go into the bios, under SATA Mode: Optane (no raid), but you can't change it. Hmmm. Maybe i'll put a call into Acer, see if they know how to disable it. === lucas_ is now known as lucascastro [15:53] tafb2: that sounds very odd, or new, or very restrictive. [15:54] tafb2: if you do figure out how to do it, please comment on https://help.ubuntu.com/rst such that we can improve instructions there. [15:54] tafb2: and hopefully next person (or you with next laptop ;-) ) will have that readily available to lookup [17:42] xnox: just got off the phone with acer, level 2 support, no way to disable Optane on that laptop. He put a suggestion into the firmware department to put a setting in the bios to disable Optane in the next bios update (if ever). [17:47] xnox: the instructions for rufus are pretty messy, just use the "reply" button at the bottom to suggest changes? [17:49] tafb2: Yeap, just reply. === cnewcome- is now known as cnewcomer [18:04] "new users are temporarily limited to 3 replies in the same topic" so much for that, lol. I'll try again in a few days. [19:49] wait how does optane relate to rst [21:32] ahasenack looking at the logs I'm a little confused [21:33] link? and bug number [21:33] https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/1883175 [21:33] Launchpad bug 1883175 in python-flake8 (Ubuntu Focal) "missing support for python3.8 language features" [Low,Fix committed] [21:33] https://autopkgtest.ubuntu.com/packages/u/update-manager/focal/amd64 [21:34] arnatious: ok, so it's elpy that failed [21:35] The bug was fixed by a version bump to 3 related packages, it looks like the tests were triggered multiple times, is it safe to assume in each of those triggered tests all 3 packages were at their latest version? [21:35] arnatious: by clicking on amd64 (the test with a red), you get to https://autopkgtest.ubuntu.com/packages/e/elpy/focal/amd64 [21:35] that shows which packages were used in the test [21:36] it also shows that it was passing before [21:36] same version [21:37] I have no idea what elpy is, but this is the test that failed: [21:37] 1 unexpected results: [21:37] FAILED elpy-profile-buffer-or-region-test-indir-failed [21:37] Looks like the failed test case was elpy-profile-buffer-or-region-test-indir-failed [21:37] and that needs investigation [21:37] right [21:37] Yeah this looks like python language support for emacs [21:38] Judging by the lisp code [21:38] It might need a version bump as well to support python 3.8 [21:39] ok, good luck, that's how troubleshooting goes [21:39] I'll work on testing that theory, in the meanwhile, the other failure cases are interesting [21:39] Update-manager and release-manager both failed, then passed [21:40] They had two separate triggered tests for the containing packages [21:41] it can be a maze tracking these down [21:41] I have to go, it's end of day for me, good luck [21:41] As a ROS dev, all I can say is better than no testing [21:41] Thanks ahasenack [21:42] indeed [23:53] tafb2: mwhudson: i think one implied the other, and optane is now end of life?! unless got resurrected? https://www.intel.co.uk/content/www/uk/en/support/articles/000055419/technologies.html [23:54] tafb2: mwhudson: unless i am very confused, one uses optane tech, to effectively bcache the drive, which requires the drive to be in the raid / RSTe mode.