rmaptest failure on google f1.micro

[Ian May]

Output from rmaptest failure.

12:33:40 INFO | Timer expired (900 sec.), nuking pid 2522
12:33:52 INFO | ERROR rmaptest rmaptest timestamp=1619354032 localtime=Apr 25 12:33:52 Unhandled AutoservRunError: Could not kill 2522
  None
  Traceback (most recent call last):
    File "/home/jenkins/autotest/client/job.py", line 510, in _runtest
      parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
    File "/home/jenkins/autotest/client/parallel.py", line 112, in fork_waitfor_timed
      utils.nuke_pid(pid)
    File "/home/jenkins/autotest/client/shared/utils.py", line 1214, in nuke_pid
      raise error.AutoservRunError('Could not kill %d' % pid, None)
  AutoservRunError: Could not kill 2522
  None

12:33:53 INFO | END ERROR rmaptest rmaptest timestamp=1619354033 localtime=Apr 25 12:33:53

[Ian May (ian-may)]

autotest job is currently set to timeout after 900 seconds. Confirmed on google f1.micro instance that extending the job timeout interval allows the rmaptest to finish correctly.

[Ian May (ian-may)]

bionic/linux-gke-5.4: 5.4.0-1043.45~18.04.1

[Ian May (ian-may)]

bionic/linux-gkeop-5.4: 5.4.0-1015.16~18.04.1

[Ian May (ian-may)]

xenial/linux-gcp: 4.15.0-1099.112~16.04.1

[Po-Hsu Lin (cypressyew)]

A quick test shows this would require > 22m on this instance with swap enabled.
With swap disabled, source code removed and rebooted, the next rerun takes 14m42s.

[Po-Hsu Lin (cypressyew)]

f1.micro is now just tested with boot tests.