Fix flaky tests #7180

mtrezza · 2021-02-11T14:10:29Z

New Issue Checklist

I am not disclosing a vulnerability.
I am not just asking a question.
I have searched through existing issues.
I can reproduce the issue with the latest version of Parse Server.

Issue Description

Flaky tests impede the CI process. With the increasing number of test scenarios to ensure Parse Server compatibility with recent versions of MongoDB, Postgres and Node.js, the likeliness of flaky tests disrupting the CI process also increases. In addition, GitHub Actions currently does not support to re-run individual jobs which makes the manual re-run a tedious effort.

Expected outcome

Identify root cause of flakiness and fix for tests to be stable.

The following lists flaky tests to analyze and possibly find a pattern to determine the root cause. The list should also be a helper for maintainers to identify flaky tests when reviewing PRs. Feel free to update the list if you encounter a flaky test that is not in the list yet.

Last list update: 2021-02-24

Flaky tests

Tests which still have to be analyzed to fix the flakiness.

Schema Performance test schema update class

Error: Could not add field fooOne

Installations update ios fails with new deviceToken and no installationId

  Message:
    Failed
  Stack:
    Error: Failed
        at <Jasmine>
        at UserContext.<anonymous> (/home/runner/work/parse-server/parse-server/spec/AuthenticationAdapters.spec.js:1671:7)
        at <Jasmine>
        at processTicksAndRejections (internal/process/task_queues.js:97:5)

