Comment 7 for bug 1668353
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 1668353] Re: Linux kernel autopkgtests often fail due to version mismatch between running kernel and tested kernel. | #7 |
On Mon, Feb 27, 2017 at 10:30:39PM -0000, Iain Lane wrote:
> I was under the impression that these are 'real' failures that need to
> be investigated. Let's take the latest one at the time of writing, which
> I suggest you download rather than opening in your browser
> https:/
> /autopkgtest-
> ...this reports that the 'ubuntu-
> If you go to line 74580 you can see that the current kernel in
> zesty-proposed gets installed. The machine then reboots (74830), and the
> tests report that the new one is in use and is the same version as the
> source package (75248).
> I feel like I'm probably misunderstanding the issue - so if you could
> point to lines in a log file that show the issue you're talking about as
> a problem in the infrastructure, we could certainly take a look at the
> problem.
It's possible that when I talked to Robert about the problem, I was
operating on stale data. If those are all genuine failing tests, that's
also bad.
But when I look at that last log, which shows in the table as: Version:
4.10.0-9.11, Triggers: gcc-6/6.
*wrong* version of Linux is being tested. Why are we testing a
proposed-only version of the kernel to validate the new upload of gcc-6 in
proposed? We should be testing the released version of linux.
That looks to me like the autopkgtest behavior has changed, as a workaround
for the previous failures, but that it's still not testing the pairs that we
would want tested for CI.