-
Notifications
You must be signed in to change notification settings - Fork 2k
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
refactor: remove functions_concepts_error_object #1484
Conversation
@ace-n Can you review this assuming the tests pass? |
@@ -15,21 +15,7 @@ | |||
|
|||
'use strict'; | |||
|
|||
const sinon = require('sinon'); | |||
const assert = require('assert'); | |||
const tools = require('@google-cloud/nodejs-repo-tools'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we remove this file, or should we add a (simple) test for executionCount
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The goal of this PR is not to remove this test file, just to remove the functions_concepts_error_object
region tag.
I'm not sure why the other functions in this file don't have tests, but that's a separate issue.
I can delete the test file upon request, but I think it's fine to leave it blank for the other functions that should be tested. |
@ace-n WDYT about this PR? |
Apologies for the delay. I'd say go ahead and delete the test file. |
…ogleCloudPlatform/nodejs-docs-samples into grant-functions_concepts_error_object
2e67ed3
to
91e0821
Compare
91e0821
to
b2ea682
Compare
Removed the test file. PTAL. |
Can be merged when tests pass. |
Not sure why the PR is out of date w.r.t. master twice. |
@ace-n Can you look to why the |
This error was a result of deleting a test file and not removing the
related Kokoro config files. Arguably, this test failure ("no tests found",
if you look at the logs) should be expected.
You'll have to remove the *functions/concepts* test configs a) internally
(from Kokoro), and b) from the *nodejs-docs-samples/.kokoro* folder. LMK if
you need more specific info on *where* all that cruft is. (I can probably
dig up an example CL.)
…On Fri, Oct 11, 2019, 10:42 AM Grant Timmerman ***@***.***> wrote:
@ace-n <https://github.com/ace-n> Can you look to why the
functions/concepts test is failing? I really think there is a bug with
the testing infrastructure rather than this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1484?email_source=notifications&email_token=AARTZRJDLJDEA5B7JLE3F6LQOCGGRA5CNFSM4IXDNVHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBAG5II#issuecomment-541093537>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARTZRPHSCZKR2ST57PFKP3QOCGGRANCNFSM4IXDNVHA>
.
|
Well, this is one reason to not remove the file...
Can we just proceed to remove the sample/region tag Do you want me to remove this file too?: |
I'd prefer if we remove the empty test file. |
Our codelab explains it very well: go/kokoro-codelab |
Kokoro config removed with cl/276701784. |
Approved. Tests pass. Merging. |
Removes unused and not useful sample.