to 13. kesäk. 2024 klo 11.52 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > Adding the dnsmasq maintainer in CC. > > to 13. kesäk. 2024 klo 11.39 Paul Gevers (elb...@debian.org) kirjoitti: > > On 13-06-2024 3:36 a.m., Martin-Éric Racine wrote: > > > Subsequent ones randomly timeout waiting for an IP from the DHCP > > > server. This could well be an issue with dnsmasq, which is what we use > > > for the test. Alternately, it could be caused by those constant fails > > > on glibc. Without more detailed logs, I am not in a position to > > > investigate this. Help is welcome. > > > > Well, I can't give you more logs than what your test writes. So that's > > in your hands, I suggest you try and make the test more verbose of > > what's going on, or maybe ensure some logs end up in the artifacts for > > inspection. Also, if dnsmasq is the problem, you might want to contact > > the maintainer and discuss the issue (e.g. in a bug report). From my > > standpoint, it's the autopkgtest of dhcpcd that's having issues and that > > *is* an issue for src:dhcpcd. You could reassign this bug and mark it > > "affects dhcpcd". > > I'm curious to hear whether any of what appears in the log rings any > bell for Simon. > > > I acknowledge that something fishy seems to be ongoing in the archive > > when new version of src:glibc binaries appear (not only with dhcpcd I > > mean). For now I'll not hold that against autopkgtest failures of > > packages too much. > > Which is where I suspect the real issue is. > > Personally, I already find it suspicious that the tracker tells me > about unrelated packages' transitions or issues. If the problem is in > someone else's code, while mine hasn't changed in ages, that's where > the bug report needs to go. In this case, dhcpcd's autopkgtest hasn't > changed in ages, and has been verified to work as-is at Ubuntu, where > isolation machines were implemented a long time before Debian.
Sorry Paul but, at this point, I'm gonna call CI itself flaky. Right now, CI hasn't even registered any test attemps for recent uploads to Unstable and its results for Testing out of sync. Given this, if you're gonna start mass-filing bugs against any package whose test reults show discrepancy, first make sure that, in fact, your code is not the one causing others unnecesary work. Martin-Éric
