test

2018-12-11 Thread Sean Bruno
Just testing mailing lists. Delete. sean signature.asc Description: OpenPGP digital signature

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-11 Thread Matthew Macy
0, rsp = 0, rbp = 0 --- > db> > > > Li-Wen > > On Mon, Aug 6, 2018 at 9:53 AM Alan Somers wrote: > > > > I can't reproduce the failure. On my VM, with a kernel from Aug-2, the > test passes. But it sure seems to be consistent in Jenkins. > > > >

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-11 Thread Li-Wen Hsu
0121589b0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- db> Li-Wen On Mon, Aug 6, 2018 at 9:53 AM Alan Somers wrote: > > I can't reproduce the failure. On my VM, with a kernel from Aug-2, the test > passes. But it sure seems to be consistent in Jenkins. > > On Sun, Aug 5, 2018 at 6

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-05 Thread Alan Somers
I can't reproduce the failure. On my VM, with a kernel from Aug-2, the test passes. But it sure seems to be consistent in Jenkins. On Sun, Aug 5, 2018 at 6:59 PM, Matthew Macy wrote: > That looks like it is tied to changes I made 3 months ago. I won't be at > my desk until the end of th

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-05 Thread Matthew Macy
changes matches up > > with the below example (from the log for amd64). It might not? > > > > For example (i386 is similar): > > > > https://ci.freebsd.org/job/FreeBSD-head-amd64-test/8493/consoleText > > > > sys/netinet/fibs_test:subnet_route_with_multiple_fibs

Re: ci.freebsd.org 's FreeBSD-head-{amd64, i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-05 Thread Li-Wen Hsu
; are from Brad Davis. It is unclear to me how the changes matches up > with the below example (from the log for amd64). It might not? > > For example (i386 is similar): > > https://ci.freebsd.org/job/FreeBSD-head-amd64-test/8493/consoleText > > sys/netinet/fibs_test:subn

ci.freebsd.org 's FreeBSD-head-{amd64,i386}-test started failing after -r337332 (last good), inp_gcmoptions involved

2018-08-05 Thread Mark Millard
example (from the log for amd64). It might not? For example (i386 is similar): https://ci.freebsd.org/job/FreeBSD-head-amd64-test/8493/consoleText sys/netinet/fibs_test:subnet_route_with_multiple_fibs_on_same_subnet -> Fatal trap 9: general protection fault while in kernel mode cpuid = 0; a

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-21 Thread Ed Maste
On 21 June 2018 at 09:09, Ed Maste wrote: > > We'll also need a man page. I took a quick look at this, and in doing so found that the output from "llvm-objdump --help" appears to be missing a large number of single-letter options, so one more thing to sort out. As it happens there are LLVM bugs

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-21 Thread Ed Maste
On 20 June 2018 at 17:26, Alexander Richardson wrote: > > When I made the change to use llvm-objdump in CheriBSD I had to change the > objdump flags from -xrsSd to -r -s -p -S -d -h -l -t. Ah yes, I recall discussing this now. Per GNU objdump's man page, -x is equivalent to -a -f -h -p -r -t.

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Alexander Richardson
On Wed, 20 Jun 2018 at 16:50 Brooks Davis wrote: > On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > > Work is in progress to migrate fully to modern and permissively > > licensed components for the tool chain. This includes moving away from > > the three obsolete binutils components

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Shawn Webb
On Wed, Jun 20, 2018 at 07:31:21PM -0400, Ed Maste wrote: > On 20 June 2018 at 18:25, Shawn Webb wrote: > > > > Would you like me to quantify the compilation breakages due to the > > full llvm toolchain switch? If so, I can do that after July 12th. > > Thanks Shawn, right now I'm interested

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Ed Maste
On 20 June 2018 at 18:25, Shawn Webb wrote: > > Would you like me to quantify the compilation breakages due to the > full llvm toolchain switch? If so, I can do that after July 12th. Thanks Shawn, right now I'm interested specifically in llvm-objdump, with the goal of sorting it out in advance

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Shawn Webb
On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > Work is in progress to migrate fully to modern and permissively > licensed components for the tool chain. This includes moving away from > the three obsolete binutils components that are still in the base > system (as, ld, objdump).

