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 5391a592858 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2ecde34ff92 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c5609fbae8f 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards bdebf1cbbf5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 5336a0188a4 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards acadcb64a22 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d67a1aac957 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards ad3c3b65901 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards eeba28d1707 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 55be940504e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards acde37f4c64 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9012c6bce13 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 3cada1a7aa4 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 4e5090eef5f 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards c81664abb0f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 28eef3235e1 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards e6a31d6c479 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 1d326d6987d 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards da5a49f5ff9 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards a8337fa300f 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 19c67288121 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards ffb6157ff86 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 8872bb396ff 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 0c4a78f6368 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards f7fa7575b90 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 51cc3a14c2e 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 5414b02684e 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 37d5a06fbd5 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards e2da92a8ebc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards d4204f9046c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ba0128dc836 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7ae91b84b54 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 4cfd0c9d6c4 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b315aa5ae0f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards b3eb09d6222 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards a51dca2bbe5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 236cd21132f 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 01d6c97dab6 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards a0279c85b57 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards a5698fbc66c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 54f1fffc059 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 426b4e769b2 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 9b94350307f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 946ae980893 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 2325312203d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 61d0e62eb2b 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 447c705182d 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards dad92ea003d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards c034cd59fd5 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 126aa838282 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 621080c9374 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards c81a62f690e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 44647e79ad1 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 379e26b79d2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 2c448f93f39 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 3a4e7765095 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 488b770cec2 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards e7723bc76b9 162: onsuccess: #624: 1: Success after linux: 10 commits discards f4a89ead038 161: onsuccess: #623: 1: Success after glibc: 9 commits discards d2cb038865a 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 9cc2ff634a2 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 31c4d614f94 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 12ae768cc9d 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 5ce7773ed4d 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 156d6a0244f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 5cb8e9c216a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 9f47d0b0d6d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 1dcf09fdee2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 690b21cb6bd 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 9785175a85e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 8be14e2f977 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 9418acde8cb 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 38271c1b3b7 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards a7a3b463fd9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 04ab3d3fc25 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 9f38e9196c3 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards c00f888b38e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0c52b0e0f2b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 55d90a58878 141: onsuccess: #601: 1: Success after linux: 794 commits discards 6132b01ff33 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 3b8bef384fc 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 7c5e657f4a7 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 5ee1cb3d91a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards caf7aa9245b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards e4903e2d9c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 640e14a5bd0 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 6f0ce6810ca 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 7e49b681aeb 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards e7d6e79f906 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 69243f9374d 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards c8523aa23b2 129: onsuccess: #588: 1: Success after linux: 4 commits discards a8aa1d07949 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 42bd41dbc18 127: onsuccess: #584: 1: Success after linux: 21 commits discards b938f39d5ab 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 8342936b560 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 0620abc6c06 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 46fffa6c17c 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 0aa1ebb9954 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 1d5824386cf 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards ef6d8f8d0ef 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards cfb655ef490 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new e1abbbf3b5e 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 8a553e51a44 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new e721e19a8e0 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 7d99e77b5f1 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new e755cba3c37 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new e020894a0f2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new dc9851cc02a 125: onsuccess: #581: 1: Success after binutils: 4 commits new 8e25dc50225 126: onsuccess: #582: 1: Success after gcc: 9 commits new 6deb1030c9f 127: onsuccess: #584: 1: Success after linux: 21 commits new 97b4ea0d1c3 128: onsuccess: #586: 1: Success after binutils: 22 commits new 0d53937b9f9 129: onsuccess: #588: 1: Success after linux: 4 commits new ecfcd27af40 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 9e38e964ca3 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 5014af5cf86 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 8261c72a094 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 9c4936483c6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 7fe484fe112 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 5a6bc9a5a04 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new f657cd7c273 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 0e8f608f667 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 292d9781203 139: onsuccess: #599: 1: Success after binutils: 10 commits new 77c06816b58 140: onsuccess: #600: 1: Success after gcc: 23 commits new 85cb926bbcf 141: onsuccess: #601: 1: Success after linux: 794 commits new 20e2d191a75 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3947070511f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new ec60844263e 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new fe3f94dfbb1 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 5aa210b658d 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a79bd57570b 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 35fb69c46cc 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 572d0ae14dd 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d4abe1d7bf0 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 6ef161d9b70 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new a579b75528e 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new f02dddfac25 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 26e78c9ec1f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new d1598da0fa1 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new f1e0a624349 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e63a02e8b1b 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new b6b17da4e1a 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e6cc2352c8b 159: onsuccess: #620: 1: Success after binutils: 12 commits new bded6cb177c 160: onsuccess: #621: 1: Success after gcc: 11 commits new 3915ad462dc 161: onsuccess: #623: 1: Success after glibc: 9 commits new 8749e34df75 162: onsuccess: #624: 1: Success after linux: 10 commits new 9c1b8baf85f 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 8c94a3ebee6 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7e87e443470 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 17a0ffbb4dd 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 3cad2557940 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 679fc8a58b7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 796a473f317 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 38e8f874b98 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new dabcf90de07 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 3b9d785841b 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b50776e0326 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new ac9984af711 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 5204ca8ba52 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new aab591cf5df 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new f41c3333cee 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new d83a8fe5ec7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 7b4691e55e3 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 76383c84cfd 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new ee8c89cb74c 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 3a0dd644d28 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 505fbe7d2a5 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 4fa2e8254b3 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 255f9f74a2e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 8753d754345 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 6785e861b55 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 25cfceb35ab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f58eef350c2 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 1b3b1977ade 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 8dd77ad2552 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 906e3677d0c 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 16b25664e89 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new c78a686e12a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 2a8671627af 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new b94d21fee54 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 94392ec19d3 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 9f8fb8358bb 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 346b3ae23a3 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 583ab404478 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 194f844c9a1 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new ab43cfad7fd 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new c8d122e89e2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new fa1f8ca049f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5c1c866909b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 61bc28819d8 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3513fc14b88 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 333bdacf924 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new dbca5f37dc0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2c30dbd0b84 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0137c182009 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 6fe857d06c7 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2349063dc4b 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 0729c9dd2ee 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new fe30e2af731 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2228ee3ccc8 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new bef38b070b5 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6a62d93b99f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new a27f7931661 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 155086031f9 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...]

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 (5391a592858) \ 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 1760 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52484 -> 52312 bytes 04-build_abe-gcc/console.log.xz | Bin 237308 -> 236040 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8780 bytes 07-build_abe-glibc/console.log.xz | Bin 235656 -> 236308 bytes 08-build_abe-gdb/console.log.xz | Bin 51332 -> 51032 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3764 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3080 -> 2560 bytes 11-check_regression/console.log.xz | Bin 7120 -> 7508 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 8 + 11-check_regression/mail-body.txt | 28 +++ 11-check_regression/results.compare | 11 +- 11-check_regression/results.compare2 | 309 ++++++++++++++++++++++---------- 11-check_regression/results.regressions | 28 +++ 12-update_baseline/console.log | 40 ++--- 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 | 30 +++- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++-- results | 28 +++ sumfiles/g++.log.xz | Bin 2905124 -> 2906556 bytes sumfiles/g++.sum | 88 ++++++++- sumfiles/gcc.log.xz | Bin 2468624 -> 2482004 bytes sumfiles/gcc.sum | 94 +++++++++- sumfiles/gfortran.log.xz | Bin 957524 -> 950240 bytes sumfiles/gfortran.sum | 9 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 234156 -> 233940 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 473876 -> 468620 bytes 41 files changed, 570 insertions(+), 162 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