svn commit: r338404 - head/sys/conf

[Mark Millard]

On 2018-Aug-31, at 9:40 AM, Glen Barber <gjb at FreeBSD.org> wrote:

> On Fri, Aug 31, 2018 at 09:34:00AM -0700, Mark Millard wrote:
>> On Fri, Aug 31, 2018 at 02:20:09PM +0000, Glen Barber wrote:
>>>> On Fri, Aug 31, 2018 at 08:51:29AM -0400, Ed Maste wrote:
>>>>> On 30 August 2018 at 22:46, Glen Barber <gjb at freebsd.org> wrote:
>>>>>> 
>>>>>> As I look closer at the log, I have a sneaking suspicion this may have
>>>>>> been a transient.  I'm redoing the i386 build against the original
>>>>>> r338401 for i386 alone as a test, if nothing else, to see if it fails in
>>>>>> the same place.
>>>>> 
>>>>> What's the failure?
>>>> 
>>>>>>> stage 3.1: building everything
>>>> --------------------------------------------------------------
>>>> In file included from /usr/src/sys/kern/genoffset.c:35:
>>>> In file included from /usr/src/sys/sys/param.h:96:
>>>> /usr/src/sys/sys/types.h:46:10: fatal error: 'machine/endian.h' file not found
>>>> #include <machine/endian.h>
>>>>          ^~~~~~~~~~~~~~~~~~
>>>> 1 error generated.
>>>> --- genoffset.o ---
>>>> *** [genoffset.o] Error code 1
>>>> 
>>>> So far, 100% reproducible with an empty /usr/obj/.
>>>> 
>>>>> I see head/i386 is green in CI.
>>>>> 
>>>> 
>>>> Does CI prune .OBJDIR for each build?
>>>> 
>>> 
>>> Make that 75% reproducible.  I suspect there is a build race occurring.
>> 
>> ci.freebsd.org occasionally shows examples of this race. For example:
>> 
>> https://ci.freebsd.org/job/FreeBSD-head-powerpc-build/7454/consoleText
>> 
>> shows:
>> 
>> --- genoffset.o ---
>> /usr/src/sys/sys/types.h:46:28: error: machine/endian.h: No such file or directory
>> *** [genoffset.o] Error code 1
>> 
>> for -r338319 but the prior build (for -r338318) and
>> following build (for -r338320) worked fine.
>> 
>> -r338319 was for something that should make no difference
>> to the issue:
>> 
>> QUOTE
>> Remove trailing slash in pathname so that valid METALOG is created in the
>> NO_ROOT case of make packages.
>> END QUOTE
>> 
>> I've seen other occasional examples.
>> 
> 
> Thanks for the link to this specific failure.  I see nothing in that
> range of commits that should have any impact here.  What caused me to
> back out the ALPHA rename is this is the first time I've seen this since
> the code freeze started, and following the first failure, restarted the
> builds with the same result.
> 
> I'll go poking around at the CI console output to try to find when the
> first occurrence happened.

Other than I'd seen the one on ci.free.org recently and thought
"oh, that again" and "although its been a long time", I think
the failures have been rare enough that without an archive of files
to search automatically, it would not be practical to find examples
via just looking around via the web interface for ci.freebsd.org .

I've seen rare failures in personal builds. But most of my
personal builds are incremental where a old file would be
around. So I expect more rare for this context. But I do
not remember the ci.freebsd.org vs. personal status for
the one I saw prior to the one that I reported --or when.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)