Fix oc status unit test

[0xmichalis]

@deads2k unit tests are broken w/o this.

[merge]

Fixes #6423

[liggitt]

Hold on, how did a breaking change make it into master without this?

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4429/) (Image: devenv-rhel7_3001)

[openshift-bot]

Evaluated for origin merge up to 1890ab0

[openshift-bot]

[Test]ing while waiting on the merge queue

[0xmichalis]

Hold on, how did a breaking change make it into master without this?

If we don't provide a fixed time, then every time these tests run, they are using time.Now() as the current time and times in oc status ("#8 build running for 2 days") will vary (note that test fixtures are using timestamps). We merged #6379 yesterday and the test was using "hours" but now the difference makes up to "days" :)

[openshift-bot]

Evaluated for origin test up to 1890ab0

[liggitt]

Ah, makes sense

[liggitt]

Though aren't the creation time stamps in the fixture ignored and overwritten at create time?

[0xmichalis]

Though aren't the creation time stamps in the fixture ignored and overwritten at create time?

I am not sure this is supposed to happen when adding resources from paths.

[liggitt]

Ah, fixture loader, not live API requests. Carry on :)

[openshift-bot]

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/8012/)