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

discards 6ebb74e6f8 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 23e26e560c 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 07e84733f5 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 11e9c9d7eb 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 2f53b27b5a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 85cae550ea 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 45c90a5bac 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 892a58480e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards c4cab788c9 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards 08debf4778 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards fd32552f2c 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 02518b7946 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 868ce3078e 104: onsuccess: #530: 1: Success after gcc: 7 commits discards e9a9ad1277 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 6343fd16ae 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 6071fb4ab0 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 67d6142b7e 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 05d2c1b242 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards d95964835f 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 6cb2eb9b5a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards c1dffd138c 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards f22dd2e8cf 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards dda1511c2d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 8e54cbe6b7 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards cd77777a47 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 54be2cd5ad 91: onsuccess: #511: 1: Success after linux: 27 commits discards 39ebc422d1 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 8ba691c6b2 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 4750b0769e 88: onsuccess: #506: 1: Success after linux: 34 commits discards 6851689ea3 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 5fd3ea1528 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 429edc58a6 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 2a474c5004 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 3f6aa93332 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards b571308bf8 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards b6a0f67231 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 9e048cbe61 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 8b13f1778b 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards e940d78da5 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 09dfb63557 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 53ecca235a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 7f1e9addc4 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards dda7e20b00 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 3040bcc4a2 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 611933324a 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 10d510c348 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 10f74fbe28 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards ca6463cdf3 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards c5652a23c5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 499348fc4f 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards afbd5bf327 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 1cbda13a54 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards f2ae37130e 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 5ce00eddf5 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 8b0c90321e 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 373bcc7c99 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 392764a2ec 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 95403630f1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards c7916a5d9f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards b202f6a564 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 4e2c752b4d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 4b159f5e47 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 84941cddd2 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards a5e39f5d8d 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 77dc44975d 52: onsuccess: #467: 1: Success after binutils: 9 commits discards b2fc2173c0 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 5c0d27421e 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 8771823f9e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 51a86caad7 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 00fb30adc3 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 68b07092d3 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards a62b1396ba 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 8e59f79da3 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards e80f066dbe 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards a897692ccc 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards f18e5d9abe 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 6c75eabe5b 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards a1d1e81b99 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 47fcfcab6e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 019fdd5b9c 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 0007b9fe83 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 10c8cad61c 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 90a69a4283 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 48912dc96a 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 82fc11f842 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards ce0d23de1f 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards aa2b728c55 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 19a2d0bf2f 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 3fe11bf9a2 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 943b3c9d0b 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards e22d3e82b6 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 878264e949 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 706388feab 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards be8aca40a9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 27244a68cf 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 235a6cb1e3 21: onsuccess: 1: Successful build after linux: 79 commits discards 016a42a82c 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1cbb43f337 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 68f65d8ca5 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c96c2d6a95 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7f68278c77 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04db2cc3e7 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5a861d27b5 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a2148f73eb 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 258fed9182 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e497b4f51 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e821b51f5f 21: onsuccess: 1: Successful build after linux: 79 commits new 9ef283606c 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0727fab6a9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 2b101e5a85 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 3d806134c2 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new bc239294c6 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new a5b6c5b7aa 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 042d319b07 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 8045dc4375 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new d4a6349307 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new d9c4ca59f6 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 823fecb3db 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new e586638346 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 51e59fba2d 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new e0f51b497c 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new fe903498f3 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 137a351850 37: onsuccess: #443: 1: Success after binutils: 2 commits new cb775541e8 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 54cf8c1e23 39: onsuccess: #447: 1: Success after binutils: 5 commits new c85f4ac660 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new d0d2460310 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 9477907f72 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 2c4d0eb4e3 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new ffd8d75c12 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new c866a81e30 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 832ab41cc7 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 9d4b3bd43c 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new de53f05c03 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 7f0a1d5f76 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 29aa48536f 50: onsuccess: #461: 1: Success after binutils: 12 commits new b0081ee11f 51: onsuccess: #464: 1: Success after binutils: 6 commits new 5e89a3986d 52: onsuccess: #467: 1: Success after binutils: 9 commits new 5c111bd8e9 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new b479998645 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 73f59ec9f9 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new a4183baf26 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new b859477cce 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new dd264dfd2f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new bbfcab3d70 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new f03a23fec3 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 13058b890a 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 8fbec3c477 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 368f6176f3 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new e747ff53fb 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new bb48ea1c2e 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new bc716236a9 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 6203ec2ffb 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new c818c63ee6 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 0e53167b4e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new ed5fa0b62d 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new ca94f3fe98 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new a4fdde7dd2 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 5c460e0779 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new ffe1cc3503 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 74cffff7bb 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 6a81afaf51 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 1384e5fc45 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 713740482f 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 897f5f92df 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new e72b7626c3 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new e0f63251ee 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 474530238e 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 804b282f92 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ca76b394e7 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 8c571d4270 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 060f758703 86: onsuccess: #503: 1: Success after binutils: 12 commits new 803b050343 87: onsuccess: #505: 1: Success after glibc: 7 commits new a9c39c7de5 88: onsuccess: #506: 1: Success after linux: 34 commits new cc00aba6bb 89: onsuccess: #508: 1: Success after binutils: 12 commits new 10f2947775 90: onsuccess: #510: 1: Success after glibc: 5 commits new 1f888c8fd0 91: onsuccess: #511: 1: Success after linux: 27 commits new d4fd7977f3 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 55650db56d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new c49527d68f 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new daa9821789 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 045d3ed316 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new d992c920cb 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new ba26645748 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new d96fc018be 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 12e640f21a 100: onsuccess: #521: 1: Success after binutils: 10 commits new 4998bdd0fe 101: onsuccess: #524: 1: Success after binutils: 2 commits new 7d81bf8e4d 102: onsuccess: #527: 1: Success after binutils: 5 commits new 3fe9707d08 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 0930921942 104: onsuccess: #530: 1: Success after gcc: 7 commits new 6f224892f1 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 41cf3f0fb2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new ffa885ed1b 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 5e574179ca 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 121a1b86e1 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 2b89e5b2d9 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new d5c1e22b56 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new b568fc1b70 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 5a4cee90d8 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 8462404dbf 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 43abccf6fd 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 6ff975fdff 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 3ad64bbbd0 117: onsuccess: #544: 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 (6ebb74e6f8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52184 -> 52200 bytes 04-build_abe-gcc/console.log.xz | Bin 233224 -> 234104 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 9504 bytes 07-build_abe-glibc/console.log.xz | Bin 234860 -> 236596 bytes 08-build_abe-gdb/console.log.xz | Bin 51596 -> 50960 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2088 -> 2128 bytes 11-check_regression/console.log.xz | Bin 6256 -> 6144 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 64 +++--- 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 62464 -> 61876 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 98072 -> 98292 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 131636 -> 131684 bytes sumfiles/ld.sum | 348 ++++++++++++++--------------- 30 files changed, 411 insertions(+), 419 deletions(-)