Skip to content

Autoconfigured TopicResolver bean with ability to replace it by user configuration #424

Autoconfigured TopicResolver bean with ability to replace it by user configuration

Autoconfigured TopicResolver bean with ability to replace it by user configuration #424

Triggered via pull request September 6, 2023 19:00
Status Success
Total duration 4m 43s
Artifacts

pullrequest.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

12 errors
Test and Build on JDK 11
Unable to remove token 'processor_name[2]'. It is not owned by node-2
Test and Build on JDK 11
Unable to process update 'processor_name[2]', concurrent write invalidated this one
Test and Build on JDK 11
Unable to process update 'processor_name[2]', concurrent write invalidated this one
Test and Build on JDK 11
Unable to process update 'processor_name[5]', concurrent write invalidated this one
Test and Build on JDK 8
Unable to claim token 'processor_name[2]', It has not been initialized yet
Test and Build on JDK 8
Unable to process update 'processor_name[2]', concurrent write invalidated this one
Test and Build on JDK 8
Unable to claim token 'processor_name[2]'. It is owned by 'node-1'
Test and Build on JDK 8
Unable to process update 'processor_name[5]', concurrent write invalidated this one
Test and Build on JDK 17
Unable to remove token 'processor_name[2]'. It is not owned by node-2
Test and Build on JDK 17
Unable to process update 'processor_name[2]', concurrent write invalidated this one
Test and Build on JDK 17
Unable to process update 'processor_name[2]', concurrent write invalidated this one
Test and Build on JDK 17
Unable to process update 'processor_name[5]', concurrent write invalidated this one