Bug #10475
Scenario "Using a persistent Electrum configuration" is fragile
0%
Description
The step “I create a new bitcoin wallet” fails quite often with mainly two errors:
Step: I create a new bitcoin wallet
Defined at: features/step_definitions/electrum.rb:17
Used in: Scenario: Using a persistent Electrum configuration
features/electrum.feature:2
Error trace:
FindFailed: can not find ElectrumEncryptWallet.png on the screen.
Line ?, in File ? (RuntimeError)
features/electrum.feature:23:in `When I create a new bitcoin wallet'
Step: I create a new bitcoin wallet
Defined at: features/step_definitions/electrum.rb:17
Used in: Scenario: Using a persistent Electrum configuration
features/electrum.feature:2
Error trace:
FindFailed: can not find ElectrumConnectServer.png on the screen.
Line ?, in File ? (RuntimeError)
features/electrum.feature:23:in `When I create a new bitcoin wallet'
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2015-07-08 |
History
#1 Updated by intrigeri 2015-11-05 02:58:02
- blocks #8668 added
#2 Updated by intrigeri 2015-11-05 02:58:13
- Status changed from New to Confirmed
#3 Updated by intrigeri 2015-11-06 06:09:49
- Deliverable for changed from 267 to 270
#4 Updated by anonym 2015-11-06 10:31:53
The whole electrum.feature
has been marked @fragile
in commit commit:7bc7535, so the fix for this ticket should revert it.
The fix likely involves solving Bug #9713 (and probably adapting the test suite to the new version of Electrum).
#5 Updated by anonym 2015-11-06 10:32:09
- blocked by
Bug #9713: Upgrade Electrum to >= 2.5.x for compatibility with all Electrum servers added
#6 Updated by kytv 2015-11-06 11:56:03
- Target version changed from Tails_1.8 to 246
#7 Updated by s7r 2015-11-12 16:09:03
- Target version changed from 246 to Tails_1.8
This should be fixed in 2.5.4. A lot of other bugs also fixed in 2.5.4. I think this version will be up and strong for reasonable time in the future. Setting same Target version with the other ticket ( Bug #9713 )
#8 Updated by kytv 2015-11-12 17:37:45
- Target version changed from Tails_1.8 to 246
s7r wrote:
> Setting same Target version with the other ticket ( Bug #9713 )
But this is for the test suite. If our tests (or test systems) themselves have problems they won’t be addressed during this release cycle.
#9 Updated by sajolida 2015-11-27 04:40:21
- Target version changed from 246 to Tails_2.0
#10 Updated by kytv 2015-11-28 18:51:35
- Target version changed from Tails_2.0 to Tails_2.2
This may be fixed by 2.x’s backporting to Tails. If not, this will probably not be addressed for 2.0.
#11 Updated by intrigeri 2016-03-03 15:23:17
- Deliverable for deleted (
270)
We can’t possibly fix all robustness and performance issues we discover as part of M6 => prioritizing areas that impact most users.
#12 Updated by anonym 2016-03-29 18:10:20
- Target version changed from Tails_2.2 to Tails_2.3
#13 Updated by anonym 2016-05-08 05:10:29
- Target version changed from Tails_2.3 to Tails_2.4
#14 Updated by anonym 2016-06-08 01:34:58
- Target version changed from Tails_2.4 to Tails_2.5
#15 Updated by BitingBird 2016-07-01 11:30:17
- Assignee deleted (
kytv) - Target version deleted (
Tails_2.5)
no news from kytv -> removing assignee and target version
#16 Updated by intrigeri 2017-12-08 07:53:06
- Affected tool set to Electrum
#17 Updated by Anonymous 2018-01-15 11:37:02
- blocked by deleted (
#8668)
#18 Updated by anonym 2018-02-27 00:14:45
- Status changed from Confirmed to In Progress
Applied in changeset commit:2ed2f4d612c3a44b7e31f401977ae0f084cbd44a.
#19 Updated by intrigeri 2019-03-08 16:52:20
Next step: check whether anonym’s fixes improve things here. Not part of core work though.
#20 Updated by intrigeri 2019-03-08 16:52:33
- Priority changed from Normal to Low