[riot-notifications] [RIOT-OS/RIOT] murdock: enable esp32-wroom-32 for CI testing (#11449)

Gunar Schorcht notifications at github.com
Mon Apr 29 16:39:54 CEST 2019


gschorcht commented on this pull request.



> @@ -22,9 +22,9 @@
 )
 
 EXPECTED_PS = (
-    '\tpid | state    Q | pri',
-    '\t  1 | pending  Q |  15',
-    '\t  2 | running  Q |   7'
+    r'\s+pid | state    Q | pri',
+    r'\s+1 | pending  Q |\s+\d+',

> It is defined here, right?
> 
> ```
> [kaspar at ng riot (master)]$ git grep -A1 -n -- wifi-event-loop
> cpu/esp32/vendor/esp-idf/esp32/event_loop.c:120:    xTaskCreatePinnedToCore(esp_event_loop_task, "wifi-event-loop",
> cpu/esp32/vendor/esp-idf/esp32/event_loop.c-121-            ESP_TASKD_EVENT_STACK, NULL, ESP_TASKD_EVENT_PRIO, NULL, 0);
> [kaspar at ng riot (master)]$
> ```

Yes, nut it is vendor code, I tried to modify as less as possible to make future updates as easy as possible. Sure, we can override the definition here.

> I think you were referring to the "wifi" hardware handler thread. Cannot find it's definition within the RIOT codebase.

No, I was refering the vendor code above.
 
> Would wifi in 1, wifi-event-loop on 2 and the netif thread on 3 work?

It should work but I don't know what the side effects are if we simply increase `GNRC_NETIF_PRIO`.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11449#discussion_r279392878
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190429/1b1d9757/attachment.html>


More information about the notifications mailing list