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 77a393f38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 375724eb76 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 3e41c40e51 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 978d00d000 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 3c4bcacabc 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 112ace12b3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 839d381ef7 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 74297ec058 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards b30d62a1f9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards cacb58b1df 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 9c385c1025 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 006b8a3763 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 0fb0b1148a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 8729bb78a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards faa1da1510 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 4c87e70201 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 81023c14aa 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 6bc40fe449 127: onsuccess: #874: 1: Success after linux: 219 commits discards 657c50cfcc 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 835dd77589 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 47c1b23d33 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards c421e848fb 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 641a9d8151 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 97d336663c 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 2e394f9b39 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards fb41c51340 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 85fd1a565c 118: onsuccess: #863: 1: Success after linux: 12 commits discards 530eba5ce5 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 574c04f0b1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 7d3409d1ab 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 6f14db952c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 0401b9c15c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards fd0c431ead 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards d6ed9c2243 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 7b3ce70931 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards af304e8035 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards c71a7d355a 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 8f5c62498e 107: onsuccess: #849: 1: Success after binutils: 5 commits discards c48b7da249 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards d145dc8d4f 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 2ff6e6f6ab 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 985666ec4a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards aecfdbdc96 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 55a98a2798 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 52e95e95a8 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 94d02e6b04 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 568d9cdc57 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 96b0f5b851 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 06988a334f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 3ca9126fdd 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 026786b387 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 06df8271ed 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 5b4accfc6b 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards abc07571a3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 0f54c2e826 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 9d5c42b655 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 2400f643e0 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards b490c099f6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 76badb6424 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 36e0550617 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards cbfd8fd6fd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 8691904441 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 402f69e6ef 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 080ba6c4f6 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7e3881f187 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 7f59f761ac 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards dfac8582f1 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards d54a435ee4 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 3ec44caac0 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 333065644e 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 8683f57d9c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 04ff134229 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 5e267444ee 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 24ee31c89b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards ebb6b78f0c 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 80b074a62b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 268bbffdee 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 8f65c70663 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards aad3b641d6 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 5dd1ae1133 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f5eff59d75 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards df2ccd9da0 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 5327f1d355 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 10e94b81f1 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards f39f6a3c44 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards fba45f217b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 36a5002f8a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards fea32b80b9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 295774c30a 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 96526bfe65 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 6cd53f163a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 543cd79c6f 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards e1ccc60399 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 1292b09ed4 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 0415cf1c39 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 0b1b120554 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b31b100852 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 1adc18cce2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 74c31ad4d5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards d365b578f5 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 29d1b93781 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new da013c2b8c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 191c2cc239 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new b2efff13e5 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 8adcf680e6 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new b0dac5b735 48: onsuccess: #782: 1: Success after binutils: 8 commits new 7af707d007 49: onsuccess: #785: 1: Success after binutils: 12 commits new d4bb7a3984 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 0d751cd653 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new e54479d540 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new f1a3127921 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 77daa8b69b 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 44145f1dd5 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new ba7a260138 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 615900261e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new a9ba0ba87c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 4f7f1532b5 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 84476c4a37 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new a22f828097 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new d47cd57242 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new e8da32b884 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e9a4754893 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 8ac606e8cf 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new f330a326b9 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 9800b9b0e8 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new e0fe7e7993 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 2a66fae41d 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 94d5131c54 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new f55c9773c1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 6710d3ec9e 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 20bf82338c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new a17d506ee6 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 04355755fc 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 774c2bb42c 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 4865057772 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 1fa7ff82df 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new fdbaa9877c 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new bdcaab6899 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new fea247141e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new ce6e4355f2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 89b045c217 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 7f053e9b3b 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 441ea34f32 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 188a7cb994 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 24c9c7f676 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new c5e1d3ba6f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 2e240b9987 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 129c240ef4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 1013e3f96f 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5ac89d31b0 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new dcb61a1b66 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 9ccd402560 94: onsuccess: #832: 1: Success after binutils: 5 commits new a1fe8fa987 95: onsuccess: #835: 1: Success after binutils: 3 commits new c58c454c12 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 6752875e5f 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 59c4d4b7e6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 3c31993f0b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 220cb39fde 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 3a42d12ebc 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 5ee49c3c9f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 5c16c55c20 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d804ff6e95 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new a6736b940d 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new f3d4754fb9 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 5c054d1aef 107: onsuccess: #849: 1: Success after binutils: 5 commits new 231484db07 108: onsuccess: #850: 1: Success after gcc: 2 commits new ae4a97746a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new b4476c07c8 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 2d959e7ee2 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2b52751c5c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 5de2315957 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 13ad58939f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new efa3a57d83 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 90a8b8f07b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 64df89c713 117: onsuccess: #861: 1: Success after binutils: 18 commits new e92ff66b31 118: onsuccess: #863: 1: Success after linux: 12 commits new 3e89817dcd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 0996a3d3cb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 3ff7aa9298 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 263e4970ef 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new a7ebaa8438 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 80c0f23c2a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new f0dd45f0be 125: onsuccess: #871: 1: Success after binutils: 26 commits new d6b0ae661d 126: onsuccess: #873: 1: Success after glibc: 2 commits new bfa8d0418d 127: onsuccess: #874: 1: Success after linux: 219 commits new aac8d9ad06 128: onsuccess: #876: 1: Success after binutils: 12 commits new bcb7055c3f 129: onsuccess: #878: 1: Success after linux: 3008 commits new 6c02710f90 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new be1eb62d5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 3636a003b9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 2cf95525bb 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 6bc663df0b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 52e44e41cb 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new e412273c69 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 4101db7bcf 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 059eaab368 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new e3d4ac71d8 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new df96f15138 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 9cb6755d8e 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 5c7be1cf12 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new b95c1c2a22 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 0c12b80ab4 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 2c9c4d16d1 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 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 (77a393f38d) \ 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 1732 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39800 -> 39776 bytes 04-build_abe-gcc/console.log.xz | Bin 214496 -> 213616 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8380 bytes 07-build_abe-glibc/console.log.xz | Bin 244684 -> 245964 bytes 08-build_abe-gdb/console.log.xz | Bin 39348 -> 39408 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3892 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2424 -> 2480 bytes 11-check_regression/console.log.xz | Bin 5656 -> 5356 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 18 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 3731524 -> 3774208 bytes sumfiles/g++.sum | 110 +- sumfiles/gcc.log.xz | Bin 3291524 -> 3305512 bytes sumfiles/gcc.sum | 4456 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1079284 -> 1073896 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232132 -> 232224 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 456444 -> 457348 bytes sumfiles/libstdc++.sum | 10 +- 36 files changed, 2378 insertions(+), 2386 deletions(-)