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 6b3a796882bd 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 0e2959e83c66 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards 6a954c0f76b4 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards f8b47cc43fac 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards 67d1bf80bca9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 6fc331c81978 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards ffd4267ec75e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 525d5e5dd6db 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards 6754adf3370e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 95e2d2ddf227 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards 1d628213f5ff 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards ffe927749853 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards ce1300b74d5c 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards 0f6bf8be8fd1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards 69241f8bec4e 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards 74fe498f8d8b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 777251ba8779 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards b0f8c505e7e8 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards b80b2657f2e9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards 69090530c681 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards 5a86c3b51906 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards 278921be3d65 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards af2e1b4bd381 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards 12bb00604f7e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards ee3aefeb83b4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards 0207eec44f01 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 57de20f52d77 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards 6b3417d3f196 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 6798eb290a05 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards ca254fc61bd6 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards 81b9e153d627 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards 2a1883995705 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 68d310562756 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards b3641cf8b7cb 102: onsuccess: #527: 1: Success after binutils: 5 commits discards f949d68be93f 101: onsuccess: #524: 1: Success after binutils: 2 commits discards d5e761b3e740 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 32ecf69a9a49 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 0ec6c1a56c7a 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 5febcf98b270 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 598ca8963b18 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 8059d933f17c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 4135ed7aec7d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 0778b87c86ca 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards 502fe57adea4 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards 7046008b6bb2 91: onsuccess: #511: 1: Success after linux: 27 commits discards e82d12750e87 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 71f6ddeeb7d5 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 7a17c13d39bb 88: onsuccess: #506: 1: Success after linux: 34 commits discards e55113e4b3cb 87: onsuccess: #505: 1: Success after glibc: 7 commits discards a36fdc63bd5c 86: onsuccess: #503: 1: Success after binutils: 12 commits discards a5cc9a108456 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 97d4c8ed4245 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 90824e665cda 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards 1f24b7c194a8 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards 9d6a5a7d2a82 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards 76a0bb7c378d 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards 8daa59c68fb1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards b6c762fe1852 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 17091b7972ad 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 35bd49aba027 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards 382bf7bc04c7 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards 8c5ad58af902 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards 98baca7d0719 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards 2bf3bd5ba2d5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 731b2f543d82 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards d715a4d04f1d 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 920c154ee0e8 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 1c1746442870 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards f30250f2c485 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 66a86d36b501 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards c1871eccd872 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards 19a0d5ce7ee7 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards bfab144dc13e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards 6b32491994da 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards 272f91a19028 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards 840d177c3d33 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards d153fc91fa01 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards 65a0461e2964 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards 75c205f6225f 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 23d04785974b 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards 6a4391491cfc 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards 3a2f4b765d6b 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards 7f631d5f47d4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards f5812b8cb8ca 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 54b15dee74bf 51: onsuccess: #464: 1: Success after binutils: 6 commits discards 6aa7fdcc2b11 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 7d7bbc3b8b9e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards c9d2a4613349 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 9d478f4d8116 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards 9ae12a45e861 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards 68a04ef39d06 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards 6043533e8273 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards fcb26f01cbb8 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards 6581838cb14d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards 262815319e66 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards 2bcf3d411432 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 76e094c16e5e 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 1375cb9fe103 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards af67a1e409cb 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 19c7f0320519 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] discards 5668ffa1fc90 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] new ad1452a4df32 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] new faac4d38f24d 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new 6d8c762c5c34 37: onsuccess: #443: 1: Success after binutils: 2 commits new e43eedf3b5d2 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 2680a2bae18d 39: onsuccess: #447: 1: Success after binutils: 5 commits new 9deb0ab2f462 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 56e3032e9ac5 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new e19320b6ccce 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new 5909889d0865 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 39931572c474 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new dde4c09e530a 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 37ac922f5684 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new 4971bead3af0 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new 21f9e13a0f65 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new af07923b3867 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new 792d08ec9ce7 50: onsuccess: #461: 1: Success after binutils: 12 commits new faeb43f7b53f 51: onsuccess: #464: 1: Success after binutils: 6 commits new b557e5332a54 52: onsuccess: #467: 1: Success after binutils: 9 commits new 8fbced2099b3 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new e8a0fa9a428e 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new a268d19b6f78 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new 1c3276a7d33d 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new b26c6828d59b 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new bf5c6e114d39 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new 96b5f9ed7337 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new 06cf450f99a2 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new 4e36e0779324 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new ba7376a4826d 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new efe90f3ef6b6 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new 29729adb6489 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 81be72cc9175 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new da79f8515f7a 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new 715277249522 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new dc6bbbeeb327 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 33754cbaa00f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new e818496f2630 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 38cabde2400c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new c47c1650fc05 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new 786e22fc8be5 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new 5aae552fbaab 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new 8e4165cbc9c5 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new 52f62c15e11d 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new 72dfc992ae6b 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new 7b61f9a43b9c 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new 60b2f1d32901 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new eca4a25c6649 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new e1b9194cf20c 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new f79045da077f 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 2d94790f7c86 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new c4c5669d6c77 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new 0b67dadd7daf 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 1f542935bfa5 86: onsuccess: #503: 1: Success after binutils: 12 commits new ccd74f9ec89b 87: onsuccess: #505: 1: Success after glibc: 7 commits new 718bad62d41a 88: onsuccess: #506: 1: Success after linux: 34 commits new 76c9ae7cdf2d 89: onsuccess: #508: 1: Success after binutils: 12 commits new 978743f153d3 90: onsuccess: #510: 1: Success after glibc: 5 commits new bcf9bb557fdf 91: onsuccess: #511: 1: Success after linux: 27 commits new ea0df8f82109 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new fd61d3f41afd 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new f33f72c87465 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 57e4e79153e7 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new b09ca7315f12 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 1adecb38bf7d 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 55f94f2c8843 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new 567c142bbb2b 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new c8ecb12e9653 100: onsuccess: #521: 1: Success after binutils: 10 commits new 9817a0c225ae 101: onsuccess: #524: 1: Success after binutils: 2 commits new 6ed92b0a87a9 102: onsuccess: #527: 1: Success after binutils: 5 commits new 3c7cf7ba22ae 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new 195f31ea1550 104: onsuccess: #530: 1: Success after gcc: 7 commits new 8f09862f1d4a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new c2680b15d38f 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new 3be30f738fc9 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new a292b57b8c7e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 36760a9ba357 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new c27c5b561bf2 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new d7b743a9cdbf 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 9c7e657f01de 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new 5f1d9826fa69 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new d3508cf47927 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new 2d12cd08c048 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 238801df883a 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new 66b5c8d250b4 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new 77b41ff954e4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 901f1e640a8c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new b560f15cee8e 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new 01fea0e62b84 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 3d7ae1f5dde1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new daa77acdab10 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new 5f384ccc0cb0 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new b39197b38bfd 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 41ce5cc696de 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new 4fc9cef0a9d8 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 8790bc273839 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new 705ae7edfe05 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 7d5e389b8688 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new ec954b1ba136 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new 6d182c7ad4d1 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new ef0016ddeace 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new a0cab2017bff 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new c3cd293aaa30 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new ec28f3e279fa 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/ [...]
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 (6b3a796882bd) \ 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 1728 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52648 -> 52608 bytes 04-build_abe-gcc/console.log.xz | Bin 234672 -> 234688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 234712 -> 236496 bytes 08-build_abe-gdb/console.log.xz | Bin 52032 -> 51912 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3812 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2256 -> 2088 bytes 11-check_regression/console.log.xz | Bin 5568 -> 5736 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 62864 -> 62664 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 100416 -> 100532 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 131576 -> 132168 bytes sumfiles/ld.sum | 360 ++++++++++++++--------------- 29 files changed, 427 insertions(+), 414 deletions(-)