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

Semi-frequent timeouts in test-unicode_all with 3.6.1 (aarch64) #1816

Closed
grahamc opened this issue Oct 28, 2019 · 8 comments
Closed

Semi-frequent timeouts in test-unicode_all with 3.6.1 (aarch64) #1816

grahamc opened this issue Oct 28, 2019 · 8 comments
Labels
kind: bug state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated

Comments

@grahamc
Copy link

grahamc commented Oct 28, 2019

On a semi-regular basis, the test-unicode_all test times out in the NixOS build farm.

This is running NixOS on the host, with GCC 8.3.0.

Full build log available: https://hydra.nixos.org/build/103809502/nixlog/1

Log snippet:

88/88 Test #80: test-unicode_all ....................***Timeout 1500.01 sec
100000 of 8860608 UTF-8 strings checked
[...]
8200000 of 8860608 UTF-8 strings checked


99% tests passed, 1 tests failed out of 88

Label Time Summary:
all        = 1627.51 sec*proc (41 tests)
default    =  25.67 sec*proc (41 tests)

Total Test time (real) = 1548.32 sec

The following tests FAILED:
         80 - test-unicode_all (Timeout)
@t-b
Copy link
Contributor

t-b commented Oct 28, 2019

In travis we use a custom timeout, see

- ctest -C Release --timeout 2700 -V -j
. Not sure if we can add that kind of setting into the test code itself which would be less error prone.

@stale
Copy link

stale bot commented Nov 27, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Nov 27, 2019
@grahamc
Copy link
Author

grahamc commented Nov 27, 2019

This is not stale.

@stale stale bot removed the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Nov 27, 2019
@nickaein
Copy link
Contributor

The test-unicode_all is known to take a long time to run. Based on the logs, it was nearly finished when the timeout occurred (around 92%). Can the time limit be slightly increased to avoid such errors?

The long-term solution is probably breaking down such tests into smaller chunks.

@stale
Copy link

stale bot commented Dec 28, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Dec 28, 2019
@grahamc
Copy link
Author

grahamc commented Dec 28, 2019

This is not stale.

@stale stale bot removed the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Dec 28, 2019
@stale
Copy link

stale bot commented Jan 27, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated label Jan 27, 2020
@stale stale bot closed this as completed Feb 3, 2020
@dota17
Copy link
Contributor

dota17 commented Apr 7, 2020

The problem is still not fixed, i think.
Currently, the test-unicode_all is always not finished because times out.
This often happens in Xcode 9.2 C++ and before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug state: stale the issue has not been updated in a while and will be closed automatically soon unless it is updated
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants