Skip to content
This repository was archived by the owner on Oct 20, 2026. It is now read-only.
This repository was archived by the owner on Oct 20, 2026. It is now read-only.

Unit tests are broken on master #829

Closed

Description

@JustinBeckwith

Just cloning the repo and running the tests, looks like the unit tests are somehow broken. PRs are starting to pile up - we should prioritize ASAP.

@olavloite @skuruppu

Activity

  1. added
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Feb 13, 2020
  2. self-assigned this
    on Feb 13, 2020
  3. olavloite commented on Feb 13, 2020

    @olavloite
    Contributor

    @skuruppu @JustinBeckwith I'll have a look right away.

  4. olavloite commented on Feb 13, 2020

    @olavloite
    Contributor

    @JustinBeckwith @skuruppu @bcoe
    The problem appears to be related to Node version 12.16.0. I had 12.15.0 installed locally and could run all tests without problems. I've now installed 12.16.0 and get the error that is also showing up in the CI:

      1) Database
           "before each" hook for "should promisify all the things":
         TypeError: Cannot assign to read only property 'errorMonitor' of function 'class Database extends service_object_1.GrpcServiceObject {
        constructor(instance, name, poolOptions) {
        ...<omitted>...
    }'
          at setProperty (node_modules/extend/index.js:46:24)
          at extend (node_modules/extend/index.js:108:7)
          at Context.<anonymous> (test/database.ts:218:5)
          at processImmediate (internal/timers.js:456:21)
    
  5. added a commit that references this issue on Feb 13, 2020
    0798cea
  6. bcoe commented on Feb 18, 2020

    @bcoe

    this was ultimately fixed in Node@12.16.1, just a fun note: https://nodejs.org/en/blog/release/v12.16.1/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

api: spannerIssues related to the googleapis/nodejs-spanner API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions