[STORM-2748] TickTupleTest is useless

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: storm-server
• Labels: pull-request-available
• Assignee: Robert Joseph Evans
• Reporter: Robert Joseph Evans
• Created: 20/Sep/17 14:22
• Updated: 21/Sep/17 18:01
• Resolved: 21/Sep/17 18:00

Description

The test starts up a small topology on a simulated time cluster with TOPOLOGY_TICK_TUPLE_FREQ_SECS set to 1. Then it simulates 2 seconds of cluster time. This is not enough time to even launch the topology. How do I know this? Because the Bolt and Spout in the topology override `writeObject` so the resulting serialized bolt and spout are empty and trying to deserialize them results in an exception.

Just running a topology that does nothing and never verifies that the ticks showed up is a really horrible test. We should either delete it entirely or actually verify that ticks are showing up once a second. I am leaning towards just removing it totally.

Issue Links

• links to: GitHub Pull Request #2334