Re: Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Brooks Davis
On Wed, Jun 20, 2018 at 10:46:46AM -0400, Ed Maste wrote: > Work is in progress to migrate fully to modern and permissively > licensed components for the tool chain. This includes moving away from > the three obsolete binutils components that are still in the base > system (as, ld, objdump).

Tool Chain Migration: objdump users, please test llvm-objdump

2018-06-20 Thread Ed Maste
Work is in progress to migrate fully to modern and permissively licensed components for the tool chain. This includes moving away from the three obsolete binutils components that are still in the base system (as, ld, objdump). objdump is a tool to report information about binary objects (such as

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-05 Thread Cy Schubert
In message , Li-Wen Hsu writes: > --79b474056de4bc0b > Content-Type: text/plain; charset="UTF-8" > > On Tue, Jun 5, 2018 at 08:10 Cy Schubert wrote: > > > In message <1731a84f-4278-43f5-b498-c3501081e...@yahoo.com>, Mark > > Millard write > > s: > > > >From ci.freebsd.org for a

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-05 Thread Li-Wen Hsu
On Tue, Jun 5, 2018 at 08:10 Cy Schubert wrote: > In message <1731a84f-4278-43f5-b498-c3501081e...@yahoo.com>, Mark > Millard write > s: > > >From ci.freebsd.org for a -r334626 + builds: > > > > --- brk_test.full --- > > cc -target aarch64-unknown-freebsd12.0 >

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-05 Thread Mark Millard
On 2018-Jun-5, at 5:09 AM, Cy Schubert wrote: > In message <1731a84f-4278-43f5-b498-c3501081e...@yahoo.com>, Mark > Millard write > s: >>> From ci.freebsd.org for a -r334626 + builds: >> >> --- brk_test.full --- >> cc -target aarch64-unknown-freebsd12.0

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-05 Thread Cy Schubert
In message <1731a84f-4278-43f5-b498-c3501081e...@yahoo.com>, Mark Millard write s: > >From ci.freebsd.org for a -r334626 + builds: > > --- brk_test.full --- > cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/arm64.aarch > 64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2

Re: svn commit: r334626 - in head: . . . [brk_test fails to build for aarch64 and stops build: no brk or sbrk to test, so undefined symbols]

2018-06-05 Thread Mark Millard
>From ci.freebsd.org for a -r334626 + builds: --- brk_test.full --- cc -target aarch64-unknown-freebsd12.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -O2 -pipe -g -std=iso9899:1999 -fstack-protector-strong -Wsystem-headers -Werror -Wall

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 --- Comment #6 from Charlie Li --- Also could someone remove current@ again? I accidentally used a cached page to comment and didn't pay attention to the CC list. -- You are receiving this mail because: You are

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 w.schwarzenf...@utanet.at changed: What|Removed |Added CC|freebsd-current@FreeBSD.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Conrad Meyer changed: What|Removed |Added CC|freebsd-current@FreeBSD.org |c...@freebsd.org

[Bug 226700] sysutils/e2fsprogs: 1.44.0, test failure on 12-CURRENT

2018-03-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226700 Charlie Li changed: What|Removed |Added CC|

Re: Run binary from test suite

2017-07-12 Thread Panagiotes Mousikides
Den 2017-07-11 kl. 20:05, skrev Ngie Cooper: On Tue, Jul 11, 2017 at 10:38 AM, Panagiotes Mousikides <pagg...@yandex.com> wrote: (Resending due to moderation.) Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests.

Re: Run binary from test suite

2017-07-12 Thread Panagiotes Mousikides
Den 2017-07-11 kl. 18:51, skrev Alan Somers: Are you using pfctl at build time or does your ATF test script need it? I'm assuming the latter. In that case, it's fine to call it directly. Your PATH will be correctly configured. Don't use /usr/obj, because that may no longer exist by the time

Re: Run binary from test suite

2017-07-11 Thread Ngie Cooper
On Tue, Jul 11, 2017 at 10:38 AM, Panagiotes Mousikides <pagg...@yandex.com> wrote: > (Resending due to moderation.) > > Hello! > > I'm a Google Summer of Code student, writing some tests for the FreeBSD test > suite, and putting them under src/tests. I need to run some

Run binary from test suite

2017-07-11 Thread Panagiotes Mousikides
Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let the shell find the binary

Run binary from test suite

2017-07-11 Thread Panagiotes Mousikides
(Resending due to moderation.) Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let

Re: Run binary from test suite

2017-07-11 Thread Alan Somers
Are you using pfctl at build time or does your ATF test script need it? I'm assuming the latter. In that case, it's fine to call it directly. Your PATH will be correctly configured. Don't use /usr/obj, because that may no longer exist by the time somebody is running the ATF test. -Alan On Tue

Re: List test, please ignore.

2017-04-11 Thread Eric Joyner
Never! On Tue, Apr 11, 2017 at 3:18 PM Sean Bruno wrote: > ignore > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

List test, please ignore.

2017-04-11 Thread Sean Bruno
ignore signature.asc Description: OpenPGP digital signature

Re: Laptop very sluggish diring smoke-test @r314036

2017-02-21 Thread David Wolfskill
; Mateusz Guzik Well I "cloned" my head slice (4) to slice 3, updating source on slice 3 to r313995, rebooted to slice 3... and noticed that it didn't seem slugglish at all (unlike the earlier "smoke-test"). So before I did anything else, I rebooted it... and the countdown afte

Re: Laptop very sluggish diring smoke-test @r314036

2017-02-21 Thread Mateusz Guzik
On Tue, Feb 21, 2017 at 06:39:08AM -0800, David Wolfskill wrote: > This morning's daily "head" update & smoke-test was from: > > FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #263 > r313988M/313991:1200021: Mon Feb 20 06:31:32 PST 2017 > r...@

Laptop very sluggish diring smoke-test @r314036

2017-02-21 Thread David Wolfskill
This morning's daily "head" update & smoke-test was from: FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #263 r313988M/313991:1200021: Mon Feb 20 06:31:32 PST 2017 r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 to FreeBSD g1-252.catwh

Re: Please test EARLY_AP_STARTUP

2016-12-01 Thread Sepherosa Ziehau
On Fri, Dec 2, 2016 at 12:53 PM, Sepherosa Ziehau wrote: > On Fri, Dec 2, 2016 at 1:49 AM, John Baldwin wrote: >> On Thursday, December 01, 2016 01:53:29 PM Sepherosa Ziehau wrote: >>> On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau

Re: Please test EARLY_AP_STARTUP

2016-12-01 Thread Sepherosa Ziehau
On Fri, Dec 2, 2016 at 1:49 AM, John Baldwin wrote: > On Thursday, December 01, 2016 01:53:29 PM Sepherosa Ziehau wrote: >> On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau >> wrote: >> >>> After fdc is disabled and hyperv/storvsc is fixed, it seems to

Re: Please test EARLY_AP_STARTUP

2016-12-01 Thread John Baldwin
On Thursday, December 01, 2016 01:53:29 PM Sepherosa Ziehau wrote: > On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau wrote: > >>> After fdc is disabled and hyperv/storvsc is fixed, it seems to boot > >>> fine, except a long delay (28~30seconds) here: > >>> > >>>

Re: Please test EARLY_AP_STARTUP

2016-11-30 Thread Sepherosa Ziehau
On Wed, Nov 30, 2016 at 9:59 AM, Sepherosa Ziehau wrote: > On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin wrote: >> On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: >>> Hi John, >>> >>> fdc seems to cause panic on Hyper-V: >>>

Re: Please test EARLY_AP_STARTUP

2016-11-29 Thread Sepherosa Ziehau
On Tue, Nov 29, 2016 at 2:27 AM, John Baldwin wrote: > On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: >> Hi John, >> >> fdc seems to cause panic on Hyper-V: >> https://people.freebsd.org/~sephe/fdc_panic.png > > You shouldn't get this panic in latest HEAD

Re: Please test EARLY_AP_STARTUP

2016-11-28 Thread Oliver Pinter
On 11/25/16, John Baldwin wrote: > I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks > have been testing it for the last week or so which has exposed some > additional things to fix. I think I've resolved most of those in one > way or another, but it will

Re: Please test EARLY_AP_STARTUP

2016-11-28 Thread John Baldwin
On Monday, November 28, 2016 02:35:07 PM Sepherosa Ziehau wrote: > Hi John, > > fdc seems to cause panic on Hyper-V: > https://people.freebsd.org/~sephe/fdc_panic.png You shouldn't get this panic in latest HEAD (post-r309148). > I then commented out device fdc, and I fixed one panic on Hyper-V

Re: Please test EARLY_AP_STARTUP

2016-11-27 Thread Sepherosa Ziehau
Hi John, fdc seems to cause panic on Hyper-V: https://people.freebsd.org/~sephe/fdc_panic.png I then commented out device fdc, and I fixed one panic on Hyper-V here: https://reviews.freebsd.org/D8656 After fdc is disabled and hyperv/storvsc is fixed, it seems to boot fine, except a long delay

Re: Please test EARLY_AP_STARTUP

2016-11-27 Thread John Baldwin
On Sunday, November 27, 2016 12:46:31 PM O. Hartmann wrote: > Am Fri, 25 Nov 2016 10:20:36 -0800 > John Baldwin schrieb: > > > I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks > > have been testing it for the last week or so which has exposed some > >

Re: Please test EARLY_AP_STARTUP

2016-11-27 Thread O. Hartmann
Am Fri, 25 Nov 2016 10:20:36 -0800 John Baldwin schrieb: > I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks > have been testing it for the last week or so which has exposed some > additional things to fix. I think I've resolved most of those in one >

Please test EARLY_AP_STARTUP

2016-11-25 Thread John Baldwin
I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks have been testing it for the last week or so which has exposed some additional things to fix. I think I've resolved most of those in one way or another, but it will make things smoother if other folks can start testing this

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-25 Thread Mark Millard
tests should all be fixed. I opened PR 210329 for the >>> usr.bin/lastcomm test. I haven't investigated the others. > > ... > >> This time the totals were 15 broken (down from 24) and 41 failed (down >> from 59). >> >> My results this time were. . .

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-25 Thread Ngie Cooper
29 for the >> usr.bin/lastcomm test. I haven't investigated the others. ... > This time the totals were 15 broken (down from 24) and 41 failed (down > from 59). > > My results this time were. . . Hi Mark, Please file bugs for all of the individual component failures, e.g

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-24 Thread Mark Millard
On 2016-Jun-24, at 2:50 PM, Alan Somers <asom...@freebsd.org> wrote: > As of r302180., the usr.sbin/rpcbind, sys/acl, and sys/sys/bitstring > tests should all be fixed. I opened PR 210329 for the > usr.bin/lastcomm test. I haven't investigated the others. > > -Alan

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-24 Thread Alan Somers
>> > On Mon, Jun 13, 2016 at 11:29 AM, Mark Millard <mar...@dsl-only.net >> > > wrote: >> > > With the newly less strict alignment requirements "kyua test -k >> > > /usr/tests/Kyuafile" runs to completion, unlike before. >> > &

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Ian Lepore
> bit_alloc(int _nbits) > { > - return ((bitstr_t *)calloc(bitstr_size(_nbits), 1)); > + return (calloc(howmany(bitstr_size(_nbits), > sizeof(bitstr_t)), > + sizeof(bitstr_t))); > } > #endif > > > > > > > On Mon, J

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Conrad Meyer
(bitstr_t))); } #endif On Mon, Jun 13, 2016 at 10:49 AM, Alan Somers <asom...@freebsd.org> wrote: > Please open a bug for the bitstring test failures and assign it to me. > Also, since I don't have any arm hardware, please provide instructions > on how to run this code in a VM,

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Alan Somers
r_t * >> bit_alloc(int _nbits) >> { >> - return ((bitstr_t *)calloc(bitstr_size(_nbits), 1)); >> + return (calloc(howmany(bitstr_size(_nbits), sizeof(bitstr_t)), >> + sizeof(bitstr_t))); >> } >> #endif >> >> >> >>

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Mark Millard
[I've added a list of core files generated and a few other notes.] On 2016-Jun-13, at 10:29 AM, Mark Millard wrote: > With the newly less strict alignment requirements "kyua test -k > /usr/tests/Kyuafile" runs to completion, unlike before. > >> ===> Summary &g

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Mark Millard
On 2016-Jun-13, at 10:49 AM, Alan Somers wrote: > Please open a bug for the bitstring test failures and assign it to me. > Also, since I don't have any arm hardware, please provide instructions > on how to run this code in a VM, or where I can get access to the > hardware. >

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Conrad Meyer
nbits), sizeof(bitstr_t)), > + sizeof(bitstr_t))); > } > #endif > > > > > > > On Mon, Jun 13, 2016 at 10:49 AM, Alan Somers <asom...@freebsd.org> wrote: >> Please open a bug for the bitstring test failures and assign it to me. >> Also, since I don't have any

