Hello. I run 12.0-STABLE r349104 and I tried to run the tests suit in /usr/tests. I got plenty of tests failing. Here is the output of "kyua report": http://termbin.com/r3tid I guess this information could also be helpful: - the custom kernel I am running: http://termbin.com/73cw2 - my make.conf: http://termbin.com/wixu - my src.conf: http://termbin.com/8787 I guess someone could be surprised that I define MACHINE_CPU in my make.conf. I do not think it has anything to do with the tests, but if someone needs to know why I do that, I wrote a wiki article about it: https://wiki.freebsd.org/LorenzoSalvadore/CPUTYPE Let me know if I can help by giving more information. Thanks. Lorenzo Salvadore. Sent with [ProtonMail](https://protonmail.com) Secure Email.
On Tue, Jun 18, 2019 at 4:46 AM Lorenzo Salvadore via freebsd-stable <freebsd-stable at freebsd.org> wrote:> > Hello. > > I run 12.0-STABLE r349104 and I tried to run the tests suit in /usr/tests. > I got plenty of tests failing. > Here is the output of "kyua report": http://termbin.com/r3tid > > I guess this information could also be helpful: > - the custom kernel I am running: http://termbin.com/73cw2 > - my make.conf: http://termbin.com/wixu > - my src.conf: http://termbin.com/8787 > > I guess someone could be surprised that I define MACHINE_CPU in my > make.conf. I do not think it has anything to do with the tests, but if > someone needs to know why I do that, I wrote a wiki article about it: > https://wiki.freebsd.org/LorenzoSalvadore/CPUTYPE > > Let me know if I can help by giving more information. > > Thanks. > > Lorenzo Salvadore.Looks like you found some tests that weren't properly feature gated. The sys/aio test failures, for example, happened because your kernel doesn't include md(4). The sys/audit tests failed because your kernel doesn't include audit(4) etc. All tests are supposed to check that their required features are present, but you found some that didn't. If you want to help, you can try repeating your experiment using the MINIMAL kernel, which should have most of the same failures. Then open a PR and assign to freebsd-testing. Thanks for your QA -Alan
On Tuesday 18 June 2019 16:04, Alan Somers <asomers at freebsd.org> wrote:> On Tue, Jun 18, 2019 at 4:46 AM Lorenzo Salvadore via freebsd-stable > freebsd-stable at freebsd.org wrote: > > > Hello. > > I run 12.0-STABLE r349104 and I tried to run the tests suit in /usr/tests. > > I got plenty of tests failing. > > Here is the output of "kyua report": http://termbin.com/r3tid > > I guess this information could also be helpful: > > > > - the custom kernel I am running: http://termbin.com/73cw2 > > - my make.conf: http://termbin.com/wixu > > - my src.conf: http://termbin.com/8787 > > > > I guess someone could be surprised that I define MACHINE_CPU in my > > make.conf. I do not think it has anything to do with the tests, but if > > someone needs to know why I do that, I wrote a wiki article about it: > > https://wiki.freebsd.org/LorenzoSalvadore/CPUTYPE > > Let me know if I can help by giving more information. > > Thanks. > > Lorenzo Salvadore. > > Looks like you found some tests that weren't properly feature gated. > The sys/aio test failures, for example, happened because your kernel > doesn't include md(4). The sys/audit tests failed because your kernel > doesn't include audit(4) etc. All tests are supposed to check that > their required features are present, but you found some that didn't. > If you want to help, you can try repeating your experiment using the > MINIMAL kernel, which should have most of the same failures. Then > open a PR and assign to freebsd-testing.I will be glad to do as you suggested. Thanks for your answer. Lorenzo Salvadore.