Skip to content
Co-KiriKiri Backend Pull Request Workflow

[feat/CK-222] Redis를 도입하고 Refresh Token을 Redis에 저장하도록 변경한다 #50

Sign in to view logs

[feat/CK-222] Redis를 도입하고 Refresh Token을 Redis에 저장하도록 변경한다

[feat/CK-222] Redis를 도입하고 Refresh Token을 Redis에 저장하도록 변경한다 #50

Triggered via pull request November 7, 2023 01:55
@miseongkmiseongk
synchronize #190
feature/CK-222
Status Failure
Total duration 2m 27s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

backend-pull-request-workflow.yml

on: pull_request
build
2m 18s
build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
RefreshTokenRepositoryTest.리프레시_토큰을_찾을때_없는경우_빈값을_보낸다(): backend/kirikiri/src/test/java/co/kirikiri/persistence/auth/RefreshTokenRepositoryTest.java#L83
java.lang.AssertionError: Expecting an empty Optional but was containing value: "identifier1"
build
Process completed with exit code 1.
리프레시_토큰을_찾을때_없는경우_빈값을_보낸다() (co.kirikiri.persistence.auth.RefreshTokenRepositoryTest) failed: co.kirikiri.persistence.auth.RefreshTokenRepositoryTest#L0
backend/kirikiri/build/test-results/test/TEST-co.kirikiri.persistence.auth.RefreshTokenRepositoryTest.xml
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/