Travis: remove status functionality

[0xc0170]

Summary of changes

Unfortunately, we need to remove status functionality as it exposes an information
it should rather not. There is no other way we can do it in the pull request coming
from forks (most of our PRs are from forks). It is better if we use pass/failure what
Travis provides. The information are in the logs. It should always print the status info at
the very end. A test should have "echo Failed with a reason...."

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@0xc0170, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

I'll run some checks (astyle failures ,etc to see how it goes with the regular status updates).

[0xc0170]

To make this PR green , I would need to remove "required status checks for travis-ci/*". The Travis provides a report for each job: https://travis-ci.org/github/ARMmbed/mbed-os/builds/727646560 - this should be sufficient to review after the failure.

@ARMmbed/mbed-os-test @ARMmbed/mbed-os-maintainers Please review

[mergify]

This PR cannot be merged due to conflicts. Please rebase to resolve them.

[0xc0170]

Rebased, testing now 2 new commits if this works as expected after the recent change to travis.

[0xc0170]

I pushed an update, to fix OK license status for Travis.

[0xc0170]

@harmut01 if I do not manage to get this green, could you take over to fix the license check and remove statuses from PRs ?

[0xc0170]

Travis green, looks like it is working now. However all Expected in travis should be removed from Github required statuses

@jamesbeyond @adbridge Please review

[adbridge]

@0xc0170 how will we know going forward if a PR has failed travis checks if they are not 'required' ?

[adbridge]

Looks good to me as far as I can tell

[jamesbeyond]

This looks good to me, though I am very familiar with the TravisCI side of code,

[0xc0170]

@0xc0170 how will we know going forward if a PR has failed travis checks if they are not 'required' ?

There is one main Travis check - if you click , it will show you the matrix of jobs. So basically the same just one more click away, no test coverage loosing. Just this is the way it is supported by Travis

[0xc0170]

CI started

[0xc0170]

The required statuses cleaned - so pr head and travis only