Hacker News new | past | comments | ask | show | jobs | submit login

This is what I don’t get, it’s extremely hard for me to believe this didn’t get caught in CI when things started blue screening. Every place I ever did test rebooting/powercycling was part of CI, with various hardware configs. This was before even our lighthouse customers even saw it.



What makes you think they have CI after what happened?


Apparently the flaw was added to the config file in post-processing after it had completed testing. So they thought they had testing, but actually didn't.


Disgruntled employee trying to use Crowd Strike to start a General Strike?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: