CI on LTS branch release-4.x is broken

[mtrezza]

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

CI fails with error:

Error: Object not found.
at then.then.result (/home/runner/work/parse-server/parse-server/lib/Controllers/DatabaseController.js:49:3084)
at process._tickCallback (internal/process/next_tick.js:68:7)

Possibly introduced by 4ac4b7f.

Steps to reproduce

Run CI on current release-4.x branch.

Actual Outcome

CI fails.

Expected Outcome

CI should pass.

Environment

Server

• Parse Server version: 4ac4b7f

Logs

See https://github.com/parse-community/parse-server/runs/4028298097?check_suite_focus=true

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[FransGH]

This is not an error but seems to be 'expected' trace output from EnableExpressErrorHandler.spec.js.

I see this too when running the test locally and it's not resulting in a failed test, although the trace output is confusing.

[mtrezza]

Then it may be some other issue. Since two different PRs face the same issue of the CI failing on this branch, I assume it's some issue with the branch, not with any of the PRs. When you run npm test locally on Node 10 with the latest commit of the 4.x branch, do all tests pass?

[mtrezza]

Closing as the LTS branch is no longer maintained.