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

loadSync: should load a test file that relies on common protos failed #412

Closed
flaky-bot bot opened this issue Mar 30, 2022 · 2 comments
Closed

loadSync: should load a test file that relies on common protos failed #412

flaky-bot bot opened this issue Mar 30, 2022 · 2 comments
Assignees
Labels
flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Mar 30, 2022

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.


commit: c8df19d
buildURL: Build Status, Sponge
status: failed

Test output
error reading first path in the walk /workspace/google/protobuf
Error: ENOENT: no such file or directory, lstat '/workspace/google/protobuf'
Error: error reading first path in the walk /workspace/google/protobuf
Error: ENOENT: no such file or directory, lstat '/workspace/google/protobuf'
    at EventEmitter. (node_modules/walkdir/walkdir.js:265:28)
    at fn (node_modules/walkdir/walkdir.js:100:17)
    at statter (node_modules/walkdir/walkdir.js:137:7)
    at walkdir (node_modules/walkdir/walkdir.js:269:3)
    at Function.walkdir.sync (node_modules/walkdir/walkdir.js:15:10)
    at /workspace/build/src/load.js:43:29
        -> /workspace/src/load.ts:50:24
    at Array.map ()
    at Function.getCommonProtoFiles (build/src/load.js:42:18)
        -> /workspace/src/load.ts:49:10
    at GoogleProtoFilesRoot.resolvePath (build/src/load.js:60:55)
        -> /workspace/src/load.ts:71:51
    at process (node_modules/protobufjs/src/root.js:132:86)
    at fetch (node_modules/protobufjs/src/root.js:178:13)
    at GoogleProtoFilesRoot.load (node_modules/protobufjs/src/root.js:206:13)
    at GoogleProtoFilesRoot.loadSync (node_modules/protobufjs/src/root.js:247:17)
    at Object.loadSync (build/src/load.js:70:17)
        -> /workspace/src/load.ts:83:15
    at Context. (build/test/load.test.js:58:39)
        -> /workspace/test/load.test.ts:73:35
    at processImmediate (internal/timers.js:461:21)
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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. labels Mar 30, 2022
@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels Apr 4, 2022
@hkdevandla
Copy link
Member

@summer-ji-eng , can you please take a look?

@summer-ji-eng
Copy link
Contributor

fixed PR #426

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. 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

3 participants