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 e9954e99562 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 98cf26b1ec6 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d3b4e56543e 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 99af40a156a 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards b7225657ec8 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5a1cb92b269 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 6cf6f4c2f2f 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 622b6d3d7a2 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 906bb4ae183 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 90aaa3249b7 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0be2279704f 129: onsuccess: #588: 1: Success after linux: 4 commits discards 3d7a96dd960 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 4c8e19f8348 127: onsuccess: #584: 1: Success after linux: 21 commits discards 78e52d9659b 126: onsuccess: #582: 1: Success after gcc: 9 commits discards bc5a1943085 125: onsuccess: #581: 1: Success after binutils: 4 commits discards c0a595dd88b 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards c9805957e83 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 6b8a5ea4158 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards e72e3a71c9f 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards c9f59af2629 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 046ec37ce73 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards dba44354cd1 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 1306f40a1c3 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 4122438539d 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards ecadef4267a 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 956b7519aa6 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 4305cd35fc9 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 61e7c5535a0 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards ecd0299608d 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 87a9d5c197c 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 618d92b280a 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 84424ad0287 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards b3dbafddf78 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards df8ee765df8 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 38e5f6fdf53 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 8de5ac2231a 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 95d6991184d 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 6597d62a986 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 51af47c9b85 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 6ea69da7fdb 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards a43632117f6 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 25eb06d924b 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 53ab0637b5d 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 589b4344ee9 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 404795b766e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 0569c6cf220 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 97c9eee12d8 93: onsuccess: #544: 1: Success after linux: 34 commits discards 0d9a10d4b87 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 6425eb7c21b 91: onsuccess: #539: 1: Success after linux: 27 commits discards ecfd71c838e 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 58aab2252c9 89: onsuccess: #536: 1: Success after binutils: 27 commits discards c14a245714e 88: onsuccess: #534: 1: Success after linux: 12 commits discards 598c97e0169 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards f5b7d02dc64 86: onsuccess: #532: 1: Success after gcc: 16 commits discards d2fdd345dec 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards e307aa808d9 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards b62a445fa5b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 203bdf47afd 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards 684cf7d72a8 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards d89f373a6a4 80: onsuccess: #524: 1: Success after linux: 9 commits discards 9dbf771404c 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 93f3298a7c6 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 1eb0d6f8ba0 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards 0c4202e32e5 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards 595163880fb 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards 47edc823342 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards e29f48133cd 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 3d7e888f134 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 8fd702b749a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 4bdf7219585 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards d845047cfa4 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards a88718c861d 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 0ce0b50c4e5 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards da406b5c0bf 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards 1de42c0c8f6 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards c977f475c15 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards cddce9b460a 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards d6b106a6647 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 2b662b2485c 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards 13e8678298b 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 61f8f1394e2 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 609634c80b1 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 18efc8a25e4 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 889f7f54c01 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 92f600512f3 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards a55a30605be 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 6a7919aa318 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 93aebbccafd 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 38160d5f359 51: onsuccess: #493: 1: Success after binutils: 13 commits discards f771802d9b7 50: onsuccess: #490: 1: Success after binutils: 6 commits discards eb136ba85b6 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 5c354cacc02 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 43fc382f163 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards dc09d73e16d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 05eda2bbf7d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards e45175b79a8 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 4412d5cbad2 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards aaaf41721c7 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 98a87d004cc 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards 689e810306d 40: onsuccess: #476: 1: Success after linux: 69 commits discards 81e3dae3238 39: onsuccess: #474: 1: Success after binutils: 8 commits new 775b54fe4b0 39: onsuccess: #474: 1: Success after binutils: 8 commits new 42074109bdc 40: onsuccess: #476: 1: Success after linux: 69 commits new 196a35292a9 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 0ef02963ce8 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new aa6b9e836d5 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 46fcd187f60 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 1c8417a8964 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 3c673c371ec 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new b721b191d50 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 722cd5a8ba7 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new e9a41826129 49: onsuccess: #487: 1: Success after binutils: 11 commits new 4f3d323e685 50: onsuccess: #490: 1: Success after binutils: 6 commits new 4c55f536773 51: onsuccess: #493: 1: Success after binutils: 13 commits new d18cb309a84 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 491617919fc 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 6b18b1f1d09 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 681da77d1e2 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 85df08df3c2 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 6fe2ea31719 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 67262c557ec 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 226de8aa6ca 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new 3d540fff352 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new 74b30234c80 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new f21a93a62bd 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 2805f52fc95 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 74ef1f1baba 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new 5eff08bc918 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 450f84bd7c8 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 55ce2d890ff 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new d3f9439e42b 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 1326313ba22 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new 481c6b9ccc1 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 7f894651378 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 4848694ac5f 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 6884739ff50 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new 20cf96f2a45 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new 64f6dd01dc3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new 4d34ae34e45 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new 3bc5d4b3a5b 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 263006335d9 78: onsuccess: #522: 1: Success after binutils: 10 commits new 7afcb7f74ef 79: onsuccess: #523: 1: Success after gcc: 25 commits new 5c67af6bc67 80: onsuccess: #524: 1: Success after linux: 9 commits new c04d07b0397 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new e35e7c75f8e 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 51288832e8d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 0b26d4797bb 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 2d5058c873f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new b9c24705936 86: onsuccess: #532: 1: Success after gcc: 16 commits new fee698c81a7 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new f4db22e57c1 88: onsuccess: #534: 1: Success after linux: 12 commits new 28b21f38137 89: onsuccess: #536: 1: Success after binutils: 27 commits new 957b56247b2 90: onsuccess: #538: 1: Success after glibc: 10 commits new 4db5f8c134b 91: onsuccess: #539: 1: Success after linux: 27 commits new 3392a0f8ff5 92: onsuccess: #543: 1: Success after glibc: 4 commits new 550403cb1df 93: onsuccess: #544: 1: Success after linux: 34 commits new 26672159508 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 30cf7131727 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 8f71e372108 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new e4b39a0b5e5 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 9fb439048da 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 243e77e4651 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new f231c8748a8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new b0253d4b190 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 6637dbedde9 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 589179fef64 103: onsuccess: #555: 1: Success after binutils: 4 commits new d52654eef03 104: onsuccess: #558: 1: Success after binutils: 3 commits new 135f4c44584 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new e2d2e9ee7c6 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 51713ac82c6 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new e6cb7740e56 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new b07610d2554 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new a572e9c2971 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 9745616378d 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 20f8ea5cadc 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new a94131c3edb 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 27c26085247 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 0e9dda5e0ff 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 51847412f76 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new bf05560a0ad 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 964ec125ad6 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new ed612e4998b 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 5afdfef3a2c 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 1e05cdea872 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 022c12d1349 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new f16b2fc7e28 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new e98efb22de3 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new ebfaf7abf08 125: onsuccess: #581: 1: Success after binutils: 4 commits new f5dbc56d51e 126: onsuccess: #582: 1: Success after gcc: 9 commits new 7e98a9856f7 127: onsuccess: #584: 1: Success after linux: 21 commits new f94e441fbc5 128: onsuccess: #586: 1: Success after binutils: 22 commits new 826095059bf 129: onsuccess: #588: 1: Success after linux: 4 commits new 607bcc7c572 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 35db7b7e9ad 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 7258d299ef2 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new d5c8ceb0fb6 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 4d901fcaa1f 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 81ff6d22a55 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new bd8172951d5 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 38b4682c253 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 997a98d9f9f 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 0bda129fce5 139: onsuccess: #599: 1: Success after binutils: 10 commits new 27cd8a3adda 140: onsuccess: #600: 1: Success after gcc: 23 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 (e9954e99562) \ 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 1792 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 53204 -> 52944 bytes 04-build_abe-gcc/console.log.xz | Bin 234180 -> 233484 bytes 06-build_abe-linux/console.log.xz | Bin 9292 -> 9412 bytes 07-build_abe-glibc/console.log.xz | Bin 235200 -> 235076 bytes 08-build_abe-gdb/console.log.xz | Bin 52036 -> 51272 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2660 -> 2484 bytes 11-check_regression/console.log.xz | Bin 4788 -> 6204 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 12 + 11-check_regression/mail-body.txt | 46 + 11-check_regression/results.compare | 29 +- 11-check_regression/results.compare2 | 125 +- 11-check_regression/results.regressions | 46 + 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 46 + sumfiles/g++.log.xz | Bin 2884436 -> 2914236 bytes sumfiles/g++.sum | 51 +- sumfiles/gcc.log.xz | Bin 2597164 -> 2590800 bytes sumfiles/gcc.sum | 4407 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 952108 -> 953488 bytes sumfiles/gfortran.sum | 62 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 229496 -> 229652 bytes sumfiles/libgomp.sum | 14 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 467816 -> 472080 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2681 insertions(+), 2302 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions