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 2102d893ed 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 5ea08bc738 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards e909816d19 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 35a788707c 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards 988b2e989d 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards a47483e722 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards c8b0390629 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards f0dcca51eb 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards dc3d3b8343 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 2674b0eb2b 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 9a3b669dd5 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards 62b430fbe1 104: onsuccess: #530: 1: Success after gcc: 7 commits discards aae0309ad0 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards ed51fcccef 102: onsuccess: #527: 1: Success after binutils: 5 commits discards d9f02c05ef 101: onsuccess: #524: 1: Success after binutils: 2 commits discards a80e4c7fcb 100: onsuccess: #521: 1: Success after binutils: 10 commits discards a131affabe 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards e08840d5ba 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards f8174cc8ff 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 601f35e054 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards addb25836c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 4a0b4db593 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 3bd67a2b5e 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 68361c9519 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards e8a96102ae 91: onsuccess: #511: 1: Success after linux: 27 commits discards a4df74d899 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 559e57cc68 89: onsuccess: #508: 1: Success after binutils: 12 commits discards ef222b4f23 88: onsuccess: #506: 1: Success after linux: 34 commits discards 28fb424c62 87: onsuccess: #505: 1: Success after glibc: 7 commits discards c1c5320a04 86: onsuccess: #503: 1: Success after binutils: 12 commits discards 255a6ffc07 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 1d75f53edc 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 0fbbf795ae 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards 020eb1fb8f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards bcf58ceb47 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards f6747baa07 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards dbd2dcea47 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 215a5b8457 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards fa925efc0b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards d84e6960d4 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards cc5c49e133 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards c8e152174c 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 495bc7755f 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 568a539c5e 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards 18cbabcedd 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 069bf7b25e 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards 0782be8a21 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 17bf15a21e 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 47bd61d0f9 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 65cac3ca20 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards e4ab053af0 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 402a92b11f 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 126cca0055 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards 9a1117e5d8 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards e8d737998b 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 2d443a0be5 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards d53f4ca4e1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards 1416a43e15 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards e94887a68b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards a18fe6c669 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards 889e6b950a 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 2a42ef757c 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards 22b4564e5a 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards 6a17296ab7 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 7a147b8983 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 7ec916903a 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 26dbbaf913 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards b1876ee0a3 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 22ff01463f 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards c6c577b542 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards f312a45f71 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards 5df1770664 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards 741bfe71ce 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards c15772c8b0 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 825b90411e 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards fbe3259629 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 4fa885e232 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 82545ebbce 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] discards f905d122cd 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 59d196cba6 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] discards db13f24bd6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] discards 7d3cd18e5d 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] discards 3dc2d44656 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] discards 5bcb94235f 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] discards d236c2bdb3 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] discards 81f946dc6d 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] discards 78e3a89a0a 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] discards f31f49ca7b 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] discards 2e62405c23 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] discards e505ed9a1b 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] discards 525934c3e2 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] discards eea1f30e65 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits discards fd1d44f31d 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c54974a24d 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b1097b7f04 21: onsuccess: 1: Successful build after linux: 79 commits discards 2e6b0661be 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ebcade6fa4 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 31a89a6793 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 250d90bd0d 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bc05d268c7 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e2984cc0ee 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f0896f2035 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f68278c77 16: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c96c2d6a95 17: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 68f65d8ca5 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cbb43f337 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 016a42a82c 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 235a6cb1e3 21: onsuccess: 1: Successful build after linux: 79 commits new 27244a68cf 22: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new be8aca40a9 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 706388feab 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 127 commits new 878264e949 25: onsuccess: #430: 1: Success after binutils/gcc/linux/gdb [...] new e22d3e82b6 26: onsuccess: #431: 1: Success after binutils/gcc/linux/gdb [...] new 943b3c9d0b 27: onsuccess: #432: 1: Success after binutils/gcc/linux/gdb [...] new 3fe11bf9a2 28: onsuccess: #433: 1: Success after binutils/gcc/linux/gli [...] new 19a2d0bf2f 29: onsuccess: #434: 1: Success after binutils/gcc/linux/gli [...] new aa2b728c55 30: onsuccess: #435: 1: Success after binutils/gcc/glibc/gdb [...] new ce0d23de1f 31: onsuccess: #436: 1: Success after binutils/gcc/linux/gli [...] new 82fc11f842 32: onsuccess: #437: 1: Success after binutils/gcc/linux/gli [...] new 48912dc96a 33: onsuccess: #438: 1: Success after binutils/gcc/linux/gdb [...] new 90a69a4283 34: onsuccess: #439: 1: Success after binutils/gcc/linux/gli [...] new 10c8cad61c 35: onsuccess: #440: 1: Success after binutils/gcc/linux/gli [...] new 0007b9fe83 36: onsuccess: #441: 1: Success after binutils/gcc/linux/gli [...] new 019fdd5b9c 37: onsuccess: #443: 1: Success after binutils: 2 commits new 47fcfcab6e 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120-g9 [...] new a1d1e81b99 39: onsuccess: #447: 1: Success after binutils: 5 commits new 6c75eabe5b 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new f18e5d9abe 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new a897692ccc 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new e80f066dbe 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 8e59f79da3 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new a62b1396ba 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 68b07092d3 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 00fb30adc3 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 51a86caad7 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 8771823f9e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 5c0d27421e 50: onsuccess: #461: 1: Success after binutils: 12 commits new b2fc2173c0 51: onsuccess: #464: 1: Success after binutils: 6 commits new 77dc44975d 52: onsuccess: #467: 1: Success after binutils: 9 commits new a5e39f5d8d 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new 84941cddd2 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new 4b159f5e47 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 4e2c752b4d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new b202f6a564 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new c7916a5d9f 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new 95403630f1 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new 392764a2ec 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new 373bcc7c99 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 8b0c90321e 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 5ce00eddf5 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new f2ae37130e 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 1cbda13a54 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new afbd5bf327 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 499348fc4f 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new c5652a23c5 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new ca6463cdf3 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 10f74fbe28 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new 10d510c348 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 611933324a 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 3040bcc4a2 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new dda7e20b00 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new 7f1e9addc4 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 53ecca235a 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 09dfb63557 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new e940d78da5 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 8b13f1778b 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 9e048cbe61 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new b6a0f67231 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new b571308bf8 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new 3f6aa93332 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 2a474c5004 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 429edc58a6 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 5fd3ea1528 86: onsuccess: #503: 1: Success after binutils: 12 commits new 6851689ea3 87: onsuccess: #505: 1: Success after glibc: 7 commits new 4750b0769e 88: onsuccess: #506: 1: Success after linux: 34 commits new 8ba691c6b2 89: onsuccess: #508: 1: Success after binutils: 12 commits new 39ebc422d1 90: onsuccess: #510: 1: Success after glibc: 5 commits new 54be2cd5ad 91: onsuccess: #511: 1: Success after linux: 27 commits new cd77777a47 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new 8e54cbe6b7 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new dda1511c2d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new f22dd2e8cf 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new c1dffd138c 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 6cb2eb9b5a 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new d95964835f 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 05d2c1b242 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 67d6142b7e 100: onsuccess: #521: 1: Success after binutils: 10 commits new 6071fb4ab0 101: onsuccess: #524: 1: Success after binutils: 2 commits new 6343fd16ae 102: onsuccess: #527: 1: Success after binutils: 5 commits new e9a9ad1277 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 868ce3078e 104: onsuccess: #530: 1: Success after gcc: 7 commits new 02518b7946 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new fd32552f2c 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new 08debf4778 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new c4cab788c9 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 892a58480e 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new 45c90a5bac 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 85cae550ea 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 2f53b27b5a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 11e9c9d7eb 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 07e84733f5 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 23e26e560c 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 6ebb74e6f8 116: onsuccess: #543: 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 (2102d893ed) \ 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 1752 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52656 -> 52184 bytes 04-build_abe-gcc/console.log.xz | Bin 234136 -> 233224 bytes 06-build_abe-linux/console.log.xz | Bin 8300 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 234976 -> 234860 bytes 08-build_abe-gdb/console.log.xz | Bin 51536 -> 51596 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2724 -> 2088 bytes 11-check_regression/console.log.xz | Bin 6104 -> 6256 bytes 11-check_regression/results.compare2 | 18 +++++--- 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 62484 -> 62464 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 98052 -> 98072 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 131504 -> 131636 bytes sumfiles/ld.sum | 7 ++-- 28 files changed, 79 insertions(+), 70 deletions(-)