-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: deductSweepCredit bad symbol table #73519
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
Labels
BugReport
Issues describing a possible bug in the Go implementation.
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Comments
is this reproducible? |
I have not seen another occurrence of this yet. I will keep you posted in case I see this again. |
Saw a different stack trace but similar looking issue today here https://github.com/hypermodeinc/dgraph/actions/runs/14758559804/job/41433147958?pr=9401. job-logs.txt
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BugReport
Issues describing a possible bug in the Go implementation.
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Go version
1.24.2
Output of
go env
in your module/workspace:What did you do?
CI was running our integration tests for dgraph, the database. The logs for CI run are available here https://github.com/hypermodeinc/dgraph/actions/runs/14650128041/job/41113653523?pr=9396. I am also attaching the logs because this link may not be valid for too long. job-logs.txt
What did you see happen?
What did you expect to see?
Not see a panic such as this
The text was updated successfully, but these errors were encountered: