CTCP test assumes that we're still using the configured, randomized nickname
Originally created by @kytv on #10228 (Redmine)
The test can fail if the randomized nickname that was generated is already in use.
Received unexpected CTCP reply 'CLIENTINFO' with data 'PING VERSION TIME USERINFO CLIENTINFO'
/home/ky/usr/bin/cucumber:13:in `<main>'er/cli/main.rb:42:in `execute!'sit_features'features'lement'd'e_filtering'
And the "irc.oftc.net" account only responds to PING and VERSION CTCP requests # features/step_definitions/pidgin.rb:346
Received unexpected CTCP reply 'CLIENTINFO' with data 'PING VERSION TIME USERINFO CLIENTINFO' (RuntimeError)
./features/support/helpers/ctcp_helper.rb:115:in `block in on_message'
./features/support/helpers/ctcp_helper.rb:105:in `each'
./features/support/helpers/ctcp_helper.rb:105:in `on_message'
./features/support/helpers/ctcp_helper.rb:38:in `block in verify_ctcp_responses'
./features/support/helpers/ctcp_helper.rb:37:in `verify_ctcp_responses'
./features/step_definitions/pidgin.rb:358:in `/^the "([^"]*)" account only responds to PING and VERSION CTCP requests$/'
features/pidgin.feature:68:in `And the "irc.oftc.net" account only responds to PING and VERSION CTCP requests'
In this case, the nickname which was generated was already on IRC so the
nickname in Pidgin in the TailsToaster VM had a 1
tacked on to the
end, causing the CTCP test to test a real user. The logs (redacted a
bit) showed the
following:
D, [2015-09-2xTxx:yy:zz.594006 #8146] DEBUG -- : RECEIVE: :nickname!~xyz@nickname.user.oftc.net NOTICE Asf7sF9ZgF :^ACLIENTINFO PING VERSION TIME USERINFO CLIENTINFO^A
A user connected via Tor in Pidgin would look like
nickname!nickname
RANDOMSTRING.tor-irc.dnsbl.oftc.net@.