Ran into a bunch of time outs in a integration tes...
# general
f
Ran into a bunch of time outs in a integration test shard run
Copy code
contrib/go/tests/python/pants_test/contrib/go/tasks:integration
src/python/pants/option:integration
tests/python/pants_test/backend/codegen/protobuf/java:integration
tests/python/pants_test/backend/codegen/wire/java:integration
tests/python/pants_test/backend/jvm/tasks/jvm_compile:declared_deps_integration
tests/python/pants_test/backend/jvm/tasks/jvm_compile:dep_exports_integration
tests/python/pants_test/backend/jvm/tasks:export_classpath_integration
tests/python/pants_test/backend/jvm/tasks:jvm_dependency_usage_integratio
tests/python/pants_test/backend/jvm/tasks:scalafix
tests/python/pants_test/backend/python/tasks:pytest_run_integration
tests/python/pants_test/backend/python/tasks:python_repl_integration
tests/python/pants_test/java:nailgun_integration
tests/python/pants_test/projects:protobuf_projects_integration
tests/python/pants_test/projects:python_testprojects_src_integration
tests/python/pants_test/projects:thrift_projects_integration
tests/python/pants_test/projects:wire_projects_integration
h
This happens occassionaly when the remote server doesn’t have enough resources. It’s why I’m bumping up the
queue_buffer_time
by 20 more seconds in that PR
f
thx for the explanation