Kernel tests

3 views
Skip to first unread message

Xiao Jia

unread,
Oct 20, 2015, 2:32:07 PM10/20/15
to aka...@googlegroups.com
Why some of them are DISABLED?

And do we need to fix those FAILED user tests?

<-- BEGIN_KERNEL_TESTS -->
<-- BEGIN_KERNEL_POSTBOOT_TESTS -->
DISABLED [test_ipi_sending]
DISABLED [test_pic_reception]
DISABLED [test_lapic_status_bit]
DISABLED [test_pit]
DISABLED [test_circ_buffer]
DISABLED [test_kernel_messages]
DISABLED [test_barrier]
PASSED   [test_interrupts_irqsave](0.000003s)   
PASSED   [test_bitmasks](0.000003s)   
DISABLED [test_checklists]
DISABLED [test_smp_call_functions]
DISABLED [test_slab]
DISABLED [test_kmalloc]
PASSED   [test_hashtable](0.000008s)   
DISABLED [test_bcq]
DISABLED [test_ucq]
PASSED   [test_vm_regions](0.000007s)   
PASSED   [test_radix_tree](0.000186s)   
DISABLED [test_random_fs]
DISABLED [test_kthreads]
DISABLED [test_kref]
PASSED   [test_atomics](0.000003s)   
DISABLED [test_abort_halt]
DISABLED [test_cv]
PASSED   [test_memset](0.000040s)   
DISABLED [test_setjmp]
DISABLED [test_apipe]
DISABLED [test_rwlock]
DISABLED [test_rv]
DISABLED [test_alarm]
DISABLED [test_kmalloc_incref]
DISABLED [test_u16pool]
<-- END_KERNEL_POSTBOOT_TESTS -->
<-- END_KERNEL_TESTS -->
mlx4_en: ether0: Link Up
<-- BEGIN_USERSPACE_TESTS -->
<-- BEGIN_USERSPACE_ALARMS_TESTS -->
FAILED   [test_alarm](1.000034s)   Assertion failure in test_alarm() at alarm.c:30: Alarms finished too soon
<-- END_USERSPACE_ALARMS_TESTS -->
<-- BEGIN_USERSPACE_EXAMPLE_TESTS -->
PASSED   [test_one](0.000000s)   
PASSED   [test_two](0.000000s)   
PASSED   [test_three](0.000000s)   
<-- END_USERSPACE_EXAMPLE_TESTS -->
<-- BEGIN_USERSPACE_FILE POSIX_TESTS -->
open f1.txt: Bad file number, Bad FD 3

FAILED   [test_openat](0.003902s)   
<-- END_USERSPACE_FILE POSIX_TESTS -->
<-- BEGIN_USERSPACE_PVCALARMS_TESTS -->
FAILED   [test_pvcalarms](1.021728s)   Assertion failure in test_pvcalarms() at pvcalarm.c:32: Alarms finished too soon
PASSED   [test_sigperf](1.005419s)   
<-- END_USERSPACE_PVCALARMS_TESTS -->
<-- BEGIN_USERSPACE_SIGNALS_TESTS -->
PASSED   [test_sigmask](0.177255s)   
<-- END_USERSPACE_SIGNALS_TESTS -->
<-- END_USERSPACE_TESTS -->

Kevin Klues

unread,
Oct 20, 2015, 2:36:36 PM10/20/15
to aka...@googlegroups.com
The disabled ones are ones that we haven't bothered to port properly
(they were originally written to just run by hand so don't conform to
the correct style dictated by the test suite). They will always fail.

Those user tests tend to fail in qemu because they are based on tsc
times which qemu sometimes gets confused about. I've mucked with them
to get them to pass on qemu in the past, but not reliably. If you
have suggestions for how to make them more reliable, that would be
great.
> --
> You received this message because you are subscribed to the Google Groups
> "Akaros" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to akaros+un...@googlegroups.com.
> To post to this group, send email to aka...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
~Kevin

Barret Rhoden

unread,
Oct 20, 2015, 2:41:06 PM10/20/15
to aka...@googlegroups.com
On 2015-10-20 at 11:31 Xiao Jia <stf...@gmail.com> wrote:
> Why some of them are DISABLED?

A few reasons. Some were meant to be run manually from the monitor,
some trash the state of the OS, some might just be loud and always
succeed, some might not work anymore, etc.


> And do we need to fix those FAILED user tests?

Probably.

> <-- BEGIN_USERSPACE_ALARMS_TESTS -->
> FAILED [test_alarm](1.000034s) Assertion failure in test_alarm()
> at alarm.c:30: Alarms finished too soon

IIRC, this one is racy, but no one has gotten around to fixing it.

> <-- END_USERSPACE_ALARMS_TESTS -->
> <-- BEGIN_USERSPACE_EXAMPLE_TESTS -->
> PASSED [test_one](0.000000s)
> PASSED [test_two](0.000000s)
> PASSED [test_three](0.000000s)
> <-- END_USERSPACE_EXAMPLE_TESTS -->
> <-- BEGIN_USERSPACE_FILE POSIX_TESTS -->
> open f1.txt: Bad file number, Bad FD 3
> FAILED [test_openat](0.003902s)

This one fails because the VFS doesn't support openat.

> <-- END_USERSPACE_FILE POSIX_TESTS -->
> <-- BEGIN_USERSPACE_PVCALARMS_TESTS -->
> FAILED [test_pvcalarms](1.021728s) Assertion failure in
> test_pvcalarms() at pvcalarm.c:32: Alarms finished too soon

Or maybe this is the racy one. Or maybe both.

Barret

Reply all
Reply to author
Forward
0 new messages