Skip to content
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

Benchmark example times out on KW24D, on ARM compiler #210

Closed
k-stachowiak opened this issue Oct 31, 2018 · 10 comments
Closed

Benchmark example times out on KW24D, on ARM compiler #210

k-stachowiak opened this issue Oct 31, 2018 · 10 comments

Comments

@k-stachowiak
Copy link
Contributor

The example times out while performing benchmark for DHE-2048. Surrounding log:

[1540134513.96][CONN][RXD]   RSA-4096                 :   20077 ms/private
[1540134527.98][HTST][INF] test suite run finished after 600.77 sec...
[1540134527.98][HTST][ERR] Expected output [\s+DHE-2048\s*:\s*\d+ ms/handshake] not received in log.
@k-stachowiak
Copy link
Contributor Author

Note that it is similar to #208

@RonEld
Copy link
Contributor

RonEld commented Jan 3, 2019

@k-stachowiak Does the example timeout when setting MBEDTLS_MPI_MAX_SIZE to 512 ?

@k-stachowiak
Copy link
Contributor Author

@sbutcher-arm @Patater Based on #231 I conclude, that the problem doesn't occur anymore. I suggest closing this issue.

@ciarmcom
Copy link
Member

@k-stachowiak thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

@ciarmcom
Copy link
Member

@k-stachowiak it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

4 similar comments
@ciarmcom
Copy link
Member

@k-stachowiak it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

@k-stachowiak it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 4, 2020

@k-stachowiak it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@ciarmcom
Copy link
Member

ciarmcom commented Nov 9, 2020

@k-stachowiak it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

@k-stachowiak
Copy link
Contributor Author

I still think we can close it. Let me free some @ciarmcom 's cycles and close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants