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-arm in repository toolchain/ci/base-artifacts.

discards 902194e3fc 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 86f88431c0 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards baeb0fdefc 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] discards e1f81bd34a 162: onsuccess: #624: 1: Success after linux: 10 commits discards 07d4cb5754 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 758261339b 160: onsuccess: #621: 1: Success after gcc: 11 commits discards c813eee6c9 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 02f951682e 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] discards 4117efb84f 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] discards d1b5e5c023 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 4d44fcb0ae 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards b5157cc47a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits discards 3682a8a9cf 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits discards aa3bb61aa2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits discards fb3a8b4d2f 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] discards 92a4a84470 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards f882882375 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] discards a8fbea88f3 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 5038bb29e9 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards d8fa4a56b9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 39e36e442b 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 3efbff3ffb 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits discards 0de1441bec 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 3ab01cd65a 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards d5408c8d0e 141: onsuccess: #601: 1: Success after linux: 794 commits discards 466768cdba 140: onsuccess: #600: 1: Success after gcc: 23 commits discards a88888453c 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 2ff5c1f7c7 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 71843d0854 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 2872b8cc42 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 5d059eefee 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] discards e8ad69b7d6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 78153da178 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards f02325f19c 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 8ec4b9ee57 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 764592d092 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] discards 96d4334bce 129: onsuccess: #588: 1: Success after linux: 4 commits discards e0c06e4e8f 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 11023549bb 127: onsuccess: #584: 1: Success after linux: 21 commits discards 6bd08812d5 126: onsuccess: #582: 1: Success after gcc: 9 commits discards a790753f86 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 68494e0b70 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 371cd14eef 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] discards cc3be9935e 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards 2793f8e180 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] discards 67741f8b02 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards de088c5ed2 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 56bf607bcb 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards 0981a74613 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards c38fa5c593 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards b579a024a9 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards fc3c59c31b 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 9f65b9fb23 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 76007acdb0 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 445bf3b085 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 3cdb5e2397 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 1a20568b77 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards a55b7c9ec4 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 1761548866 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards a1fff2794d 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 09b600e775 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards c3a584e20c 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 2c0587e596 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 10f3d8ae91 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 2b21b42924 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 44988b1d0b 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 96f6c2c0f9 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e025d96fd6 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 626413fdee 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 404652dec6 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards e04830195a 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 4947811bc3 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 802af712e0 93: onsuccess: #544: 1: Success after linux: 34 commits discards eafaa7c8bc 92: onsuccess: #543: 1: Success after glibc: 4 commits discards e34891d3be 91: onsuccess: #539: 1: Success after linux: 27 commits discards d72929b427 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 64bcf57f8a 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 370d0ac6ab 88: onsuccess: #534: 1: Success after linux: 12 commits discards d6a255c0b6 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 5e516fa2e2 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 28ce665f4f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 5f4967c8cc 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 32e5185482 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 1e3f2c0369 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 73409cf128 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 6941e4e23f 80: onsuccess: #524: 1: Success after linux: 9 commits discards 226ec3d0c6 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 14c08b7eda 78: onsuccess: #522: 1: Success after binutils: 10 commits discards f78911891e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 28e9c9b12e 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards f9ab802a67 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 5640c74e9a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 4c1da0ee89 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards b927bf7cd0 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards c09f5a622c 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards d21a681649 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards f5147f59f3 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 20b371f254 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 6361c76ba7 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 09436ad8e2 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 0d59b0c315 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new e53d4a3a81 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new b164d0561e 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 0a161175a6 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new d36d33d64e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 2c4a96a5f6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 10fbdbf7cf 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 771a19b988 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new f446a10fbb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 825813f750 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 5ed3361abd 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 131a91c776 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 4df6dc655e 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 09cacb6644 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new a89033d331 78: onsuccess: #522: 1: Success after binutils: 10 commits new f6c2e4db9d 79: onsuccess: #523: 1: Success after gcc: 25 commits new 4346120e72 80: onsuccess: #524: 1: Success after linux: 9 commits new 2d47222e26 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 0b1a21c05b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 71dcde1913 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new cd3c3cde05 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 4ca7583998 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 8d933bef98 86: onsuccess: #532: 1: Success after gcc: 16 commits new d5d424f004 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 23ce1e07ff 88: onsuccess: #534: 1: Success after linux: 12 commits new 454af8fa06 89: onsuccess: #536: 1: Success after binutils: 27 commits new aeba021080 90: onsuccess: #538: 1: Success after glibc: 10 commits new 68dbdf3158 91: onsuccess: #539: 1: Success after linux: 27 commits new 237eccb149 92: onsuccess: #543: 1: Success after glibc: 4 commits new db960e9ac3 93: onsuccess: #544: 1: Success after linux: 34 commits new f94c12deb4 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 1195026d8c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new ef445d785c 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new c2a72e68f3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new e3050c8b05 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 39d550665c 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new fc2e1d4d0d 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 51579e15ce 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 4583da3eec 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new b04cb14795 103: onsuccess: #555: 1: Success after binutils: 4 commits new 60d7114f40 104: onsuccess: #558: 1: Success after binutils: 3 commits new 3403581846 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 850bde2ee1 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 2b3f13c961 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 7e13713d7c 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 830a60d941 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 14f8c03bba 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 2de5303224 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 104e0f2385 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 1221d3dce1 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 8b0d5b3f89 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 8c99e4b122 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 67c02ea6b2 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new bc1ce1e625 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new 50ae375857 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 0dfb514da8 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new a41c3d7971 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new e7b0157908 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...] new 7100f587f9 122: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new 7f34f27554 123: onsuccess: #578: 1: Success after binutils/gcc/linux/gl [...] new 5c1392dbc6 124: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new d22f1e6a0c 125: onsuccess: #581: 1: Success after binutils: 4 commits new 4de34d0e38 126: onsuccess: #582: 1: Success after gcc: 9 commits new 6d247c8789 127: onsuccess: #584: 1: Success after linux: 21 commits new f1c35759c0 128: onsuccess: #586: 1: Success after binutils: 22 commits new 2e9ac1d36f 129: onsuccess: #588: 1: Success after linux: 4 commits new 6fcc2eaa2f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/gl [...] new 3770cb8ba2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new a4d3677bc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6ef45f0f76 133: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new f0cd57a053 134: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 17dd63107a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/gd [...] new b77a602ca4 136: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new c5f65a4410 137: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 6695c2fa93 138: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new bfe37b77c1 139: onsuccess: #599: 1: Success after binutils: 10 commits new 3cd70410d5 140: onsuccess: #600: 1: Success after gcc: 23 commits new 8cb8047ed2 141: onsuccess: #601: 1: Success after linux: 794 commits new 5f33e69b42 142: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 5bf88c4fc5 143: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 17da9a12b4 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 commits new 17fb5ac508 145: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new cf1f9c82ef 146: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 16e2d0ec95 147: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new 77484fec85 148: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9aec6a929d 149: onsuccess: #609: 1: Success after binutils/gcc/linux/gd [...] new 88154a8101 150: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new d6c651a248 151: onsuccess: #611: 1: Success after binutils/gcc/linux/gd [...] new d20bb59390 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 commits new e9168e395d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 commits new c795c16ea1 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 commits new f689815fd1 155: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 231ed5957e 156: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 2362a2abb4 157: onsuccess: #617: 1: Success after binutils/gcc/linux/gd [...] new 8ae2e3e6c8 158: onsuccess: #618: 1: Success after binutils/gcc/linux/gd [...] new 5a0760f031 159: onsuccess: #620: 1: Success after binutils: 12 commits new 72a4825b8f 160: onsuccess: #621: 1: Success after gcc: 11 commits new 8ddd1eeec5 161: onsuccess: #623: 1: Success after glibc: 9 commits new e86dac748b 162: onsuccess: #624: 1: Success after linux: 10 commits new 2238944064 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/gd [...] new 8a969651d2 164: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 84c337780a 165: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new f001be8d98 166: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...]

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 (902194e3fc) \ 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 1744 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53044 -> 53512 bytes 04-build_abe-gcc/console.log.xz | Bin 238452 -> 237668 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8944 bytes 07-build_abe-glibc/console.log.xz | Bin 236356 -> 236396 bytes 08-build_abe-gdb/console.log.xz | Bin 52944 -> 52712 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2600 -> 2580 bytes 11-check_regression/console.log.xz | Bin 6728 -> 6736 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 58 +- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2903956 -> 2920612 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2575500 -> 2563684 bytes sumfiles/gcc.sum | 4900 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 952784 -> 958120 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230672 -> 230700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473876 -> 473568 bytes sumfiles/libstdc++.sum | 13 +- 38 files changed, 2664 insertions(+), 2643 deletions(-)