Re: 11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Alan Somers
Please open a bug for the bitstring test failures and assign it to me. Also, since I don't have any arm hardware, please provide instructions on how to run this code in a VM, or where I can get access to the hardware. -Alan On Mon, Jun 13, 2016 at 11:29 AM, Mark Millard <mar...@dsl-only.

11.0 -r301815 "kyua test -k /usr/tests/Kyuafile" on rpi2 [armv7-a/cortex-a7]: broken (24) and failing (59) lists

2016-06-13 Thread Mark Millard
With the newly less strict alignment requirements "kyua test -k /usr/tests/Kyuafile" runs to completion, unlike before. > ===> Summary > Results read from > /root/.kyua/store/results.usr_tests.20160613-080302-120731.db > Test cases: 5694 total, 54 skipped, 21 expecte

Re: please test your commits

2016-05-04 Thread Adrian Chadd
sorry, big pointyhat here. I only did a kernel test. I'll have to figure out a cleaner way to fix this. (this is all so we don't have collisions with the linux "struct device" for linuxkpi updates, fwiw.) -a On 4 May 2016 at 18:53, Ngie Cooper (yaneurabeya) <yaneurab...@gma

Re: please test your commits

2016-05-04 Thread Ngie Cooper (yaneurabeya)
> On May 4, 2016, at 17:56, Steve Kargl > wrote: > > % make -j7 buildworld |& tee sgk.log > > --- lib/libkvm__L --- > In file included from /usr/src/lib/libkvm/kvm_pcpu.c:43: > /usr/obj/usr/src/tmp/usr/include/sys/pcpu.h:163:2: error: unknown type name >

