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 d0af5deb57 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards a5c9ca67f6 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards b8056990a5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards f5ce690a54 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 71939dc98a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards be46af1ddd 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 4673605634 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 83c3c31759 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 6e99a01556 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 0769724829 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 8d346792cb 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 1012184d7d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 9e008956a0 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 226172bbbf 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 95331711cb 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards ec009382e6 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards fbfa707a15 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards fe1a5c1703 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 148e4f7e78 91: onsuccess: #511: 1: Success after linux: 27 commits discards 74cd6be632 90: onsuccess: #510: 1: Success after glibc: 5 commits discards fd10c3aea5 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 008df7d471 88: onsuccess: #506: 1: Success after linux: 34 commits discards a01032d3a0 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 7db2e4791c 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 0a3900adb5 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 1bf61e6634 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards df234bb994 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards e894bc99ff 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 96bd98cc9c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 875d29db23 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 976d6ed284 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 92e2328345 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards af8602111e 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 8d3907205a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 83edea58d0 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 732b0f0343 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards c53e7d8658 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 37a80a5487 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 87da74b40f 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 7bd02f3eeb 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 57466b732e 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards e9688ab0ed 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 1a941cc0f0 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards eb155e4b0a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 531b79c34a 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards dbc7b97132 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards b9e1ada0ce 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 0f79e8bc08 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 66e1f2c276 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 60de58428e 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards b62faa5ea8 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards aede2b8a8a 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards ed6cc3d1b8 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 3c6f8083d4 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 1d955f99df 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 779b6f81e1 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 6773cc4ec4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 176f3613cc 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 62c897e8bf 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 82e3d9b317 50: onsuccess: #461: 1: Success after binutils: 12 commits discards c867df8c64 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 22892e9d5f 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 25ed65debf 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 0fb469a26b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 11f932f57d 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards e7c3612ae6 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 9e3a2e9e8f 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards fb0ec9e5a3 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards b0e7326c52 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 1f6bcdbef8 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 102b5cbac5 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 833906f841 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards 5b24468310 37: onsuccess: #443: 1: Success after binutils: 2 commits discards c2f68f4e60 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 0814d7566f 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards c4c91c37a3 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards c4a64dceef 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 9f4a2dcced 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards b97904859c 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 7bb7f6a6b8 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 75d8da61b6 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 03a6ddfea5 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 01db5635c0 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 57b8b04bdd 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 3d928bdedc 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards f44293ef31 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards ad2cb73833 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f188f244b2 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c81758a874 21: onsuccess: 1: Successful build after linux: 79 commits discards b5c8f95f59 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 599b3c005e 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1edb5cdf69 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77d3431ca2 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ad74332b24 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 03535c8028 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4491fb113 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2257e45d1e 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fde594219f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6cb6e3d19b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7cd391f436 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8bedb56ecf 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 113f757d04 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fcd760faf4 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f5be402a85 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6dae99d77d 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0642f48c64 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 32d1a43af6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 580bddb62e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9248d81b07 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f87634f3ec 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ea1b6e2b1 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 43e067debb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d384945dcb 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a64117b45 21: onsuccess: 1: Successful build after linux: 79 commits new a03c5cde71 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d47c5511e 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9b20bc7c11 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new ed8d9c6534 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new c7a5ef1e2d 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new fdd87720b5 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 65e2842fc8 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 713a1beb83 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new ff953c670c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new 89a98f4180 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new bbacd50232 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 76173ae81b 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 439b5b2919 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new d5d96b303d 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 833be0e97d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 8fc7748dc8 37: onsuccess: #443: 1: Success after binutils: 2 commits new 98866b0cda 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 678a024f72 39: onsuccess: #447: 1: Success after binutils: 5 commits new 25a7e8dd39 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 6d1b248cc0 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new a37b157081 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 96419428a7 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 7f6cb1bacd 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 7e7031fd16 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 16798529fb 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 5a9a959017 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 70187b7e33 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new bbd37f04af 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 242f6edc73 50: onsuccess: #461: 1: Success after binutils: 12 commits new d6f07cca46 51: onsuccess: #464: 1: Success after binutils: 6 commits new 891db5f263 52: onsuccess: #467: 1: Success after binutils: 9 commits new feeb12e415 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new b7fbb6e4c7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new ae7b74d944 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 3bf4ded5d0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 533deedda6 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new cbb2e1c8c6 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new c389d5db82 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 9c371b3ea1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 9c57f9edc5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 8cf0820d6c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 7cbf3c9f85 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new abb2555019 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 542f0c0036 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 5d0b7a84d5 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 825b1a844e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 5eea50c266 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new e2dc25f36b 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new bdd6cbe3a9 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 93f5a2cdd4 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 58634318d5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 2c7bb17a69 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 0b41ebdb4f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 943ac455ad 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 249ab0fd8b 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new fe6878b509 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 1ceff7bfe2 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 7a0f04ccc8 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 3801a43188 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new a56dae8f3e 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e4910cbf54 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 2edd0dbd35 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new ade150a175 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 5c3c926026 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 1684b7b4f7 86: onsuccess: #503: 1: Success after binutils: 12 commits new 630d27f0df 87: onsuccess: #505: 1: Success after glibc: 7 commits new f33e2b7032 88: onsuccess: #506: 1: Success after linux: 34 commits new c690305bc3 89: onsuccess: #508: 1: Success after binutils: 12 commits new 62625c11b7 90: onsuccess: #510: 1: Success after glibc: 5 commits new 7420d1881b 91: onsuccess: #511: 1: Success after linux: 27 commits new cc57cc19be 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 850c3dd742 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new d75043b229 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new e5418c9777 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 7e23e51f76 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 4ef55c11d8 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 274e5aeb4c 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new d18e0df2b5 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 82c8bb0258 100: onsuccess: #521: 1: Success after binutils: 10 commits new 58cdf877d9 101: onsuccess: #524: 1: Success after binutils: 2 commits new d0c64af967 102: onsuccess: #527: 1: Success after binutils: 5 commits new 91ce07dbf8 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new bd46a610d9 104: onsuccess: #530: 1: Success after gcc: 7 commits new ddd2861d2a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 120ecf07b2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 681a6f4af5 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new fa769a2acc 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new b0914f6421 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 37bc5dc66e 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/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 (d0af5deb57) \ 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 1676 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52176 -> 52976 bytes 04-build_abe-gcc/console.log.xz | Bin 234268 -> 233716 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8320 -> 8376 bytes 07-build_abe-glibc/console.log.xz | Bin 235268 -> 235516 bytes 08-build_abe-gdb/console.log.xz | Bin 51592 -> 50940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2216 -> 2200 bytes 11-check_regression/console.log.xz | Bin 5760 -> 5692 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 34 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +-- sumfiles/binutils.log.xz | Bin 62300 -> 61984 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98144 -> 98056 bytes sumfiles/gas.sum | 270 +++++++++++----------- sumfiles/ld.log.xz | Bin 131520 -> 131532 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 388 insertions(+), 388 deletions(-)