Prevent rare rbt_insert_and_remove unit test failures
When two or more absolute, two-label names are added to a completely empty RBT, an extra, empty node for the root name will be created due to node splitting. check_tree() expects that, but the extra node will not be created when just one name is added to a completely empty RBT. This problem could be handled inside check_tree(), but that would introduce unnecessary complexity into it since adding a single name will result in a different node count for a completely empty RBT (node count will be 1) and an RBT containing only an empty node for the root name, created due to prior node splitting (node count will be 2). Thus, first explicitly create a node for the root name to prevent rare check_tree() failures caused by a single name being added in the first iteration of the insert/remove loop.
471-fix-rbt_insert_and_remove-unit-test in 10 minutes and 35 seconds (queued for 4 seconds)25 jobs for