please test your commits

2016-05-04 Thread Steve Kargl
% make -j7 buildworld |& tee sgk.log --- lib/libkvm__L --- In file included from /usr/src/lib/libkvm/kvm_pcpu.c:43: /usr/obj/usr/src/tmp/usr/include/sys/pcpu.h:163:2: error: unknown type name 'device_t' device_tpc_device; ^ -- Steve

Re: Missing locales causing test failures

2015-11-16 Thread Baptiste Daroussin
; en_AU.ISO8859-15 > en_CA.ISO8859-15 > en_NZ.ISO8859-15 > en_US.ISO8859-15 > fr_CA.ISO8859-15 > lt_LT.ISO8859-4 > sr_YU.ISO8859-2 > sr_YU.ISO8859-5 > sr_YU.UTF-8 > > Can we bring these back? Their absence is causing test failures. > I would be surprised they do caus

Re: Missing locales causing test failures

2015-11-16 Thread Craig Rodrigues
e latest build. The latest build still has some > > missing locales, > > > > > > af_ZA.ISO8859-15 > > en_AU.ISO8859-15 > > en_CA.ISO8859-15 > > en_NZ.ISO8859-15 > > en_US.ISO8859-15 > > fr_CA.ISO8859-15 > > lt_LT.ISO8859-4 > > sr_YU.

