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

Upstash Redis SDK - CI tests crash #11036

Open
ogzhanolguncu opened this issue May 13, 2024 · 2 comments
Open

Upstash Redis SDK - CI tests crash #11036

ogzhanolguncu opened this issue May 13, 2024 · 2 comments
Labels
bug Something isn't working crash An issue that could cause a crash

Comments

@ogzhanolguncu
Copy link

How can we reproduce the crash?

This issue doesn't happen locally; it only occurs in CI. When we first introduced Bun 1.0 about six months ago, we didn't have these issues. Lately, they have become more prominent.

https://github.com/upstash/upstash-redis

JavaScript/TypeScript code that reproduces the crash?

No response

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.8 (89d2580) on linux x86_64_baseline [TestCommand]

Segmentation fault at address 0x00000000

@ogzhanolguncu ogzhanolguncu added bug Something isn't working crash An issue that could cause a crash labels May 13, 2024
@Electroid
Copy link
Contributor

Is there a particular test file we can take a look at that appears to cause the crash?

@ogzhanolguncu
Copy link
Author

https://github.com/upstash/upstash-redis/actions/runs/9061862211/job/24894513352 In this case it failed at pkg/commands/spop.test.ts. I feel like its random. But somehow manage to succeed here https://github.com/upstash/upstash-redis/actions/runs/9025180709. Also we started to see these problems after we introduced custom CI runner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working crash An issue that could cause a crash
Projects
None yet
Development

No branches or pull requests

2 participants