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 ec28f3e279fa 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] discards c3cd293aaa30 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards a0cab2017bff 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards ef0016ddeace 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 6d182c7ad4d1 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards ec954b1ba136 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 7d5e389b8688 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards 705ae7edfe05 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 8790bc273839 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards 4fc9cef0a9d8 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 41ce5cc696de 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards b39197b38bfd 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 5f384ccc0cb0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards daa77acdab10 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards 3d7ae1f5dde1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards 01fea0e62b84 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards b560f15cee8e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 901f1e640a8c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards 77b41ff954e4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards 66b5c8d250b4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards 238801df883a 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards 2d12cd08c048 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards d3508cf47927 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards 5f1d9826fa69 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards 9c7e657f01de 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards d7b743a9cdbf 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards c27c5b561bf2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 36760a9ba357 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards a292b57b8c7e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 3be30f738fc9 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards c2680b15d38f 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards 8f09862f1d4a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards 195f31ea1550 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 3c7cf7ba22ae 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards 6ed92b0a87a9 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 9817a0c225ae 101: onsuccess: #524: 1: Success after binutils: 2 commits discards c8ecb12e9653 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 567c142bbb2b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 55f94f2c8843 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 1adecb38bf7d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards b09ca7315f12 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 57e4e79153e7 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards f33f72c87465 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards fd61d3f41afd 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards ea0df8f82109 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards bcf9bb557fdf 91: onsuccess: #511: 1: Success after linux: 27 commits discards 978743f153d3 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 76c9ae7cdf2d 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 718bad62d41a 88: onsuccess: #506: 1: Success after linux: 34 commits discards ccd74f9ec89b 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 1f542935bfa5 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 0b67dadd7daf 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards c4c5669d6c77 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 2d94790f7c86 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards f79045da077f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards e1b9194cf20c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards eca4a25c6649 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards 60b2f1d32901 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 7b61f9a43b9c 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 72dfc992ae6b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 52f62c15e11d 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards 8e4165cbc9c5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards 5aae552fbaab 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards 786e22fc8be5 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards c47c1650fc05 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 38cabde2400c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards e818496f2630 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 33754cbaa00f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards dc6bbbeeb327 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 715277249522 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards da79f8515f7a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards 81be72cc9175 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards 29729adb6489 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards efe90f3ef6b6 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards ba7376a4826d 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards 4e36e0779324 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards 06cf450f99a2 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards 96b5f9ed7337 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards bf5c6e114d39 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards b26c6828d59b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 1c3276a7d33d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards a268d19b6f78 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards e8a0fa9a428e 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards 8fbced2099b3 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards b557e5332a54 52: onsuccess: #467: 1: Success after binutils: 9 commits discards faeb43f7b53f 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 792d08ec9ce7 50: onsuccess: #461: 1: Success after binutils: 12 commits discards af07923b3867 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards 21f9e13a0f65 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 4971bead3af0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards 37ac922f5684 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards dde4c09e530a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards 39931572c474 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards 5909889d0865 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards e19320b6ccce 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards 56e3032e9ac5 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards 9deb0ab2f462 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 2680a2bae18d 39: onsuccess: #447: 1: Success after binutils: 5 commits discards e43eedf3b5d2 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards 6d8c762c5c34 37: onsuccess: #443: 1: Success after binutils: 2 commits discards faac4d38f24d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new b52fc27d59a0 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new b53ee0e6e525 37: onsuccess: #443: 1: Success after binutils: 2 commits new 751279e885f7 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 951af30222f8 39: onsuccess: #447: 1: Success after binutils: 5 commits new 0e302a4e892a 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 5898f16a11aa 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new 49884f8b591a 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new abcadcd0f193 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 625f2bf7ade1 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new b9180883f52c 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 5767c1f854a7 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new c58ae4671805 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new 574a03f60bbc 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new 66ad428c8a63 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new c43f432c26eb 50: onsuccess: #461: 1: Success after binutils: 12 commits new 78e881221b9c 51: onsuccess: #464: 1: Success after binutils: 6 commits new c8d281bf0480 52: onsuccess: #467: 1: Success after binutils: 9 commits new 183323b65bb5 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new 22c2b6f1d54e 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new 174b94961bb6 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new cfecd5051030 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new 0e8d71ca4888 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new dd005179b90a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new a68dfd7ec33e 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new e80a2a281840 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new a860a946eb2e 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new f92da1d87ab9 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 911a7ac1738e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new 233df5128843 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new c4983f254340 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 14e25f7e6817 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new f9bec8855c1d 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 85f1e7f0d03e 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new d5a8ace01dbe 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new ced905bbf702 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 88618a98020e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new b3dec44253de 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new f0dddc34f088 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new 14386884534c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new 3ea5e0c11272 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new ba402309ac48 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new d0022390ec53 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new c25d54e2eb0a 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new 21342b487a81 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 1d066409960c 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 83e795497c08 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 7f32bfb3f4dc 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 4302d75fa77b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new fc2dc07e1458 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new a818fb73ccb3 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 8be92f57464e 86: onsuccess: #503: 1: Success after binutils: 12 commits new d461c5e50631 87: onsuccess: #505: 1: Success after glibc: 7 commits new d276829efd34 88: onsuccess: #506: 1: Success after linux: 34 commits new a39187929b18 89: onsuccess: #508: 1: Success after binutils: 12 commits new aacaf0a1346f 90: onsuccess: #510: 1: Success after glibc: 5 commits new c8567462abe6 91: onsuccess: #511: 1: Success after linux: 27 commits new 872b362d4e8c 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 6388da10c333 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 62b1d7996f17 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 1ef8428f751c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new b80d8c172ce7 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 76ee30049c6f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new ca5570ebfaff 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new eaa7b66bc9b8 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new a26eb4fd9c5c 100: onsuccess: #521: 1: Success after binutils: 10 commits new 183990b6460a 101: onsuccess: #524: 1: Success after binutils: 2 commits new 41a5bab5bb04 102: onsuccess: #527: 1: Success after binutils: 5 commits new 18f1052568f3 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new 7e5c1be6b32a 104: onsuccess: #530: 1: Success after gcc: 7 commits new 3a9eec330c1d 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new 07df3328b7ba 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new cb5c20d59077 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new 47a8b4c03e5d 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 166d2c6ec99e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new 70ce05933c3e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new beadfe229d42 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 5b0870ee2b85 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new 49cbf51c36cf 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new 7e0334c77bb6 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new a5b59a2d3371 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 459ed2146e64 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new 1384fb027e0e 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new 035ea0dcb21c 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 742cf655a560 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new 178457252eb6 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new c63d42df4b14 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 25ba14c7bf95 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new 35a0a2d6f676 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new 69ae87b2a2c8 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new 7ae999efdc61 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new b876a94256f6 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new 8b462fdc64ed 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 2693dec1f1a4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new b9986bef2adb 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new a85c838ddfdc 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new b8e800d59a49 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new e181f42628cb 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new befe8ff7fa54 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new e2a9963b3b94 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 36397ec97934 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 1437d9d888ff 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...] new c8c44bc171e3 137: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...]
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 (ec28f3e279fa) \ 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 1756 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52608 -> 52600 bytes 04-build_abe-gcc/console.log.xz | Bin 234688 -> 234248 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 9200 bytes 07-build_abe-glibc/console.log.xz | Bin 236496 -> 237924 bytes 08-build_abe-gdb/console.log.xz | Bin 51912 -> 51904 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2088 -> 2236 bytes 11-check_regression/console.log.xz | Bin 5736 -> 6204 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 27 +-- 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 | 36 +-- sumfiles/binutils.log.xz | Bin 62664 -> 62704 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100532 -> 100392 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132168 -> 132136 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 409 insertions(+), 422 deletions(-)