Project

General

Profile

Bug #10500

Bug #10288: Fix newly identified issues to make our test suite more robust and faster

Monitor failure modes of Seahorse

Added by kytv about 4 years ago. Updated over 2 years ago.

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

0%

Feature Branch:
Type of work:
Wait
Blueprint:
Starter:
Affected tool:

Description

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


Related issues

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

History

#1 Updated by kytv about 4 years ago

  • Related to Bug #9095: Seahorse tests lack robustness added

#2 Updated by kytv about 4 years ago

  • Assignee set to kytv

#3 Updated by kytv about 4 years ago

  • Target version set to Tails_2.2
  • Type of work changed from Code to Wait

#4 Updated by intrigeri about 4 years ago

  • Related to Bug #9970: Seahorse may segfault during key synchronization added

#5 Updated by anonym almost 4 years ago

  • 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?

#7 Updated by anonym over 3 years ago

  • Target version changed from Tails_2.3 to Tails_2.4

#8 Updated by anonym over 3 years ago

  • Target version changed from Tails_2.4 to Tails_2.5

#9 Updated by BitingBird over 3 years ago

  • Assignee deleted (kytv)
  • Target version deleted (Tails_2.5)

no news from kytv -> removing assignee and target version

#10 Updated by intrigeri over 2 years ago

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

Also available in: Atom PDF