Missing locales causing test failures

2015-11-16 Thread Craig Rodrigues
.ISO8859-2 sr_YU.ISO8859-5 sr_YU.UTF-8 Can we bring these back? Their absence is causing test failures. -- Craig ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "

Re: Quick test building a module cross all targets and architectures

2015-11-03 Thread Hans Petter Selasky
On 10/27/15 17:16, Hans Petter Selasky wrote: On 10/27/15 16:49, John Baldwin wrote: With MAKE_JUST_WORLDS you would only build a "generic" module once per architecture. That savings is likely far more than the cost of the additional tools. I will try it out. Thanks for your hints and

Re: Quick test building a module cross all targets and architectures

2015-11-03 Thread Ian Lepore
On Tue, 2015-11-03 at 13:24 +0100, Hans Petter Selasky wrote: > On 10/27/15 17:16, Hans Petter Selasky wrote: > > On 10/27/15 16:49, John Baldwin wrote: > > > With MAKE_JUST_WORLDS you would only build > > > a "generic" module once per architecture. That savings is likely > > > far > > > more >

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Hans Petter Selasky
On 10/26/15 19:03, John Baldwin wrote: On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote: Hi, We have NO_MODULES for building kernel without modules, but no NO_KERNEL to only build the modules. What do you think about the following patch: diff --git a/sys/conf/kern.post.mk

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Hans Petter Selasky
ifferrent. Hi, I understand that the compilation environments are different. How would you suggest to build-test a handful of C-files under a single device keyword and associated kernel module cross all kernels we have in a 10-minutes time-frame? MODULES_OVERRIDE can be defined from within

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Hans Petter Selasky
On 10/27/15 13:16, Konstantin Belousov wrote: On Tue, Oct 27, 2015 at 10:31:26AM +0100, Hans Petter Selasky wrote: I understand that the compilation environments are different. How would you suggest to build-test a handful of C-files under a single device keyword and associated kernel module

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Hans Petter Selasky
On 10/27/15 13:16, Konstantin Belousov wrote: On Tue, Oct 27, 2015 at 10:31:26AM +0100, Hans Petter Selasky wrote: I understand that the compilation environments are different. How would you suggest to build-test a handful of C-files under a single device keyword and associated kernel module

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Konstantin Belousov
On Tue, Oct 27, 2015 at 10:31:26AM +0100, Hans Petter Selasky wrote: > I understand that the compilation environments are different. > > How would you suggest to build-test a handful of C-files under a single > device keyword and associated kernel module cross all kernels we hav

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Ian Lepore
; > > How would you suggest to build-test a handful of C-files under a > > > single > > > device keyword and associated kernel module cross all kernels we > > > have in > > > a 10-minutes time-frame? MODULES_OVERRIDE can be defined from > > > with

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread John Baldwin
On Tuesday, October 27, 2015 10:06:41 AM Hans Petter Selasky wrote: > On 10/26/15 19:03, John Baldwin wrote: > > On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote: > >> Hi, > >> > >> We have NO_MODULES for building kernel without modules, but no NO_KERNEL > >> to only build the

