Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iot CI failing #1527

Closed
fhinkel opened this issue Oct 25, 2019 · 9 comments
Closed

iot CI failing #1527

fhinkel opened this issue Oct 25, 2019 · 9 comments
Assignees
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@fhinkel
Copy link
Contributor

fhinkel commented Oct 25, 2019

Hi @hongalex , I can't get the iot manager test to pass, e.g., on this PR

https://source.cloud.google.com/results/invocations/ae9e7ed3-31f2-4454-b0e3-57fef10e1b2d/targets/cloud-devrel%2Fnodejs-docs-samples%2Fpresubmit%2Fiot%2Fiot-manager/log

Refs

Could you have a look? Thanks

@fhinkel
Copy link
Contributor Author

fhinkel commented Oct 25, 2019

The iot/manager test failing seem to be related to this change:
googleapis/nodejs-iot@68a1d6e

Method name changed, but test from sample code was not updated.
client.registryPath -> client.deviceRegistryPath

@mesmacosta
Copy link
Contributor

I sent a PR with a proposed fix: #1528

@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Oct 26, 2019
@fhinkel fhinkel added priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed triage me I really want to be triaged. labels Oct 28, 2019
@JustinBeckwith JustinBeckwith added the type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. label Oct 28, 2019
@fhinkel
Copy link
Contributor Author

fhinkel commented Oct 31, 2019

@hongalex @gguuss We deactivated the tests for now. Were you able to roll back the API change? Or should we adapt the test?

@gguuss
Copy link
Contributor

gguuss commented Oct 31, 2019

@JustinBeckwith to comment on rolling back the breaking change, I lost track of the thread where this discussion was taking place and am currently traveling so I'm unable to really be very responsive here. The v0.3 iot library introduces the issue.

@gguuss
Copy link
Contributor

gguuss commented Oct 31, 2019

We have this PR with a fix, I'm open to merging it and then resolving if we can roll back.

@fhinkel
Copy link
Contributor Author

fhinkel commented Nov 5, 2019

ping @JustinBeckwith

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Nov 5, 2019
@JustinBeckwith
Copy link
Contributor

Tracking in b/143947540

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Nov 10, 2019
@gguuss
Copy link
Contributor

gguuss commented Nov 13, 2019

This will be fixed when this PR merges.

@gguuss
Copy link
Contributor

gguuss commented Nov 13, 2019

This is now fixed, thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

6 participants