QEMU NIOS2 sporadic FAIL in tests/legacy/kernel/test_context

[nashif]

Reported by Javier B Perez:

https://logs.zephyrproject.org/production/vex-yul-zep-jenkins-1/zephyr-verify/ Builds: 10955, 11000, 11055

tc_start() - Test Nanokernel CPU and thread routines
Initializing nanokernel objects
Testing interrupt locking and unlocking
Testing irq_disable() and irq_enable()
===================================================================
FAIL - main.
===================================================================
PROJECT EXECUTION FAILED

Found 3 in 254 builds.

(Imported from Jira ZEP-1238)

[nashif]

by Mark Linkmeyer:

Fixing incorrect priority

[nashif]

by Andrew Boie:

Inaky Perez-Gonzalez do we still see this issue?

[nashif]

by Ramakrishna Pallala:

Mark Linkmeyer , This issue not valid anymore as we don't have "tests/legacy/kernel/test_context" test app.

I have ran the same test which is now under "tests/kernel/context" and it passes on qemu_nios2. We can close this issue now.

make[3]: 'isr_tables.o' is up to date. To exit from QEMU enter: 'CTRL+a, x' [QEMU] CPU: nios2 cpu->env.reset_addr: 0 cpu->env.exception_addr: 400020 BOOTING ZEPHYR OS v1.8.99 - BUILD: Jun 30 2017 00:26:02 tc_start() - Test kernel CPU and thread routines Initializing kernel objects Testing interrupt locking and unlocking Testing irq_disable() and irq_enable() Testing some kernel context routines Testing k_current_get() from an ISR and task Testing k_is_in_isr() from an ISR Testing k_is_in_isr() from a preemptible thread Spawning a thread from a task Thread to test k_current_get() and k_is_in_isr() Thread to test k_yield() Testing k_busy_wait() Thread busy waiting for 20000 usecs Thread busy waiting completed Testing k_sleep() thread sleeping for 50 milliseconds thread back from sleep Testing k_thread_create() without cancellation thread (q order: 2, t/o: 500) is running got thread (q order: 2, t/o: 500) as expected thread (q order: 3, t/o: 750) is running got thread (q order: 3, t/o: 750) as expected thread (q order: 0, t/o: 1000) is running got thread (q order: 0, t/o: 1000) as expected thread (q order: 6, t/o: 1250) is running got thread (q order: 6, t/o: 1250) as expected thread (q order: 1, t/o: 1500) is running got thread (q order: 1, t/o: 1500) as expected thread (q order: 4, t/o: 1750) is running got thread (q order: 4, t/o: 1750) as expected thread (q order: 5, t/o: 2000) is running got thread (q order: 5, t/o: 2000) as expected Testing k_thread_create() with cancellations cancelling [q order: 0, t/o: 1000, t/o order: 0] thread (q order: 3, t/o: 750) is running got (q order: 3, t/o: 750, t/o order 1) as expected thread (q order: 0, t/o: 1000) is running got (q order: 0, t/o: 1000, t/o order 2) as expected cancelling [q order: 3, t/o: 750, t/o order: 3] cancelling [q order: 4, t/o: 1750, t/o order: 4] thread (q order: 4, t/o: 1750) is running got (q order: 4, t/o: 1750, t/o order 5) as expected cancelling [q order: 6, t/o: 1250, t/o order: 6]

PASS - main.

PROJECT EXECUTION SUCCESSFUL

[nashif]

by Andrew Boie:

How many times did you run the test? As noted above, was seen in only 3 of 254 runs.

[nashif]

by Mark Linkmeyer:

Hi Ramakrishna Pallala , next time please go ahead and close the issue and select the appropriate resolution value. There's no need to let me know. If the reporter disagrees or has input for you, they'll comment and/or reopen the bug. I'll go ahead and close it for you this time.

[nashif]

by Mark Linkmeyer:

Closing per Ramakrishna Pallala 's comment.

[nashif]

by Andrew Boie:

Reopening this as I'm not convinced this intermittent issue is truly gone.