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 7f748c9f8b 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 5e98107d42 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 725492654e 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 874e8d2992 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 6eac8def15 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards fc343278f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 0cf820ff57 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 58dfb77eae 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 7347b8cac3 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 30bdccf7af 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards b56e2f1d68 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 3f5b507fee 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards f3905ed345 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 9242a5cd89 128: onsuccess: #876: 1: Success after binutils: 12 commits discards ec988a8eac 127: onsuccess: #874: 1: Success after linux: 219 commits discards fc202f5fc4 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 1e20f9f9ff 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 6274e50acf 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 58f22242cd 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 9c9a4b241a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 812352d978 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 3654d4ce54 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 11c097cdc8 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 071bb0b231 118: onsuccess: #863: 1: Success after linux: 12 commits discards 292c5dac64 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 157f1d05d9 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards f727e73f96 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards f1e214cfa6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 6106d74fd3 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 2f922b6ba5 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 37e1efa0fe 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 53114692b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 292c4a82ea 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards d381e456d5 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 2038b63924 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 826df00a12 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 89886fb464 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards a17b81562c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 49ace43587 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 0e710a808f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards f034a45e9a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 40171fdc3e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 80ae81bbbc 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 32140ef6bd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards f7661a4f97 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 599f5dc6fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 21880ad077 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 08e5689093 94: onsuccess: #832: 1: Success after binutils: 5 commits discards f37ecde2cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 84351e89ed 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards e2f2bd34df 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 526f518485 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards bfdcef1712 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9403844414 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards bbb7e51926 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 45e244fc36 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards dc55ed843b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards f46a8b716f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 057966f958 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e9dee4ddd4 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 93be9a5a5c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0f43ab70ad 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 3704759ed3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards c74ec7a797 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards bf3e434219 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 316220ca02 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards fc8d5ac74d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 9540134751 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 17d5c057db 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards e6ccf067bb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards d9454f990b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards bf40473b79 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards aa9e5c28b6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 8fec567f01 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards bb08907010 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 99222aa8df 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 6c41724080 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 73c2973c63 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 7ebd579502 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards c7af2bdcd1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 1d1a0ce0a7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 811b047418 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards afb67b375b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards dc926458e0 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 15334b5ae9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards b320c43e38 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards f5bf51178a 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards fde951f267 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 1b3e34b0c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 73059d7073 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards fd1fe5e6a8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards bed22023a5 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 5fd60c4dc7 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 0025c26a17 48: onsuccess: #782: 1: Success after binutils: 8 commits discards c7aa23f6c8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 348f7cfc6e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 5dcdd28cd1 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards 3a8c427118 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards aa49f8711b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 10c737049b 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 86b6a8ddab 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 27646bd138 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new b0e0c4a5a8 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new 19301529d4 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new a585dba7e0 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 49961bc5d4 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 4d25f275c6 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 930cac6add 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new cb92101fe4 48: onsuccess: #782: 1: Success after binutils: 8 commits new 30bd1c7eb8 49: onsuccess: #785: 1: Success after binutils: 12 commits new 8ebaa39e93 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new e58047d4c3 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 3fad6e3070 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 547c6c760c 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new 555d945c76 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new a33b59f430 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 6bfe6d7ace 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new d8ddbc6b2c 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new df2acbed40 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new c2e8399cd5 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new cc8c9225f3 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 61156cd036 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new a6f6944178 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 26d34463dc 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new ae5ac02254 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 2c2c25f357 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 31eb8f9dcb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new daa7f83625 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new a37ee2ac8f 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new e55550582b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 3df18066dc 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new a9bc360c43 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 80242565fe 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 5a75cf5b56 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 1a7a1bf71e 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new d365b16fd4 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new da09e02acc 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new c0abd4f070 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 518787c3f2 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 543fc34d54 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 7f598e8ae7 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 0f7fc85153 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 1b6f504a02 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new e31fbd64ff 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 589be7e0f2 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new be992f5fb8 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 5d4ecc0662 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 5f8a3a1787 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 8297c09f56 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new f61d385cd0 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 5ed7e926ee 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new fdfea221f3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new d033e12d16 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 7ac3d20fbd 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 786b807dbe 94: onsuccess: #832: 1: Success after binutils: 5 commits new 3584053455 95: onsuccess: #835: 1: Success after binutils: 3 commits new d3f7f91a06 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 7ec330cf3c 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new e1d910b666 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 2046e4b605 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 84a4518e3d 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 59754e044a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 4b563ea81e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new fa2bafa08a 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new a78ee770c4 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new bb15c09cb2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 2e85305058 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 56d7a3bd41 107: onsuccess: #849: 1: Success after binutils: 5 commits new ae3bf1b623 108: onsuccess: #850: 1: Success after gcc: 2 commits new 81a23fc65a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 4f86164f2d 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 9734a77fe4 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 73bf92dd86 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 17388d6129 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new dc1689b933 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new e0a53d4119 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 9096bd2d3f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 8478395c5d 117: onsuccess: #861: 1: Success after binutils: 18 commits new a03742b715 118: onsuccess: #863: 1: Success after linux: 12 commits new 95c371bb5d 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 8ede70d677 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 19c469ff2a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 85e2818c5c 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 8f6b3bef90 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 5ac87d3ff0 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new a64bebdd30 125: onsuccess: #871: 1: Success after binutils: 26 commits new a92dba7178 126: onsuccess: #873: 1: Success after glibc: 2 commits new 95a300c13f 127: onsuccess: #874: 1: Success after linux: 219 commits new 5275732da4 128: onsuccess: #876: 1: Success after binutils: 12 commits new 55bb913f4d 129: onsuccess: #878: 1: Success after linux: 3008 commits new 898ca0d6fa 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new bd7f808efc 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 4c2a253977 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 496ca9fabe 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 414ed10724 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 91e8afca98 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new e09e49bf15 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 3cfef9a824 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 03cf47014f 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 3b617db836 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 1e92817642 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new e6f6eca283 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 5b7db6ac3f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...]

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 (7f748c9f8b) \ 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 1760 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39856 -> 40044 bytes 04-build_abe-gcc/console.log.xz | Bin 216820 -> 215436 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8560 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 245548 -> 245028 bytes 08-build_abe-gdb/console.log.xz | Bin 39748 -> 39936 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3848 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3284 -> 2648 bytes 11-check_regression/console.log.xz | Bin 6800 -> 7652 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 61 +- 11-check_regression/results.compare | 34 +- 11-check_regression/results.compare2 | 426 ++- 11-check_regression/results.regressions | 42 - 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 42 - sumfiles/g++.log.xz | Bin 3775616 -> 3745176 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 3310296 -> 3312456 bytes sumfiles/gcc.sum | 5414 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1080828 -> 1077080 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2272 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232248 -> 232308 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462656 -> 457192 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 3292 insertions(+), 3088 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