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

tests/python/pants_test/backend/native/subsystems:: timed out after 60 seconds #8235

Closed
cattibrie opened this issue Sep 3, 2019 · 1 comment

Comments

@cattibrie
Copy link
Contributor

cattibrie commented Sep 3, 2019

The test tests/python/pants_test/backend/native/subsystems:: timed out after 60 seconds for #8233 PR

Command '['/usr/local/Cellar/python/3.6.5_1/Frameworks/Python.framework/Versions/3.6/bin/python3.6', '/Users/travis/build/pantsbuild/pants/.pants.d/test/pytest-prep/CPython-3.6.5/64d3d094edd8f36f207f75ccda19e96f2aa1d339', '-c', '/dev/null', '-ocache_dir=/Users/travis/build/pantsbuild/pants/.pants.d/test/pytest/.pytest_cache', '--junitxml', '/Users/travis/build/pantsbuild/pants/.pants.d/test/pytest/tests.python.pants_test.backend.native.subsystems.subsystems/junitxml/TEST-tests.python.pants_test.backend.native.subsystems.subsystems.xml', '--confcutdir', '/Users/travis/build/pantsbuild/pants', '--continue-on-collection-errors', '--color', 'yes', '-q', '-rfa', '--rootdir', '/Users/travis/build/pantsbuild/pants', '-p', '__pants_backend_python_tasks_pytest_prep_pytest_plugin__', '--pants-sources-map-path', '/Users/travis/build/pantsbuild/pants/.pants.d/test/pytest/tmp6chd_gup/sources_map.json', '/Users/travis/build/pantsbuild/pants/.pants.d/pyprep/sources/825f77b63603c275a1ac533d8d69a225f7a7e845/pants_test/backend/native/subsystems/test_libc_resolution.py', '/Users/travis/build/pantsbuild/pants/.pants.d/pyprep/sources/825f77b63603c275a1ac533d8d69a225f7a7e845/pants_test/backend/native/subsystems/test_native_toolchain.py']' timed out after 60 seconds

Locally this test took 29 seconds with my changes.

@stuhood
Copy link
Member

stuhood commented Sep 4, 2019

@cattibrie : With those timeouts being relatively close to one another, it's possible that it would have run only slightly longer than its timeout before succeeding. We should only track something as flaky if we can't increase its timeout.

If you have time to increase the timeout for that one, that would be appreciated!

@stuhood stuhood closed this as completed Sep 4, 2019
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

2 participants