| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Bumps [org.jetbrains.kotlin.jvm](https://github.com/JetBrains/kotlin) from 2.2.21 to 2.3.0. - [Release notes](https://github.com/JetBrains/kotlin/releases) - [Changelog](https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md) - [Commits](JetBrains/kotlin@v2.2.21...v2.3.0) --- updated-dependencies: - dependency-name: org.jetbrains.kotlin.jvm dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results 335 files ±0 335 suites ±0 5m 11s ⏱️ +3s Results for commit fc51ce6. ± Comparison against base commit 20e6880. This pull request removes 154 and adds 130 tests. Note that renamed tests count towards both. ?
, expected: combo-\"\\\b\f\n\r\t, #4]
__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 }
…
graphql.ScalarsBooleanTest ‑ parseValue throws exception for invalid input <java.lang.Object@77974494> graphql.ScalarsBooleanTest ‑ serialize throws exception for invalid input <java.lang.Object@1ffffb5a> graphql.ScalarsIDTest ‑ parseValue allows any object via String.valueOf <java.lang.Object@22ce0047> graphql.ScalarsIDTest ‑ serialize allows any object via String.valueOf <java.lang.Object@db18fb> graphql.ScalarsIntTest ‑ parseValue throws exception for invalid input <java.lang.Object@3bc2f110> graphql.ScalarsIntTest ‑ serialize throws exception for invalid input <java.lang.Object@4c6b7958> graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@5e9ca323 fieldCollector=graphql.execution.FieldCollector@16baf4f2 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@4f525aec dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@576a950f resolvedType=graphql.execution.ResolveType@6c54b17a>, #0] graphql.execution.instrumentation.TracingInstrumentationTest ‑ do not trace introspection information [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@70506f01 fieldCollector=graphql.execution.FieldCollector@73115ee9 executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@3a07ee90 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@514faf43 resolvedType=graphql.execution.ResolveType@2214ea0c>, #1] graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncExecutionStrategy@79761fcd fieldCollector=graphql.execution.FieldCollector@216de73d executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@1a573336 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@3dcfb61f resolvedType=graphql.execution.ResolveType@740e4e1c>, #0] graphql.execution.instrumentation.TracingInstrumentationTest ‑ tracing captures timings as expected [testExecutionStrategy: <graphql.execution.AsyncSerialExecutionStrategy@7a2dbc66 fieldCollector=graphql.execution.FieldCollector@77bedd5d executionStepInfoFactory=graphql.execution.ExecutionStepInfoFactory@4562ce56 dataFetcherExceptionHandler=graphql.execution.SimpleDataFetcherExceptionHandler@7c6bd2ed resolvedType=graphql.execution.ResolveType@6b328f8a>, #1] … ♻️ This comment has been updated with latest results. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Bumps org.jetbrains.kotlin.jvm from 2.2.21 to 2.3.0.
Release notesSourced from org.jetbrains.kotlin.jvm's releases.
... (truncated)
ChangelogSourced from org.jetbrains.kotlin.jvm's changelog.
... (truncated)
CommitsDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: