|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
hmmm.. interesting, we have tens projects (multi-configuration projects) and mail sent from master always look like this:
hpc-ompi-shmem - Build # 2217 - Still Failing:
Git:
origin/master 368c6bb3261e77d1c12f473ed692ca21bf28c7d3
Check console output at http://hpc-master.lab.mtl.com:8080/job/hpc-ompi-shmem/2217/ to view the results.
Build log:
...
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building on master in workspace /scrap/jenkins/workspace/hpc-ompi-shmem-2
Deleting project workspace... done
Checkout:hpc-ompi-shmem-2 / /scrap/jenkins/workspace/hpc-ompi-shmem-2 - hudson.remoting.LocalChannel@7fd2c81d
Using strategy: Default
Last Built Revision: Revision 9fe0dd82ba28da9e918d0c8495c42d04dac628ac (origin/master, origin/HEAD) Cloning the remote Git repository Cloning repository http://bgate.mellanox.com:8080/git/ompi-vendor.git
git --version
git version 1.8.4.3
Fetching upstream changes from origin
Seen branch in repository origin/HEAD
Seen branch in repository origin/master
Seen branch in repository origin/mellanox-master Seen branch in repository origin/mellanox-shmem-from-v1.6 Seen branch in repository origin/mellanox-test_branch Seen branch in repository origin/mellanox-v1.6 Seen branch in repository origin/mellanox-v1.7 Seen branch in repository origin/ompi-hcoll-datatype Seen branch in repository origin/test_branch Seen branch in repository origin/v1.6 Seen branch in repository origin/v1.7 Seen 11 remote branches Multiple candidate revisions Scheduling another build to catch up with hpc-ompi-shmem Commencing build of Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Checking out Revision 368c6bb3261e77d1c12f473ed692ca21bf28c7d3 (origin/master, origin/HEAD) Warning : There are multiple branch changesets here No emails were triggered.
Triggering r-vmb-rhel6-u3-x86-64
Triggering r-vmb-fedora14-x86-64
Triggering r-vmb-rhel5-u10-x86-64
Triggering r-vmb-rhel6-u2-x86-64
Triggering r-vmb-rhel6-u4-x86-64
Triggering hpc-test-node
Triggering r-vmb-sles11-sp3-x86-64
Triggering r-vmb-rhel5-u9-x86-64
Triggering r-vmb-centos5-u7-x86-64
Triggering r-vmb-sles11-sp1-x86-64
Triggering r-vmb-fedora16-x86-64
Triggering r-vmb-fedora17-x86-64
Triggering r-vmb-rhel5-u8-x86-64
Triggering r-vmb-ubuntu13-u10-x86-64
Triggering r-vmb-rhel7-u0-beta-x86-64
Triggering r-vmb-rhel6-u5-x86-64
Triggering r-vmb-sles11-sp2-x86-64
Triggering r-vmb-ole6-u2-x86-64
Triggering r-vmb-centos6-u0-x86-64
Triggering r-vmb-rhel6-u1-x86-64
Triggering r-vmb-ubuntu12-u4-x86-64
Triggering r-vmb-sles11-sp0-x86-64
r-vmb-rhel6-u3-x86-64 completed with result SUCCESS
r-vmb-fedora14-x86-64 completed with result SUCCESS
r-vmb-rhel5-u10-x86-64 completed with result SUCCESS
r-vmb-rhel6-u2-x86-64 completed with result SUCCESS
r-vmb-rhel6-u4-x86-64 completed with result SUCCESS
hpc-test-node completed with result FAILURE
r-vmb-sles11-sp3-x86-64 completed with result SUCCESS
r-vmb-rhel5-u9-x86-64 completed with result SUCCESS
r-vmb-centos5-u7-x86-64 completed with result SUCCESS
r-vmb-sles11-sp1-x86-64 completed with result SUCCESS
r-vmb-fedora16-x86-64 completed with result SUCCESS
r-vmb-fedora17-x86-64 completed with result SUCCESS
r-vmb-rhel5-u8-x86-64 completed with result SUCCESS
r-vmb-ubuntu13-u10-x86-64 completed with result SUCCESS
r-vmb-rhel7-u0-beta-x86-64 completed with result SUCCESS
r-vmb-rhel6-u5-x86-64 completed with result SUCCESS
r-vmb-sles11-sp2-x86-64 completed with result SUCCESS
r-vmb-ole6-u2-x86-64 completed with result SUCCESS
r-vmb-centos6-u0-x86-64 completed with result SUCCESS
r-vmb-rhel6-u1-x86-64 completed with result SUCCESS
r-vmb-ubuntu12-u4-x86-64 completed with result SUCCESS
r-vmb-sles11-sp0-x86-64 completed with result SUCCESS
Email was triggered for: Failure
Sending email for trigger: Failure