React bug fixes #7
xenobiasoftstaging.yml
on: pull_request
build-and-test-frontend
31s
deploy-swa-staging
0s
Annotations
6 errors and 1 warning
|
build-and-test-frontend
Process completed with exit code 1.
|
|
src/hooks/usePlayerService.test.ts > usePlayerService > clearPlayer > should clear player data and localStorage:
src/frontend/Sudoku.React/src/hooks/usePlayerService.test.ts#L216
AssertionError: expected 'player-to-clear-555' to be null
- Expected:
null
+ Received:
"player-to-clear-555"
❯ src/hooks/usePlayerService.test.ts:216:42
|
|
src/hooks/usePlayerService.test.ts > usePlayerService > manual initialization > should allow manual re-initialization:
src/frontend/Sudoku.React/src/hooks/usePlayerService.test.ts#L168
AssertionError: expected "vi.fn()" to be called with arguments: [ 'cached-player-333' ]
Number of calls: 0
❯ src/hooks/usePlayerService.test.ts:168:38
|
|
src/hooks/usePlayerService.test.ts > usePlayerService > initialization > should create new player when playerExists API call fails:
src/frontend/Sudoku.React/src/hooks/usePlayerService.test.ts#L109
AssertionError: expected "vi.fn()" to be called with arguments: [ 'existing-player-456' ]
Number of calls: 0
❯ src/hooks/usePlayerService.test.ts:109:38
|
|
src/hooks/usePlayerService.test.ts > usePlayerService > initialization > should create new player when stored alias no longer exists on server:
src/frontend/Sudoku.React/src/hooks/usePlayerService.test.ts#L92
AssertionError: expected "vi.fn()" to be called with arguments: [ 'invalid-player-789' ]
Number of calls: 0
❯ src/hooks/usePlayerService.test.ts:92:38
|
|
src/hooks/usePlayerService.test.ts > usePlayerService > initialization > should use existing valid player alias from localStorage:
src/frontend/Sudoku.React/src/hooks/usePlayerService.test.ts#L74
AssertionError: expected "vi.fn()" to be called with arguments: [ 'existing-player-456' ]
Number of calls: 0
❯ src/hooks/usePlayerService.test.ts:74:38
|
|
build-and-test-frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|