Skip to content

Evaluate skipped system nox session for django-google-spanner #16099

@ohmayr

Description

@ohmayr

Determine this is the right repository

  • I determined this is the correct repository in which to report this bug.

Summary of the issue

We temporarily skipped the nox -s system session for django-google-spanner during the monorepo migration because they crash when run against a live Spanner instance. This is consistent to what we see in the split repo. See: googleapis/python-spanner-django#929.

These integration tests are already running successfully against the Spanner Emulator via GitHub Actions.

Decide if we should adapt these tests to support live Spanner on Kokoro, or permanently remove/repurpose the system nox session for this package to avoid CI confusion.

API client name and version

No response

Reproduction steps: code

file: main.py

   def reproduce():
    # complete code here

Reproduction steps: supporting files

file: mydata.csv

alpha,1,3
beta,2,5

Reproduction steps: actual results

file: output.txtmydata.csv

Calculated: foo

Reproduction steps: expected results

file: output.txtmydata.csv

Calculated: bar

OS & version + platform

No response

Python environment

No response

Python dependencies

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    api: spannerIssues related to the Spanner API.priority: p2Moderately-important priority. Fix may not be included in 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