server/web2py/applications/vidjil/tests/functional/: add close_everything

Unfortunately Ryan did a nice job not to prevent this. But our test
architecture is probably slightly underoptimal and the close_everything
was called many times with ObjectSpace.define_finalizer (once by test)
which is not possible anymore when printing the console
20 jobs for feature-sc/refactor-browser-test in 4841 minutes and 8 seconds (queued for 8 minutes and 7 seconds)
latest
Status Job ID Name Coverage
  Test Tools
passed #576765
test_tools

00:00:10

 
  Test Quality
passed #576766
web
code_quality

00:00:10

 
  Test Unit
passed #576767
web
test_browser_unit

00:00:44

passed #576768
web
test_server_unit

00:00:16

 
  Deploy Review
passed #576769
web
deploy_review

00:00:15

manual #576770
web allowed to fail manual
stop_deploy_review
 
  Test Functional
failed #577043
web
chrome-browser-functional

06:05:00

passed #576771
web
ff32-browser-functional

00:02:36

passed #576775
docker x86_64
ff32-server-functional

00:04:59

passed #576772
web
ff45-browser-functional

00:03:08

passed #576776
docker x86_64
ff45-server-functional

00:05:08

failed #577068
legacy
old-chrome-browser-functional

78:26:19

failed #576980
web
chrome-browser-functional

06:05:00

failed #576773
web
chrome-browser-functional

06:05:00

failed #576923
legacy
old-chrome-browser-functional

11:26:49

failed #576774
legacy
old-chrome-browser-functional

02:32:28

 
  Test Functional External
skipped #576779
web
chrome-browser-functional-external
skipped #576777
web
ff32-browser-functional-external
skipped #576778
web
ff45-browser-functional-external
skipped #576780
legacy
old-chrome-browser-functional-external-chrome
 
Name Stage Failure
failed
old-chrome-browser-functional Test Functional The script exceeded the maximum execution time set for the job
	from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:360:in `on_signal'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:347:in `with_info_handler'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:319:in `run'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:159:in `block in __run'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:159:in `map'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:159:in `__run'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:136:in `run'
from /usr/local/rvm/gems/ruby-2.6.1/gems/minitest-5.11.3/lib/minitest.rb:63:in `block in autorun'
ERROR: Job failed: execution took longer than 6h0m0s seconds
failed
chrome-browser-functional Test Functional The script exceeded the maximum execution time set for the job
Testing Vidjil client at file:///home/gitlab-runner/builds/b8d876c1/0/vidjil/vidjil/browser/index.html
Vidjil client loaded, launching tests.
Welcome popup.
Import data.
data: /home/gitlab-runner/builds/b8d876c1/0/vidjil/vidjil/doc/analysis-example1.vidjil
......
Tests finished, closing browser.
WARNING: Timed out waiting for the build to finish
ERROR: Job failed: execution took longer than 6h0m0s seconds