That test is a bit non-deterministic. I looked into it awhile back. I think it has something to do with how the executor service retains a link to the thread-local parent span in Tracing (or rather, fails to do so). To fix, we probably need a proper trace-aware thread service, but that's probably not going to happen any time soon (because it's not critical, and the future of the tracing libraries are a bit uncertain at the moment, with HTrace retiring).
In my CI server, I saw ShellServerIT fail for this reason, and then pass on a subsequent run. On Tue, Jul 30, 2019 at 1:06 PM Keebler, Holly I <[email protected]> wrote: > > Confirmed that this is not failing for me. > > ________________________________ > From: Owens, Mark <[email protected]> > Sent: Tuesday, July 30, 2019 12:15:59 PM > To: accumulo-dev <[email protected]> > Subject: rc2 test question > > [External Email] > > ---------------------------------------------------------------------- > Is anyone having any issues with ShellServerIT failing in the RC2 release? > > It is consistently failing for me at line 1691. > > assertTrue(trace.contains("sendMutations")); > > > Log output from test displays 'binMutations' but no 'sendMutations' output. > > Trace started at 2019/07/30 15:31:22.336 > Time Start Service@Location Name > 3417+0 shell@ip-10-113-10-222 shell:root > 2+163 [email protected] beginFateOperation > 5+170 [email protected] executeFateOperation > 6+177 [email protected] CreateTable > 2+183 [email protected] CreateTable > 16+187 [email protected] SetupPermissions > 3+207 [email protected] PopulateZookeeper > 25+210 [email protected] PopulateZookeeper > 101+176 [email protected] waitForFateOperation > 4+278 [email protected] finishFateOperation > 1507+288 shell@ip-10-113-10-222 close > 10+288 shell@ip-10-113-10-222 BinMutations 1 > 5+288 shell@ip-10-113-10-222 binMutations > 2+290 [email protected] startScan > 1+292 [email protected] startScan > 1+292 [email protected] scan-meta 7 > 3+1796 [email protected] getTableConfiguration > 1+1799 shell@ip-10-113-10-222 client:getTableConfiguration > 3+1800 [email protected] getTableConfiguration > 3+1804 [email protected] getTableConfiguration > 3+1808 [email protected] getTableConfiguration > 8+1814 shell@ip-10-113-10-222 scan > 8+1814 shell@ip-10-113-10-222 scan:location > 8+1814 [email protected] startScan > 7+1815 [email protected] scan-default 14 > 1+1823 [email protected] beginFateOperation > 11+1825 [email protected] executeFateOperation > 7+1837 [email protected] DeleteTable > 2+1844 [email protected] DeleteTable > 3+2294 [email protected] CleanUp > 1+2296 [email protected] scan > 1+2296 [email protected] scan:location > 102+2297 [email protected] CleanUp > 1+2310 [email protected] batch scanner 659- 1 > 2+2311 [email protected] scan > 2+2311 [email protected] scan:location > 2+2311 [email protected] startScan > 2+2311 [email protected] scan-meta 4 > 1+2313 [email protected] close > 1+2315 [email protected] scan > 1+2315 [email protected] scan:location > 1+2315 [email protected] startScan > 574+1836 [email protected] waitForFateOperation > 6+2410 [email protected] finishFateOperation > > > ________________________________ > > The preceding message (including attachments) is covered by the Electronic > Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for > the person or entity to which it is addressed, and may contain information > that is confidential, protected by attorney-client or other privilege, or > otherwise protected from disclosure by law. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. Please > reply to the sender that you have received the message in error and destroy > the original message and all copies.
