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 835acf4f7d 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 4e19ad0584 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 664d5733a2 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 12fc765e71 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards f5cfc9e34e 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 32ed3d4188 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards ec72aa59ed 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 1e1d70c199 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards dabc071d31 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards be18b8171d 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards dee6999f9f 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 6d1309a595 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards fc4f00a18b 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 6cd7f698cf 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 55401b95ba 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 206c7d65ac 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards c079d697f1 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards f81e5226c5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 9d8e1d0c3f 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 7543283d5f 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 33661d9485 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards bd5515e5bd 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 6ce794ee04 128: onsuccess: #876: 1: Success after binutils: 12 commits discards ddd4d88237 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2608c2c6dc 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 6809f4b343 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 66d131cbd1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 9f302521cc 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 47f9f3917b 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 4024a1a635 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards a45f3c22dd 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 2c16b49bae 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 8b6f0bf14a 118: onsuccess: #863: 1: Success after linux: 12 commits discards 8504cb3fa0 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 7830d68c41 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards d3d90bfc41 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards fc6629167d 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 3204fd0687 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards dd40a982d1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards d136f2c11d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 41c5a115fe 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards cb64d6ed3c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 6f82845432 108: onsuccess: #850: 1: Success after gcc: 2 commits discards d785473a29 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 988e994cef 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards bf4bbffd80 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards d427c0358b 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 5badedd0df 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 4bc7fdd485 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 9e8b2b85d7 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 61ef4e3547 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards ff13d6f275 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 36758678c3 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ee2c34ae99 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 5652be85be 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 48ad7cb7ea 95: onsuccess: #835: 1: Success after binutils: 3 commits discards b1cf1d55cc 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 4da927f5a7 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0f50e0c98c 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards befc8464b8 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 6d0d5e41ae 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards a69fc2919f 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards ecda45521e 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards ce2c08700a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards d5b7d593a2 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards e21a534941 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 6c8a72a162 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3c0ca24030 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards c9ec982ecf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 2b76c4239e 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 3b5f477da1 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards f3c433d8b6 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 748b2b9349 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 53247a0a59 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards bf8fd28b3b 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards feaa908c56 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 22ed462eef 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 9978272aa9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 9b12957c31 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 97af540a63 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards b207af2f44 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 003445b4e8 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards fcaae8480e 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 81e5f30bfb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 947e1d4b6a 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 786a87e579 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 131a39566e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 43582277c9 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards f018bca34f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 8701e42ccc 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 358fdf1358 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards fc51528e8e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 2b5331f032 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 87da58a11d 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards a923504272 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards b0e01cc3de 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards ee0ff2b2f2 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards f0dfafef7d 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 7386146e73 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 9aa984c72b 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards e1bbdbddc8 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 47a95a2656 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 2472a4fc04 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new e806ad0822 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 9969a4ee31 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 68f548370d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 902912f9b1 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new a473655ece 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new c1eee23393 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 08ee2e1f29 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 098373edb1 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new dcd740c6d4 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new c31117f71b 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new dafb949153 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 53f418c321 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new fdbfa5cf47 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 15a3b7d35f 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new eb9eb3df57 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 49704e18af 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 840a1728de 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new 66c1d728ad 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 6e019d9f6f 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 949b0fae83 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 2cd19275bb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new bbc09a1e30 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new f237753418 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 1168116f80 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 4a23a7be04 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 8272c5461f 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new fd2f0d84c7 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new aa72237941 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 46b53c3b71 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 621b81b6fa 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 91465ddcc0 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 8fcd93153a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new c3165f34eb 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new d28a8092f0 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 823fdc8cf8 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 4e7d44097c 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new b5035294fa 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 2f408278cb 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 88e42d8fff 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 023261aab2 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 12fb8b9815 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new e427d38ad6 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new af9fa7a6f0 94: onsuccess: #832: 1: Success after binutils: 5 commits new cfb7772b9d 95: onsuccess: #835: 1: Success after binutils: 3 commits new a0c93668b7 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new aeeb40f880 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new f698001610 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c8ef69d755 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new c068311cc4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 26d177b261 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new b1351bdaf6 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 3c3c21bb05 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 519c3b4bbe 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 4c0599a562 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 8771b37109 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 6d623b1a9f 107: onsuccess: #849: 1: Success after binutils: 5 commits new a541e1913b 108: onsuccess: #850: 1: Success after gcc: 2 commits new a5e57525f8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 8fcec8be15 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 154518103d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new ec8edf22c1 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new dbc48705c4 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 1b15ede0ac 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 301eca7cc2 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 6487c05b8c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 4d581df780 117: onsuccess: #861: 1: Success after binutils: 18 commits new 62f566fb47 118: onsuccess: #863: 1: Success after linux: 12 commits new 61c0f9f327 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 33411116a8 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 40a23f92f9 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new ffce1d1015 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 79fcd27f71 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new eabf253d52 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 693332f44b 125: onsuccess: #871: 1: Success after binutils: 26 commits new 5216cc3e43 126: onsuccess: #873: 1: Success after glibc: 2 commits new da44929693 127: onsuccess: #874: 1: Success after linux: 219 commits new 8a566524e0 128: onsuccess: #876: 1: Success after binutils: 12 commits new 2269bd4e31 129: onsuccess: #878: 1: Success after linux: 3008 commits new c13153fb0b 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new f9b43fffe3 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new d1383ca69b 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 125a95a5e2 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 462bc12442 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 66ecebbd18 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new c59dfce611 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 4dfd74711a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 19ab30fc29 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new fb61008626 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new d9c6137a40 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 4abea06adc 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 4dcaf22171 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new c10e9d06ec 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 58583a60d8 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 70c01721da 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 94be98e308 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 57a155e7cd 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new 12227a03d5 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 31ac52ca1a 149: onsuccess: #899: 1: Success after binutils: 15 commits new 0c48af2ef7 150: onsuccess: #900: 1: Success after gcc: 11 commits new e9a89962ca 151: onsuccess: #902: 1: Success after glibc: 8 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 (835acf4f7d) \ 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 1756 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39988 -> 39740 bytes 04-build_abe-gcc/console.log.xz | Bin 215656 -> 214344 bytes 06-build_abe-linux/console.log.xz | Bin 8944 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 245928 -> 245540 bytes 08-build_abe-gdb/console.log.xz | Bin 39872 -> 39576 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3844 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3128 -> 3172 bytes 11-check_regression/console.log.xz | Bin 5260 -> 5324 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 54 +- 11-check_regression/results.compare | 15 +- 11-check_regression/results.compare2 | 52 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 48 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 56 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 + sumfiles/g++.log.xz | Bin 3775416 -> 3746000 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 3313268 -> 3346744 bytes sumfiles/gcc.sum | 4952 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1085476 -> 1088248 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2272 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 232276 -> 232124 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 465320 -> 462164 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2675 insertions(+), 2620 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