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 66476be9a5 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards f721711b40 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 7ec1a93f37 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards d70a1d1fe4 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards fec17fbfe7 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 57a0e723a2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards f2d26f3f4e 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 843a8fc553 104: onsuccess: #530: 1: Success after gcc: 7 commits discards ef9bf0196f 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards f5ba2ed8b6 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 294baba708 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 83107ea0cc 100: onsuccess: #521: 1: Success after binutils: 10 commits discards ee9e629d4f 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards cdb7199f3d 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 326e268b7f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 92f241539b 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0dd7affbb7 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 267cae23f9 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 743fc07f04 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards f8a708c5cb 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 563d01d4ce 91: onsuccess: #511: 1: Success after linux: 27 commits discards 6c0f9dd0cb 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 69b14a7336 89: onsuccess: #508: 1: Success after binutils: 12 commits discards ac6c6f36cf 88: onsuccess: #506: 1: Success after linux: 34 commits discards cfc26b86f0 87: onsuccess: #505: 1: Success after glibc: 7 commits discards d89772d26e 86: onsuccess: #503: 1: Success after binutils: 12 commits discards a42cf2a85a 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards e125553eef 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 4b70a89297 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 1a21e5d3b0 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 0f0bc96326 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 87acea9894 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards f6f8a5f72f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 5989ceef9d 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 7359f9cbde 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 59123af4b3 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 6f5a28d125 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 7cba58307e 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 724a2a7bec 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards feeba21157 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 98c7b81463 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 04d18468a0 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards b8a9c95080 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards a5d5a1adfc 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 9d07e3b010 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 3ae7880cf6 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 1102cbbd01 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 2d7c8649f3 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 9ad93e408a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards ebca6863ba 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards fc3a2d6ef5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 9e248c76d4 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards 411e46d6a0 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 775e5b8e7e 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 0bac300b6b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 1674009158 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 8ba1c0d9a2 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 2e48a313d0 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards bf6004df9e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 768f17bcd2 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 792cc50e83 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 63e14afae0 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 51f9005075 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards caabb1f1b1 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards e001246832 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards ed7c99b955 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 897c9c9cd9 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 89a53ac4cb 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards d394abdcf0 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 12c6db7900 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 3928780819 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 2e4869c759 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards be2da42a16 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 949fe3cd6e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards dd0b2658e1 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 9c4ac7295b 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 8b671b1dbf 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 836e9f2d5b 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards b904f7dfee 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards f6f4893a3d 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 9aeaf9bbf0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 871cd4a1f6 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 61f407622c 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards ed05c40275 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards b5cc8935d1 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 38d78bc72b 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards a9bceb4994 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 3c2ff8a742 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards f68d09b28d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards ca49bebf1f 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6714927818 21: onsuccess: 1: Successful build after linux: 79 commits discards 41d78427de 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ccb1ac632f 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a29851e8ca 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f7df094b5 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 61f9649da2 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ddc606dc02 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29de8be289 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ab52e511d5 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a242f7388b 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e9e9444ac4 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3200436e82 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3f7b1b358f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0276cd19da 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e83cff9853 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7ac2475255 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e8a800cbb6 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41ae884f3d 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ddfe77a0e9 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 49ac6b44f7 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0cfe9acd44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7961fcc08 21: onsuccess: 1: Successful build after linux: 79 commits new e7978e1f57 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 060ee68332 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 89cc963ec9 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 45b3b26b7f 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new 7af7bb623c 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 035e852633 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new e062e491ad 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new c915eed763 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 74aeeab4bd 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new ece6a88d79 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new abe9eea959 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 4c8ef27eef 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new d3b4954aa7 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new b574d27ac3 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 2f68099058 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new ab3d93932d 37: onsuccess: #443: 1: Success after binutils: 2 commits new 9b49216f1c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 080aaed2f4 39: onsuccess: #447: 1: Success after binutils: 5 commits new a8f3e6f320 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new ffea22251c 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new 89217527ce 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 1e7277d65c 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 4963be2ce7 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 5655cedc4c 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new d0061daf2b 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 3ab94226cb 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new f53162bcf2 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new f2f78bc7c1 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 50c846d65b 50: onsuccess: #461: 1: Success after binutils: 12 commits new 9ec2fb7520 51: onsuccess: #464: 1: Success after binutils: 6 commits new 078a967ced 52: onsuccess: #467: 1: Success after binutils: 9 commits new a73645bc9f 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new e57ec48991 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 7b93f7165b 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new f94b503063 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new 86639b721b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 9a2a68520f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new fab7bf1cf1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new bce1902b7d 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 9856f27ca2 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new ac4a8ffbe3 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 311c54b3e1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 29a384ad23 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new c979ed308b 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 942a295751 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 63eee4501c 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 6a6f8a6b8f 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new fd140bde0f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new ffd05fbbee 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new c95e76623e 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new f9d939cd34 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 2d698835e1 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new d1b78a3a44 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new cd49c344f6 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 9da22fda0e 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 548363f83f 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 8fef83cbeb 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new edcfcebbaa 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 3484d4a8ef 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new fc12081229 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 8e1be7cf66 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 3af29c3798 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 93987ca758 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 780b5981f1 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 168af27680 86: onsuccess: #503: 1: Success after binutils: 12 commits new 3b63ea5d1c 87: onsuccess: #505: 1: Success after glibc: 7 commits new 55954d5aef 88: onsuccess: #506: 1: Success after linux: 34 commits new def61ddbde 89: onsuccess: #508: 1: Success after binutils: 12 commits new ac827665d2 90: onsuccess: #510: 1: Success after glibc: 5 commits new 678f1940eb 91: onsuccess: #511: 1: Success after linux: 27 commits new 3a088cfd88 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 3d6bd9a79a 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new c132c3df83 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new dbfeaa17e6 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new caa19093bc 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new b79b6b8cc8 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new c2ab5a4c39 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 9d22cba355 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new b73b5a8f63 100: onsuccess: #521: 1: Success after binutils: 10 commits new c8d05b7a2e 101: onsuccess: #524: 1: Success after binutils: 2 commits new 396f352a02 102: onsuccess: #527: 1: Success after binutils: 5 commits new da5bcad3ef 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new dac4b6e7fc 104: onsuccess: #530: 1: Success after gcc: 7 commits new 9104699324 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new a04a2eb674 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 5f1d10cb5b 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new a40cd90b8d 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new c55b665c27 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 460212b7e8 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 844168c63f 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new a4c7fee788 112: onsuccess: #538: 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 (66476be9a5) \ 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 1664 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52008 -> 52820 bytes 04-build_abe-gcc/console.log.xz | Bin 236352 -> 233836 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8344 -> 8540 bytes 07-build_abe-glibc/console.log.xz | Bin 235976 -> 235052 bytes 08-build_abe-gdb/console.log.xz | Bin 51860 -> 51920 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3808 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2176 -> 2612 bytes 11-check_regression/console.log.xz | Bin 5268 -> 5860 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- 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 62760 -> 62912 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98092 -> 98020 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131516 -> 131508 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 29 files changed, 391 insertions(+), 391 deletions(-)