cloud-sql/postgres/knex: should handle insert error failed

[flaky-bot[bot]]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and I will stop commenting.

---

commit: e8e7284066dcbe7335c26589b5e7623329220784 buildURL: Build Status, Sponge status: failed

Test output

expected 400 "Bad Request", got 500 "Internal Server Error"
Error: expected 400 "Bad Request", got 500 "Internal Server Error"
    at Context. (test/server.test.js:59:6)
    at processImmediate (internal/timers.js:461:21)
----
    at Test._assertStatus (node_modules/supertest/lib/test.js:252:14)
    at /tmpfs/src/github/nodejs-docs-samples/cloud-sql/postgres/knex/node_modules/supertest/lib/test.js:306:17
    at Test._assertFunction (node_modules/supertest/lib/test.js:285:13)
    at Test.assert (node_modules/supertest/lib/test.js:164:23)
    at localAssert (node_modules/supertest/lib/test.js:120:14)
    at /tmpfs/src/github/nodejs-docs-samples/cloud-sql/postgres/knex/node_modules/supertest/lib/test.js:125:7
    at Test.Request.callback (node_modules/superagent/lib/node/index.js:943:3)
    at IncomingMessage. (node_modules/superagent/lib/node/index.js:1165:20)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (e8e7284066dcbe7335c26589b5e7623329220784), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[bcoe]

(I'm just testing out labeling behavior, to see if we're properly changing ownership in our bug backlog, will switch back to api: cloudsql).

[bcoe]

@jackwotherspoon this test has been green for weeks, let's revisit this flake next time it crops up.