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.

Sign up for GitHub

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

Jump to bottom

Drive is failing with exit code 132 (illegal instruction) #2429

Open
shumkov opened this issue Jan 16, 2025 · 0 comments
Open

Drive is failing with exit code 132 (illegal instruction) #2429

shumkov opened this issue Jan 16, 2025 · 0 comments
Assignees
@shumkov @lklimek
Labels
bug Something isn't working

Comments

@shumkov
Copy link
Member

shumkov commented Jan 16, 2025

Expected Behavior

Current Behavior

Drive is failing with exit code 132 (illegal instruction) on Xeon® E5-2698 v3 around get best chain lock call on start.

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

  • Version used:
  • Environment name and version (e.g. Chrome 39, node.js 5.4):
  • Operating System and version (desktop, server, or mobile):
  • Link to your project:
@shumkov shumkov added the bug Something isn't working label Jan 16, 2025
@shumkov shumkov moved this to In Progress in Platform team Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shumkov shumkov

@lklimek lklimek

Labels
bug Something isn't working
Projects
Platform team
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shumkov @lklimek