Bug #10500

Monitor failure modes of Seahorse

Added by kytv 2015-11-06 10:49:34 . Updated 2017-06-29 15:23:51 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Test suite
Target version:
Start date:
2015-11-06
Due date:
% Done:

0%

Feature Branch:
Type of work:
Wait
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Seahorse has multiple failure modes. This ticket’s purpose is to track them.

Files

03_16_02_Fetching_OpenPGP_keys_using_Seahorse_via_the_Tails_OpenPGP_Applet_should_work_and_be_done_over_Tor..png (47605 B) kytv, 2015-11-06 10:49:09
03_48_55_Syncing_OpenPGP_keys_using_Seahorse_started_from_the_Tails_OpenPGP_Applet_should_work_and_be_done_over_Tor..png (41918 B) kytv, 2015-11-06 10:49:13
torified_gnupg-2015-10-10T12_36_19-07_00.png (49773 B) kytv, 2015-11-06 10:49:17

Subtasks

Related issues

Related to Tails - Bug #9095: Seahorse tests lack robustness Resolved 2015-05-05
Related to Tails - Bug #9970: Seahorse may segfault during key synchronization Rejected 2015-08-11

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).