Walkingmind / embox

Automatically exported from code.google.com/p/embox
2 stars 0 forks source link

Correctness of semaphore_timedwait #669

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.x86/zrv-qt
2.r12339
3.

What is the expected output? What do you see instead?
    test: running embox.test.kernel.thread.sy   test: running embox.test.kernel.thread.sync.sem_test .
    failure at src/tests/kernel/thread/sync/sem_test.c : 80, in function h_high_run
        test_assert_zero(semaphore_timedwait(&s, &time))
       case at src/tests/kernel/thread/sync/sem_test.c : 91
        "Correctness of semaphore_timedwait"

    testing sem_test (Semaphore test) failed
        1/2 failures
Failed to get into level 3, current level 0
nc.sem_test .
    failure at src/tests/kernel/thread/sync/sem_test.c : 80, in function h_high_run
        test_assert_zero(semaphore_timedwait(&s, &time))
       case at src/tests/kernel/thread/sync/sem_test.c : 91
        "Correctness of semaphore_timedwait"

    testing sem_test (Semaphore test) failed
        1/2 failures
Failed to get into level 3, current level 0

Please use labels and text to provide additional information.

Original issue reported on code.google.com by ki.stfu on 8 Jan 2014 at 2:39

GoogleCodeExporter commented 9 years ago

Original comment by ki.stfu on 16 Jan 2014 at 9:39

GoogleCodeExporter commented 9 years ago
very slow machine (qemu) can be a reason, changed in r14037

Original comment by drakon.m...@gmail.com on 8 Aug 2014 at 9:38