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 8e54783611f 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1a190ee12a3 140: onsuccess: #600: 1: Success after gcc: 23 commits discards c7ba31e46dc 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 186eda20f20 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 7043248a58f 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 139450e1fb3 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards c451af5c623 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 8ba45b403e4 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 1d135088044 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards cc4bee45890 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 545cd6cf81f 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 30cd91e22c6 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 28c25b01fb3 129: onsuccess: #588: 1: Success after linux: 4 commits discards 446d8f28f3e 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 3ed8412fd5e 127: onsuccess: #584: 1: Success after linux: 21 commits discards 7483bbd42c5 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 90e04bdc176 125: onsuccess: #581: 1: Success after binutils: 4 commits discards a79d89a3654 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards d30cca61042 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 7bd1428b702 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 2e28e861d43 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 9aab8a79afe 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards c089a828da6 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards bc3d035fc3b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 21d3fde3aa9 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards e2459c0762f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 15286af0b0e 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 9358974281b 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 619ffb074ae 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 8addc2e9fe4 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 461905e89c0 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 0c7b23acfc4 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards fe96153d419 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6187a630393 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards ab470555761 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards e2330b85f7e 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 5dad9b35e1e 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 9a24243517a 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 8afa3976e8f 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 0e547254fe0 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 69d576ce018 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards c3d79ab3fb5 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards de7e96e18a8 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 61815470e5c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 6fc141886d4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards e2249f13f1b 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 4a463ace741 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 130d47dc276 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 44303630c4f 93: onsuccess: #544: 1: Success after linux: 34 commits discards c85e53c5dc8 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 5921da33da0 91: onsuccess: #539: 1: Success after linux: 27 commits discards 20f28a1aec4 90: onsuccess: #538: 1: Success after glibc: 10 commits discards ad1f809fc64 89: onsuccess: #536: 1: Success after binutils: 27 commits discards ee0015c280e 88: onsuccess: #534: 1: Success after linux: 12 commits discards 6381323e10a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 272651450a0 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 25d84f6f3d1 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 115e4467936 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 20f41e9a0df 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 6d12381cc6d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards b9b8dca359f 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 3f77c0851f3 80: onsuccess: #524: 1: Success after linux: 9 commits discards dcac5a0bfd3 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 388ec24b858 78: onsuccess: #522: 1: Success after binutils: 10 commits discards c7e0e05261e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards a7d0543f64d 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards a20bb3f3121 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards fc096af7732 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards c4d86c75d97 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 21fd074aa19 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards e2593b802d3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 144a7a62fe3 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 9c92703f1f6 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards b0525411cd4 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 54d75ba970e 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards e826f86593f 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards ee498693135 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 3ce42d5c9a5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 44fcaa7b9e6 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards 4e5135f1dfe 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 99ca653c98b 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards eab612cc9f0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 1bc3c4f2099 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 3a32495944f 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 40dffa05186 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards b3dcf404370 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards dab0d5d38df 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 65d36c726fb 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 6e41eae8654 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 36663906b87 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards bca59b05e22 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 74d512d2a5a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 412c7a1811d 49: onsuccess: #487: 1: Success after binutils: 11 commits discards a1e226a7252 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards c0261f440bb 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 7bccf1e3456 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 2944101251b 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards 8cd66dd3a12 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 616e78380e9 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 04e484aee27 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 1cfd52e55a8 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new afd95af648b 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new d15a3ce87fa 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 0c4a6bd9680 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new b28c9b5f713 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new f1f218c438c 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 9e4e828fe1a 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 945aaeedb12 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 695bdb4294b 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new b9742704a81 49: onsuccess: #487: 1: Success after binutils: 11 commits new 23665f7e359 50: onsuccess: #490: 1: Success after binutils: 6 commits new 306e5947e3a 51: onsuccess: #493: 1: Success after binutils: 13 commits new 823655f6d55 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new ca653b02cf8 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new c71e34d1ffd 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 3ac372592f5 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 396e3b8ed40 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 55fad0a7f0c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new f88ae51b425 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 492cd624633 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new b5231237715 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new f2716409b2f 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new ec602fa9902 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 371518e4783 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new d6a46fb3630 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new 6ed7c731cb3 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 09b8143de43 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 02fa787fc45 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new d21fc16be7e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 72ee2ee9c94 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new 73e1d8b43c0 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 880527062d3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new c3baf22bdfe 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 10af231a1fe 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new f30dfb84904 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new e11601dfc84 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new eac3dfe2812 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new f44d5e0b61a 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 71a58d0786a 78: onsuccess: #522: 1: Success after binutils: 10 commits new 0562cc76dc2 79: onsuccess: #523: 1: Success after gcc: 25 commits new 4ec6f31cc4e 80: onsuccess: #524: 1: Success after linux: 9 commits new 89aebce7650 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 1ba78a45dcf 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 6326e8e1839 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new c9607e46d5a 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 8064ec15932 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 31cb72c041a 86: onsuccess: #532: 1: Success after gcc: 16 commits new d46fe5a4d10 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new 615cdfad4f6 88: onsuccess: #534: 1: Success after linux: 12 commits new 699b294fb66 89: onsuccess: #536: 1: Success after binutils: 27 commits new 4686920c318 90: onsuccess: #538: 1: Success after glibc: 10 commits new 8039a27408f 91: onsuccess: #539: 1: Success after linux: 27 commits new 508061ec548 92: onsuccess: #543: 1: Success after glibc: 4 commits new ad0676ccd5c 93: onsuccess: #544: 1: Success after linux: 34 commits new 76244742800 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 068b5563fb7 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 379eaeb29ac 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new b1a679bf010 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 5890a22b88e 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 330496a62ac 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 730e1223204 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 3a50d0460e9 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 3d6688ac2b6 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new cf5ee619cd4 103: onsuccess: #555: 1: Success after binutils: 4 commits new 9d297d086a2 104: onsuccess: #558: 1: Success after binutils: 3 commits new 29117a6c13a 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 157c25e643a 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 603066c51d1 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new e01092ff8c0 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 64b72d85401 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 32d806c10fd 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 23de49eebb9 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new d74c5a68224 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 38705d565f1 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 9728e8eaccc 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new ce9ef1d58b4 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 56659bfa6ff 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new fa6eec0c452 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new a53c5b1af1c 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new f3851197e3c 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new c36b3f5b576 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 03f5faa6005 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new c7384fe6ced 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new de79595edad 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 20796e334ad 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 20ec215fd41 125: onsuccess: #581: 1: Success after binutils: 4 commits new b660bcec951 126: onsuccess: #582: 1: Success after gcc: 9 commits new 2e74c0783d1 127: onsuccess: #584: 1: Success after linux: 21 commits new b3f4da60d2a 128: onsuccess: #586: 1: Success after binutils: 22 commits new fd9c995ea1e 129: onsuccess: #588: 1: Success after linux: 4 commits new 4b127b99141 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new fc62bbed684 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 106a1b762f3 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 9112f10c9de 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 978fd8aa6fe 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new a9e86b8c7cb 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 57bf1d57016 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 834ed8dc2be 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 56ab76db59a 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 804420a0100 139: onsuccess: #599: 1: Success after binutils: 10 commits new 76bc7156473 140: onsuccess: #600: 1: Success after gcc: 23 commits new e3a007eae7b 141: onsuccess: #601: 1: Success after linux: 794 commits new 08c46c06832 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...]
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 (8e54783611f) \ 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 1748 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53700 -> 52988 bytes 04-build_abe-gcc/console.log.xz | Bin 233156 -> 233460 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9660 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 235280 -> 234812 bytes 08-build_abe-gdb/console.log.xz | Bin 51848 -> 51024 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2536 -> 2668 bytes 11-check_regression/console.log.xz | Bin 4804 -> 7968 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 74 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 201 +- .../results.regressions | 75 +- 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 | 76 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 46 + sumfiles/g++.log.xz | Bin 2892712 -> 2924716 bytes sumfiles/g++.sum | 191 +- sumfiles/gcc.log.xz | Bin 2567444 -> 2568608 bytes sumfiles/gcc.sum | 4901 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 954040 -> 951820 bytes sumfiles/gfortran.sum | 98 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229700 -> 230612 bytes sumfiles/libgomp.sum | 28 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470152 -> 475896 bytes sumfiles/libstdc++.sum | 21 +- 43 files changed, 3102 insertions(+), 2785 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum copy mail/mail-body.txt => 11-check_regression/results.regressions (62%)