Skip to content

test_sync_query_w_dml has num_dml_affected_rows unset #3742

Closed

Description

@dhermes

See: https://circleci.com/gh/GoogleCloudPlatform/google-cloud-python/2753

@tswast Any idea what would cause this "flake" to happen? (Note that the 2.7 system tests in the same build did not have this failure, as well as every other time this test case has run on CI.)

Activity

  1. tswast commented on Aug 7, 2017

    @tswast
    Contributor

    Bah! No clue. I wish we logged the Job ID so that I could pass it on to the backend team to investigate further.

  2. dhermes commented on Aug 7, 2017

    @dhermes
    ContributorAuthor

    Are the job IDs generated by the client? If yes, they probably match some specific regex with the build ID in it.

  3. tswast commented on Aug 7, 2017

    @tswast
    Contributor
  4. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Aug 7, 2017
  5. dhermes commented on Aug 7, 2017

    @dhermes
    ContributorAuthor

    Nice find. Is it worth making it possible to pass in a job_id (so the system test callers can use something unique)?

  6. tswast commented on Aug 7, 2017

    @tswast
    Contributor

    It doesn't fit the DB-API, but yeah I think we need to have some way to introspect.

  7. dhermes commented on Aug 9, 2017

    @dhermes
    ContributorAuthor
  8. tswast commented on Aug 9, 2017

    @tswast
    Contributor

    I'll update those tests to set a job ID prefix so it'll be easier to track down.

  9. tswast commented on Aug 9, 2017

    @tswast
    Contributor

    Ah, one thing it could be is the load job may not have finished. I'll use our handy new Futures API to wait until they are done before doing the DML query.

  10. tswast commented on Aug 9, 2017

    @tswast
    Contributor

    The other thing to keep in mind is that I'd very much like to remove the sync query method. Hopefully you got my redesign proposal doc?

  11. lukesneeringer commented on Aug 10, 2017

    @lukesneeringer
    Contributor

    I did, but we are in fix-it week so I will not read it until Monday.

  12. tswast commented on Aug 10, 2017

    @tswast
    Contributor

    Unfortunately the query verb doesn't take a job ID, so we'll only be able to debug half the flakes (DB-API, but not sync query). I'll finish my PR for the DB-API part, though.

  13. tswast commented on Oct 24, 2017

    @tswast
    Contributor

    Closing, as I haven't seen this flake on the bigquery-b2 branch and #4245 is now out to merge that to master.

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

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the BigQuery API.priority: p2Moderately-important priority. Fix may not be included in next release.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions