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 2b1909e3cf2b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards c632cdba2547 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 65c9f8f13e24 141: onsuccess: #601: 1: Success after linux: 794 commits discards 4a9167daca8b 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 6f08d08a210e 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 21932e931b8f 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 13c3ae285f96 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 73c73fae6784 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards 944d7bd57069 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards f9b3954acc16 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 4c763cab0bed 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards c422e26da98a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards 262f808c5ae9 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 139a35e20ac5 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards 3e0a32d7fd32 129: onsuccess: #588: 1: Success after linux: 4 commits discards 82c7862dc2d7 128: onsuccess: #586: 1: Success after binutils: 22 commits discards c15b34d87ea3 127: onsuccess: #584: 1: Success after linux: 21 commits discards 65c1813ace2d 126: onsuccess: #582: 1: Success after gcc: 9 commits discards db93e7835b79 125: onsuccess: #581: 1: Success after binutils: 4 commits discards e0d9412567a2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] discards 8f4c7bf62d3e 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] discards 0c0c8a2f2a2a 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards d0571fe37ef9 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards 4071955d5f00 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards 5987eda95523 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] discards 1e610a8df420 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] discards 17134a806a19 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] discards 1ffc7d96a87f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] discards 6f74eea8c59d 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 9ba80f9ffac1 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] discards 6a9e72a10d1b 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] discards 925429b38605 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards e1cd0a3ec5c9 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 73859115e48e 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards 8b363528787b 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards 3413e6243a78 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] discards 6f88586ae252 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards d768fe4e70b0 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards eb8a09c1f417 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 1f612240ffe4 104: onsuccess: #558: 1: Success after binutils: 3 commits discards a7a292aef63b 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 8e51f116940d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards d6ace63e8312 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 57836245467e 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 3da90d7d3d24 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 6d24870c87a3 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 930d5e5f56e3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 2438e29c65ab 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards b780628c235a 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 2c1d6a6339a4 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards e1d491fc0455 93: onsuccess: #544: 1: Success after linux: 34 commits discards 3dc204e1d43b 92: onsuccess: #543: 1: Success after glibc: 4 commits discards b0c0ad981d5a 91: onsuccess: #539: 1: Success after linux: 27 commits discards 5af6d1f8db8e 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 4d4c6b91a1e6 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 43d898e17928 88: onsuccess: #534: 1: Success after linux: 12 commits discards 10eed17c8190 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] discards 9d9dc12a7dd4 86: onsuccess: #532: 1: Success after gcc: 16 commits discards d6f45b89435c 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards 4b25d1970f19 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] discards 239fcdc6498b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] discards 32844776f3b1 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] discards 2ba5c173b45e 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] discards e9d7c5f8cbf5 80: onsuccess: #524: 1: Success after linux: 9 commits discards 98ff80c41956 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 87224e063e26 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 94f1ec628d5c 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] discards c05e19d85c2f 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards 1733d1f7e255 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards 5c736f703463 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 90da4f2f0b7e 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] discards 1bead442ea9c 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] discards 424b4c3656e3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards dd1388b4cad4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards 18012905fd7f 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards 46df7090e459 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] discards 345d2f0363c4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] discards fcdf0a4932d5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] discards 6b46d9efbcf8 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] discards d0b5e4a983bc 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] discards 2fb008b785a5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] discards 39e3a120dfb4 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] discards 1fcc28e4cdfe 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] discards 01f921ea44bf 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] discards 675d5645e73d 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] discards 77035447a057 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 9761613fdc0c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 66102c106926 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards b93ee148f07d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards e846d5e2650e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards d20384fb0b72 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards e47cc4196d21 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 47f2d8c61953 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 439812e3af87 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 77fb47ed1c77 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 17f67230368f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 79b52bb7b20b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 2f33187ce148 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards 0a76104176c4 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards 9cbe115d4009 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards 3154a272c5a4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/g [...] new d436dd4b43eb 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/g [...] new 59c6ffe4ae78 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 6602148bc1c8 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 923a393e45ae 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new f7c1f4fa8d6d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 15e735d1a94f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new 464b68124a09 49: onsuccess: #487: 1: Success after binutils: 11 commits new 864048cbff86 50: onsuccess: #490: 1: Success after binutils: 6 commits new 4b6c42523add 51: onsuccess: #493: 1: Success after binutils: 13 commits new c9281f49afe1 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new d6049e0c8699 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new 6e16c56b075e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new 7ffafec27935 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new bafafd6117ec 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 982aef4df58e 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new 6caa45fd6027 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 252b9a49f052 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] new 2d2fbde57c1c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] new d687f2592585 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] new e507ceeac6f1 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] new 0b54cb6bfd0f 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] new 09c9befef30b 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] new 4791f515f3d5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] new 3d1836698bcc 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] new f68ffc667cb4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] new d0ad8e8639fc 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] new e54a418de600 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new 0723e260aee7 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 9fca6bfdd8ef 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 363dbbe51a78 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] new 9ac7427e04f6 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] new 8d52dc8a518a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 7773aef67160 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new 838f6a91d4cf 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 5c2093d4b430 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] new 12831863ae96 78: onsuccess: #522: 1: Success after binutils: 10 commits new 54179e24df47 79: onsuccess: #523: 1: Success after gcc: 25 commits new 6ffd2029fe85 80: onsuccess: #524: 1: Success after linux: 9 commits new 85761e26a0d7 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] new a6ee4b700c0c 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] new b3ea7223a4b7 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] new e5f913926daa 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] new 15d5460bbe6d 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 92f18afb8a7a 86: onsuccess: #532: 1: Success after gcc: 16 commits new 1568a781b3b4 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] new 62f08e002ee0 88: onsuccess: #534: 1: Success after linux: 12 commits new 81824bf85231 89: onsuccess: #536: 1: Success after binutils: 27 commits new cdd81a79829c 90: onsuccess: #538: 1: Success after glibc: 10 commits new 8926d0fe3e85 91: onsuccess: #539: 1: Success after linux: 27 commits new b32e36b855ad 92: onsuccess: #543: 1: Success after glibc: 4 commits new b556b8d78fe7 93: onsuccess: #544: 1: Success after linux: 34 commits new aa87dd8f6287 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 6c244e6378a5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new a84e17482695 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 8af7b357958d 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 0b806cddde20 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 63aa52a9c87d 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 7a6eab72a6f4 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new de475f991135 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new db3311e6f25c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new e62e19a93187 103: onsuccess: #555: 1: Success after binutils: 4 commits new 14c457d6df61 104: onsuccess: #558: 1: Success after binutils: 3 commits new 14958ea5a0f1 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new 1ecbb4968a5a 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 851b0d4abfd3 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 223494c1106c 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] new 90029301a34d 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 90ec3a8fbf62 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new 42a698d6751e 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 9e877a4dd7b3 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new d13aeeb651ae 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] new 33ce42922c97 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] new c0278b8e0cdf 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new 42d84b75cef4 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] new 55c5d3191390 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] new ca09a0047e4d 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] new bf26a8a3a0ec 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] new 25a915683a2f 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new d14aa7d900e8 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 66da2471c2c5 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 7a9e865973d3 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] new 681d4bb50dec 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] new f6c451681257 125: onsuccess: #581: 1: Success after binutils: 4 commits new 14ff3301701c 126: onsuccess: #582: 1: Success after gcc: 9 commits new 52bd31ea6301 127: onsuccess: #584: 1: Success after linux: 21 commits new afa93a310ca4 128: onsuccess: #586: 1: Success after binutils: 22 commits new 3e6aa301fbc5 129: onsuccess: #588: 1: Success after linux: 4 commits new aad3aca07ae7 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new 456e7535ef5b 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new bebd59d41cf8 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 79514261c80c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new 6ebdf46627ec 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 326966755683 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new ee3dadbc91bf 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new f6aac32ebc69 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new b8e7ffe47d4e 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 7f50bc54a7ff 139: onsuccess: #599: 1: Success after binutils: 10 commits new 1630ec00c4ac 140: onsuccess: #600: 1: Success after gcc: 23 commits new c0c7cd81f973 141: onsuccess: #601: 1: Success after linux: 794 commits new d0b24d392af7 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 06180f122ad6 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 0e80a300ae5b 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...]

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 (2b1909e3cf2b) \ 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 1756 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 53116 -> 52732 bytes 04-build_abe-gcc/console.log.xz | Bin 235308 -> 234472 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 236956 -> 234656 bytes 08-build_abe-gdb/console.log.xz | Bin 52792 -> 52152 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3848 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2672 bytes 11-check_regression/console.log.xz | Bin 6324 -> 5760 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 73 +- 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 61 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 + sumfiles/g++.log.xz | Bin 2905260 -> 2910864 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2571516 -> 2550408 bytes sumfiles/gcc.sum | 4222 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 953576 -> 949524 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230804 -> 230460 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469524 -> 469580 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2439 insertions(+), 2424 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