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 7b50105aa6f 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 4b64be3b71c 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 549b5c0442a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 08f0604d2e0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards eca6e580fe2 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 22ddbecda30 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards a13aa8828e5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards ee255d5c9bb 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 709669aeb16 118: onsuccess: #863: 1: Success after linux: 12 commits discards 98505b3bdfa 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 573759605ef 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 3d421bd2deb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 044ff0f3194 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 2bb57884697 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 9b2b8cb3416 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 22f629c991e 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 240b2756c64 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 0b7f625bd54 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards c932bea0022 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 57a7208cfbc 107: onsuccess: #849: 1: Success after binutils: 5 commits discards feb647ef96f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] discards b4db12a0e42 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] discards 50bb3b353b8 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] discards 79ff81d57c2 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] discards 65e27f03c04 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] discards bae0ca9a380 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] discards 9a0a0572201 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] discards 808cdfe26e2 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] discards dac443bb21b 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] discards aee332345f3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] discards 04eff527652 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] discards 1892aa053cf 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 9215b66d08a 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 9fa06547220 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] discards e93d92dea15 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] discards 4db90aecaad 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] discards 2e94d067ac4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] discards 99c13d66d92 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] discards d3c344bb1ea 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] discards 470a52d55e1 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] discards b91c943f38e 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] discards b85a2293935 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] discards 86facfabb21 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] discards c08f5fa222e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] discards af63c6a1ea7 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] discards 536d9e406cb 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] discards 0c02d1ed2ee 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] discards d84cbcb4b06 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] discards 5d3e98bc2ee 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] discards fcbb79769fe 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] discards dfd2ceb40c9 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] discards 0de8c805dcf 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] discards 5f43bd78d81 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] discards 6f6cdad7569 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] discards 88feb218869 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] discards 2012689e515 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] discards d3cfa337df9 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] discards d30af7aed73 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] discards 7ccf8cc46d0 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] discards b2296fdef10 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] discards 946fbe5aabb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] discards fa7004690ba 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] discards 4881947f9fa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] discards 8ef5f6cba39 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] discards 0550464486e 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] discards 0bc17309257 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] discards f49bd65ae6a 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] discards 6040d526d06 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] discards 74d0d5f7573 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] discards a3d9d1b4b0f 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] discards a3084d4fee0 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] discards d7eab650ba3 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] discards e909bd25943 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] discards cac39176f11 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] discards c80df5222f2 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] discards 44c381592cd 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] discards b9d9946af5c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] discards 634c2d9b95d 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 3efd68200eb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 7c79d7400fc 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] discards 71a16499d9f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] discards e0b8f497d05 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] discards a23b7087aec 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] discards ea86f2ebc35 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] discards 1ec990d0845 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] discards 765b47c591a 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] discards 6c5fa26d2f4 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] discards 35b0d057fc3 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] discards d20bb2f3706 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] discards 936a17f01b9 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] discards 85ca7b4710a 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits discards f5e5e116e70 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] discards 1c2bf9098a2 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] discards bcbb0305aa8 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] discards 6d23ac6bfdf 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] discards de8cd4517d6 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] discards 0a2b474e3a9 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] discards f1bcf0f2077 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] discards e1d0303f6a6 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] discards a52c5f6f511 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] discards 37fc2f8c114 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new 9d4eab034c1 26: onsuccess: #759: 1: Success after binutils/gcc/linux/gl [...] new f5ef36d8ed7 27: onsuccess: #760: 1: Success after binutils/gcc/linux/gl [...] new e2c09a4fe29 28: onsuccess: #761: 1: Success after binutils/gcc/linux/gd [...] new 4782019acd2 29: onsuccess: #762: 1: Success after binutils/gcc/linux/gl [...] new aaff9ee077b 30: onsuccess: #763: 1: Success after binutils/gcc/linux/gl [...] new 427ddcf6e29 31: onsuccess: #764: 1: Success after binutils/gcc/linux/gd [...] new 29155f74282 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/gd [...] new b41643fcc09 33: onsuccess: #766: 1: Success after binutils/gcc/linux/gd [...] new 50e53702e42 34: onsuccess: #767: 1: Success after binutils/gcc/linux/gl [...] new ae35b99ed89 35: onsuccess: #768: 1: Success after binutils/gcc/linux/gl [...] new 566c883c642 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 commits new c25d2f1d3f0 37: onsuccess: #770: 1: Success after binutils/gcc/linux/gl [...] new 42e468e0595 38: onsuccess: #771: 1: Success after binutils/gcc/linux/gl [...] new 6c48b7b210a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/gl [...] new 1d1bc7c6273 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gl [...] new 1974b3d8dcc 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gl [...] new c9f83c43ce3 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gl [...] new 705a007928e 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gd [...] new 38a08e0d3ef 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gl [...] new dd81c818b4f 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gd [...] new 63e535b7ade 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gd [...] new 77689bcb17e 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gl [...] new 8a74e500a81 48: onsuccess: #782: 1: Success after binutils: 8 commits new 59d6fe3e22a 49: onsuccess: #785: 1: Success after binutils: 12 commits new 86759fa49ec 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gl [...] new c610029bb65 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gl [...] new f83caf9e368 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gl [...] new 21e2be1d045 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gl [...] new 126efc08504 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gl [...] new 673b8f7421f 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gl [...] new d20f92b12e1 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gl [...] new 4a6b7ba74ce 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gl [...] new c43a579ee0f 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gd [...] new edc7caf76cb 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gl [...] new 682bbfaac20 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gd [...] new a78185b2c2c 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gl [...] new 1f65f34ef78 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gd [...] new 1958d476c7a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gl [...] new 7f62bf100a8 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gl [...] new 8ee563fb79b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gl [...] new bb516b7b590 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gl [...] new 8e98a23eb69 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gd [...] new 80d03ec5e43 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gl [...] new eac752c3980 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gl [...] new 51354009fd4 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gl [...] new 99aba6cf153 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gd [...] new 19972588f36 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gl [...] new 4d358b89ff1 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gd [...] new bba04f6894c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gd [...] new 22a07cae717 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gl [...] new d5b1b3121a7 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gl [...] new d39e795342b 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gl [...] new d5b02d976d5 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gl [...] new 3979b504663 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gl [...] new 0ef1b1d5ade 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gl [...] new 10d18ddce2a 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gd [...] new c881198732c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gl [...] new f1a0d82bf2c 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gl [...] new ecc947350e3 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gl [...] new 2e90fd66f99 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gl [...] new ad46bcde9e5 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gl [...] new d9b31eff9c5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gl [...] new 03db7680074 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gd [...] new b9ed9fc05d7 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gl [...] new 7899375cd2f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gl [...] new 2a22c8eef91 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gl [...] new 7460f9963c3 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gl [...] new b09522420b8 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gd [...] new 1dfb0abf36f 94: onsuccess: #832: 1: Success after binutils: 5 commits new d8e3c21b3c2 95: onsuccess: #835: 1: Success after binutils: 3 commits new 3d8b7421b24 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gl [...] new f98fed18224 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gd [...] new 62b32bdb4ed 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gl [...] new 4663f61cea6 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gd [...] new a67401ae33a 100: onsuccess: #841: 1: Success after binutils/gcc/linux/g [...] new 40a4062fe2e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/g [...] new a8682c5a159 102: onsuccess: #843: 1: Success after binutils/gcc/linux/g [...] new 14a4f2bbb92 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 [...] new 4dcb286956e 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 [...] new c71fe58bb37 105: onsuccess: #846: 1: Success after binutils/gcc/linux/g [...] new 5f11150c41c 106: onsuccess: #847: 1: Success after binutils/gcc/linux/g [...] new b1b07598e90 107: onsuccess: #849: 1: Success after binutils: 5 commits new 09c2321e170 108: onsuccess: #850: 1: Success after gcc: 2 commits new 6fb76649b5b 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new e3abd4c985c 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new d8c9b2b4c3b 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new d5bd4134283 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new b3c2b362ddc 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new 7d26b6e61ca 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new fc1b7887f3a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new bf75c75b9ab 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new a8cb220109c 117: onsuccess: #861: 1: Success after binutils: 18 commits new 072a315cc81 118: onsuccess: #863: 1: Success after linux: 12 commits new 978bc65f9f6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new fd49875ed30 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new e04a67abc25 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 889eb29d76e 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new e077798113f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new e16c4ef842d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 25d2c123f32 125: onsuccess: #871: 1: Success after binutils: 26 commits new 42b6f276e66 126: onsuccess: #873: 1: Success after glibc: 2 commits new c78940caae8 127: onsuccess: #874: 1: Success after linux: 219 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 (7b50105aa6f) \ 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 1796 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39564 -> 39520 bytes 04-build_abe-gcc/console.log.xz | Bin 213256 -> 213816 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8856 -> 8784 bytes 07-build_abe-glibc/console.log.xz | Bin 243240 -> 243872 bytes 08-build_abe-gdb/console.log.xz | Bin 39372 -> 39452 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2684 -> 2760 bytes 11-check_regression/console.log.xz | Bin 4608 -> 4788 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 3770740 -> 3748832 bytes sumfiles/g++.sum | 110 +- sumfiles/gcc.log.xz | Bin 3303912 -> 3302024 bytes sumfiles/gcc.sum | 5008 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1079188 -> 1078432 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233064 -> 232404 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455572 -> 454056 bytes sumfiles/libstdc++.sum | 10 +- 34 files changed, 2644 insertions(+), 2644 deletions(-)