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 9e45d4f8e96b 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards f0d470245b29 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 213a224afa11 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards 75fb6a8bd63c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 474123d23f54 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards d66e8acad7fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 9f55e9f3f06a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards cc89c34c0f4e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 60204071b2a0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards f17333b4bfe4 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 8282a44dd96d 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 968d1e64e66f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards 0696d52d5204 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards ff748e5ab126 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards d3b0527f3dcc 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 70033d85242c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards 4db0d310dfa4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards c99565536efd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards 42199b8af0b2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards a2a9f234284f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards 4c4e7f6b3dfb 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards 240eccf21ce0 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards 19d67c9fbb3a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards 27c3971f5cb4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards 97c2e79c29c3 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 5990f67c7766 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards fe6dd4e54d8e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 241cf1b412ed 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards cfceaac147f2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards bf7ceed54571 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards cb396d49e99b 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 16d5d2118649 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards 614b4bcd7faa 102: onsuccess: #527: 1: Success after binutils: 5 commits discards 8ace3b5b06fe 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 28568691eae4 100: onsuccess: #521: 1: Success after binutils: 10 commits discards fd0e46e2a1ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards be6b9ba0d058 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 6347d051d894 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 2be185d9de16 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 6eea2149eb01 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards ab3a8c4189b2 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 579392452ce1 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards 498d6d6a0464 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards 78714e597419 91: onsuccess: #511: 1: Success after linux: 27 commits discards 9e69f4d24f87 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 5c38a39f9382 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 0418e4eb62a3 88: onsuccess: #506: 1: Success after linux: 34 commits discards 375f504a145f 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 8552ab43e583 86: onsuccess: #503: 1: Success after binutils: 12 commits discards dce3f68ddb53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 94425cc3f68f 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards b635aeb1fd4b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards 0fa68e3d503d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards 143abc0bb0b2 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards 8f2422098e9b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards c6cd4e4c2a63 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 117d78ebbdf8 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 42cbf86e3bd9 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 9b82393d2468 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards da2095167dd7 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards bed67bee838f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards b0e7bedcc7b8 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards f52ec0066562 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 078311204a09 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards 77c4364d0ad7 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 490ede91d07f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 63c31fc0e46c 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 65580a123bde 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards d8cf22fea5c3 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards 1e8cff21a164 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards add8173434b0 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards 38a06828fc49 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards 48a59c656f3c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards d1702b1c2db4 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards d505e7989ddc 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards 07e12dcbcf09 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards 44cd662e5eed 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards d796275db320 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 5c007c0858e0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards 080ab395dc62 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards 6e4f0a406c9a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards f47be0348588 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards abe128478517 52: onsuccess: #467: 1: Success after binutils: 9 commits discards dce3306fff5a 51: onsuccess: #464: 1: Success after binutils: 6 commits discards ae6d2ce8ead7 50: onsuccess: #461: 1: Success after binutils: 12 commits discards af55e0ed116e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards 2d79c9188c07 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 118f09826b4b 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards 82ee4ea00774 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards 0b608f931681 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards 6e20208b0986 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards 1525447adc1a 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards e2ab3e5decb4 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards 790b3ee81ec9 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards b28ef193affc 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 0f88895e59a2 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 4d4fa62eab4c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards 1fccfc7635e8 37: onsuccess: #443: 1: Success after binutils: 2 commits discards 37d5895fd3d4 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] discards 74e180f528d0 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] discards debbdf6fec87 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] new 8cebbf3f2127 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] new 5668ffa1fc90 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] new 19c7f0320519 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new af67a1e409cb 37: onsuccess: #443: 1: Success after binutils: 2 commits new 1375cb9fe103 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 76e094c16e5e 39: onsuccess: #447: 1: Success after binutils: 5 commits new 2bcf3d411432 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 262815319e66 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new 6581838cb14d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new fcb26f01cbb8 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 6043533e8273 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new 68a04ef39d06 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 9ae12a45e861 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new 9d478f4d8116 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new c9d2a4613349 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new 7d7bbc3b8b9e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new 6aa7fdcc2b11 50: onsuccess: #461: 1: Success after binutils: 12 commits new 54b15dee74bf 51: onsuccess: #464: 1: Success after binutils: 6 commits new f5812b8cb8ca 52: onsuccess: #467: 1: Success after binutils: 9 commits new 7f631d5f47d4 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new 3a2f4b765d6b 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new 6a4391491cfc 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new 23d04785974b 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new 75c205f6225f 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new 65a0461e2964 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new d153fc91fa01 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new 840d177c3d33 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new 272f91a19028 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new 6b32491994da 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new bfab144dc13e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new 19a0d5ce7ee7 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new c1871eccd872 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 66a86d36b501 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new f30250f2c485 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 1c1746442870 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 920c154ee0e8 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new d715a4d04f1d 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 731b2f543d82 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new 2bf3bd5ba2d5 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new 98baca7d0719 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new 8c5ad58af902 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new 382bf7bc04c7 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new 35bd49aba027 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new 17091b7972ad 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new b6c762fe1852 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new 8daa59c68fb1 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 76a0bb7c378d 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 9d6a5a7d2a82 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 1f24b7c194a8 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 90824e665cda 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 97d4c8ed4245 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new a5cc9a108456 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new a36fdc63bd5c 86: onsuccess: #503: 1: Success after binutils: 12 commits new e55113e4b3cb 87: onsuccess: #505: 1: Success after glibc: 7 commits new 7a17c13d39bb 88: onsuccess: #506: 1: Success after linux: 34 commits new 71f6ddeeb7d5 89: onsuccess: #508: 1: Success after binutils: 12 commits new e82d12750e87 90: onsuccess: #510: 1: Success after glibc: 5 commits new 7046008b6bb2 91: onsuccess: #511: 1: Success after linux: 27 commits new 502fe57adea4 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 0778b87c86ca 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 4135ed7aec7d 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 8059d933f17c 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new 598ca8963b18 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 5febcf98b270 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 0ec6c1a56c7a 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new 32ecf69a9a49 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new d5e761b3e740 100: onsuccess: #521: 1: Success after binutils: 10 commits new f949d68be93f 101: onsuccess: #524: 1: Success after binutils: 2 commits new b3641cf8b7cb 102: onsuccess: #527: 1: Success after binutils: 5 commits new 68d310562756 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new 2a1883995705 104: onsuccess: #530: 1: Success after gcc: 7 commits new 81b9e153d627 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new ca254fc61bd6 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new 6798eb290a05 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new 6b3417d3f196 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 57de20f52d77 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new 0207eec44f01 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new ee3aefeb83b4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 12bb00604f7e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new af2e1b4bd381 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new 278921be3d65 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new 5a86c3b51906 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 69090530c681 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new b80b2657f2e9 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new b0f8c505e7e8 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 777251ba8779 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new 74fe498f8d8b 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new 69241f8bec4e 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 0f6bf8be8fd1 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new ce1300b74d5c 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new ffe927749853 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new 1d628213f5ff 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 95e2d2ddf227 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new 6754adf3370e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 525d5e5dd6db 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new ffd4267ec75e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 6fc331c81978 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new 67d1bf80bca9 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new f8b47cc43fac 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new 6a954c0f76b4 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 0e2959e83c66 134: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 6b3a796882bd 135: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...]

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 (9e45d4f8e96b) \ 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 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 54160 -> 52648 bytes 04-build_abe-gcc/console.log.xz | Bin 234536 -> 234672 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8692 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 234588 -> 234712 bytes 08-build_abe-gdb/console.log.xz | Bin 52504 -> 52032 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3844 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2628 -> 2256 bytes 11-check_regression/console.log.xz | Bin 5932 -> 5568 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 20 +- 12-update_baseline/console.log | 34 +-- 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 62996 -> 62864 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100400 -> 100416 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131564 -> 131576 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 390 insertions(+), 398 deletions(-)