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 aea686249a9 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 3de9ee626f7 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 8590c71a6ba 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 38f70becc8a 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 1e869a9e51b 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards f1d31b28273 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 5a4b3a6f518 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards fbbb766ad11 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards af875be94b2 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 17bed9627a2 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 5719a96a86e 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards ace8a16998e 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards a15d7d0ef5b 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 4eb294c983c 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f8478de73fd 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 5c155762f50 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 050a15d87fa 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards cd7f23fbd8c 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 1fa32d9d51f 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards be65aef1df4 104: onsuccess: #558: 1: Success after binutils: 3 commits discards d9143d1abe2 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 2fce0b940ba 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 913b14aa2d9 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 037e67f9832 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards ead40724eb0 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards cd71f0277e5 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 854a977dcbc 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 0a596361466 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards aa0f5fe083e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 8952a594bc2 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 421506da734 93: onsuccess: #544: 1: Success after linux: 34 commits discards b0f003728a9 92: onsuccess: #543: 1: Success after glibc: 4 commits discards cd15f0f44ad 91: onsuccess: #539: 1: Success after linux: 27 commits discards a8995ee02d3 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 7e2b8f7c975 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 69239198f16 88: onsuccess: #534: 1: Success after linux: 12 commits discards bd19b08343e 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 22ef1399330 86: onsuccess: #532: 1: Success after gcc: 16 commits discards afa4ef4b599 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards fa2c2caf1d2 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 18d44bc475b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards cad405c5d4e 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards f6b954f3431 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 25ed8ac403d 80: onsuccess: #524: 1: Success after linux: 9 commits discards 2571b2417b7 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 18702137904 78: onsuccess: #522: 1: Success after binutils: 10 commits discards e03af2610b7 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards 90425d3a9fd 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards e5084256bb6 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards 9430e13581b 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards e3b2c3d77e2 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards ec3eaf2b262 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 9b40b3584e2 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 338afc2366d 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards feff8268842 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards b2f06b69225 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards b7d3eb99827 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards 85b876415d9 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards c7ea43e5fbf 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 1a8f22d7c25 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 7066922b724 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards d6421bfd644 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 8f85aa8b672 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards 14c6c5e39a2 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 0537d7de9cf 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 77051d33dc2 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 0ae46d5cfe9 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards ed69fb3b8a9 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 2da3584f8be 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards ecf2b1ba298 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards b3a3a4b0591 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards cda773fbbb6 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 7bebbc9ef53 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 51cab626cfb 50: onsuccess: #490: 1: Success after binutils: 6 commits discards d8da7896ea4 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 86bda35d046 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 03c0256a744 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards dd40aa32ba1 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards ce105aab183 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards fd7d7965971 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards d1ea5d9078a 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 2e12689aef5 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 78d80307652 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards c9a31b00909 40: onsuccess: #476: 1: Success after linux: 69 commits discards 38f7bfd28e5 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 088f7d38c6a 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards 40ce930ed1a 37: onsuccess: #470: 1: Success after binutils: 3 commits discards aaf03871136 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards c0656d58ef5 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 256b5ffc9a1 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 3d7934b2e38 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] discards d3ea21aedf4 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] discards 853c7177cac 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] discards 9129b6a7a65 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] discards 398e5f1fe2f 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] discards 65c07ae5460 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] discards 74a358ab411 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards db79019c4e3 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] discards f66a61f5510 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] discards 48b425cdab3 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gd [...] discards bb4642912aa 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 [...] new 496da195998 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 [...] new 8a47812f328 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gd [...] new 0d76f35a8f1 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 2d2789a33d0 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] new 331e217943c 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 4af6cd9c471 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] new ac8da649ec0 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] new 8b26b8cd401 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] new 84208199655 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] new 7ffdb8edfdb 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] new 5e2e04ce63b 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] new ff21dfbc2aa 34: onsuccess: #465: 1: Success after binutils: 11 commits new 9222123b587 35: onsuccess: #467: 1: Success after glibc: 2 commits new 48bde742bcc 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 163bb9849e5 37: onsuccess: #470: 1: Success after binutils: 3 commits new aae0b6cc5e0 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new 04f9d60ed15 39: onsuccess: #474: 1: Success after binutils: 8 commits new 77f06ddd53c 40: onsuccess: #476: 1: Success after linux: 69 commits new bca869a49bc 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new e28758e5ca5 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 33860a4075b 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 69d330041e5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 975df507591 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 6b3fec85130 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 9c292bec971 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new f29e3336d54 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new df4cba7c63b 49: onsuccess: #487: 1: Success after binutils: 11 commits new e4a98d29ffd 50: onsuccess: #490: 1: Success after binutils: 6 commits new 6548a8888ef 51: onsuccess: #493: 1: Success after binutils: 13 commits new df4f3fc31f9 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new a476fbe2e3d 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 91e761efdae 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new a6ce783c571 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 26fd058e490 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new d70c17bedac 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 7758bf2292d 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 614ce69c9b0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new ccd9a2c8de3 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new 80a3449ed4a 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new 0e866ae925f 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new b81a6db6c18 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new fd4d3790271 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new 0bfb5664e9a 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new c86be41d075 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new d0af01320ac 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new b43e1bc911c 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 5793325b5e7 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new bfb519f56bc 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 9959ba76cdb 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 89506d48ee8 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new a82bc465dcc 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new db2173de864 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new 2be9376ea48 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new d578eb63f85 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new ffe17a20307 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new cfa9892c790 78: onsuccess: #522: 1: Success after binutils: 10 commits new 135a2b4dc69 79: onsuccess: #523: 1: Success after gcc: 25 commits new 1f361b06308 80: onsuccess: #524: 1: Success after linux: 9 commits new 6a6aeebcef6 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 0cedcf00868 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 7906e79fa56 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 5f7de55e848 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new c07e6339e72 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 4d67838c6a5 86: onsuccess: #532: 1: Success after gcc: 16 commits new 655ca62b3d6 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new ef89a73c2dd 88: onsuccess: #534: 1: Success after linux: 12 commits new 61e6d20c0e5 89: onsuccess: #536: 1: Success after binutils: 27 commits new bcc0bdced88 90: onsuccess: #538: 1: Success after glibc: 10 commits new 79f22c040e8 91: onsuccess: #539: 1: Success after linux: 27 commits new ed7060aad37 92: onsuccess: #543: 1: Success after glibc: 4 commits new f868b612ef4 93: onsuccess: #544: 1: Success after linux: 34 commits new bf62463baa0 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 2533cbf82c6 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 9cd37aaa7f0 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new a811d5baa49 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 0fb03355a3f 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 3c4cab4e5bf 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new b936a5a484c 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 562d87724d5 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 1db55da60e0 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 110c5bceb6f 103: onsuccess: #555: 1: Success after binutils: 4 commits new ecdd519c4b7 104: onsuccess: #558: 1: Success after binutils: 3 commits new 487dd11ce68 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new fa959783bd3 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 91de68d93dd 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 40fd4293041 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 34470404b70 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 9e5e09ea0d7 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new f07df9edb97 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 641bfbf90c2 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 99a11ffafad 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 794e2d40476 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 071845be358 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new c3dd05c097c 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 75b8398858c 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 6f4a4fa8afe 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 31e9fb47a37 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new c0f0ae66100 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new c07fa772dfb 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new e997e45c3f6 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 601904098f0 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 21c017457aa 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...]

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 (aea686249a9) \ 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 1692 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52640 -> 53064 bytes 04-build_abe-gcc/console.log.xz | Bin 233908 -> 235860 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9068 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 234564 -> 236228 bytes 08-build_abe-gdb/console.log.xz | Bin 51828 -> 51820 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2472 -> 2956 bytes 11-check_regression/console.log.xz | Bin 8300 -> 6092 bytes 11-check_regression/mail-body.txt | 101 - 11-check_regression/results.compare | 35 +- 11-check_regression/results.compare2 | 190 +- 12-update_baseline/console.log | 38 +- 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 | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2898104 -> 2897516 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2576528 -> 2583872 bytes sumfiles/gcc.sum | 4590 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 955076 -> 952000 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229724 -> 229428 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468520 -> 473236 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2473 insertions(+), 2838 deletions(-)