This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards c78940caae8 127: onsuccess: #874: 1: Success after linux: 219 commits discards 42b6f276e66 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 25d2c123f32 125: onsuccess: #871: 1: Success after binutils: 26 commits discards e16c4ef842d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards e077798113f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 889eb29d76e 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards e04a67abc25 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards fd49875ed30 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 978bc65f9f6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 072a315cc81 118: onsuccess: #863: 1: Success after linux: 12 commits discards a8cb220109c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards bf75c75b9ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards fc1b7887f3a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 7d26b6e61ca 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards b3c2b362ddc 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards d5bd4134283 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards d8c9b2b4c3b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards e3abd4c985c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 6fb76649b5b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 09c2321e170 108: onsuccess: #850: 1: Success after gcc: 2 commits discards b1b07598e90 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 5f11150c41c 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards c71fe58bb37 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 4dcb286956e 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 14a4f2bbb92 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards a8682c5a159 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards 40a4062fe2e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards a67401ae33a 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 4663f61cea6 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards 62b32bdb4ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards f98fed18224 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 3d8b7421b24 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards d8e3c21b3c2 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 1dfb0abf36f 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b09522420b8 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards 7460f9963c3 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 2a22c8eef91 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 7899375cd2f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards b9ed9fc05d7 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards 03db7680074 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards d9b31eff9c5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards ad46bcde9e5 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards 2e90fd66f99 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards ecc947350e3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards f1a0d82bf2c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards c881198732c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 10d18ddce2a 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 0ef1b1d5ade 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards 3979b504663 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards d5b02d976d5 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards d39e795342b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards d5b1b3121a7 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 22a07cae717 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards bba04f6894c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 4d358b89ff1 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 19972588f36 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 99aba6cf153 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards 51354009fd4 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards eac752c3980 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 80d03ec5e43 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards 8e98a23eb69 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards bb516b7b590 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards 8ee563fb79b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 7f62bf100a8 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 1958d476c7a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 1f65f34ef78 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards a78185b2c2c 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards 682bbfaac20 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards edc7caf76cb 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards c43a579ee0f 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards 4a6b7ba74ce 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards d20f92b12e1 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards 673b8f7421f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards 126efc08504 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards 21e2be1d045 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards f83caf9e368 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards c610029bb65 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards 86759fa49ec 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 59d6fe3e22a 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 8a74e500a81 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 77689bcb17e 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 63e535b7ade 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards dd81c818b4f 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards 38a08e0d3ef 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards 705a007928e 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards c9f83c43ce3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 1974b3d8dcc 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 1d1bc7c6273 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 6c48b7b210a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards 42e468e0595 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards c25d2f1d3f0 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 566c883c642 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards ae35b99ed89 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 50e53702e42 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards b41643fcc09 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 29155f74282 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards 427ddcf6e29 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards aaff9ee077b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards 4782019acd2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards e2c09a4fe29 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards f5ef36d8ed7 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 6a3b54d4c5a 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new 65398d42d54 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 06cdf3c2453 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new 71b86a3a039 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 3fb18565df6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new f1b32e7954b 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new dfc0ad17ea0 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 754ba4c2214 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new bba25b6ac36 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 7f85919fd99 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new ae9bea16205 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 950ace9f8b3 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new a858443d5bb 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 57b6c1b4344 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new d0e02943341 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new a98b20dc7b9 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 4fa28a42aed 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 9bbb37cc20d 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new a38d2f14550 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 2abc71184f2 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 42efa61bd59 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 871992d41cf 48: onsuccess: #782: 1: Success after binutils: 8 commits new ad8d8b5eb67 49: onsuccess: #785: 1: Success after binutils: 12 commits new cde9fa6e6c2 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new 8e80b1be663 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new 298c3edba7d 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 7f293f9c940 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 940d3950d31 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new a145a7e0436 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new ae7eff1a29e 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 4546987c65d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new f8b8470d8fe 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new b25d0b42597 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 81e39e32b40 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new 93eaa6aaee6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 241d254e3d2 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 88391493e47 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 1bf3f2f1633 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new e850c5291aa 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new a2f00b86661 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 557879eace5 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 9a4dde9c134 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new 93120211d14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 8fccbbb9021 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new bcffd521e8a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 79467be59fc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new ca11acfb6e9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new 9f915a78c3c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 2d3087341ec 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new b8cc6ae8395 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new d81cef9c5a2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new fba1f34feb7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 05f88d72a0f 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new ff3d1640044 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new a6bbf118d7c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new 846a827a9bf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new 0d8d1a4b89e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new 4445a6499d4 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 090046e7ed3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new c9412b9c12b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new a601205f72d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 7671406cd2f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new e88ee6c0bee 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 6aa4c5a98c3 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 902351f8d53 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new b52c4498bf5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new f668fdb4791 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 2d4fbdcd9d3 94: onsuccess: #832: 1: Success after binutils: 5 commits new eecf69684be 95: onsuccess: #835: 1: Success after binutils: 3 commits new 95d4d60d0d1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new 3d5d20a2747 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 0a788a3479e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new cf07d2d2306 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new 750d69a394d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new f43497919da 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new deb534468a7 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new a89c7aaea91 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new cc5814dcc96 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new 6e51612a160 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 541cb8a7875 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new bacd61d48e0 107: onsuccess: #849: 1: Success after binutils: 5 commits new 1258c122dea 108: onsuccess: #850: 1: Success after gcc: 2 commits new 8fd51f3ec19 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 07db1483d29 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new ba82ab543e2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new c2e61198da3 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new 6295e1492ee 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 4a1ed264b71 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new 8cc641a53cd 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 67464f41eef 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 64ac98a4193 117: onsuccess: #861: 1: Success after binutils: 18 commits new ad9a2de0d66 118: onsuccess: #863: 1: Success after linux: 12 commits new b2c58b813ff 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 74a9870cbaa 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 68d1fa572d6 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new f3627707e26 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new fd2bf22aae7 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 4183cc380f9 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 1c426a74124 125: onsuccess: #871: 1: Success after binutils: 26 commits new 3af8cabf8b8 126: onsuccess: #873: 1: Success after glibc: 2 commits new a6ad1c1d36b 127: onsuccess: #874: 1: Success after linux: 219 commits new e013fd4b33c 128: onsuccess: #876: 1: Success after binutils: 12 commits

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (c78940caae8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39520 -> 41052 bytes 04-build_abe-gcc/console.log.xz | Bin 213816 -> 216744 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 8860 bytes 07-build_abe-glibc/console.log.xz | Bin 243872 -> 245808 bytes 08-build_abe-gdb/console.log.xz | Bin 39452 -> 40972 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3964 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2760 -> 2664 bytes 11-check_regression/console.log.xz | Bin 4788 -> 4872 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 3748832 -> 3762068 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3302024 -> 3316376 bytes sumfiles/gcc.sum | 4900 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1078432 -> 1080012 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232404 -> 233172 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 454056 -> 457880 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2616 insertions(+), 2616 deletions(-)