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 636db8701a 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 76681ca08f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 646d5203c7 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards b8971d974b 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards d3887ddafd 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 0e0936a001 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 9ce926e7d4 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 35f0742add 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 468c961dcf 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 6adef38786 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards b08677aa9b 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 3601de8892 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 81a775cb2d 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 6474f46d92 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 3542b8bac0 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 026852d530 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards d0b127fa27 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards c4b6d247de 129: onsuccess: #878: 1: Success after linux: 3008 commits discards b2c87e5a65 128: onsuccess: #876: 1: Success after binutils: 12 commits discards e3593de626 127: onsuccess: #874: 1: Success after linux: 219 commits discards 032049a9c8 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 9009e2ac40 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 9f570deb52 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 3ac8470477 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards af35e28351 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards ef3c721c9e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards a88327f2bb 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 6470de4b03 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 2c1c127364 118: onsuccess: #863: 1: Success after linux: 12 commits discards 4d0ae1a368 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 79264bcb2b 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards ed22399e8e 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards e8da5fba3d 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards f01cb6bb18 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards b222cb2e17 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards aefa149328 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 56a504bf44 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 4f05080a10 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards e0469c97b1 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c8f0deaeac 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f1e18f9734 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 94f129fa6a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards e53ee4d694 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 8aab0cc648 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 34a99b987c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards eb76ecab13 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 87cfbb9378 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 6ace2ef6a5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d8cb2c76ff 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 04da78fdbb 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 89dae9367a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 82e89d5b48 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 401771b0f9 94: onsuccess: #832: 1: Success after binutils: 5 commits discards e407d0f548 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards c04245d0d7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 71a4e95274 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards ed6405d99e 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 704309e10c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 72b57f2c9d 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards f6699d54ed 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5f8707f622 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 4895e0ae54 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards cd149b4904 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards f0d49e0240 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards b8c7af95d5 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 7d1210e836 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 93fd0e4fbe 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards cca8dc2e1d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 846ca034ed 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 03c49d11ca 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 1514bca4ef 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 1ba63f6ec0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 688c4cffe9 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 40fcc78a46 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 39808a8b17 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 312035b396 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 95cb5298d7 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards db80bc7afc 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 823149e278 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards a7f86f3cab 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 4ed9467a92 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards c151828c8b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards f4b9902077 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards c20f6d47e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards f2acf57acc 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 2a4473f973 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 56465ddd61 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards a4874be3ef 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 6a23996195 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 637351a90e 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 6b592cbb01 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 9689867ea0 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards db2d192fef 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards 713e35bf27 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 443811ad5e 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 9f62af61a7 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 5ae0193d0b 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 5dfff25fb3 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 141c28d732 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 45f4c2565d 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards bbfeb9a5c1 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new 2ec7b6dc33 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new acf65adf88 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new f62aa4ed68 48: onsuccess: #782: 1: Success after binutils: 8 commits new 29c09ebead 49: onsuccess: #785: 1: Success after binutils: 12 commits new a9eea1a37c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new 7d1de8d0da 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 4f3d06fa26 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new fbb70e1468 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new ddca3fbd7d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 7019ac1d36 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new fd82b387d7 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new b2f0d72488 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new c763cb8cbc 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new bbb29f026e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 62f8952cb9 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new bb5dd26e26 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new a42cbcaa14 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 613b6f9240 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 2968957363 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new c3537b1463 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 1c29144bda 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 3710304143 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new e7f32a873a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new d3f3dd0643 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 30fd7fd0ad 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 139ca3cb2e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 30967ee1fb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new b781431715 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 266a0fe377 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new b2f956463c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 6e65ca6890 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 57998df50e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 2def7e5b61 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 6387a4486d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 7dd7365689 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new b2892fdd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new d8f5a7426a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 72fde0fc9b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new eef123e276 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 13efa39ca1 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new cab312206b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new ccd39e5a9a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 4edd2e5dc3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new c473832f3b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 423c29c10f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new effd8e2dcc 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 97913fb77e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new b7de52b187 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 8cf88fd87d 94: onsuccess: #832: 1: Success after binutils: 5 commits new f80cdc0b18 95: onsuccess: #835: 1: Success after binutils: 3 commits new d78cb541c1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new 00e3de8ad3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new c2b3e2aa8e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new ea518265e8 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new f5b26b169f 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 07d9239765 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 3295483c9c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 3aedfadf37 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new 8a93261383 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 8f4c4661f1 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 2dd1569fad 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new c6cc3b144d 107: onsuccess: #849: 1: Success after binutils: 5 commits new 432681c08b 108: onsuccess: #850: 1: Success after gcc: 2 commits new 76f081d3f8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 63c562f5be 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new c1caeebd8c 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new d4025bc1fc 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new cbf62e31da 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 8d293d9741 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 7df87d2328 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 90cbbae1e1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 63475c6bee 117: onsuccess: #861: 1: Success after binutils: 18 commits new fd589f0ac3 118: onsuccess: #863: 1: Success after linux: 12 commits new c9fca99108 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new d63ad49690 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 691937f356 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 1c7d6343cd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new c86c76237f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 40711cbe96 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new eaa94e2133 125: onsuccess: #871: 1: Success after binutils: 26 commits new 95d2668515 126: onsuccess: #873: 1: Success after glibc: 2 commits new 4b5244a9b9 127: onsuccess: #874: 1: Success after linux: 219 commits new 0c4d8b9acf 128: onsuccess: #876: 1: Success after binutils: 12 commits new e881c0dce6 129: onsuccess: #878: 1: Success after linux: 3008 commits new 43959548d0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 8523cb7893 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 213fcc1b08 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 5589973f3e 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 995a0429b7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new e2b8605f0b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 87f39a73d3 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 4299e208f4 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f6782dd1b3 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new de0ebea120 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 6b26584580 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 29cb01e581 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 495b94dc7d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new daa74a19cc 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new e5ecd2c38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 15237383c4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 1cd5937f83 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 909a5e2cc3 147: onsuccess: #896: 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 (636db8701a) \ 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 1800 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40304 -> 40144 bytes 04-build_abe-gcc/console.log.xz | Bin 214628 -> 214096 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9220 -> 9080 bytes 07-build_abe-glibc/console.log.xz | Bin 244836 -> 244620 bytes 08-build_abe-gdb/console.log.xz | Bin 40072 -> 39664 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3892 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2876 -> 3020 bytes 11-check_regression/console.log.xz | Bin 6324 -> 5812 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 44 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3762788 -> 3776248 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 3307468 -> 3301752 bytes sumfiles/gcc.sum | 4324 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1084536 -> 1095552 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232204 -> 232984 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466916 -> 459740 bytes sumfiles/libstdc++.sum | 12 +- 37 files changed, 2324 insertions(+), 2332 deletions(-)