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

Brim CI failure: "TypeError: Cannot read property 'name' of undefined" #1529

Closed
philrz opened this issue Mar 23, 2021 · 1 comment · Fixed by #1533
Closed

Brim CI failure: "TypeError: Cannot read property 'name' of undefined" #1529

philrz opened this issue Mar 23, 2021 · 1 comment · Fixed by #1533
Labels
bug Something isn't working

Comments

@philrz
Copy link
Contributor

philrz commented Mar 23, 2021

https:/brimsec/brim/actions/runs/677403237 was a run of the Brim CI that was triggered by the advance of the zq pointer. The run was at Brim commit 31bbcd0 attempting to run with zq commit brimdata/super@50bd002 (associated with brimdata/super#2386). The failure was in the "histogram deep inspection" test in itest/tests/ingest.test.ts and the failure was attached in this screenshot:

image

I've since performed a local run of the Brim CI using that combination of commits and was not able to reproduce the failure. A subsequent zq commit triggered a re-run of the CI and it passed, so the zq pointer has since been successfully advanced. This seems to indicate that the problem might be intermittent.

@jameskerr
Copy link
Member

jameskerr commented Mar 24, 2021

I was able to reproduce this by navigating to a workspace that did not exist. In the PR that fixes this, I'll add a global function called navTo(url). I'll add an integration test that does this too.

@philrz philrz linked a pull request Apr 2, 2021 that will close this issue
@philrz philrz closed this as completed Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants