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 7a9c1a2b4c64 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 5223c6ed3052 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] discards 30f19af5888f 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] discards 2fde9244b638 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] discards 3ebfe7c5c0c1 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] discards 74fe88fafbe4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] discards 9914923e4eb3 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] discards 50e35d9783a6 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards 12db70d44034 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 0a9704970d17 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 91e75f19ec07 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] discards b52d9ecb6a1f 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] discards 46eb06e2a035 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] discards 53980337aed1 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] discards 639701292231 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] discards 888e566c333e 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] discards 68061ec4a98a 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] discards aa3c30230ce9 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] discards ecc30acdba74 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] discards 63800cdda9ef 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] discards 411e376602c3 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] discards d00c0d735e2e 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] discards 955733fe3b72 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] discards 7b2f2c4e2da8 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] discards 7984d206e87f 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] discards 201cd62292a1 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] discards 4110114132fc 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] discards 18ee23db1411 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] discards 95d4a76f4786 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] discards f2ee2bfb96f4 104: onsuccess: #530: 1: Success after gcc: 7 commits discards b0c8157e9b9d 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] discards 93e66b0acb71 102: onsuccess: #527: 1: Success after binutils: 5 commits discards cd89ee051bdf 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 3f74a5266495 100: onsuccess: #521: 1: Success after binutils: 10 commits discards 76caa0eff154 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 0e6de8c6a90b 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards a99b3f37a072 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards c088e328ec7e 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] discards 8d50f4b73861 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] discards 1d0e47e95519 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 84e301e53d2d 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards cf309a10c621 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards 4f1245164aeb 91: onsuccess: #511: 1: Success after linux: 27 commits discards 538dfe5fc285 90: onsuccess: #510: 1: Success after glibc: 5 commits discards 3e1ba27017a7 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 1938e21383ab 88: onsuccess: #506: 1: Success after linux: 34 commits discards a9e7efa1d268 87: onsuccess: #505: 1: Success after glibc: 7 commits discards dde5501fcdca 86: onsuccess: #503: 1: Success after binutils: 12 commits discards dd634d0ba88f 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 9c742624ff13 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 96d264b2b7c3 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards f34e5eeb33b1 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards ba255fc9e8e3 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards 3f60bf39194d 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards dd195f1e6159 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 1905456dc6ad 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] discards 923f902617ed 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] discards 4d11d821df31 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] discards c127e1d9d320 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] discards 569a63a1a910 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] discards a20bf74ce0d0 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] discards 91de8dad797b 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] discards 3178be2066dc 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] discards 097c287c7027 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] discards 4eb682b49a98 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 1920271f141f 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 7ef700a6d738 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 80ff1dd40786 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] discards dd9299ba57df 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards fc07457fab14 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards df7e9ee3256e 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] discards 83f997f569c7 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] discards 622b914f47d5 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] discards 9af8583fc357 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] discards 7d7522952b41 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] discards c5be521ec2fa 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] discards 5af8d9608157 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] discards 86185577ecca 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] discards a118d715e3dc 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] discards 3d98169cbb99 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] discards e9cfe01c8017 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] discards c4bddc9375fb 52: onsuccess: #467: 1: Success after binutils: 9 commits discards dd1289761e42 51: onsuccess: #464: 1: Success after binutils: 6 commits discards a8a512c3acf9 50: onsuccess: #461: 1: Success after binutils: 12 commits discards 93d4bce7d4f1 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] discards 2fd54201ce2a 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] discards 2b0b12067877 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] discards bccf461b36a6 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] discards 1e46995f1754 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] discards fc3dc72efaee 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] discards 15499c459145 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] discards 15b6c8a0bd6d 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] discards fd17274d72f1 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] discards e609be111406 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] discards 37e68296bf08 39: onsuccess: #447: 1: Success after binutils: 5 commits discards 63b066baadc0 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] discards 38e139d8dbec 37: onsuccess: #443: 1: Success after binutils: 2 commits discards b2931f68788b 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] discards 44e84bc02aa6 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] discards a56c11a10f30 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] discards fca14f57c720 33: onsuccess: #438: 1: Success after binutils/gcc/linux/g [...] new 0c51c456f4e5 33: onsuccess: #438: 1: Success after binutils/gcc/linux/g [...] new debbdf6fec87 34: onsuccess: #439: 1: Success after binutils/gcc/linux/g [...] new 74e180f528d0 35: onsuccess: #440: 1: Success after binutils/gcc/linux/g [...] new 37d5895fd3d4 36: onsuccess: #441: 1: Success after binutils/gcc/linux/g [...] new 1fccfc7635e8 37: onsuccess: #443: 1: Success after binutils: 2 commits new 4d4fa62eab4c 38: onsuccess: #445: 1: Success after glibc-2.36.9000-120- [...] new 0f88895e59a2 39: onsuccess: #447: 1: Success after binutils: 5 commits new b28ef193affc 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121- [...] new 790b3ee81ec9 41: onsuccess: #450: 1: Success after binutils/gcc/linux/g [...] new e2ab3e5decb4 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/g [...] new 1525447adc1a 43: onsuccess: #452: 1: Success after binutils/gcc/linux/g [...] new 6e20208b0986 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/g [...] new 0b608f931681 45: onsuccess: #454: 1: Success after binutils/gcc/linux/g [...] new 82ee4ea00774 46: onsuccess: #455: 1: Success after binutils/gcc/linux/g [...] new 118f09826b4b 47: onsuccess: #457: 1: Success after binutils/gcc/linux/g [...] new 2d79c9188c07 48: onsuccess: #458: 1: Success after binutils/gcc/linux/g [...] new af55e0ed116e 49: onsuccess: #459: 1: Success after binutils/gcc/linux/g [...] new ae6d2ce8ead7 50: onsuccess: #461: 1: Success after binutils: 12 commits new dce3306fff5a 51: onsuccess: #464: 1: Success after binutils: 6 commits new abe128478517 52: onsuccess: #467: 1: Success after binutils: 9 commits new f47be0348588 53: onsuccess: #469: 1: Success after binutils/gcc/linux/g [...] new 6e4f0a406c9a 54: onsuccess: #470: 1: Success after binutils/gcc/linux/g [...] new 080ab395dc62 55: onsuccess: #471: 1: Success after binutils/gcc/linux/g [...] new 5c007c0858e0 56: onsuccess: #472: 1: Success after binutils/gcc/linux/g [...] new d796275db320 57: onsuccess: #473: 1: Success after binutils/gcc/linux/g [...] new 44cd662e5eed 58: onsuccess: #474: 1: Success after binutils/gcc/linux/g [...] new 07e12dcbcf09 59: onsuccess: #475: 1: Success after binutils/gcc/linux/g [...] new d505e7989ddc 60: onsuccess: #476: 1: Success after binutils/gcc/linux/g [...] new d1702b1c2db4 61: onsuccess: #477: 1: Success after binutils/gcc/linux/g [...] new 48a59c656f3c 62: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 38a06828fc49 63: onsuccess: #479: 1: Success after binutils/gcc/linux/g [...] new add8173434b0 64: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 1e8cff21a164 65: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new d8cf22fea5c3 66: onsuccess: #482: 1: Success after binutils/gcc/linux/g [...] new 65580a123bde 67: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 63c31fc0e46c 68: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 490ede91d07f 69: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new 77c4364d0ad7 70: onsuccess: #486: 1: Success after binutils/gcc/linux/g [...] new 078311204a09 71: onsuccess: #487: 1: Success after binutils/gcc/linux/g [...] new f52ec0066562 72: onsuccess: #488: 1: Success after binutils/gcc/linux/g [...] new b0e7bedcc7b8 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/g [...] new bed67bee838f 74: onsuccess: #490: 1: Success after binutils/gcc/linux/g [...] new da2095167dd7 75: onsuccess: #491: 1: Success after binutils/gcc/linux/g [...] new 9b82393d2468 76: onsuccess: #492: 1: Success after binutils/gcc/linux/g [...] new 42cbf86e3bd9 77: onsuccess: #493: 1: Success after binutils/gcc/linux/g [...] new 117d78ebbdf8 78: onsuccess: #494: 1: Success after binutils/gcc/linux/g [...] new c6cd4e4c2a63 79: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new 8f2422098e9b 80: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 143abc0bb0b2 81: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 0fa68e3d503d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new b635aeb1fd4b 83: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 94425cc3f68f 84: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new dce3f68ddb53 85: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 8552ab43e583 86: onsuccess: #503: 1: Success after binutils: 12 commits new 375f504a145f 87: onsuccess: #505: 1: Success after glibc: 7 commits new 0418e4eb62a3 88: onsuccess: #506: 1: Success after linux: 34 commits new 5c38a39f9382 89: onsuccess: #508: 1: Success after binutils: 12 commits new 9e69f4d24f87 90: onsuccess: #510: 1: Success after glibc: 5 commits new 78714e597419 91: onsuccess: #511: 1: Success after linux: 27 commits new 498d6d6a0464 92: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 579392452ce1 93: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new ab3a8c4189b2 94: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 6eea2149eb01 95: onsuccess: #515: 1: Success after binutils/gcc/linux/g [...] new 2be185d9de16 96: onsuccess: #516: 1: Success after binutils/gcc/linux/g [...] new 6347d051d894 97: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new be6b9ba0d058 98: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new fd0e46e2a1ef 99: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 28568691eae4 100: onsuccess: #521: 1: Success after binutils: 10 commits new 8ace3b5b06fe 101: onsuccess: #524: 1: Success after binutils: 2 commits new 614b4bcd7faa 102: onsuccess: #527: 1: Success after binutils: 5 commits new 16d5d2118649 103: onsuccess: #529: 1: Success after binutils/gcc/linux/ [...] new cb396d49e99b 104: onsuccess: #530: 1: Success after gcc: 7 commits new bf7ceed54571 105: onsuccess: #531: 1: Success after binutils/gcc/linux/ [...] new cfceaac147f2 106: onsuccess: #532: 1: Success after binutils/gcc/linux/ [...] new 241cf1b412ed 107: onsuccess: #533: 1: Success after binutils/gcc/linux/ [...] new fe6dd4e54d8e 108: onsuccess: #534: 1: Success after binutils/gcc/linux/ [...] new 5990f67c7766 109: onsuccess: #535: 1: Success after binutils/gcc/linux/ [...] new 97c2e79c29c3 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/ [...] new 27c3971f5cb4 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 6 [...] new 19d67c9fbb3a 112: onsuccess: #538: 1: Success after binutils/gcc/linux/ [...] new 240eccf21ce0 113: onsuccess: #539: 1: Success after binutils/gcc/linux/ [...] new 4c4e7f6b3dfb 114: onsuccess: #541: 1: Success after binutils/gcc/linux/ [...] new a2a9f234284f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/ [...] new 42199b8af0b2 116: onsuccess: #543: 1: Success after binutils/gcc/linux/ [...] new c99565536efd 117: onsuccess: #544: 1: Success after binutils/gcc/linux/ [...] new 4db0d310dfa4 118: onsuccess: #545: 1: Success after binutils/gcc/linux/ [...] new 70033d85242c 119: onsuccess: #546: 1: Success after binutils/gcc/linux/ [...] new d3b0527f3dcc 120: onsuccess: #547: 1: Success after binutils/gcc/linux/ [...] new ff748e5ab126 121: onsuccess: #548: 1: Success after binutils/gcc/linux/ [...] new 0696d52d5204 122: onsuccess: #549: 1: Success after binutils/gcc/linux/ [...] new 968d1e64e66f 123: onsuccess: #550: 1: Success after binutils/gcc/linux/ [...] new 8282a44dd96d 124: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new f17333b4bfe4 125: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 60204071b2a0 126: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new cc89c34c0f4e 127: onsuccess: #554: 1: Success after binutils/gcc/linux/ [...] new 9f55e9f3f06a 128: onsuccess: #555: 1: Success after binutils/gcc/linux/ [...] new d66e8acad7fe 129: onsuccess: #556: 1: Success after binutils/gcc/linux/ [...] new 474123d23f54 130: onsuccess: #557: 1: Success after binutils/gcc/linux/ [...] new 75fb6a8bd63c 131: onsuccess: #558: 1: Success after binutils/gcc/linux/ [...] new 213a224afa11 132: onsuccess: #559: 1: Success after binutils/gcc/linux/ [...] new f0d470245b29 133: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 9e45d4f8e96b 134: onsuccess: #561: 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 (7a9c1a2b4c64) \ 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 1732 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 53040 -> 54160 bytes 04-build_abe-gcc/console.log.xz | Bin 233880 -> 234536 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8836 -> 8692 bytes 07-build_abe-glibc/console.log.xz | Bin 236408 -> 234588 bytes 08-build_abe-gdb/console.log.xz | Bin 51920 -> 52504 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3824 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2448 -> 2628 bytes 11-check_regression/console.log.xz | Bin 6280 -> 5932 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 16 +- 12-update_baseline/console.log | 60 ++--- 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 62488 -> 62996 bytes sumfiles/binutils.sum | 65 +++--- sumfiles/gas.log.xz | Bin 100532 -> 100400 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 131620 -> 131564 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 29 files changed, 407 insertions(+), 406 deletions(-)