Bug #10500
Monitor failure modes of Seahorse
Start date:
2015-11-06
Due date:
% Done:
0%
Description
Seahorse has multiple failure modes. This ticket’s purpose is to track them.
Files
Subtasks
History
#1 Updated by kytv 2015-11-06 10:53:14
- related to
Bug #9095: Seahorse tests lack robustness added
#2 Updated by kytv 2015-11-06 11:49:20
- Assignee set to kytv
#3 Updated by kytv 2015-11-06 12:23:06
- Target version set to Tails_2.2
- Type of work changed from Code to Wait
#4 Updated by intrigeri 2015-12-07 11:51:29
- related to
Bug #9970: Seahorse may segfault during key synchronization added
#5 Updated by anonym 2016-02-20 13:40:19
- Target version changed from Tails_2.2 to Tails_2.3
Can you please elaborate on what this is about? Turn this into something more actionable?
#6 Updated by intrigeri 2016-03-03 15:54:29
- Deliverable for deleted (
270)
#7 Updated by anonym 2016-05-08 05:10:29
- Target version changed from Tails_2.3 to Tails_2.4
#8 Updated by anonym 2016-06-08 01:34:59
- Target version changed from Tails_2.4 to Tails_2.5
#9 Updated by BitingBird 2016-07-01 11:30:52
- Assignee deleted (
kytv) - Target version deleted (
Tails_2.5)
no news from kytv -> removing assignee and target version
#10 Updated by intrigeri 2017-06-29 15:23:51
- Status changed from Confirmed to Rejected
I don’t think that’s very actionable. Let’s handle this as part of triaging false positives on Jenkins (none of the affected tests are flagged as fragile).