Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Backend tests failing

See original GitHub issue

Something has changed in my environment such that I’m getting 7 back end test failures even on the release 1.7.0 code (I originally thought I’d broken something in my async branch).

The first reported error is:

  setText
    1) Sets text on a pad Id
superagent: double callback bug

with log messages:

[2019-02-28 17:52:30.905] [INFO] console -   1) setText
       Sets text on a pad Id:
     TypeError: Cannot read property 'body' of undefined
      at /home/ray/etherpad-old/tests/backend/specs/api/pad.js:392:14
      at Test._assertFunction (node_modules/supertest/lib/test.js:281:11)
      at Test.assert (node_modules/supertest/lib/test.js:171:18)
      at assert (node_modules/supertest/lib/test.js:131:12)
      at /home/ray/etherpad-old/src/node_modules/supertest/lib/test.js:128:5
      at Test.Request.callback (node_modules/superagent/lib/node/index.js:728:3)
      at ClientRequest.req.once.err (node_modules/superagent/lib/node/index.js:647:10)
      at Socket.socketErrorListener (_http_client.js:392:9)
      at emitErrorNT (internal/streams/destroy.js:82:8)
      at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
      at process._tickCallback (internal/process/next_tick.js:63:19)

I’m suspecting that an upstream module has changed in an incompatible way.

@muxator Are you able to replicate this?

Issue Analytics

State:
Created 5 years ago
Comments:12 (12 by maintainers)

Top GitHub Comments

1reaction

Wikinautcommented, Mar 1, 2019

@muxator May I suggest that you commit your clean.sh (as shown above) script to the /bin directory in the repo as a maintenance script? What do you/the others think?

0reactions

muxatorcommented, Jun 23, 2019

I guess this can be closed (see previous comment for explanation).

There is a remaining issue with the HTTP API, and for that we have a dedicated ticket (#3568).

Top Results From Across the Web

Foresight Blog | How to Fix Your Failing End-to-End Tests?

Troubleshooting test failures will be much harder if you have to check if your test fails because of memory exhaustion or an actual...

Debugging Failing Tests and Test Pipelines - GitLab

These guidelines are intended to help you to investigate end-to-end test pipeline failures so that they can be properly addressed. This will involve...

Tests fail when backend is set to server · Issue #2319 - GitHub

Switching to prefect backend cloud resolves the test failures. Expected Behavior. Tests should be independent of a user's local environment ...

Failing at Integration Testing: Common Mistakes - TestQuality

While it may be impossible to maintain all tests running at 100% all of the time, not performing tests at all is not...

Fixing Tests in CI/CD: Why are Your Tests Failing?

There are multiple reasons to take failing tests seriously. First, failed tests can block the delivery of new releases, because the CI/CD ...