Skip to content

reduce forks to 2 to make perf tests faster #3948

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

Merged
merged 1 commit into from
May 1, 2025

Conversation

andimarek
Copy link
Member

No description provided.

Copy link
Contributor

github-actions bot commented May 1, 2025

Test Results

  312 files  ±0    312 suites  ±0   55s ⏱️ -1s
3 581 tests ±0  3 576 ✅ ±0  5 💤 ±0  0 ❌ ±0 
3 670 runs  ±0  3 665 ✅ ±0  5 💤 ±0  0 ❌ ±0 

Results for commit 2863a12. ± Comparison against base commit 876c9ae.

This pull request removes 150 and adds 128 tests. Note that renamed tests count towards both.
	?
                __schema { types { fields { args { type { name fields { name }}}}}}
                __schema { types { fields { type { name fields { name }}}}}
                __schema { types { inputFields { type { inputFields { name }}}}}
                __schema { types { interfaces { fields { type { interfaces { name } } } } } }
                __schema { types { name} }
                __type(name : "t") { name }
                a1: __schema { types { name} }
                a1: __type(name : "t") { name }
                a2 :  __type(name : "t1") { name }
…
graphql.ScalarsBooleanTest ‑ parseValue throws exception for invalid input <java.lang.Object@642b9d4e>
graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@66b390e7>
graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@6b7080ab>
graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@655cde75>
graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@153f9f2e>
graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@7dd16ed9>
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@50363f77 fieldCollector=graphql.execution.FieldCollector@54eee3c executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@2389801d dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@76589dd1 resolvedType=graphql.execution.ResolveType@17f4c9ea>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@a5f17e4 fieldCollector=graphql.execution.FieldCollector@38dba56b executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@9519003 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@2393b3d5 resolvedType=graphql.execution.ResolveType@51017074>, #1]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@5a2916f1 fieldCollector=graphql.execution.FieldCollector@2e25c9e0 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@70cea7d9 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@5f23c321 resolvedType=graphql.execution.ResolveType@4dafc8aa>, #0]
graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@7ad3c86 fieldCollector=graphql.execution.FieldCollector@4e92267 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@a09b2 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@49e21e0e resolvedType=graphql.execution.ResolveType@274542b8>, #1]
…

@andimarek andimarek merged commit 24b955a into master May 1, 2025
2 checks passed
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

Successfully merging this pull request may close these issues.

3 participants