You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed a segmentation fault in one of the hourly CI workflow, for golang-test job.
This has not re-occurred since, but was unable to completely root cause the problem with the existing logs, so leaving an issue in case it re-occurs in the future.
The segmentation fault occurs with the urfave/cli library, where one of the inner methods that parse string receives a null value instead of a string during setup. I suspect there must have been some kind of memory corruption in the runtime that altered the string value, because no code changes were made around the time and all other executions completed without any issues.
Steps to Reproduce
Not reproducible
Expected behavior
No segmentation fault happens and the application runs fine for testing.
Environment Information:
Refer to CI job (#8583)’s golang test (golang-test (32820) job).
Bug Description
Noticed a segmentation fault in one of the hourly CI workflow, for golang-test job.
This has not re-occurred since, but was unable to completely root cause the problem with the existing logs, so leaving an issue in case it re-occurs in the future.
The segmentation fault occurs with the urfave/cli library, where one of the inner methods that parse string receives a null value instead of a string during setup. I suspect there must have been some kind of memory corruption in the runtime that altered the string value, because no code changes were made around the time and all other executions completed without any issues.
Steps to Reproduce
Not reproducible
Expected behavior
No segmentation fault happens and the application runs fine for testing.
Environment Information:
Refer to CI job (#8583)’s golang test (golang-test (32820) job).
Configurations:
Logs:
The error log:
Additional context
Please ensure all required sections are filled out accurately to expedite the debugging process and improve issue resolution efficiency.
The text was updated successfully, but these errors were encountered: