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 2c9c4d16d1 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 0c12b80ab4 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards b95c1c2a22 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 5c7be1cf12 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 9cb6755d8e 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards df96f15138 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards e3d4ac71d8 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 059eaab368 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 4101db7bcf 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards e412273c69 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 52e44e41cb 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 6bc663df0b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 2cf95525bb 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 3636a003b9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards be1eb62d5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 6c02710f90 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards bcb7055c3f 129: onsuccess: #878: 1: Success after linux: 3008 commits discards aac8d9ad06 128: onsuccess: #876: 1: Success after binutils: 12 commits discards bfa8d0418d 127: onsuccess: #874: 1: Success after linux: 219 commits discards d6b0ae661d 126: onsuccess: #873: 1: Success after glibc: 2 commits discards f0dd45f0be 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 80c0f23c2a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a7ebaa8438 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 263e4970ef 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 3ff7aa9298 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 0996a3d3cb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 3e89817dcd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards e92ff66b31 118: onsuccess: #863: 1: Success after linux: 12 commits discards 64df89c713 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 90a8b8f07b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards efa3a57d83 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 13ad58939f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 5de2315957 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 2b52751c5c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 2d959e7ee2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards b4476c07c8 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards ae4a97746a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 231484db07 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 5c054d1aef 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f3d4754fb9 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards a6736b940d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards d804ff6e95 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 5c16c55c20 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 5ee49c3c9f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 3a42d12ebc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 220cb39fde 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 3c31993f0b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 59c4d4b7e6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 6752875e5f 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards c58c454c12 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a1fe8fa987 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 9ccd402560 94: onsuccess: #832: 1: Success after binutils: 5 commits discards dcb61a1b66 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 5ac89d31b0 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 1013e3f96f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 129c240ef4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 2e240b9987 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards c5e1d3ba6f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 24c9c7f676 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 188a7cb994 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 441ea34f32 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 7f053e9b3b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 89b045c217 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards ce6e4355f2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards fea247141e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards bdcaab6899 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards fdbaa9877c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 1fa7ff82df 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 4865057772 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 774c2bb42c 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 04355755fc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards a17d506ee6 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 20bf82338c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 6710d3ec9e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards f55c9773c1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 94d5131c54 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 2a66fae41d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards e0fe7e7993 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 9800b9b0e8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards f330a326b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 8ac606e8cf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards e9a4754893 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards e8da32b884 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards d47cd57242 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards a22f828097 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 84476c4a37 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 4f7f1532b5 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards a9ba0ba87c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 615900261e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards ba7a260138 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 44145f1dd5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 77daa8b69b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards f1a3127921 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards e54479d540 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 0d751cd653 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards d4bb7a3984 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 7af707d007 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b0dac5b735 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 8adcf680e6 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards b2efff13e5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 191c2cc239 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new abc029c57a 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new bbfeb9a5c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 45f4c2565d 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 141c28d732 48: onsuccess: #782: 1: Success after binutils: 8 commits new 5dfff25fb3 49: onsuccess: #785: 1: Success after binutils: 12 commits new 5ae0193d0b 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 9f62af61a7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 443811ad5e 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 713e35bf27 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new db2d192fef 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 9689867ea0 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 6b592cbb01 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 637351a90e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 6a23996195 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new a4874be3ef 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 56465ddd61 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 2a4473f973 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f2acf57acc 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new c20f6d47e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new f4b9902077 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new c151828c8b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 4ed9467a92 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new a7f86f3cab 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 823149e278 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new db80bc7afc 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 95cb5298d7 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 312035b396 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 39808a8b17 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 40fcc78a46 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 688c4cffe9 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1ba63f6ec0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 1514bca4ef 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 03c49d11ca 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 846ca034ed 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new cca8dc2e1d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 93fd0e4fbe 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 7d1210e836 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new b8c7af95d5 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new f0d49e0240 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new cd149b4904 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 4895e0ae54 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5f8707f622 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new f6699d54ed 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 72b57f2c9d 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 704309e10c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new ed6405d99e 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 71a4e95274 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new c04245d0d7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e407d0f548 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 401771b0f9 94: onsuccess: #832: 1: Success after binutils: 5 commits new 82e89d5b48 95: onsuccess: #835: 1: Success after binutils: 3 commits new 89dae9367a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 04da78fdbb 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new d8cb2c76ff 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6ace2ef6a5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 87cfbb9378 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new eb76ecab13 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 34a99b987c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 8aab0cc648 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new e53ee4d694 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 94f129fa6a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new f1e18f9734 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new c8f0deaeac 107: onsuccess: #849: 1: Success after binutils: 5 commits new e0469c97b1 108: onsuccess: #850: 1: Success after gcc: 2 commits new 4f05080a10 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 56a504bf44 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new aefa149328 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new b222cb2e17 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new f01cb6bb18 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new e8da5fba3d 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new ed22399e8e 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 79264bcb2b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 4d0ae1a368 117: onsuccess: #861: 1: Success after binutils: 18 commits new 2c1c127364 118: onsuccess: #863: 1: Success after linux: 12 commits new 6470de4b03 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new a88327f2bb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new ef3c721c9e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new af35e28351 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 3ac8470477 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 9f570deb52 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 9009e2ac40 125: onsuccess: #871: 1: Success after binutils: 26 commits new 032049a9c8 126: onsuccess: #873: 1: Success after glibc: 2 commits new e3593de626 127: onsuccess: #874: 1: Success after linux: 219 commits new b2c87e5a65 128: onsuccess: #876: 1: Success after binutils: 12 commits new c4b6d247de 129: onsuccess: #878: 1: Success after linux: 3008 commits new d0b127fa27 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 026852d530 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 3542b8bac0 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 6474f46d92 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 81a775cb2d 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 3601de8892 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new b08677aa9b 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 6adef38786 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 468c961dcf 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 35f0742add 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 9ce926e7d4 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 0e0936a001 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new d3887ddafd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b8971d974b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 646d5203c7 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 76681ca08f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 636db8701a 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...]

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 (2c9c4d16d1) \ 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 1784 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39776 -> 40304 bytes 04-build_abe-gcc/console.log.xz | Bin 213616 -> 214628 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8380 -> 9220 bytes 07-build_abe-glibc/console.log.xz | Bin 245964 -> 244836 bytes 08-build_abe-gdb/console.log.xz | Bin 39408 -> 40072 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3892 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2480 -> 2876 bytes 11-check_regression/console.log.xz | Bin 5356 -> 6324 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3774208 -> 3762788 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 3305512 -> 3307468 bytes sumfiles/gcc.sum | 4957 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1073896 -> 1084536 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232224 -> 232204 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 457348 -> 466916 bytes sumfiles/libstdc++.sum | 10 +- 38 files changed, 2652 insertions(+), 2639 deletions(-)