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_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 27cd8a3adda 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 0bda129fce5 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 997a98d9f9f 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 38b4682c253 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards bd8172951d5 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 81ff6d22a55 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 4d901fcaa1f 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards d5c8ceb0fb6 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 7258d299ef2 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 35db7b7e9ad 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 607bcc7c572 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 826095059bf 129: onsuccess: #588: 1: Success after linux: 4 commits discards f94e441fbc5 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 7e98a9856f7 127: onsuccess: #584: 1: Success after linux: 21 commits discards f5dbc56d51e 126: onsuccess: #582: 1: Success after gcc: 9 commits discards ebfaf7abf08 125: onsuccess: #581: 1: Success after binutils: 4 commits discards e98efb22de3 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards f16b2fc7e28 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 022c12d1349 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 1e05cdea872 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 5afdfef3a2c 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards ed612e4998b 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 964ec125ad6 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards bf05560a0ad 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 51847412f76 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 0e9dda5e0ff 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 27c26085247 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards a94131c3edb 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 20f8ea5cadc 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 9745616378d 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards a572e9c2971 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards b07610d2554 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards e6cb7740e56 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 51713ac82c6 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards e2d2e9ee7c6 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 135f4c44584 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards d52654eef03 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 589179fef64 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 6637dbedde9 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards b0253d4b190 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards f231c8748a8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 243e77e4651 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 9fb439048da 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards e4b39a0b5e5 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 8f71e372108 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 30cf7131727 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 26672159508 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 550403cb1df 93: onsuccess: #544: 1: Success after linux: 34 commits discards 3392a0f8ff5 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 4db5f8c134b 91: onsuccess: #539: 1: Success after linux: 27 commits discards 957b56247b2 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 28b21f38137 89: onsuccess: #536: 1: Success after binutils: 27 commits discards f4db22e57c1 88: onsuccess: #534: 1: Success after linux: 12 commits discards fee698c81a7 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards b9c24705936 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 2d5058c873f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 0b26d4797bb 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 51288832e8d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards e35e7c75f8e 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards c04d07b0397 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 5c67af6bc67 80: onsuccess: #524: 1: Success after linux: 9 commits discards 7afcb7f74ef 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 263006335d9 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 3bc5d4b3a5b 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards 4d34ae34e45 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards 64f6dd01dc3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards 20cf96f2a45 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards 6884739ff50 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 4848694ac5f 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 7f894651378 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 481c6b9ccc1 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 1326313ba22 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards d3f9439e42b 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 55ce2d890ff 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards 450f84bd7c8 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards 5eff08bc918 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 74ef1f1baba 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 2805f52fc95 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards f21a93a62bd 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 74b30234c80 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards 3d540fff352 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 226de8aa6ca 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 67262c557ec 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 6fe2ea31719 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 85df08df3c2 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 681da77d1e2 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 6b18b1f1d09 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 491617919fc 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards d18cb309a84 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 4c55f536773 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 4f3d323e685 50: onsuccess: #490: 1: Success after binutils: 6 commits discards e9a41826129 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 722cd5a8ba7 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards b721b191d50 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 3c673c371ec 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 1c8417a8964 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards 46fcd187f60 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards aa6b9e836d5 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 0ef02963ce8 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 196a35292a9 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards 42074109bdc 40: onsuccess: #476: 1: Success after linux: 69 commits new 3a3bc15768c 40: onsuccess: #476: 1: Success after linux: 69 commits new 1cfd52e55a8 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 04e484aee27 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 616e78380e9 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 8cd66dd3a12 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 2944101251b 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 7bccf1e3456 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new c0261f440bb 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new a1e226a7252 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 412c7a1811d 49: onsuccess: #487: 1: Success after binutils: 11 commits new 74d512d2a5a 50: onsuccess: #490: 1: Success after binutils: 6 commits new bca59b05e22 51: onsuccess: #493: 1: Success after binutils: 13 commits new 36663906b87 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 6e41eae8654 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 65d36c726fb 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new dab0d5d38df 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new b3dcf404370 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 40dffa05186 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 3a32495944f 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 1bc3c4f2099 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new eab612cc9f0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new 99ca653c98b 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new 4e5135f1dfe 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 44fcaa7b9e6 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 3ce42d5c9a5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new ee498693135 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new e826f86593f 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 54d75ba970e 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new b0525411cd4 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 9c92703f1f6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new 144a7a62fe3 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new e2593b802d3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 21fd074aa19 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new c4d86c75d97 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new fc096af7732 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new a20bb3f3121 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new a7d0543f64d 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new c7e0e05261e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 388ec24b858 78: onsuccess: #522: 1: Success after binutils: 10 commits new dcac5a0bfd3 79: onsuccess: #523: 1: Success after gcc: 25 commits new 3f77c0851f3 80: onsuccess: #524: 1: Success after linux: 9 commits new b9b8dca359f 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 6d12381cc6d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 20f41e9a0df 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 115e4467936 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 25d84f6f3d1 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 272651450a0 86: onsuccess: #532: 1: Success after gcc: 16 commits new 6381323e10a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new ee0015c280e 88: onsuccess: #534: 1: Success after linux: 12 commits new ad1f809fc64 89: onsuccess: #536: 1: Success after binutils: 27 commits new 20f28a1aec4 90: onsuccess: #538: 1: Success after glibc: 10 commits new 5921da33da0 91: onsuccess: #539: 1: Success after linux: 27 commits new c85e53c5dc8 92: onsuccess: #543: 1: Success after glibc: 4 commits new 44303630c4f 93: onsuccess: #544: 1: Success after linux: 34 commits new 130d47dc276 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 4a463ace741 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new e2249f13f1b 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 6fc141886d4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 61815470e5c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new de7e96e18a8 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new c3d79ab3fb5 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 69d576ce018 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 0e547254fe0 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 8afa3976e8f 103: onsuccess: #555: 1: Success after binutils: 4 commits new 9a24243517a 104: onsuccess: #558: 1: Success after binutils: 3 commits new 5dad9b35e1e 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new e2330b85f7e 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new ab470555761 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 6187a630393 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new fe96153d419 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 0c7b23acfc4 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 461905e89c0 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 8addc2e9fe4 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 619ffb074ae 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 9358974281b 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 15286af0b0e 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new e2459c0762f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 21d3fde3aa9 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new bc3d035fc3b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new c089a828da6 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 9aab8a79afe 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 2e28e861d43 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 7bd1428b702 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new d30cca61042 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new a79d89a3654 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 90e04bdc176 125: onsuccess: #581: 1: Success after binutils: 4 commits new 7483bbd42c5 126: onsuccess: #582: 1: Success after gcc: 9 commits new 3ed8412fd5e 127: onsuccess: #584: 1: Success after linux: 21 commits new 446d8f28f3e 128: onsuccess: #586: 1: Success after binutils: 22 commits new 28c25b01fb3 129: onsuccess: #588: 1: Success after linux: 4 commits new 30cd91e22c6 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 545cd6cf81f 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new cc4bee45890 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 1d135088044 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 8ba45b403e4 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new c451af5c623 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 139450e1fb3 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 7043248a58f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 186eda20f20 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new c7ba31e46dc 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1a190ee12a3 140: onsuccess: #600: 1: Success after gcc: 23 commits new 8e54783611f 141: onsuccess: #601: 1: Success after linux: 794 commits
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 (27cd8a3adda) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]
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 1664 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 52944 -> 53700 bytes 04-build_abe-gcc/console.log.xz | Bin 233484 -> 233156 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9412 -> 9660 bytes 07-build_abe-glibc/console.log.xz | Bin 235076 -> 235280 bytes 08-build_abe-gdb/console.log.xz | Bin 51272 -> 51848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3836 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2484 -> 2536 bytes 11-check_regression/console.log.xz | Bin 6204 -> 4804 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 12 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 127 +- 11-check_regression/results.regressions | 46 - 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 46 - sumfiles/g++.log.xz | Bin 2914236 -> 2892712 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2590800 -> 2567444 bytes sumfiles/gcc.sum | 4630 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 953488 -> 954040 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229652 -> 229700 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 472080 -> 470152 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2512 insertions(+), 2751 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions