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

Segfaults caused by 'import plateau' in CI #100

Closed
IzerOnadimQC opened this issue Sep 29, 2023 · 1 comment
Closed

Segfaults caused by 'import plateau' in CI #100

IzerOnadimQC opened this issue Sep 29, 2023 · 1 comment

Comments

@IzerOnadimQC
Copy link
Collaborator

IzerOnadimQC commented Sep 29, 2023

Occasionally, the CI pipeline fails with a seg fault during the 'Test import' stage. Specifically, most of the time the segfault occurs during import plateau.api.serialization or import plateau.serialization with pyarrow 10.0.1, however, it has also happened when importing other modules within plateau, and with other pyarrow versions. It doesn't happen all the time, and it always goes away upon the second or third time re-running the CI job.

For example, in this job the first attempted produced a seg fault, but the second passed.

/home/runner/work/_temp/30f92123-be37-4fc8-bb7e-ecd68eb49daa.sh: line 8:  3592 Segmentation fault      (core dumped) python -c "import plateau.serialization"
Error: Process completed with exit code 139.

Ideally, we should find the source of these seg faults, probably by comparing successful and failed runs, and eliminate them to avoid the hassle of re-running the pipeline.

@IzerOnadimQC
Copy link
Collaborator Author

This was a transitory issue which seems to have resolved itself, so I'll close this issue for now and re-open it if the problem crops up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant