Revert "Flag online scenarios as fragile."

This reverts commit f8e5fb99.

features/checks.feature

@@ -25,7 +25,7 @@ Feature: Various checks
     Given I have started Tails from DVD without network and logged in
     Then the shipped Debian repository key will be valid for the next 3 months
 
-  @doc @fragile
+  @doc
   Scenario: The "Report an Error" launcher will open the support documentation
     Given I have started Tails from DVD without network and logged in
     And the network is plugged
@@ -40,7 +40,6 @@ Feature: Various checks
     And the live user is a member of only its own group and "audio cdrom dialout floppy video plugdev netdev scanner lp lpadmin vboxsf"
     And the live user owns its home dir and it has normal permissions
 
-  @fragile
   Scenario: No initial network
     Given I have started Tails from DVD without network and logged in
     And I wait between 30 and 60 seconds
@@ -50,21 +49,18 @@ Feature: Various checks
     And the time has synced
     And process "vidalia" is running within 30 seconds
 
-  @fragile
   Scenario: The 'Tor is ready' notification is shown when Tor has bootstrapped
     Given I have started Tails from DVD without network and logged in
     And the network is plugged
     When I see the 'Tor is ready' notification
     Then Tor is ready
 
-  @fragile
   Scenario: The tor process should be confined with Seccomp
     Given I have started Tails from DVD without network and logged in
     And the network is plugged
     And Tor is ready
     Then the running process "tor" is confined with Seccomp in filter mode
 
-  @fragile
   Scenario: No unexpected network services
     Given I have started Tails from DVD without network and logged in
     When the network is plugged

features/dhcp.feature

-@product @fragile
+@product
 Feature: Getting a DHCP lease without leaking too much information
   As a Tails user
   when I connect to a network with a DHCP server

features/electrum.feature

-#10497: wait_until_tor_is_working
 #10720: Tails Installer freezes on Jenkins
 @product @check_tor_leaks @fragile
 Feature: Electrum Bitcoin client

features/i2p.feature

@@ -15,13 +15,11 @@ Feature: I2P
     And the I2P Browser sudo rules are present
     And the I2P firewall rules are enabled
 
-  @fragile
   Scenario: I2P's AppArmor profile is in enforce mode
     Given I have started Tails from DVD with I2P enabled and logged in and the network is connected
     When I2P is running
     Then the running process "i2p" is confined with AppArmor in enforce mode
 
-  @fragile
   Scenario: The I2P Browser works as it should
     Given I have started Tails from DVD with I2P enabled and logged in and the network is connected
     And the I2P router console is ready
@@ -29,7 +27,6 @@ Feature: I2P
     Then the I2P router console is displayed in I2P Browser
     And the I2P Browser uses all expected TBB shared libraries
 
-  @fragile
   Scenario: Closing the I2P Browser shows a stop notification and properly tears down the chroot.
     Given I have started Tails from DVD with I2P enabled and logged in and the network is connected
     And the I2P router console is ready
@@ -38,7 +35,6 @@ Feature: I2P
     Then I see the I2P Browser stop notification
     And the I2P Browser chroot is torn down
 
-  @fragile
   Scenario: The I2P internal websites can be viewed in I2P Browser
     Given I have started Tails from DVD with I2P enabled and logged in and the network is connected
     And the I2P router console is ready
@@ -48,8 +44,7 @@ Feature: I2P
     When I open the address "http://i2p-projekt.i2p" in the I2P Browser
     Then the I2P homepage loads in I2P Browser
 
-  @fragile
-  Scenario: I2P is configured to run in Hidden mode
+ Scenario: I2P is configured to run in Hidden mode
     Given I have started Tails from DVD with I2P enabled and logged in and the network is connected
     And the I2P router console is ready
     When I start the I2P Browser through the GNOME menu
@@ -70,7 +65,6 @@ Feature: I2P
     Then Pidgin successfully connects to the "I2P" account
     And I can join the "#i2p" channel on "I2P"
 
-  @fragile
   Scenario: I2P displays a notice when bootstrapping fails
     Given I have started Tails from DVD with I2P enabled and logged in
     And I2P is not running
@@ -85,7 +79,6 @@ Feature: I2P
     When I start the I2P Browser through the GNOME menu
     Then the I2P router console is displayed in I2P Browser
 
-  @fragile
   Scenario: I2P displays a notice when it fails to start
     Given I have started Tails from DVD with I2P enabled and logged in
     And I2P is not running

features/icedove.feature

-@product @check_tor_leaks @fragile
+@product @check_tor_leaks
 Feature: Icedove email client
   As a Tails user
   I may want to use an email client

features/localization.feature

-@product @fragile
+@product
 Feature: Localization
   As a Tails user
   I want Tails to be localized in my native language

features/mac_spoofing.feature

@@ -10,7 +10,6 @@ Feature: Spoofing MAC addresses
     And I capture all network traffic
     And the network is plugged
 
-  @fragile
   Scenario: MAC address spoofing is disabled
     When I enable more Tails Greeter options
     And I disable MAC spoofing in Tails Greeter
@@ -21,7 +20,6 @@ Feature: Spoofing MAC addresses
     And the network device has its default MAC address configured
     And the real MAC address was leaked
 
-  @fragile
   Scenario: MAC address spoofing is successful
     When I log in to a new session
     And the Tails desktop is ready

features/pidgin.feature

-#10497: wait_until_tor_is_working
-@product @fragile
+@product
 Feature: Chatting anonymously using Pidgin
   As a Tails user
   when I chat using Pidgin

features/ssh.feature

-#10497: wait_until_tor_is_working
-#10498: SSH tests are fragile
 @product @fragile
 Feature: Logging in via SSH
   As a Tails user

features/time_syncing.feature

@@ -4,16 +4,12 @@ Feature: Time syncing
   I want Tor to work properly
   And for that I need a reasonably accurate system clock
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock with host's time
     Given I have started Tails from DVD without network and logged in
     When the network is plugged
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock with host's time in bridge mode
     Given I have started Tails from DVD without network and logged in with bridge mode enabled
     When the network is plugged
@@ -22,8 +18,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock is one day in the past
     Given I have started Tails from DVD without network and logged in
     When I bump the system time with "-1 day"
@@ -31,8 +25,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock is one day in the past in bridge mode
     Given I have started Tails from DVD without network and logged in with bridge mode enabled
     When I bump the system time with "-1 day"
@@ -42,8 +34,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock is way in the past
     Given I have started Tails from DVD without network and logged in
     # 13 weeks will span over two Tails release cycles.
@@ -52,8 +42,7 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
+ @fragile
   Scenario: Clock way in the past in bridge mode
     Given I have started Tails from DVD without network and logged in with bridge mode enabled
     When I bump the system time with "-6 weeks"
@@ -63,8 +52,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  #10440: Time syncing tests are fragile
   @fragile
   Scenario: Clock is one day in the future
     Given I have started Tails from DVD without network and logged in
@@ -73,8 +60,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  @fragile
   Scenario: Clock is one day in the future in bridge mode
     Given I have started Tails from DVD without network and logged in with bridge mode enabled
     When I bump the system time with "+1 day"
@@ -84,8 +69,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  #10440: Time syncing tests are fragile
   @fragile
   Scenario: Clock way in the future
     Given I have started Tails from DVD without network and logged in
@@ -94,8 +77,6 @@ Feature: Time syncing
     And Tor is ready
     Then Tails clock is less than 5 minutes incorrect
 
-  #10497: wait_until_tor_is_working
-  #10440: Time syncing tests are fragile
   @fragile
   Scenario: Clock way in the future in bridge mode
     Given I have started Tails from DVD without network and logged in with bridge mode enabled

features/tor_bridges.feature

-@product @fragile
+@product
 Feature: Using Tails with Tor pluggable transports
   As a Tails user
   I want to circumvent censorship of Tor by using Tor pluggable transports

features/tor_enforcement.feature

-#10497: wait_until_tor_is_working
-@product @fragile
+@product
 Feature: The Tor enforcement is effective
   As a Tails user
   I want all direct Internet connections I do by mistake or applications do by misconfiguration or buggy leaks to be blocked

features/tor_stream_isolation.feature

-#10497: wait_until_tor_is_working
-@product @check_tor_leaks @fragile
+@product @check_tor_leaks
 Feature: Tor stream isolation is effective
   As a Tails user
   I want my Torified sessions to be sensibly isolated from each other to prevent identity correlation

features/torified_browsing.feature

-#10376: The "the Tor Browser loads the (startup page|Tails roadmap)" step is fragile
-#10497: wait_until_tor_is_working
 @product @fragile
 Feature: Browsing the web using the Tor Browser
   As a Tails user
@@ -134,7 +132,7 @@ Feature: Browsing the web using the Tor Browser
     And the Tor Browser has started and loaded the startup page
     Then the Tor Browser has no plugins installed
 
-  #10497, #10720
+  #10720
   @fragile
   Scenario: The persistent Tor Browser directory is usable
     Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in

features/torified_git.feature

-#10497: wait_until_tor_is_working
-#10444: Git tests are fragile
 @product @check_tor_leaks @fragile
 Feature: Cloning a Git repository
   As a Tails user

features/torified_gnupg.feature

-@product @check_tor_leaks @fragile
+@product @check_tor_leaks
 Feature: Keyserver interaction with GnuPG
   As a Tails user
   when I interact with keyservers using various GnuPG tools

features/torified_misc.feature

-@product @check_tor_leaks @fragile
+@product @check_tor_leaks
 Feature: Various checks for torified software
 
   Background:

features/totem.feature

@@ -40,7 +40,6 @@ Feature: Using Totem
     # as /lib/live/mount/overlay.
     And AppArmor has denied "/usr/bin/totem" from opening "/lib/live/mount/overlay/home/amnesia/.gnupg/video.mp4"
 
-  #10497: wait_until_tor_is_working
   @check_tor_leaks @fragile
   Scenario: Watching a WebM video over HTTPS
     Given I have started Tails from DVD and logged in and the network is connected

features/unsafe_browser.feature

@@ -4,7 +4,6 @@ Feature: Browsing the web using the Unsafe Browser
   when I browse the web using the Unsafe Browser
   I should have direct access to the web
 
-  @fragile
   Scenario: The Unsafe Browser can access the LAN
     Given I have started Tails from DVD and logged in and the network is connected
     And a web server is running on the LAN
@@ -12,7 +11,6 @@ Feature: Browsing the web using the Unsafe Browser
     And I open a page on the LAN web server in the Unsafe Browser
     Then I see "UnsafeBrowserHelloLANWebServer.png" after at most 20 seconds
 
-  @fragile
   Scenario: Starting the Unsafe Browser works as it should.
     Given I have started Tails from DVD and logged in and the network is connected
     When I successfully start the Unsafe Browser
@@ -25,7 +23,6 @@ Feature: Browsing the web using the Unsafe Browser
     And the Unsafe Browser has no proxy configured
     And the Unsafe Browser uses all expected TBB shared libraries
 
-  @fragile
   Scenario: Closing the Unsafe Browser shows a stop notification and properly tears down the chroot.
     Given I have started Tails from DVD and logged in and the network is connected
     When I successfully start the Unsafe Browser
@@ -33,7 +30,6 @@ Feature: Browsing the web using the Unsafe Browser
     Then I see the Unsafe Browser stop notification
     And the Unsafe Browser chroot is torn down
 
-  @fragile
   Scenario: Starting a second instance of the Unsafe Browser results in an error message being shown.
     Given I have started Tails from DVD and logged in and the network is connected
     When I successfully start the Unsafe Browser
@@ -48,13 +44,11 @@ Feature: Browsing the web using the Unsafe Browser
     Then I see "UnsafeBrowserTorCheckFail.png" after at most 60 seconds
     And the clearnet user has sent packets out to the Internet
 
-  @fragile
   Scenario: The Unsafe Browser cannot be configured to use Tor and other local proxies.
     Given I have started Tails from DVD and logged in and the network is connected
     When I successfully start the Unsafe Browser
     Then I cannot configure the Unsafe Browser to use any local proxies
 
-  @fragile
   Scenario: The Unsafe Browser will not make any connections to the Internet which are not user initiated
     Given I have started Tails from DVD and logged in and the network is connected
     And I capture all network traffic