Hello,
I'm currently using version 2024.09, and when running the test monitor, I encounter the following error at the top of my job: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')). I don't notice anything unusual in the test logs. Could this be a bug with the test monitor?
Best Regards, Andy
On Mon, Oct 14, 2024 at 3:31 PM andy.sabathier@nxp.com wrote:
Hello,
I'm currently using version 2024.09, and when running the test monitor, I encounter the following error at the top of my job: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')). I don't notice anything unusual in the test logs. Could this be a bug with the test monitor?
Andy,
I'm also curious about these notifications. They started with 2024.05. I'm not using monitors and still see them. They seem harmless, but it would be nice to understand what they mean. My example: https://lava.infra.foundries.io/scheduler/job/54229
Best Regards, Milosz
On Mon, 14 Oct 2024 at 22:47, Milosz Wasilewski milosz.wasilewski@foundries.io wrote:
On Mon, Oct 14, 2024 at 3:31 PM andy.sabathier@nxp.com wrote:
Hello,
I'm currently using version 2024.09, and when running the test monitor, I encounter the following error at the top of my job: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')). I don't notice anything unusual in the test logs. Could this be a bug with the test monitor?
Andy,
I'm also curious about these notifications. They started with 2024.05. I'm not using monitors and still see them. They seem harmless, but it would be nice to understand what they mean. My example: https://lava.infra.foundries.io/scheduler/job/54229
In my instance, I started seeing similar messages with 2024.03. I think it is reported by this change https://gitlab.com/lava/lava/-/commit/c041879e7847f87f54bf216f04b1cae1b1f545....
Cheers, Chase
Best Regards, Milosz _______________________________________________ lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
Hello,
I fixed the bug on my end by implementing a retry mechanism when the request triggers an exception. What do you think of this solution? Should I submit a merge request to include the retry?
Best regards, Andy
Hi,
I've just submitted a merge request and would love to hear your feedback( https://gitlab.com/lava/lava/-/merge_requests/2657 ). If anyone has comments, suggestions, or improvements to propose, please feel free to share your thoughts. Your input is highly appreciated, and I look forward to any ideas that could help enhance the solution.
Thank you in advance! Andy
lava-users@lists.lavasoftware.org
-
andy.sabathier＠nxp.com -
Chase Qi -
Milosz Wasilewski