Re: Quick test building a module cross all targets and architectures

2015-10-27 Thread Hans Petter Selasky
On 10/27/15 16:49, John Baldwin wrote: With MAKE_JUST_WORLDS you would only build a "generic" module once per architecture. That savings is likely far more than the cost of the additional tools. I will try it out. Thanks for your hints and tips. --HPS

Re: Quick test building a module cross all targets and architectures

2015-10-26 Thread Adrian Chadd
+1 to this thankyou! -adrian On 26 October 2015 at 02:11, Hans Petter Selasky wrote: > Hi, > > We have NO_MODULES for building kernel without modules, but no NO_KERNEL to > only build the modules. > > What do you think about the following patch: > >> diff --git

Quick test building a module cross all targets and architectures

2015-10-26 Thread Hans Petter Selasky
Hi, We have NO_MODULES for building kernel without modules, but no NO_KERNEL to only build the modules. What do you think about the following patch: diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk index ddf828e..f0920df 100644 --- a/sys/conf/kern.post.mk +++

Re: Quick test building a module cross all targets and architectures

2015-10-26 Thread Adrian Chadd
for modules. I am only aware of > exceptions for i915kms, which was done for a reason which is no longer > valid. In other words, if your goal is to check that the change does not > break compilation of some kernel code, then it is wrong to not compile > kernels. > > Note tha

