On Thu, Jun 21, 2018 at 10:49 PM Mark Millard wrote:
> Has the range r328278 < PROBLEM_START <= r330304 been narrowed down
> some more?
>
> (I'm just curious were the problem started.)
After several rounds of binary search, I found it might have something
todo with r329625.
The only thing I thin
On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote:
> On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>>
>> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>>
>>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
Li-Wen reported that the build is done in a 11.1-rel jail though, so
the li
On 2018-Jun-19, at 9:14 PM, Li-Wen Hsu wrote:
> On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>>
>> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>>
>>> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
Li-Wen reported that the build is done in a 11.1-rel jail though, so
the
On Tue, Jun 19, 2018 at 9:24 PM Mark Millard wrote:
>
> On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
>
> > On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> >> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> >> the libarchive (or any userland) change shouldn't be responsi
On 2018-Jun-19, at 8:02 AM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
>> Li-Wen reported that the build is done in a 11.1-rel jail though, so
>> the libarchive (or any userland) change shouldn't be responsible.
>>
>> Can we update a canary builder to somewhere betwe
On Mon, Jun 18, 2018 at 8:36 PM Ed Maste wrote:
> Li-Wen reported that the build is done in a 11.1-rel jail though, so
> the libarchive (or any userland) change shouldn't be responsible.
>
> Can we update a canary builder to somewhere between r328278 and r88?
butler1.nyi.freebsd.org is runnin
On 2018-Jun-18, at 6:03 PM, Mark Millard wrote:
> On 2018-Jun-18, at 4:08 PM, Bryan Drewery wrote:
>
>> On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
>>> ranlib -D libpcap.a
>>> ranlib: fatal: Failed to open 'libpcap.a'
>>
>> Where is this error even coming from? It's not in the usr.bin/ar code
>> an
On 2018-Jun-18, at 4:08 PM, Bryan Drewery wrote:
> On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
>> ranlib -D libpcap.a
>> ranlib: fatal: Failed to open 'libpcap.a'
>
> Where is this error even coming from? It's not in the usr.bin/ar code
> and ranlib does not cause it.
>
> # ranlib -D uh
> ranlib
On 18 June 2018 at 19:29, Bryan Drewery wrote:
>
> The error is coming from libarchive which had a change between those
> revisions:
>
>>
>> r328332 | mm | 2018-01-24 06:24:17 -0800 (Wed, 24 Jan 2018) | 14 lines
Li-Wen repor
On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 5:04 PM Mark Millard via freebsd-toolchain
> wrote:
>>
>> On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
>>
>>> On 6/15/2018 10:55 PM, Mark Millard wrote:
In watching ci.freebsd.org builds I've seen a notable
number of
On 6/18/2018 3:27 PM, Li-Wen Hsu wrote:
> ranlib -D libpcap.a
> ranlib: fatal: Failed to open 'libpcap.a'
Where is this error even coming from? It's not in the usr.bin/ar code
and ranlib does not cause it.
# ranlib -D uh
ranlib: warning: uh: no such file
--
Regards,
Bryan Drewery
signature
On 6/18/2018 3:31 PM, Li-Wen Hsu wrote:
> On Mon, Jun 18, 2018 at 6:27 PM Bryan Drewery wrote:
>>
>> On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
>>> On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
On 6/15/2018 10:55 PM, Mark Millard wrote:
> In watching ci.freebsd.org
On Mon, Jun 18, 2018 at 5:04 PM Mark Millard via freebsd-toolchain
wrote:
>
> On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
>
> > On 6/15/2018 10:55 PM, Mark Millard wrote:
> >> In watching ci.freebsd.org builds I've seen a notable
> >> number of one time failures, such as (example from
> >>
On Mon, Jun 18, 2018 at 6:27 PM Bryan Drewery wrote:
>
> On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
> > On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
> >> On 6/15/2018 10:55 PM, Mark Millard wrote:
> >>> In watching ci.freebsd.org builds I've seen a notable
> >>> number of o
On 6/18/2018 1:45 PM, Konstantin Belousov wrote:
> On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
>> On 6/15/2018 10:55 PM, Mark Millard wrote:
>>> In watching ci.freebsd.org builds I've seen a notable
>>> number of one time failures, such as (example from
>>> powerpc64):
>>>
>>> --
On 2018-Jun-18, at 12:42 PM, Bryan Drewery wrote:
> On 6/15/2018 10:55 PM, Mark Millard wrote:
>> In watching ci.freebsd.org builds I've seen a notable
>> number of one time failures, such as (example from
>> powerpc64):
>>
>> --- all_subdir_lib/libufs ---
>> ranlib -D libufs.a
>> ranlib: fat
On Mon, Jun 18, 2018 at 12:42:46PM -0700, Bryan Drewery wrote:
> On 6/15/2018 10:55 PM, Mark Millard wrote:
> > In watching ci.freebsd.org builds I've seen a notable
> > number of one time failures, such as (example from
> > powerpc64):
> >
> > --- all_subdir_lib/libufs ---
> > ranlib -D libufs.a
On 6/15/2018 10:55 PM, Mark Millard wrote:
> In watching ci.freebsd.org builds I've seen a notable
> number of one time failures, such as (example from
> powerpc64):
>
> --- all_subdir_lib/libufs ---
> ranlib -D libufs.a
> ranlib: fatal: Failed to open 'libufs.a'
> *** [libufs.a] Error code 70
>
18 matches
Mail list logo
