-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Greentea: Remove TLSSocket_simultaneous test #9730
Greentea: Remove TLSSocket_simultaneous test #9730
Conversation
TESTS/netsocket/tls/main.cpp
Outdated
@@ -196,7 +196,10 @@ Case cases[] = { | |||
Case("TLSSOCKET_SEND_TIMEOUT", TLSSOCKET_SEND_TIMEOUT), | |||
Case("TLSSOCKET_NO_CERT", TLSSOCKET_NO_CERT), | |||
#ifndef __IAR_SYSTEMS_ICC__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should remove the #ifndef __IAR
as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I removed it, but added a further warning comment, so someone doesn't spend hours debugging this test in case it gets uncommented in distant future.
The reason is that some platforms lack memory to run it. To be brought back once TLS library memory consumption is optimized.
0f6f6f0
to
a089661
Compare
@michalpasztamobica, thank you for your changes. |
While we can get at least one more review, CI started |
As this is being skipped, is there tracking issue for reenabling this test case? Is not #8306 ? |
@VeijoPesonen , @KariHaapalehto , @mtomczykmobica , @tymoteuszblochmobica , can we get at least one more code review here, please? @0xc0170 , to track the IAR heap allocation fix there is an issue, that I am subscribed to. @SeppoTakalo , you mentioned that TLS library memory allocation is being looked at - is there a ticket to track this? |
Test run: FAILEDSummary: 1 of 10 test jobs failed Failed test jobs:
|
I see exporters were restarted, failure was in CI script |
Yes, I restarted them after I saw the failure message. If we can get this in before the nightly build start, the results will get cleaner tomorrow. |
CI job restarted: |
@KariHaapalehto @mtomczykmobica @tymoteuszblochmobica |
Description
The reason is that some platforms lack memory to run it. To be brought back once TLS library memory consumption is optimized.
Pull request type
Reviewers
@SeppoTakalo
@VeijoPesonen
@mtomczykmobica
@KariHaapalehto
@tymoteuszblochmobica
Release Notes