Re: Quick test building a module cross all targets and architectures

2015-10-26 Thread John Baldwin
On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote: > Hi, > > We have NO_MODULES for building kernel without modules, but no NO_KERNEL > to only build the modules. > > What do you think about the following patch: > > > diff --git a/sys/conf/kern.post.mk b/sys/conf/kern.post.mk >

Re: Quick test building a module cross all targets and architectures

2015-10-26 Thread Konstantin Belousov
On Mon, Oct 26, 2015 at 11:03:07AM -0700, John Baldwin wrote: > On Monday, October 26, 2015 10:11:43 AM Hans Petter Selasky wrote: > > Hi, > > > > We have NO_MODULES for building kernel without modules, but no NO_KERNEL > > to only build the modules. > > > > What do you think about the

Re: sa(4) driver changes available for test

2015-08-24 Thread Kenneth D. Merry
-byte tape record bigger than supplied buffer Is this just informational? If so, I'll ignore it. Yes, it's informational. It tells you that your tape blocks are 64512 bytes long. Or at least the first one is. The initial tape mount inside the sa(4) driver does a test read with an 8K buffer

Re: sa(4) driver changes available for test

2015-08-24 Thread Dan Langille
On Mar 2, 2015, at 12:26 PM, Kenneth D. Merry k...@freebsd.org wrote: On Mon, Mar 02, 2015 at 11:43:15 -0500, Dan Langille wrote: On Mar 1, 2015, at 9:06 PM, Kenneth D. Merry k...@freebsd.org wrote: On Sun, Mar 01, 2015 at 19:40:40 -0500, Dan Langille wrote: On Mar 1, 2015, at 7:36

Re: Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-11 Thread Ed Maste
On 8 June 2015 at 11:29, Adrian Chadd adr...@freebsd.org wrote: Sigh. This patch: https://people.freebsd.org/~adrian/net80211/20150524-iwn-delay-xmit-passive-1.diff along with the latest net80211 tree in -HEAD will buffer frames until the first beacon is received after association. It

Re: Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-11 Thread Adrian Chadd
Hi , Thanks. It didn't look like it even attempted to transmit on the 5ghz band at all (no SCAN - AUTH, then xmit attempts.) -a ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-11 Thread Poul-Henning Kamp
In message CAPyFy2Cd5FgOKoTEvFNH3PHL-t0Q6roYV9nYgLK3jkBXJpe=l...@mail.gmail.com , Ed Maste writes: I'm running with the patch at BSDCan. Failed to associate several times at 5Ghz before settling on channel 11 (2462 MHz 11g ht/20). A log with: wlandebug +assoc +state +rate sysctl

Re: Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-11 Thread Adrian Chadd
On 11 June 2015 at 05:03, Poul-Henning Kamp p...@phk.freebsd.dk wrote: In message CAPyFy2Cd5FgOKoTEvFNH3PHL-t0Q6roYV9nYgLK3jkBXJpe=l...@mail.gmail.com , Ed Maste writes: I'm running with the patch at BSDCan. Failed to associate several times at 5Ghz before settling on channel 11

Re: Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-08 Thread David Wolfskill
On Mon, Jun 08, 2015 at 08:29:17AM -0700, Adrian Chadd wrote: Sigh. This patch: https://people.freebsd.org/~adrian/net80211/20150524-iwn-delay-xmit-passive-1.diff along with the latest net80211 tree in -HEAD will buffer frames until the first beacon is received after association. It

please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-08 Thread Adrian Chadd
Hi, This patch: ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Those at BSDCan 2015: please test: iwn(4) patch to buffer 5ghz frames before transmitting

2015-06-08 Thread Adrian Chadd
Sigh. This patch: https://people.freebsd.org/~adrian/net80211/20150524-iwn-delay-xmit-passive-1.diff along with the latest net80211 tree in -HEAD will buffer frames until the first beacon is received after association. It doesn't (yet!) purge frames in all the right places, but it should be

