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 d1bc973eb9 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 9a352d6083 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 31c44aacf3 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards df65621665 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards 33d9721450 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 0b8f89ef74 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 42348654df 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards b11bc1b826 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards bf3985b794 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 06a68a9b73 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards c41e09355e 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 04f9e7675d 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 9d477bcbb4 102: onsuccess: #527: 1: Success after binutils: 5 commits discards e7f9fe1afe 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 19170cd14f 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 2d2bfa11ac 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards ef4a43b8fd 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 10fa29495f 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 4e1c4ff2f4 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 9c227887d0 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 40b8aedc7b 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 1e3f4f938d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 51ba86d720 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards 2fad2365d5 91: onsuccess: #511: 1: Success after linux: 27 commits discards c1e5c88040 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 5f0e3eb8d6 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 198e156da8 88: onsuccess: #506: 1: Success after linux: 34 commits discards 814570d907 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 41b46ce621 86: onsuccess: #503: 1: Success after binutils: 12 commits discards d016c0725e 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards ec6ec91d91 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 678c7c17c0 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards fd5e258080 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards 363d9b0745 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards a4f5eed08e 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 1282e84a32 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 16dc08a108 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 0c79f2ca2c 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 563b6a3c47 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards de182c8995 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards ba29a86892 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards a1c0e496eb 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 2dc550c897 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 872c1447ff 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 8049a77da7 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 22bb55c2d0 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 9ea205e052 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 7533069b05 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards d346da63ea 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards 11e7c16b0f 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards d65fe3ec5f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards e3794ea9b1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 8ee1e6bb05 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards 03a5789de5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 0d5d2a01dd 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards e682b30f49 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards d91e0cdf4f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards b17bd5ea69 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 0272968c72 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 14a6484763 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards be17401897 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards e349d2ed10 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards d3741e630b 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 4188166c81 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 94343e8440 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 7db112db40 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards d8de576c1d 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 05dfbe61d4 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 52ce7bd2d0 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 0657dd3c07 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards f41dc030f5 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards a7df4f81a9 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 9bace4fdc6 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 243079b657 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 2775deedb6 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 9784f76983 39: onsuccess: #447: 1: Success after binutils: 5 commits discards c3dc95126c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards d6a94d17e8 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 6f505f3b6c 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards 02cb21ff68 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 6da9afa820 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 3f02517dbe 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards cdcca4cda8 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards 2b444d61d0 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards ad0052b50c 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 9b59272f7d 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards 2389b257a1 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 0ad16437bd 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards 48e252ad05 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 05ac285d35 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards 0c2ff3aad7 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards 41b6f2fa6d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards b02d5fc829 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e5c95807ad 21: onsuccess: 1: Successful build after linux: 79 commits discards 6903b0f5a4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 38815af82f 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eea1b7a250 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 053acf2229 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c929ae917d 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 521108100e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0489ea685f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ddf1a5b3ab 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2984cc0ee 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc05d268c7 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 250d90bd0d 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 31a89a6793 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ebcade6fa4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e6b0661be 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b1097b7f04 21: onsuccess: 1: Successful build after linux: 79 commits new c54974a24d 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fd1d44f31d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new eea1f30e65 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 525934c3e2 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new e505ed9a1b 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 2e62405c23 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new f31f49ca7b 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 78e3a89a0a 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new 81f946dc6d 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new d236c2bdb3 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 5bcb94235f 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 3dc2d44656 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 7d3cd18e5d 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new db13f24bd6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 59d196cba6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new f905d122cd 37: onsuccess: #443: 1: Success after binutils: 2 commits new 82545ebbce 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new 4fa885e232 39: onsuccess: #447: 1: Success after binutils: 5 commits new fbe3259629 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 825b90411e 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new c15772c8b0 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 741bfe71ce 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 5df1770664 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new f312a45f71 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new c6c577b542 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 22ff01463f 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new b1876ee0a3 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 26dbbaf913 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 7ec916903a 50: onsuccess: #461: 1: Success after binutils: 12 commits new 7a147b8983 51: onsuccess: #464: 1: Success after binutils: 6 commits new 6a17296ab7 52: onsuccess: #467: 1: Success after binutils: 9 commits new 22b4564e5a 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 2a42ef757c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 889e6b950a 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new a18fe6c669 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new e94887a68b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 1416a43e15 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new d53f4ca4e1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 2d443a0be5 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new e8d737998b 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 9a1117e5d8 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 126cca0055 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 402a92b11f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new e4ab053af0 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new 65cac3ca20 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 47bd61d0f9 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 17bf15a21e 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 0782be8a21 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 069bf7b25e 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 18cbabcedd 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 568a539c5e 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 495bc7755f 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new c8e152174c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new cc5c49e133 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new d84e6960d4 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new fa925efc0b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new 215a5b8457 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new dbd2dcea47 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new f6747baa07 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new bcf58ceb47 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 020eb1fb8f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 0fbbf795ae 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 1d75f53edc 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 255a6ffc07 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new c1c5320a04 86: onsuccess: #503: 1: Success after binutils: 12 commits new 28fb424c62 87: onsuccess: #505: 1: Success after glibc: 7 commits new ef222b4f23 88: onsuccess: #506: 1: Success after linux: 34 commits new 559e57cc68 89: onsuccess: #508: 1: Success after binutils: 12 commits new a4df74d899 90: onsuccess: #510: 1: Success after glibc: 5 commits new e8a96102ae 91: onsuccess: #511: 1: Success after linux: 27 commits new 68361c9519 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 3bd67a2b5e 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 4a0b4db593 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new addb25836c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 601f35e054 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new f8174cc8ff 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new e08840d5ba 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new a131affabe 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new a80e4c7fcb 100: onsuccess: #521: 1: Success after binutils: 10 commits new d9f02c05ef 101: onsuccess: #524: 1: Success after binutils: 2 commits new ed51fcccef 102: onsuccess: #527: 1: Success after binutils: 5 commits new aae0309ad0 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 62b430fbe1 104: onsuccess: #530: 1: Success after gcc: 7 commits new 9a3b669dd5 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new 2674b0eb2b 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new dc3d3b8343 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new f0dcca51eb 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new c8b0390629 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new a47483e722 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 988b2e989d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 35a788707c 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new e909816d19 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 5ea08bc738 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 2102d893ed 115: onsuccess: #542: 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 (d1bc973eb9) \ 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 1704 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52796 -> 52656 bytes 04-build_abe-gcc/console.log.xz | Bin 233608 -> 234136 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8300 bytes 07-build_abe-glibc/console.log.xz | Bin 234684 -> 234976 bytes 08-build_abe-gdb/console.log.xz | Bin 52280 -> 51536 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2780 -> 2724 bytes 11-check_regression/console.log.xz | Bin 5768 -> 6104 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 +- 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 62392 -> 62484 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 98036 -> 98052 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131548 -> 131504 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 391 insertions(+), 391 deletions(-)