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 48e70a22a2 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards f04b513417 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards b2179b6a59 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 7e9e1c8fcc 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 4039d3a9d2 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards eadb43fa94 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 9fa7ef5d67 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 5eff371ab2 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 13a5d41f84 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 48906f5f8d 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards f92d6abfa3 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards c384b54312 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards d945f65d05 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 6ec55e04ab 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards 1887bb3af5 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 01e919b2ae 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards e466cde023 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 59f7cb1d88 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards dc12d229e8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards 3bf5601089 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 30aaac4e1a 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards f02660d514 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards f64c2f4368 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 505494b3e8 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards ef76d04715 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 15fc40fb21 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards c771dd3eb2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 8a59b9290c 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 7a4bb0bcce 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards fac062e5e9 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards c7de524883 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 88bff2d9ab 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards e3ca6d6776 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards a51e1be137 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards a5e27970be 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 0315910c9a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards c41076b6ea 104: onsuccess: #530: 1: Success after gcc: 7 commits discards a967a788d5 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 35314f1eb6 102: onsuccess: #527: 1: Success after binutils: 5 commits discards f0ca82864c 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 039863e323 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 76b9c8f5d9 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 624a6a3036 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards aaaf86e312 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 72dd3af9ba 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 43f3e453a8 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards d888c43039 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards aeab9e6f15 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 65e96e1ae9 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards fdc7012606 91: onsuccess: #511: 1: Success after linux: 27 commits discards b31f74818a 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 8acff65794 89: onsuccess: #508: 1: Success after binutils: 12 commits discards a30f031add 88: onsuccess: #506: 1: Success after linux: 34 commits discards 4d23ec1a46 87: onsuccess: #505: 1: Success after glibc: 7 commits discards c3b561c92d 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 920317dfdf 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 57f8bf8629 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards b371e92d98 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards af5b5ce18d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards c6eb3e9881 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 7bf2bec380 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 7657b0e445 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards b239434b79 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 65d9b0efe5 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 02fc581d04 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards e5e881120a 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 13a25c378b 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 5061e4c75e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 5a506c8152 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards c335354f3c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards d41d073a97 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 54e0a1c658 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 5535e84d65 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 1a5ab6639e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards fcd52f7c94 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 58ff13fc9c 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 6eb661763c 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 6b786f67c1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 483b197d95 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards b258bc7ef8 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards d72f0a6bff 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards b2cd5d98a2 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 5441204552 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards dab8020e2e 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 616ca514ec 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards c02f890d88 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards e4fb8885c7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 096b2a8f9e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 56c9e7ec38 52: onsuccess: #467: 1: Success after binutils: 9 commits discards c0877b90d6 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 5d241c1384 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 60aa750228 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 9a656c0753 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 8c2e78f12e 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0d15a240a5 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 3c43bc6381 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 049c71b775 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 801b3d9d2a 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards c74409cdd1 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 8538cc11d6 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 86a7b0a418 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new c9b23d5ca8 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new b71386832b 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 36d6c8e09a 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 441bf76440 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 0c4d826570 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 57fbbc6127 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new e308d2bb2e 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 0041fb8078 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 7df003efde 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 91ec327869 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 708863062b 50: onsuccess: #461: 1: Success after binutils: 12 commits new c41b7460a5 51: onsuccess: #464: 1: Success after binutils: 6 commits new ed26630d4f 52: onsuccess: #467: 1: Success after binutils: 9 commits new 8913a39c45 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 9864eb5041 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new b9325b37d5 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 958c79b9d5 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new f6b5b8f783 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 003096a387 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new c8525d8606 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 7b866360b6 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new e638621290 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 1c4f863e1c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 6f04555533 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 0084681744 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 575ef74ab1 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new a08491a3a1 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 6caef250b0 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new a9f19f3e35 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new cc2cbce371 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 1ab54f3a45 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 7e1077fc22 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 9c060091fb 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new c5c57d2312 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 5257530cec 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 809a0ce1dc 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 7a0719f074 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 49aee44ada 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 1930774729 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 78575b13f4 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new b002a62c12 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 71a107223b 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 145d8b9703 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 36f1dcbc00 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new a29a3b0115 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 5007cafe7e 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 7d5cef0fb2 86: onsuccess: #503: 1: Success after binutils: 12 commits new c09fa1070c 87: onsuccess: #505: 1: Success after glibc: 7 commits new 8a162c64be 88: onsuccess: #506: 1: Success after linux: 34 commits new cb50b9b405 89: onsuccess: #508: 1: Success after binutils: 12 commits new 81e6ccb476 90: onsuccess: #510: 1: Success after glibc: 5 commits new 5379ae563f 91: onsuccess: #511: 1: Success after linux: 27 commits new b85a653259 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 57f8c653ab 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 9bb7b9a296 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 619b767a27 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new f0eb129b67 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 241f830efa 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d50e5e4925 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 36ded76503 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new e7808bf31d 100: onsuccess: #521: 1: Success after binutils: 10 commits new 0903682768 101: onsuccess: #524: 1: Success after binutils: 2 commits new 560f54d0d4 102: onsuccess: #527: 1: Success after binutils: 5 commits new 52099bb132 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 4802054293 104: onsuccess: #530: 1: Success after gcc: 7 commits new 1a17cc6966 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new ee27906f26 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new e577797688 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 3391fa2370 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 7491b659f0 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new f19dfabbcd 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 4522338539 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new ba0831f89c 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new d6794cdc43 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 27fea9b0c3 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 547a2602fe 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new fa46b38791 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 2c2b92c289 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new d00b881425 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new f5bda8412c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new 556a73f471 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new b3fc60b511 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 4d9c1587de 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new 8b0997b291 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new 007a884d30 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 8b40c51f4c 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 13fe4ac5bb 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 499b43c89d 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new 7ba1e82a54 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new a673187de9 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new a2859c6c1d 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 27076455ce 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new d773c9754a 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 5e7cd4fb13 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 83b9378d9f 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 2636833f27 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 5a9745b59f 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 77632b00b0 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new d83df6e930 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new a6f374b368 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new a0ead1b17a 140: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 43d9d36c43 141: onsuccess: #568: 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 (48e70a22a2) \ 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 1736 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52416 -> 52580 bytes 04-build_abe-gcc/console.log.xz | Bin 238636 -> 237428 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 236760 -> 236940 bytes 08-build_abe-gdb/console.log.xz | Bin 51600 -> 52452 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3864 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2180 -> 2424 bytes 11-check_regression/console.log.xz | Bin 6240 -> 5808 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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/binutils.log.xz | Bin 62576 -> 62624 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100504 -> 100420 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132416 -> 132216 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 389 insertions(+), 389 deletions(-)