Skip to content

Scenario "Connecting to the #i2p IRC channel" is fragile

As one can see in this job in Jenkins and others, this scenario fails often and seems a bit fragile:

3:26:19     Then Pidgin successfully connects to the "I2P" account                                          # features/step_definitions/pidgin.rb:319
03:26:19       FindFailed: can not find PidginAccount_I2P.png on the screen.
03:26:19       Line ?, in File ? (RuntimeError)
03:26:19       ./features/step_definitions/pidgin.rb:313:in `deactivate_and_activate_pidgin_account'
03:26:19       ./features/step_definitions/pidgin.rb:326:in `block (2 levels) in <top (required)>'
03:26:19       ./features/support/helpers/misc_helpers.rb:128:in `call'
03:26:19       ./features/support/helpers/misc_helpers.rb:128:in `rescue in block in retry_action'
03:26:19       ./features/support/helpers/misc_helpers.rb:120:in `block in retry_action'
03:26:19       ./features/support/helpers/misc_helpers.rb:119:in `loop'
03:26:19       ./features/support/helpers/misc_helpers.rb:119:in `retry_action'
03:26:19       ./features/support/helpers/misc_helpers.rb:109:in `retry_i2p'
03:26:19       ./features/step_definitions/pidgin.rb:330:in `call'
03:26:19       ./features/step_definitions/pidgin.rb:330:in `/^Pidgin successfully connects to the "([^"]+)" account$/'

Feature Branch: kytv/test/10474-i2p-irc-is-fragile

Attachments

Parent Task: #10288

Related issues

Original created by @bertagaz on 10474 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information