ci: Test install kata-runtime in "No GO command or GOPATH not set" mode

[teawater]

Add a test to install kata-runtime in "No GO command or GOPATH not set" mode.

Fixes: #1233

Signed-off-by: Hui Zhu [email protected]

[teawater]

/test

[jodh-intel]

GOPATH is set on line 91 and you're using sudo -E so isn't GOPATH set here?

[teawater]

I think it found the issue of "GOPATH not set mode".
I need to fix it in runtime first.
kata-containers/runtime#1286

[jodh-intel]

I still don't understand this - GOPATH is set here so how can it be "No GO command or GOPATH not set mode" ?

[teawater]

@jodh-intel This part use:

sudo -E KATA_RUNTIME="${KATA_RUNTIME}" make install

without

PATH="$PATH"

Then no go command can work.

[jodh-intel]

Doh! I always read -E as "export the entire env" rather than "export the vars you give me" 😄

[teawater]

/test

[teawater]

/test

[teawater]

jenkins-metrics-ubuntu-16-04 failed:

Report Summary:
+-----+----------------------+-------+-------+--------+-------+-------+--------+-------+------+-----+
| P/F |         NAME         |  FLR  | MEAN  |  CEIL  |  GAP  |  MIN  |  MAX   |  RNG  | COV  | ITS |
+-----+----------------------+-------+-------+--------+-------+-------+--------+-------+------+-----+
| P   | boot-times           | 95.0% | 99.7% | 105.0% | 10.0% | 92.5% | 104.8% | 13.4% | 3.6% |  20 |
| *F* | memory-footprint     | 95.0% | 92.9% | 105.0% | 10.0% | 92.9% | 92.9%  | 0.0%  | 0.0% |   1 |
| *F* | memory-footprint-ksm | 95.0% | 69.5% | 105.0% | 10.0% | 69.5% | 69.5%  | 0.0%  | 0.0% |   1 |
+-----+----------------------+-------+-------+--------+-------+-------+--------+-------+------+-----+
Fails: 2, Passes 1
Failed
checkmetrics FAILED (1)
restoring KSM settings
Build step 'Execute shell' marked build as failure

This pr doesn't change the default behavior of kata-runtime.
So I think this pr does not relate to this fail.

[grahamwhaley]

Hi @teawater - I 'adjusted' the metrics CI yesterday, so hopefully it is more stable. I have nudged a rebuild of that job, but indeed, this PR should not affect metrics.

[grahamwhaley]

@jodh-intel @devimc - pls re-review