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
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.
The text was updated successfully, but these errors were encountered:
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
orimport plateau.serialization
withpyarrow
10.0.1, however, it has also happened when importing other modules withinplateau
, and with otherpyarrow
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.
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.
The text was updated successfully, but these errors were encountered: