Fix 1221 stateless memory leak #2385
geekalaapull-request-checks.yml
on: pull_request
checks
/
pre-commit
32s
checks
/
readme-snippets
9s
Matrix: checks / test
Annotations
16 warnings and 4 notices
|
checks / test (3.13, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dRySaAAAAABiubkfK+n9T7CceU3oIyuZQkwyQUEyMDMwMTA3MDI1AEVkZ2U=
|
|
checks / test (3.13, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0dhySaAAAAACr79XAi8DGRJNWoEbZnReHQkwyQUEyMDMwMTA1MDExAEVkZ2U=
|
|
checks / test (3.11, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0eRySaAAAAABqbo2ZhiBGQb6+0UaJikHxUEFPRURHRTA2MTYARWRnZQ==
|
|
checks / test (3.10, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0fRySaAAAAAAKisqBJgPEQYRvOefRvYn9QkwyQUEyMDMwMTA4MDUxAEVkZ2U=
|
|
checks / test (3.12, ubuntu-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0vxySaAAAAACz5QUHSlEfRIyBff+4nBN4Q0hHRURHRTE4MTMARWRnZQ==
|
|
checks / test (3.11, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.13, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zRySaAAAAAC+odpMphNIR4m3rENYmh15QkwyQUEyMDMwMTA3MDI1AEVkZ2U=
|
|
checks / test (3.13, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.12, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>01RySaAAAAACOHfE5iZFOQp3XaKzKqU0IQkwyQUEyMDMwMTA4MDIxAEVkZ2U=
|
|
checks / test (3.12, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.10, windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>02RySaAAAAADbfa2ggOGdRL50gOZcyIl/Q0hJMzBFREdFMDQxOQBFZGdl
|
|
checks / test (3.10, windows-latest)
Failed to restore: Cache service responded with 400
|
|
checks / test (3.11, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.13, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.12, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
checks / test (3.10, windows-latest)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|