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 c9317b2082 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards d73f0f5785 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 8cc66b449e 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards d8254c9638 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 709cf9e784 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 2737191146 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 3685c3167b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards d11387d00f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards bca677ab85 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards da24daa9c7 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards f0468aefd0 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards d9d036227f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 61feb5c3fb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards f0d204bbc9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 2f2e994899 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards a55fd06101 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards c2f45ce419 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards c3ae617bd2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 2ad382cbdb 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e8723433b2 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 804029df2b 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 5989b3d373 127: onsuccess: #874: 1: Success after linux: 219 commits discards d76d061e89 126: onsuccess: #873: 1: Success after glibc: 2 commits discards ed0b3b9d1d 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 8fb8546ded 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards a4a50cb323 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards a11852cd0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards fd47b85d28 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards b4c23c0a66 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 1ebd91c3bd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 3be6490eb5 118: onsuccess: #863: 1: Success after linux: 12 commits discards ad4e42dbee 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 49a341010f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 048e974d7c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 55fbca9f28 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards e16d09eee6 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards fee1892c9f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 4c8cb2fe13 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 42be4ac336 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards e8d5e1f4c9 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 8893f5a10b 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 0756698898 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 661b36c595 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 4e5f028922 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards cde73792b6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 00e824d288 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 660e3dc5b0 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 7b2349db23 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards bee0849850 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards c309faa0e5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 79bcf39199 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ad77844c70 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 150a20862b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 6a0d7e9ef6 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 2f72f6d102 94: onsuccess: #832: 1: Success after binutils: 5 commits discards c0432df23a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0473850d72 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 2938802beb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 73f165a61d 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 91c8e65f72 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9d95c046ef 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards f6013b5ff5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 077d6224ce 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 6fb9842ac5 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 5ebca48324 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 6a30f65e73 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 9ba4021b93 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 21e2feba74 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards c61b662d8b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards da34aa03a7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 719144053d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards fdba836102 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 88f2aebfa8 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 89da1e68d2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 588b602915 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 2b4f05e608 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 855b7e82cb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 1f221a5a64 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards c77beafd34 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards c5bb0e5854 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards f378e378df 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards fb09c2e8eb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards f9c926e7eb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 53a147ec95 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 3ee565bcce 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards b56d8cb5e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards f3243a1805 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 797b378d45 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards a154b76fa0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 7d1f2bebbd 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 43780e2e18 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards fd03b85701 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 2418a9414d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 1922da90ea 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards edcb33eecc 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 7744c6ece2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 26b8245f25 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards dbcfba8080 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 176019d2d6 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 1baa0788d1 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 54d310815f 48: onsuccess: #782: 1: Success after binutils: 8 commits new 25a6623d52 48: onsuccess: #782: 1: Success after binutils: 8 commits new 0aae0cf040 49: onsuccess: #785: 1: Success after binutils: 12 commits new 9b23c7efa6 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new fb468ed4be 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new ce63c4dae8 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new baa1102ca6 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 8b30c3ceaf 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 1300ec82be 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 2d05da0641 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 01fea97be1 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 5b9a90c910 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 3f8d2930d4 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 33c496fcd5 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 4c3e777a07 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ec235b2750 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 8febdb9595 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new f9f1fb4dc7 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 6bcd8b52c3 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 457eba1391 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 6dfbc90ef4 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 7b74eee3bb 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 1225c5f116 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 1ab3d6febb 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new da2219396a 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 7b7c240958 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new f172255606 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new b44072dc8e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 149ca9fd50 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 64a3f31096 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new b313d4a2b0 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 79b19b0b68 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 1f3eeb4f02 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0a081f82c7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 0b5b0ad8d0 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new b6d7ce7979 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 1a1f7e3428 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 99ae8e0834 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new e41a91071e 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new e441002d7a 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 87a1b4a283 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 8456b6f054 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 20ad9c859f 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 2069146c4e 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 170838f521 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new b99047122f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new a36339d83a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 027d66e869 94: onsuccess: #832: 1: Success after binutils: 5 commits new ead04ecf2a 95: onsuccess: #835: 1: Success after binutils: 3 commits new 15c929fa71 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 6ed94030f2 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 698d6ff57d 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 9138212945 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new eb26df0773 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 8c4fefa1bf 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new d42d481d35 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 3fe71fd479 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 65b7608e09 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 699490b0ce 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new cd077feb4f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 62c640edc9 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4b7c8b6dae 108: onsuccess: #850: 1: Success after gcc: 2 commits new 4248a48759 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 560a06e08e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new e8cd0687bb 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 779b573a0f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 2ce66c100b 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 2e3f085c16 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new c074fe0a0a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 86e43816c1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 945ffc0d8c 117: onsuccess: #861: 1: Success after binutils: 18 commits new 1988b1dbfa 118: onsuccess: #863: 1: Success after linux: 12 commits new c9c9be6c54 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 93b522f795 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 74f55e0c00 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new b140ab14d4 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 98ef063e28 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 6344926b55 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 485b5d2486 125: onsuccess: #871: 1: Success after binutils: 26 commits new 3d48e479c0 126: onsuccess: #873: 1: Success after glibc: 2 commits new 7c2d6e6ea1 127: onsuccess: #874: 1: Success after linux: 219 commits new 302f647190 128: onsuccess: #876: 1: Success after binutils: 12 commits new b95e52194a 129: onsuccess: #878: 1: Success after linux: 3008 commits new 7baab2d4b4 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 2eac5cf7fb 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new b9c5270aa2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 1af31462f2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new edd84a18fb 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new d1366813c7 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 90f0d527db 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 6461da999c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new a6953be439 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 760bd64853 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 46d402c40b 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 98c4e220b0 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 742819081f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 0e17abd74d 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 71820db460 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new fb6ec00a01 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new e44e2011b5 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new c8ac036bc7 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 2766842fec 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new bf5dcf9043 149: onsuccess: #899: 1: Success after binutils: 15 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 (c9317b2082) \ 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 1740 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 39768 -> 39900 bytes 04-build_abe-gcc/console.log.xz | Bin 216332 -> 216292 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 246148 -> 245660 bytes 08-build_abe-gdb/console.log.xz | Bin 39808 -> 39716 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3896 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3140 -> 3204 bytes 11-check_regression/console.log.xz | Bin 5984 -> 5364 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 40 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 + sumfiles/g++.log.xz | Bin 3740940 -> 3738840 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 3335600 -> 3307884 bytes sumfiles/gcc.sum | 4618 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1079556 -> 1086688 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232056 -> 233120 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459468 -> 453696 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2615 insertions(+), 2473 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions