avamingli commented on issue #765: URL: https://github.com/apache/cloudberry/issues/765#issuecomment-2533786054
Hi, @edespino Truly appreciate your willingness to help with this issue in our CI/CD pipeline. Implementing a system to detect core dump files and fail the build if they exist is an excellent proactive measure. This will not only enhance our testing process but also ensure that we maintain a high standard of stability and reliability in our builds. > Before proceeding, could you clarify if any of the current core file generations are intentional test cases? Only have this one after regression passed on my Ubuntu. Do you mean which case triggers that ? There are: > Unfortunately, I don't know which specific test case is causing the core dump at this point; identifying that is the key of addressing this issue. The call stack indicates that the core dump is triggered by an auxiliary process, but it's unclear which test case activates that process And if you’re asking about which core file names might be intentional? It’s important to note that the naming of core dump files is determined by the Linux user settings using core_pattern. > /proc/sys/kernel/core_pattern Essentially, the user configuration dictates how these files are generated and named. What we currently have is the information from the call stack. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
