|
2024-03-28
| ||
| 16:39 | • Ticket [ca7a0d33ce] Megatest dboard process taking 100% for 400+ hours status still Open with 5 other changes artifact: 3c25d42d86 user: mmgraham | |
|
2024-03-26
| ||
| 11:03 | • New ticket [ca7a0d33ce]. artifact: 57223f4726 user: mmgraham | |
| Ticket Hash: | ca7a0d33ce251202cef5261568a11ede4aa9a34c | |||
| Title: | Megatest dboard process taking 100% for 400+ hours | |||
| Status: | Open | Type: | Code_Defect | |
| Severity: | Important | Priority: | Immediate | |
| Subsystem: | Resolution: | Open | ||
| Last Modified: | 2024-03-28 16:39:31 | |||
| Version Found In: | 1.65/92 | |||
| Description: | ||||
|
Megatest dboard process taking 100% for 400+ hours
It happens to multiple users and hosts | ||||
| User Comments: | ||||
|
mmgraham added on 2024-03-28 22:39:31:
Another user experienced: If you leave running Megatest dashboard for many hours, the errors below will start appearing in the xterm the app was kicked off from. After that, the xterm is not usable due to the amount of messages sent forcing to kill the app. "Error: in callback: (vector-ref) bad argument type: #f" | ||||