nix(loadtest): prevent timing errors for worst-case JWT test
Instead of taking wild guesses at the runtime of the target generation itself, we're just making sure to reset the system time to a fixed value when we ultimately start PostgREST. This allows us to create the right JWT expiry values ahead of time.
This commit is contained in:
@@ -128,8 +128,6 @@ jobs:
|
||||
fail-fast: false
|
||||
matrix:
|
||||
kind: ['mixed', 'errors', 'jwt-hs', 'jwt-hs-cache', 'jwt-hs-cache-worst', 'jwt-rsa', 'jwt-rsa-cache', 'jwt-rsa-cache-worst']
|
||||
# This test currently fails repeatedly - let's ignore that failure for the moment.
|
||||
continue-on-error: ${{ matrix.kind == 'jwt-rsa-cache-worst' }}
|
||||
name: Loadtest
|
||||
runs-on: ubuntu-24.04
|
||||
steps:
|
||||
|
||||
Reference in New Issue
Block a user