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 909a5e2cc3 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 1cd5937f83 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 15237383c4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards e5ecd2c38d 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards daa74a19cc 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 495b94dc7d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 29cb01e581 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 6b26584580 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards de0ebea120 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards f6782dd1b3 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 4299e208f4 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 87f39a73d3 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards e2b8605f0b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 995a0429b7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 5589973f3e 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 213fcc1b08 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 8523cb7893 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 43959548d0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards e881c0dce6 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 0c4d8b9acf 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 4b5244a9b9 127: onsuccess: #874: 1: Success after linux: 219 commits discards 95d2668515 126: onsuccess: #873: 1: Success after glibc: 2 commits discards eaa94e2133 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 40711cbe96 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards c86c76237f 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 1c7d6343cd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 691937f356 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards d63ad49690 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards c9fca99108 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards fd589f0ac3 118: onsuccess: #863: 1: Success after linux: 12 commits discards 63475c6bee 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 90cbbae1e1 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 7df87d2328 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 8d293d9741 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards cbf62e31da 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards d4025bc1fc 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards c1caeebd8c 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 63c562f5be 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 76f081d3f8 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 432681c08b 108: onsuccess: #850: 1: Success after gcc: 2 commits discards c6cc3b144d 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 2dd1569fad 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 8f4c4661f1 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 8a93261383 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 3aedfadf37 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 3295483c9c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 07d9239765 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards f5b26b169f 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards ea518265e8 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards c2b3e2aa8e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 00e3de8ad3 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards d78cb541c1 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards f80cdc0b18 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 8cf88fd87d 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b7de52b187 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 97913fb77e 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards effd8e2dcc 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 423c29c10f 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards c473832f3b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 4edd2e5dc3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards ccd39e5a9a 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards cab312206b 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 13efa39ca1 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards eef123e276 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 72fde0fc9b 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards d8f5a7426a 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b2892fdd17 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 7dd7365689 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6387a4486d 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 2def7e5b61 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 57998df50e 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 6e65ca6890 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards b2f956463c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 266a0fe377 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards b781431715 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 30967ee1fb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 139ca3cb2e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 30fd7fd0ad 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards d3f3dd0643 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards e7f32a873a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 3710304143 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 1c29144bda 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards c3537b1463 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 2968957363 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 613b6f9240 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards a42cbcaa14 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards bb5dd26e26 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 62f8952cb9 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards bbb29f026e 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards c763cb8cbc 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards b2f0d72488 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards fd82b387d7 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 7019ac1d36 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards ddca3fbd7d 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards fbb70e1468 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 4f3d06fa26 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards 7d1de8d0da 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards a9eea1a37c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 29c09ebead 49: onsuccess: #785: 1: Success after binutils: 12 commits discards f62aa4ed68 48: onsuccess: #782: 1: Success after binutils: 8 commits discards acf65adf88 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 8c82acebb2 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 54d310815f 48: onsuccess: #782: 1: Success after binutils: 8 commits new 1baa0788d1 49: onsuccess: #785: 1: Success after binutils: 12 commits new 176019d2d6 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new dbcfba8080 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 26b8245f25 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 7744c6ece2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new edcb33eecc 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new 1922da90ea 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 2418a9414d 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new fd03b85701 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new 43780e2e18 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 7d1f2bebbd 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a154b76fa0 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 797b378d45 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new f3243a1805 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new b56d8cb5e1 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 3ee565bcce 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 53a147ec95 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new f9c926e7eb 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new fb09c2e8eb 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new f378e378df 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new c5bb0e5854 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new c77beafd34 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 1f221a5a64 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 855b7e82cb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2b4f05e608 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 588b602915 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 89da1e68d2 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 88f2aebfa8 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new fdba836102 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new 719144053d 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new da34aa03a7 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new c61b662d8b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 21e2feba74 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 9ba4021b93 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 6a30f65e73 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new 5ebca48324 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 6fb9842ac5 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 077d6224ce 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new f6013b5ff5 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9d95c046ef 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 91c8e65f72 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 73f165a61d 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 2938802beb 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 0473850d72 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new c0432df23a 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 2f72f6d102 94: onsuccess: #832: 1: Success after binutils: 5 commits new 6a0d7e9ef6 95: onsuccess: #835: 1: Success after binutils: 3 commits new 150a20862b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new ad77844c70 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 79bcf39199 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new c309faa0e5 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new bee0849850 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 7b2349db23 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 660e3dc5b0 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 00e824d288 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new cde73792b6 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 4e5f028922 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 661b36c595 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 0756698898 107: onsuccess: #849: 1: Success after binutils: 5 commits new 8893f5a10b 108: onsuccess: #850: 1: Success after gcc: 2 commits new e8d5e1f4c9 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 42be4ac336 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 4c8cb2fe13 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new fee1892c9f 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new e16d09eee6 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 55fbca9f28 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 048e974d7c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 49a341010f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new ad4e42dbee 117: onsuccess: #861: 1: Success after binutils: 18 commits new 3be6490eb5 118: onsuccess: #863: 1: Success after linux: 12 commits new 1ebd91c3bd 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new b4c23c0a66 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new fd47b85d28 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new a11852cd0d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new a4a50cb323 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 8fb8546ded 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new ed0b3b9d1d 125: onsuccess: #871: 1: Success after binutils: 26 commits new d76d061e89 126: onsuccess: #873: 1: Success after glibc: 2 commits new 5989b3d373 127: onsuccess: #874: 1: Success after linux: 219 commits new 804029df2b 128: onsuccess: #876: 1: Success after binutils: 12 commits new e8723433b2 129: onsuccess: #878: 1: Success after linux: 3008 commits new 2ad382cbdb 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new c3ae617bd2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new c2f45ce419 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new a55fd06101 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 2f2e994899 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new f0d204bbc9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 61feb5c3fb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new d9d036227f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new f0468aefd0 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new da24daa9c7 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new bca677ab85 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d11387d00f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 3685c3167b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 2737191146 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 709cf9e784 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new d8254c9638 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 8cc66b449e 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new d73f0f5785 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new c9317b2082 148: onsuccess: #897: 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 (909a5e2cc3) \ 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 1748 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40144 -> 39768 bytes 04-build_abe-gcc/console.log.xz | Bin 214096 -> 216332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9080 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 244620 -> 246148 bytes 08-build_abe-gdb/console.log.xz | Bin 39664 -> 39808 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3880 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3020 -> 3140 bytes 11-check_regression/console.log.xz | Bin 5812 -> 5984 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 6 +- 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 3776248 -> 3740940 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 3301752 -> 3335600 bytes sumfiles/gcc.sum | 4730 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1095552 -> 1079556 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232984 -> 232056 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459740 -> 459468 bytes sumfiles/libstdc++.sum | 12 +- 37 files changed, 2531 insertions(+), 2533 deletions(-)