Clarify the UX of merge requests

Summary

After the latest update, this is what I saw:

I believe that the message here is not clear and actually contradictory. In previous versions of this UX component, the green mark would signal that this MR builds successfully. Right now I feel confused - if the build failed, why is the tick green? Does that mean anything that the button is red?

What is the expected correct behavior?

Make it more intuitive to read this part of the MR view. Perhaps some visual clues could make it easier to understand?

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:         Debian 8.9
Current User:   git
Using RVM:      no
Ruby Version:   2.3.3p222
Gem Version:    2.6.6
Bundler Version:1.13.7
Rake Version:   12.0.0
Redis Version:  3.2.5
Git Version:    2.13.5
Sidekiq Version:5.0.4
Go Version:     unknown
GitLab information
Version:        9.5.1
Revision:       c47ae37
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            https://gitlab.profound.net
HTTP Clone URL: https://gitlab.profound.net/some-group/some-project.git
SSH Clone URL:  ssh://git@gitlab.profound.net:1027/some-group/some-project.git
Using LDAP:     no
Using Omniauth: no
GitLab Shell
Version:        5.8.0
Repository storage paths:

• default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git