3 ms·
> 2. Either the corrupted files slipped through internal testing, or there is no internal testing. This is the most interesting question to me because it doesn
by rainsford 2y ago
> 2. Either the corrupted files slipped through internal testing, or there is no internal testing.
This is the most interesting question to me because it doesn't seem like there is an obviously guessable answer. It seem very unlikely to me that a company like CrowdStrike pushes out updates of any kind without doing some sort of testing, but the widespread nature of the outage would also seem to suggest any sort of testing setup should have caught the issue. Unless it's somehow possible for CrowdStrike to test an update that was different than what was deployed, it's not obvious what went wrong here.
- bloopernova 2y agoI had read somewhere that the definition file was corrupted after testing, during the final CI/CD pipeline.
- dboreham 2y agoBecause nowadays nobody knows you test the actual bits you're going to ship, not whatever random crap comes out of someone's build script run in a different place and time that's supposed to be the same as what you'll ship.