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 bf5dcf9043 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 2766842fec 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards c8ac036bc7 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards e44e2011b5 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards fb6ec00a01 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 71820db460 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 0e17abd74d 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 742819081f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 98c4e220b0 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 46d402c40b 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 760bd64853 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards a6953be439 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 6461da999c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 90f0d527db 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards d1366813c7 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards edd84a18fb 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 1af31462f2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards b9c5270aa2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 2eac5cf7fb 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 7baab2d4b4 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards b95e52194a 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 302f647190 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 7c2d6e6ea1 127: onsuccess: #874: 1: Success after linux: 219 commits discards 3d48e479c0 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 485b5d2486 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 6344926b55 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 98ef063e28 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards b140ab14d4 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 74f55e0c00 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 93b522f795 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards c9c9be6c54 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 1988b1dbfa 118: onsuccess: #863: 1: Success after linux: 12 commits discards 945ffc0d8c 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 86e43816c1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards c074fe0a0a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 2e3f085c16 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 2ce66c100b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 779b573a0f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards e8cd0687bb 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 560a06e08e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 4248a48759 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 4b7c8b6dae 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 62c640edc9 107: onsuccess: #849: 1: Success after binutils: 5 commits discards cd077feb4f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 699490b0ce 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 65b7608e09 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3fe71fd479 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards d42d481d35 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 8c4fefa1bf 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards eb26df0773 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 9138212945 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 698d6ff57d 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 6ed94030f2 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 15c929fa71 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards ead04ecf2a 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 027d66e869 94: onsuccess: #832: 1: Success after binutils: 5 commits discards a36339d83a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards b99047122f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 170838f521 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 2069146c4e 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 20ad9c859f 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 8456b6f054 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 87a1b4a283 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards e441002d7a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards e41a91071e 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 99ae8e0834 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 1a1f7e3428 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b6d7ce7979 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 0b5b0ad8d0 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0a081f82c7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 1f3eeb4f02 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 79b19b0b68 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards b313d4a2b0 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 64a3f31096 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 149ca9fd50 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards b44072dc8e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards f172255606 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 7b7c240958 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards da2219396a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 1ab3d6febb 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 1225c5f116 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 7b74eee3bb 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 6dfbc90ef4 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 457eba1391 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 6bcd8b52c3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f9f1fb4dc7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 8febdb9595 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards ec235b2750 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 4c3e777a07 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 33c496fcd5 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 3f8d2930d4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 5b9a90c910 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 01fea97be1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 2d05da0641 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 1300ec82be 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 8b30c3ceaf 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards baa1102ca6 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards ce63c4dae8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards fb468ed4be 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 9b23c7efa6 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 0aae0cf040 49: onsuccess: #785: 1: Success after binutils: 12 commits new 18eb09e5ff 49: onsuccess: #785: 1: Success after binutils: 12 commits new e1bbdbddc8 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 9aa984c72b 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 7386146e73 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new f0dfafef7d 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new ee0ff2b2f2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new b0e01cc3de 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new a923504272 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 87da58a11d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 2b5331f032 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new fc51528e8e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 358fdf1358 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 8701e42ccc 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f018bca34f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 43582277c9 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 131a39566e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 786a87e579 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 947e1d4b6a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 81e5f30bfb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new fcaae8480e 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 003445b4e8 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new b207af2f44 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 97af540a63 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 9b12957c31 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 9978272aa9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 22ed462eef 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new feaa908c56 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new bf8fd28b3b 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 53247a0a59 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 748b2b9349 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new f3c433d8b6 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 3b5f477da1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 2b76c4239e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new c9ec982ecf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 3c0ca24030 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 6c8a72a162 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new e21a534941 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new d5b7d593a2 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new ce2c08700a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new ecda45521e 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new a69fc2919f 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 6d0d5e41ae 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new befc8464b8 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 0f50e0c98c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 4da927f5a7 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b1cf1d55cc 94: onsuccess: #832: 1: Success after binutils: 5 commits new 48ad7cb7ea 95: onsuccess: #835: 1: Success after binutils: 3 commits new 5652be85be 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new ee2c34ae99 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 36758678c3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ff13d6f275 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 61ef4e3547 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 9e8b2b85d7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 4bc7fdd485 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 5badedd0df 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new d427c0358b 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new bf4bbffd80 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 988e994cef 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new d785473a29 107: onsuccess: #849: 1: Success after binutils: 5 commits new 6f82845432 108: onsuccess: #850: 1: Success after gcc: 2 commits new cb64d6ed3c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 41c5a115fe 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new d136f2c11d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new dd40a982d1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 3204fd0687 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new fc6629167d 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new d3d90bfc41 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 7830d68c41 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 8504cb3fa0 117: onsuccess: #861: 1: Success after binutils: 18 commits new 8b6f0bf14a 118: onsuccess: #863: 1: Success after linux: 12 commits new 2c16b49bae 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new a45f3c22dd 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 4024a1a635 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 47f9f3917b 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 9f302521cc 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 66d131cbd1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 6809f4b343 125: onsuccess: #871: 1: Success after binutils: 26 commits new 2608c2c6dc 126: onsuccess: #873: 1: Success after glibc: 2 commits new ddd4d88237 127: onsuccess: #874: 1: Success after linux: 219 commits new 6ce794ee04 128: onsuccess: #876: 1: Success after binutils: 12 commits new bd5515e5bd 129: onsuccess: #878: 1: Success after linux: 3008 commits new 33661d9485 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 7543283d5f 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 9d8e1d0c3f 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new f81e5226c5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new c079d697f1 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 206c7d65ac 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 55401b95ba 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 6cd7f698cf 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new fc4f00a18b 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 6d1309a595 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new dee6999f9f 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new be18b8171d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new dabc071d31 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 1e1d70c199 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new ec72aa59ed 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 32ed3d4188 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new f5cfc9e34e 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 12fc765e71 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 664d5733a2 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 4e19ad0584 149: onsuccess: #899: 1: Success after binutils: 15 commits new 835acf4f7d 150: onsuccess: #900: 1: Success after gcc: 11 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 (bf5dcf9043) \ 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 1804 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39900 -> 39988 bytes 04-build_abe-gcc/console.log.xz | Bin 216292 -> 215656 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8944 bytes 07-build_abe-glibc/console.log.xz | Bin 245660 -> 245928 bytes 08-build_abe-gdb/console.log.xz | Bin 39716 -> 39872 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3204 -> 3128 bytes 11-check_regression/console.log.xz | Bin 5364 -> 5260 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 | 25 +- 11-check_regression/results.compare2 | 52 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 27 - sumfiles/g++.log.xz | Bin 3738840 -> 3775416 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3307884 -> 3313268 bytes sumfiles/gcc.sum | 5092 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1086688 -> 1085476 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233120 -> 232276 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453696 -> 465320 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2761 insertions(+), 2816 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