Parse.User testing only creates a single session for an installation / user pair (#2885)

 Message:
  Expected 2 to be 1.
Stack:
  Error: Expected 2 to be 1.
      at <Jasmine>
      at query.find.then.results (/home/runner/work/parse-server/parse-server/spec/ParseUser.spec.js:1294:32)
      at process._tickCallback (internal/process/next_tick.js:68:7)
Message:
  Expected 'r:a49facd19f31028da42c3058ce5c35a3' to be 'r:0bcc75ade014c3ecbc500a5a29606929'.
Stack:
  Error: Expected 'r:a49facd19f31028da42c3058ce5c35a3' to be 'r:0bcc75ade014c3ecbc500a5a29606929'.
      at <Jasmine>
      at query.find.then.results (/home/runner/work/parse-server/parse-server/spec/ParseUser.spec.js:1295:48)
      at process._tickCallback (internal/process/next_tick.js:68:7)

Observed in environment(s): Postgres 12, Postgis 3.0

ParseLiveQuery expect afterEvent delete

 Message:
  Failed
Stack:
  Error: Failed
      at <Jasmine>
      at UserContext.it (/home/runner/work/parse-server/parse-server/spec/AuthenticationAdapters.spec.js:1671:7)
      at process._tickCallback (internal/process/next_tick.js:68:7)

Observed in environment(s): Node 10

Apple Game Center Auth adapter validateAuthData should validate

Message:
  Error: Timeout - Async function did not complete within 20000ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
Stack:
  Error: Timeout - Async function did not complete within 20000ms (set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
      at <Jasmine>
      at ontimeout (timers.js:436:11)
      at tryOnTimeout (timers.js:300:5)
      at listOnTimeout (timers.js:263:5)
      at Timer.processTimers (timers.js:223:10)

Observed in environment(s): Node 10

Cloud Code test beforeSave with invalid field

  Message:
    Failed: deadlock detected
  Stack:
    error properties: Object({ length: 317, severity: 'ERROR', code: '40P01', detail: 'Process 151 waits for AccessExclusiveLock on relation 50837 of database 19568; blocked by process 156.
    Process 156 waits for AccessShareLock on relation 50712 of database 19568; blocked by process 151.', hint: 'See server log for query details.', position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, dataType: undefined, constraint: undefined, file: 'deadlock.c', routine: 'DeadLockReport' })
        at <Jasmine>
        at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
        at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
        at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
        at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
        at Socket.emit (events.js:198:13)
        at Socket.EventEmitter.emit (domain.js:448:20)
        at addChunk (_stream_readable.js:288:12)
        at readableAddChunk (_stream_readable.js:269:11)
        at Socket.Readable.push (_stream_readable.js:224:10)
        at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

rest create test specified session length

Message:
  Expected 28 to equal 27.
Stack:
  Error: Expected 28 to equal 27.
  at rest.create.then.then.r (/home/runner/work/parse-server/parse-server/spec/rest.spec.js:602:37)
  at process._tickCallback (internal/process/next_tick.js:68:7)

Observed in environment(s): ?

ParseGraphQLServer Auto API Schema Objects Queries Get read preferences should support includeReadPreference argument

Error: GraphQL error: Object not found.

ParseGraphQLServer Auto API Schema Objects Queries Find read preferences should support readPreference argument

Message:
  Expected false to be true.
Stack:
  Error: Expected false to be true.
  at UserContext. (/home/runner/work/parse-server/parse-server/spec/ParseGraphQLServer.spec.js:5512:52)
  at processTicksAndRejections (internal/process/task_queues.js:93:5)

Observed in environment(s): ?

ParseGraphQLServer Auto API Schema Files Mutations Create should return File object

Message:
  TypeError: Cannot read property 'clientMutationId' of null
Stack:
  at UserContext. (/home/runner/work/parse-server/parse-server/spec/ParseGraphQLServer.spec.js:6603:43)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)

Possibly fixed

Tests for which a PR has been merged to fix the flakiness. These are currently under observation to confirm the fix. If you observe such a test to fail, please post a comment for further evaluation.

by #7187:

ParseServerRESTController transactions should handle a batch request with transaction = true

Unhandled promise rejection: [object Object],[object Object]

Observed in environment(s):
- Mongo 4.2, ReplicaSet, WiredTiger, Node 10
- Mongo 4.0, ReplicaSet, WiredTiger, Node 14

by #7196:

Cloud Code cloud jobs should define a job

Unhandled promise rejection: ParseError: 101 Object not found.

Observed in environment(s):
- Mongo 4.4, ReplicaSet, WiredTiger, Node 14

Cloud Code cloud jobs should define a job

Message:
  Unhandled promise rejection: error: relation "_JobStatus" does not exist (line 1180)
Stack:
  error properties: Object({ length: 108, severity: 'ERROR', code: '42P01', detail: undefined, hint: undefined, position: '8', internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, dataType: undefined, constraint: undefined, file: 'parse_relation.c', routine: 'parserOpenTable' })
  at <Jasmine>
  at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
  at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
  at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
  at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
  at Socket.emit (events.js:198:13)
  at Socket.EventEmitter.emit (domain.js:448:20)
  at addChunk (_stream_readable.js:288:12)
  at readableAddChunk (_stream_readable.js:269:11)
  at Socket.Readable.push (_stream_readable.js:224:10)
  at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

Observed in environment(s):
- Postgres 11, Postgis 3.1, Node 14.15.5

Cloud Code cloud jobs should run with master key basic auth

Message:
  Unhandled promise rejection: ParseError: 101 Object not found.
Stack:
  error properties: Object({ code: 101 })
  Error: Object not found.
      at /home/runner/work/parse-server/parse-server/lib/Controllers/DatabaseController.js:49:3084
      at <Jasmine>
      at processTicksAndRejections (internal/process/task_queues.js:93:5)

Observed in environment(s):
- Redis Cache, Node 14.15.5

by #7212:

RedisCacheAdapter should find un-expired records

Message:
  Expected null to equal 'world'.
Stack:
  Error: Expected null to equal 'world'.
  at /home/runner/work/parse-server/parse-server/spec/RedisCacheAdapter.spec.js:97:36
  at processTicksAndRejections (internal/process/task_queues.js:93:5)
Message:
  Expected null not to equal null.
Stack:
  Error: Expected null not to equal null.
  at /home/runner/work/parse-server/parse-server/spec/RedisCacheAdapter.spec.js💯40
  at processTicksAndRejections (internal/process/task_queues.js:93:5)

bv #7213:

PushController properly creates _PushStatus

Message:
  Expected 'pending' to be 'running'.
Stack:
  Error: Expected 'pending' to be 'running'.
  at reconfigureServer.then.then.then.then.then.catch.then (/home/runner/work/parse-server/parse-server/spec/PushController.spec.js:618:48)
at process._tickCallback (internal/process/next_tick.js:68:7)

by #7228:

PostgresStorageAdapter should use index for caseInsensitive query using default indexname

  Message:
    error: duplicate key value violates unique constraint "_User_pkey" (line 434)
  Stack:
    error properties: Object({ length: 219, severity: 'ERROR', code: '23505', detail: 'Key ("objectId")=(d3c9d0cbebeeb2efcc62a95f09255ff2) already exists.', hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: 'public', table: '_User', dataType: undefined, constraint: '_User_pkey', file: 'nbtinsert.c', routine: '_bt_check_unique' })
        at <Jasmine>
        at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
        at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
        at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
        at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
        at Socket.emit (events.js:198:13)
        at Socket.EventEmitter.emit (domain.js:448:20)
        at addChunk (_stream_readable.js:288:12)
        at readableAddChunk (_stream_readable.js:269:11)
        at Socket.Readable.push (_stream_readable.js:224:10)
        at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

by #7265:

Parse.GeoPoint testing creating geo point exception two fields

Message:
  Failed: deadlock detected
Stack:
  error properties: Object({ length: 319, severity: 'ERROR', code: '40P01', detail: 'Process 150 waits for AccessExclusiveLock on relation 139374 of database 19581; blocked by process 154.
  Process 154 waits for AccessShareLock on relation 139249 of database 19581; blocked by process 150.', hint: 'See server log for query details.', position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, dataType: undefined, constraint: undefined, file: 'deadlock.c', routine: 'DeadLockReport' })
      at <Jasmine>
      at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
      at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
      at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
      at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
      at Socket.emit (events.js:198:13)
      at Socket.EventEmitter.emit (domain.js:448:20)
      at addChunk (_stream_readable.js:288:12)
      at readableAddChunk (_stream_readable.js:269:11)
      at Socket.Readable.push (_stream_readable.js:224:10)
      at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

Observed in environment(s): Postgres

by #7267:

Cloud Code cloud jobs should set the message / success on the job

Message:
  Expected 'running' to equal 'succeeded'.
Stack:
  Error: Expected 'running' to equal 'succeeded'.
      at <Jasmine>
      at promise.then.then.jobStatus (/home/runner/work/parse-server/parse-server/spec/CloudCode.spec.js:1666:45)
      at process._tickCallback (internal/process/next_tick.js:68:7)

PushController should not enqueue push when device token is not set

  Message:
    Expected 'running' to be 'succeeded'.
  Stack:
    Error: Expected 'running' to be 'succeeded'.
        at <Jasmine>
        at query.find.then.results (/home/runner/work/parse-server/parse-server/spec/PushController.spec.js:1128:44)
        at process._tickCallback (internal/process/next_tick.js:68:7)

Parse.Push does not get stuck with _PushStatus 'running' on 1 installation added

Message:
  Expected 'running' to equal 'succeeded'.
Stack:
  Error: Expected 'running' to equal 'succeeded'.
      at <Jasmine>
      at reconfigureServer.then.then.then.then.then.results (/home/runner/work/parse-server/parse-server/spec/Parse.Push.spec.js:388:38)
      at process._tickCallback (internal/process/next_tick.js:68:7)
Message:
  Expected 1 to equal undefined.
Stack:
  Error: Expected 1 to equal undefined.
      at <Jasmine>
      at reconfigureServer.then.then.then.then.then.results (/home/runner/work/parse-server/parse-server/spec/Parse.Push.spec.js:390:37)
      at process._tickCallback (internal/process/next_tick.js:68:7)

Fixed tests

Tests that have not been observed anymore for a while and are therefore considered fixed.

The text was updated successfully, but these errors were encountered:

mtrezza · 2021-02-11T14:25:18Z

@dplewis Do you have any idea how we can investigate this? Maybe add NewRelic to it to get the call stack when a test fails?

davimacedo · 2021-02-16T06:05:40Z

@dplewis Do you have any idea how we can investigate this? Maybe add NewRelic to it to get the call stack when a test fails?

The way I do is basically creating a loop around the test and making it to execute let's say 100 times. By this way you can see it failing and you can debug. I am tackling the second one now.

davimacedo · 2021-02-16T08:50:37Z

#7196 probably solves items 2 and 3

davimacedo · 2021-02-18T20:00:46Z

Few more flaky tests that I've observed:

rest create test specified session length
49
Message:
50
Expected 28 to equal 27.
51
Stack:
52
Error: Expected 28 to equal 27.
53
at
54
at rest.create.then.then.r (/home/runner/work/parse-server/parse-server/spec/rest.spec.js:602:37)
55
at process._tickCallback (internal/process/next_tick.js:68:7)
Parse.GeoPoint testing creating geo point exception two fields
49
Message:
50
Failed: deadlock detected
51
Stack:
52
error properties: Object({ length: 319, severity: 'ERROR', code: '40P01', detail: 'Process 158 waits for AccessExclusiveLock on relation 139308 of database 19596; blocked by process 152.
53
Process 152 waits for AccessShareLock on relation 139183 of database 19596; blocked by process 158.', hint: 'See server log for query details.', position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, dataType: undefined, constraint: undefined, file: 'deadlock.c', routine: 'DeadLockReport' })
54
at
55
at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
56
at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
57
at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
58
at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
59
at Socket.emit (events.js:198:13)
60
at Socket.EventEmitter.emit (domain.js:448:20)
61
at addChunk (_stream_readable.js:288:12)
62
at readableAddChunk (_stream_readable.js:269:11)
63
at Socket.Readable.push (_stream_readable.js:224:10)
64
at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
ParseGraphQLServer Auto API Schema Objects Queries Find read preferences should support readPreference argument
22
Message:
23
Expected false to be true.
24
Stack:
25
Error: Expected false to be true.
26
at
27
at UserContext. (/home/runner/work/parse-server/parse-server/spec/ParseGraphQLServer.spec.js:5512:52)
28
at
29
at processTicksAndRejections (internal/process/task_queues.js:93:5)

mtrezza · 2021-02-18T20:33:12Z

I added them to the list above. I'll mark tests as solved by #7196 if they don't occur anymore after some time.

davimacedo · 2021-02-18T23:15:58Z

"ParseServerRESTController transactions should handle a batch request with transaction = true" was actually also solved by #7187 so let's observe this one as well.

mtrezza · 2021-02-18T23:58:11Z

Thanks, updated.

davimacedo · 2021-02-19T03:41:39Z

One more:

PushController properly creates _PushStatus
Message:
Expected 'pending' to be 'running'.
Stack:
Error: Expected 'pending' to be 'running'.
at
at reconfigureServer.then.then.then.then.then.catch.then (/home/runner/work/parse-server/parse-server/spec/PushController.spec.js:618:48)
at process._tickCallback (internal/process/next_tick.js:68:7)

mtrezza · 2021-02-19T08:39:33Z

Added!

davimacedo · 2021-02-19T17:30:33Z

For "Parse.GeoPoint testing creating geo point exception two fields" I've run all geo point related tests 300 times for Postgres and Mongo in a row with no error. I remember in that time there was other strange messages happening for the Postgres database, so I guess the Postgres was in an inconsistent state maybe because of anther test but it does not look to have a problem with this test itself. I suggest we observe it more and investigate it again in the case it happens to fail.

davimacedo · 2021-02-19T18:03:39Z

This one is for Redis cache:

RedisCacheAdapter should find un-expired records
Message:
Expected null to equal 'world'.
Stack:
Error: Expected null to equal 'world'.
at
at /home/runner/work/parse-server/parse-server/spec/RedisCacheAdapter.spec.js:97:36
at
at processTicksAndRejections (internal/process/task_queues.js:93:5)
Message:
Expected null not to equal null.
Stack:
Error: Expected null not to equal null.
at
at /home/runner/work/parse-server/parse-server/spec/RedisCacheAdapter.spec.js:100:40
at
at processTicksAndRejections (internal/process/task_queues.js:93:5)

dplewis · 2021-02-19T19:24:37Z

I think I may have a fix for this one in another branch. Or it fixes the
PushController properly creates _PushStatus test

1) Cloud Code cloud jobs should set the message / success on the job
  Message:
    Expected 'running' to equal 'succeeded'.
  Stack:
    Error: Expected 'running' to equal 'succeeded'.
        at <Jasmine>
        at promise.then.then.jobStatus (/home/runner/work/parse-server/parse-server/spec/CloudCode.spec.js:1666:45)
        at process._tickCallback (internal/process/next_tick.js:68:7)
Pending:

davimacedo · 2021-02-20T01:44:34Z

"rest create test specified session length" is now possibly fixed by #7208

davimacedo · 2021-02-20T01:46:41Z

I think I may have a fix for this one in another branch. Or it fixes the
PushController properly creates _PushStatus test

1) Cloud Code cloud jobs should set the message / success on the job
  Message:
    Expected 'running' to equal 'succeeded'.
  Stack:
    Error: Expected 'running' to equal 'succeeded'.
        at <Jasmine>
        at promise.then.then.jobStatus (/home/runner/work/parse-server/parse-server/spec/CloudCode.spec.js:1666:45)
        at process._tickCallback (internal/process/next_tick.js:68:7)
Pending:

Cool! Could you please open a PR?

davimacedo · 2021-02-20T02:19:51Z

I've also couldn't reproduce "ParseGraphQLServer Auto API Schema Objects Queries Find read preferences should support readPreference argument" yet. I suggest now we observe more as most of the flaky tests were tackled. I will continue working in other stuff and come back to here when seeing something else failing.

mtrezza · 2021-02-20T17:53:50Z

Added the 2 above mentioned tests and one of them as possibly fixed by #7212.

dplewis · 2021-02-20T20:25:00Z

PushController properly creates _PushStatus possibly fixed by #7213
I added a description of the issue that you might find interesting

mtrezza · 2021-02-20T21:01:31Z

Updated list.

mtrezza · 2021-02-24T07:59:21Z

Added new flaky test: PostgresStorageAdapter should use index for caseInsensitive query using default indexname

davimacedo · 2021-02-24T21:37:22Z

One more: 1) ParseGraphQLServer Auto API Schema Files Mutations Create should return File object
22
Message:
23
TypeError: Cannot read property 'clientMutationId' of null
24
Stack:
25
at
26
at UserContext. (/home/runner/work/parse-server/parse-server/spec/ParseGraphQLServer.spec.js:6603:43)
27
at
28
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Reference: https://github.com/parse-community/parse-server/runs/1972047490?check_suite_focus=true

mtrezza · 2021-02-25T00:36:29Z

Added!

cbaker6 · 2021-03-05T19:58:39Z

https://github.com/parse-community/parse-server/runs/2041751762#step:8:30

2) Installations update ios fails with new deviceToken and no installationId

  Message:

    Failed

  Stack:

    Error: Failed

        at <Jasmine>

        at UserContext.<anonymous> (/home/runner/work/parse-server/parse-server/spec/AuthenticationAdapters.spec.js:1671:7)

        at <Jasmine>

        at processTicksAndRejections (internal/process/task_queues.js:97:5)

mtrezza · 2021-03-05T23:52:00Z

Added!

cbaker6 · 2021-03-07T01:03:32Z

https://github.com/parse-community/parse-server/runs/2048364609#step:8:48

1) Cloud Code test beforeSave with invalid field
  Message:
    Failed: deadlock detected
  Stack:
    error properties: Object({ length: 317, severity: 'ERROR', code: '40P01', detail: 'Process 151 waits for AccessExclusiveLock on relation 50837 of database 19568; blocked by process 156.
    Process 156 waits for AccessShareLock on relation 50712 of database 19568; blocked by process 151.', hint: 'See server log for query details.', position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, dataType: undefined, constraint: undefined, file: 'deadlock.c', routine: 'DeadLockReport' })
        at <Jasmine>
        at Parser.parseErrorMessage (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:278:15)
        at Parser.handlePacket (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:126:29)
        at Parser.parse (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/parser.js:39:38)
        at Socket.stream.on (/home/runner/work/parse-server/parse-server/node_modules/pg-protocol/dist/index.js:10:42)
        at Socket.emit (events.js:198:13)
        at Socket.EventEmitter.emit (domain.js:448:20)
        at addChunk (_stream_readable.js:288:12)
        at readableAddChunk (_stream_readable.js:269:11)
        at Socket.Readable.push (_stream_readable.js:224:10)
        at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

https://github.com/parse-community/parse-server/pull/7242/checks?check_run_id=2048468586#step:8:48
and another (different from the other PuseController tests):

1) PushController should not enqueue push when device token is not set
  Message:
    Expected 'running' to be 'succeeded'.
  Stack:
    Error: Expected 'running' to be 'succeeded'.
        at <Jasmine>
        at query.find.then.results (/home/runner/work/parse-server/parse-server/spec/PushController.spec.js:1128:44)
        at process._tickCallback (internal/process/next_tick.js:68:7)

dplewis · 2021-03-15T07:14:19Z

Parse.GeoPoint testing creating geo point exception two fields fixed by #7265

mtrezza · 2021-03-16T00:35:19Z

Updated, added 2, fixed 1

dplewis · 2021-03-16T01:16:13Z

Jobs and Push flaky tests are addressed by #7267

Cloud Code cloud jobs should set the message / success on the job
PushController should not enqueue push when device token is not set
Parse.Push does not get stuck with _PushStatus 'running' on 1 installation added

mtrezza · 2021-03-16T13:07:32Z

Nice, updated!

mtrezza · 2021-03-28T21:23:54Z

Added

ParseGraphQLServer Auto API Schema Objects Queries Get read preferences should support includeReadPreference argument

Error: GraphQL error: Object not found.

parseplatformorg · 2023-05-01T20:27:04Z

🎉 This change has been released in version 6.1.0-alpha.8

parseplatformorg · 2023-05-01T21:37:41Z

🎉 This change has been released in version 6.1.0-beta.2

parseplatformorg · 2023-05-01T21:53:04Z

🎉 This change has been released in version 6.1.0

dplewis · 2024-07-17T14:33:21Z

Closing via #8468

mtrezza added the type:meta Non-code issue label Feb 11, 2021

mtrezza mentioned this issue Feb 11, 2021

Flaky tests (track flaky tests for further investigation) #7094

Closed

mtrezza pinned this issue Feb 11, 2021

mtrezza unpinned this issue Feb 11, 2021

mtrezza pinned this issue Feb 11, 2021

davimacedo mentioned this issue Feb 12, 2021

Fix flaky test with transactions #7187

Merged

5 tasks

davimacedo mentioned this issue Feb 16, 2021

Fix error when a not yet inserted job is updated #7196

Merged

5 tasks

davimacedo mentioned this issue Feb 18, 2021

Fix session expiration test #7208

Merged

6 tasks

davimacedo mentioned this issue Feb 20, 2021

Fix flaky test4 #7212

Merged

6 tasks

mtrezza mentioned this issue Mar 17, 2021

Improve single schema cache #7214

Merged

8 tasks

mtrezza mentioned this issue Mar 28, 2021

fix: empty file tags cause upload error for some providers #7300

Merged

4 tasks

mtrezza unpinned this issue Jul 24, 2021

mtrezza mentioned this issue Sep 19, 2021

feat: add onLoginFailed trigger #7536

Closed

8 tasks

mtrezza added type:ci CI related issue and removed type:meta Non-code issue labels Oct 9, 2021

mtrezza mentioned this issue Oct 9, 2021

fix: alphabetical GraphQL API, improved GraphQL Schema cache system and fix internal reassign #7344

Merged

7 tasks

This was referenced Jan 2, 2022

test: improve PushController tests #7760

Merged

test: improve transaction tests to use async/await #7759

Merged

test: make GraphQL server test more reliable #7758

Merged

dblythy mentioned this issue Oct 6, 2022

ci: add retries for flaky Postgres tests #8214

Closed

3 tasks

dblythy mentioned this issue Mar 8, 2023

ci: Fix flaky tests #8468

Merged

1 task

parseplatformorg added the state:released-alpha Released as alpha version label May 1, 2023

parseplatformorg added the state:released-beta Released as beta version label May 1, 2023

parseplatformorg added the state:released Released as stable version label May 1, 2023

mtrezza mentioned this issue Jun 22, 2023

Add test retry logic for flaky tests #8654

Closed

3 tasks

dplewis closed this as completed Jul 17, 2024

mtrezza mentioned this issue Jul 18, 2024

ci: Add test retry logic for flaky tests #9218

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix flaky tests #7180

Fix flaky tests #7180

mtrezza commented Feb 11, 2021 •

edited

Loading

mtrezza commented Feb 11, 2021

davimacedo commented Feb 16, 2021

davimacedo commented Feb 16, 2021

davimacedo commented Feb 18, 2021

mtrezza commented Feb 18, 2021 •

edited

Loading

davimacedo commented Feb 18, 2021

mtrezza commented Feb 18, 2021

davimacedo commented Feb 19, 2021

mtrezza commented Feb 19, 2021

davimacedo commented Feb 19, 2021

davimacedo commented Feb 19, 2021

dplewis commented Feb 19, 2021 •

edited

Loading

davimacedo commented Feb 20, 2021

davimacedo commented Feb 20, 2021

davimacedo commented Feb 20, 2021

mtrezza commented Feb 20, 2021

dplewis commented Feb 20, 2021

mtrezza commented Feb 20, 2021

mtrezza commented Feb 24, 2021

davimacedo commented Feb 24, 2021

mtrezza commented Feb 25, 2021

cbaker6 commented Mar 5, 2021

mtrezza commented Mar 5, 2021

cbaker6 commented Mar 7, 2021 •

edited

Loading

dplewis commented Mar 15, 2021

mtrezza commented Mar 16, 2021

dplewis commented Mar 16, 2021

mtrezza commented Mar 16, 2021

mtrezza commented Mar 28, 2021

parseplatformorg commented May 1, 2023

parseplatformorg commented May 1, 2023

parseplatformorg commented May 1, 2023

dplewis commented Jul 17, 2024

Fix flaky tests #7180

Fix flaky tests #7180

Comments

mtrezza commented Feb 11, 2021 • edited Loading

New Issue Checklist

Issue Description

Expected outcome

Flaky tests

Possibly fixed

Fixed tests

mtrezza commented Feb 11, 2021

davimacedo commented Feb 16, 2021

davimacedo commented Feb 16, 2021

davimacedo commented Feb 18, 2021

mtrezza commented Feb 18, 2021 • edited Loading

davimacedo commented Feb 18, 2021

mtrezza commented Feb 18, 2021

davimacedo commented Feb 19, 2021

mtrezza commented Feb 19, 2021

davimacedo commented Feb 19, 2021

davimacedo commented Feb 19, 2021

dplewis commented Feb 19, 2021 • edited Loading

davimacedo commented Feb 20, 2021

davimacedo commented Feb 20, 2021

davimacedo commented Feb 20, 2021

mtrezza commented Feb 20, 2021

dplewis commented Feb 20, 2021

mtrezza commented Feb 20, 2021

mtrezza commented Feb 24, 2021

davimacedo commented Feb 24, 2021

mtrezza commented Feb 25, 2021

cbaker6 commented Mar 5, 2021

mtrezza commented Mar 5, 2021

cbaker6 commented Mar 7, 2021 • edited Loading

dplewis commented Mar 15, 2021

mtrezza commented Mar 16, 2021

dplewis commented Mar 16, 2021

mtrezza commented Mar 16, 2021

mtrezza commented Mar 28, 2021

parseplatformorg commented May 1, 2023

parseplatformorg commented May 1, 2023

parseplatformorg commented May 1, 2023

dplewis commented Jul 17, 2024

mtrezza commented Feb 11, 2021 •

edited

Loading

mtrezza commented Feb 18, 2021 •

edited

Loading

dplewis commented Feb 19, 2021 •

edited

Loading

cbaker6 commented Mar 7, 2021 •

edited

Loading