Re: What's the official method to test the build now?

2015-03-22 Thread Garrett Cooper
On Mar 21, 2015, at 5:32, Ryan Stone ryst...@gmail.com wrote: I still see the compile errors that I reported here: https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054803.html It affects these builds: sparc64 LINT kernel failed, check _.sparc64.LINT for details powerpc

Re: What's the official method to test the build now?

2015-03-21 Thread Garrett Cooper
On Mar 21, 2015, at 06:35, Ian Lepore i...@freebsd.org wrote: On Fri, 2015-03-20 at 19:52 -0400, Ryan Stone wrote: make tinderbox has been broken for weeks, so I presume it's not what I'm supposed to be using to test my commits anymore. What's the officially supported make target that I'm

Re: What's the official method to test the build now?

2015-03-21 Thread Ryan Stone
I still see the compile errors that I reported here: https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054803.html It affects these builds: sparc64 LINT kernel failed, check _.sparc64.LINT for details powerpc LINT kernel failed, check _.powerpc.LINT for details powerpc LINT64

Re: What's the official method to test the build now?

2015-03-21 Thread Ian Lepore
On Fri, 2015-03-20 at 19:52 -0400, Ryan Stone wrote: make tinderbox has been broken for weeks, so I presume it's not what I'm supposed to be using to test my commits anymore. What's the officially supported make target that I'm supposed to use? I use make universe, sometimes

Re: What's the official method to test the build now?

2015-03-21 Thread Dimitry Andric
On 21 Mar 2015, at 17:25, Garrett Cooper yaneurab...@gmail.com wrote: On Mar 21, 2015, at 06:35, Ian Lepore i...@freebsd.org wrote: On Fri, 2015-03-20 at 19:52 -0400, Ryan Stone wrote: make tinderbox has been broken for weeks, so I presume it's not what I'm supposed to be using to test my

Re: What's the official method to test the build now?

2015-03-21 Thread Garrett Cooper
for weeks, so I presume it's not what I'm supposed to be using to test my commits anymore. What's the officially supported make target that I'm supposed to use? I use make universe, sometimes with the -DMAKE_JUST_KERNELS option. make universe doesn't error out; make tinderbox does however

Re: What's the official method to test the build now?

2015-03-20 Thread NGie Cooper
On Fri, Mar 20, 2015 at 4:52 PM, Ryan Stone ryst...@gmail.com wrote: make tinderbox has been broken for weeks, so I presume it's not what I'm supposed to be using to test my commits anymore. What's the officially supported make target that I'm supposed to use? It should work. If it doesn't

What's the official method to test the build now?

2015-03-20 Thread Ryan Stone
make tinderbox has been broken for weeks, so I presume it's not what I'm supposed to be using to test my commits anymore. What's the officially supported make target that I'm supposed to use? ___ freebsd-current@freebsd.org mailing list http

SLR140 with new mt(1) [Was: Re: sa(4) driver changes available for test]

2015-03-11 Thread Harald Schmalzbauer
to add DDS5 to the density table in libmt. Can you send the output of 'mt status -v'? It would actually be helpful for all three drives. Hello, I'd like to present some test results. All tests were done with 10-stable-r273923 and Ken's sa_driver_changes-patchset, reduced by the commited scsi-sys

Re: SLR140 with new mt(1) [Was: Re: sa(4) driver changes available for test]

2015-03-11 Thread Kenneth D. Merry
correctly, you have your DDS4 reporting DDS4? That means that we need to add DDS5 to the density table in libmt. Can you send the output of 'mt status -v'? It would actually be helpful for all three drives. Hello, I'd like to present some test results. All tests were done with 10-stable

Re: sa(4) driver changes available for test

2015-03-11 Thread Kenneth D. Merry
On Sat, Mar 07, 2015 at 14:30:26 +0100, Harald Schmalzbauer wrote: Bez?glich Kenneth D. Merry's Nachricht vom 19.02.2015 01:13 (localtime): I have updated the patches. I have removed the XPT_DEV_ADVINFO changes from the patches to head, since I committed those separately. I have

  1   2   3   4   5   6   7   8   >