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 6adabf09cb 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 2288a48c3d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 5f3cb4e778 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 6a1162183c 152: onsuccess: #903: 1: Success after linux: 22 commits discards ab7bfb352c 151: onsuccess: #902: 1: Success after glibc: 8 commits discards e76421e8e3 150: onsuccess: #900: 1: Success after gcc: 11 commits discards ef8314b80c 149: onsuccess: #899: 1: Success after binutils: 15 commits discards da121a2647 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards ec20a406b7 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 477e5135a8 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 5b3fd27054 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 40f826cd20 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 222c543e44 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 4f992efe13 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 9a3f12c899 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards c94a0e0112 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards f47d4042f3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 2c2b7730be 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 8cb535fd9a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards cf16e68d19 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards f0c08328f7 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards e18beedba4 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 7702bdafcc 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 3c5098b250 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 524d4dd8e2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 0a031183ac 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 8821eba090 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 564d239f17 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 42e9a9de29 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2d6a824fac 126: onsuccess: #873: 1: Success after glibc: 2 commits discards eed166df02 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 802dae1812 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards af072bd0d5 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards cabacf769b 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards ddc880d467 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 228ae554c6 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 8866a9c270 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 2eda4e2b40 118: onsuccess: #863: 1: Success after linux: 12 commits discards 739e4bd187 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 1cb318825c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 29e8dadab6 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 6a6f3b4c13 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards d9fd6d591a 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 088153d542 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 7b6a1ac23a 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 225b7cb36e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 1293d90f30 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards df8af22053 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c62d023968 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f7c2bc4ce1 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards e4d2f71878 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 4b4421b6a3 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 0922e7064f 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 6fd11237c4 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 68b2ac51b7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 71b8f6c4d8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards f19d0c96d8 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 0eb4e456ce 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 0246924484 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 6355ac14b2 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 3807e5daca 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b76d0963e3 94: onsuccess: #832: 1: Success after binutils: 5 commits discards d1bcd771e5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 2083cff53e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 605fb1aed2 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 84c956c38d 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards c6037df6e7 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards ff981b9826 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 9e5fafc7fe 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 959a049681 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 15dfc81180 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards bb73e63c6b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1d342f5b44 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 45af30fa24 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 495f31ac71 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards bc286286ed 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards a2bbf72db2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards c32ab7468b 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards b466d90399 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 90c1315b40 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 3f9807d083 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards e930031b70 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 5eb8ca301c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards d81c563cae 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 943f48a3ce 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 2ebd48a56a 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards dd5b45c796 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards dde9fdccc2 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 118e45edda 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 9424dcbc2b 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 8b88e02f0a 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 9b4dd4e064 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards f8949c6dcf 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 595abe1d9e 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 1704373c47 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 32e464f810 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 326a48d09b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 6408fd3e98 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards f2ddd013e6 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards acc47fd1be 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 153e8354d6 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 644b2d4e64 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 9f96a0831d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 5413bfb9ea 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 0c85fc073c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new b5922255be 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 7389c0530e 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 006527a8d6 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new 5cc07f7100 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 6e1f2a63ca 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 5c3ba23804 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 3e23681216 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 933661b3b2 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 65de296a9c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 0cb5b02558 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 0dc992cf7c 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 0e3380db76 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 62e9e35e3a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 60944cc5e6 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 7d1fe886ae 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new e45b8e3bca 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new e6569651a1 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new afe7ec4427 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 5c08f15f6e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 9a47abcd8e 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 9fe15b3d11 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 330cb62b24 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 769583d737 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new ee57bc5fbd 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 88dc01f8fe 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 7c68edaf24 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new ccb3bf5d40 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new acbd376554 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 0da740e194 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 2939a743d2 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 2a6d38b56b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 0a6769cadc 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e78225b4d2 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 225d29cef5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 5fafb32ee9 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new f4145be1e3 94: onsuccess: #832: 1: Success after binutils: 5 commits new 7b0b02de30 95: onsuccess: #835: 1: Success after binutils: 3 commits new ab48f6137a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 0b6403f8e6 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 274d0889de 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 05c84a05c5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new f89d2f56df 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new cc5db5feaf 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 699c0f446e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 28b2fd7773 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 8e2eafe16c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 4f4adfd63f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 8062bb4c4e 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 07494b5e97 107: onsuccess: #849: 1: Success after binutils: 5 commits new afe77c41f0 108: onsuccess: #850: 1: Success after gcc: 2 commits new aac77a0aca 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 485eef0705 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 276af47374 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new aaae09ef54 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 8c2ab01237 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 08fc991b56 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new cdba276800 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 2e96964f3f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 2959f86fde 117: onsuccess: #861: 1: Success after binutils: 18 commits new f523a4aad4 118: onsuccess: #863: 1: Success after linux: 12 commits new a77b80310a 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 0170a8b825 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new c256a199c0 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new f804520224 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 865e79d66d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 5493c11cbe 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 6841159378 125: onsuccess: #871: 1: Success after binutils: 26 commits new b33d2539ca 126: onsuccess: #873: 1: Success after glibc: 2 commits new 92d125be01 127: onsuccess: #874: 1: Success after linux: 219 commits new dfda2ae2ff 128: onsuccess: #876: 1: Success after binutils: 12 commits new ed69ac1d38 129: onsuccess: #878: 1: Success after linux: 3008 commits new fa8d45e210 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new eef7c496cd 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new d0d8eed43a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new d50d77a17b 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new f975877472 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new a5f33c4d17 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 49d2f35bda 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 0a2270919a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new d79af2b588 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 78ce46402c 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new a8a337cf52 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new a518442c53 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new e83a83ac92 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 2d9ce5d12b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new f9910dff24 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 24a1489791 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 528dd771e2 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 616d028efb 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 1a1e091916 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new eedc0045f7 149: onsuccess: #899: 1: Success after binutils: 15 commits new ec2c249511 150: onsuccess: #900: 1: Success after gcc: 11 commits new 1f0ff8c0bf 151: onsuccess: #902: 1: Success after glibc: 8 commits new aaa2f2dd46 152: onsuccess: #903: 1: Success after linux: 22 commits new 3edc82b68f 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 80382bbcfa 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 4a01b2a508 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 233d1f98bc 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...]
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 (6adabf09cb) \ 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 1748 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40484 -> 40184 bytes 04-build_abe-gcc/console.log.xz | Bin 216212 -> 213896 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8972 -> 8448 bytes 07-build_abe-glibc/console.log.xz | Bin 245164 -> 244740 bytes 08-build_abe-gdb/console.log.xz | Bin 40044 -> 40192 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2572 bytes 11-check_regression/console.log.xz | Bin 7160 -> 7416 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 127 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 - sumfiles/g++.log.xz | Bin 3738244 -> 3736688 bytes sumfiles/g++.sum | 146 +- sumfiles/gcc.log.xz | Bin 3323176 -> 3333804 bytes sumfiles/gcc.sum | 4417 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1083084 -> 1082620 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232292 -> 232248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 461692 -> 446620 bytes sumfiles/libstdc++.sum | 13 +- 42 files changed, 2525 insertions(+), 2498 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions