Oh dear. Thanks for testing! You could try changing the: i < 100 up to something bigger. Maybe 10000, otherwise that's going to be tricky to diagnose without access to hardware... Was it the same on all Ethernet ports?
edit: I've started a separate thread for this: Ethernet cable test feature bug fix - testers needed