Unlike the UASF timebomb, SegWit2x won't activate unless there's 80%+ support, so it's not going to trigger a fork. (Well, technically it will, but if activated the non-SegWit2x rump will quickly be reduced to irrelevance.)
It seems rather premature to call it working before it gets properly tested. And three weeks is a woefully short time to test something like this, fix any issues that are found, and then re-test.
