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 08c46c068327 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards e3a007eae7b0 141: onsuccess: #601: 1: Success after linux: 794 commits discards 76bc71564737 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 804420a01001 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 56ab76db59af 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] discards 834ed8dc2bec 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] discards 57bf1d57016a 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] discards a9e86b8c7cb5 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] discards 978fd8aa6fe2 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] discards 9112f10c9de4 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] discards 106a1b762f3b 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] discards fc62bbed6842 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] discards 4b127b991412 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] discards fd9c995ea1ed 129: onsuccess: #588: 1: Success after linux: 4 commits discards b3f4da60d2a0 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 2e74c0783d1c 127: onsuccess: #584: 1: Success after linux: 21 commits discards b660bcec951b 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 20ec215fd41a 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 20796e334add 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] discards de79595edade 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] discards c7384fe6ced8 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] discards 03f5faa60055 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] discards c36b3f5b576d 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] discards f3851197e3c3 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] discards a53c5b1af1cc 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] discards fa6eec0c4527 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] discards 56659bfa6ff5 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] discards ce9ef1d58b48 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] discards 9728e8eaccc3 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] discards 38705d565f15 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] discards d74c5a68224a 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] discards 23de49eebb95 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] discards 32d806c10fd6 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] discards 64b72d854017 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] discards e01092ff8c0a 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] discards 603066c51d1a 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] discards 157c25e643ad 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] discards 29117a6c13ac 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] discards 9d297d086a2b 104: onsuccess: #558: 1: Success after binutils: 3 commits discards cf5ee619cd4c 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 3d6688ac2b67 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] discards 3a50d0460e91 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] discards 730e1223204c 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] discards 330496a62aca 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards 5890a22b88ed 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards b1a679bf0107 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] discards 379eaeb29ac7 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 068b5563fb73 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] discards 76244742800c 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards ad0676ccd5cf 93: onsuccess: #544: 1: Success after linux: 34 commits discards 508061ec5483 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 8039a27408f2 91: onsuccess: #539: 1: Success after linux: 27 commits discards 4686920c318d 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 699b294fb663 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 615cdfad4f6a 88: onsuccess: #534: 1: Success after linux: 12 commits discards d46fe5a4d10f 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] discards 31cb72c041ae 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 8064ec159327 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] discards c9607e46d5a2 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] discards 6326e8e1839e 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] discards 1ba78a45dcfd 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] discards 89aebce76508 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] discards 4ec6f31cc4e7 80: onsuccess: #524: 1: Success after linux: 9 commits discards 0562cc76dc2a 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 71a58d0786ad 78: onsuccess: #522: 1: Success after binutils: 10 commits discards f44d5e0b61a9 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] discards eac3dfe28127 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] discards e11601dfc840 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] discards f30dfb84904a 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] discards 10af231a1fe7 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] discards c3baf22bdfe2 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] discards 880527062d3a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] discards 73e1d8b43c0b 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] discards 72ee2ee9c94f 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] discards d21fc16be7e4 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] discards 02fa787fc452 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] discards 09b8143de43c 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] discards 6ed7c731cb35 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] discards d6a46fb36307 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] discards 371518e4783e 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] discards ec602fa9902f 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] discards f2716409b2f9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] discards b52312377158 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] discards 492cd624633d 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] discards f88ae51b4256 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] discards 55fad0a7f0ca 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] discards 396e3b8ed400 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] discards 3ac372592f53 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] discards c71e34d1ffde 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] discards ca653b02cf8c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] discards 823655f6d55f 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] discards 306e5947e3a2 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 23665f7e359a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards b9742704a816 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 695bdb4294bf 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] discards 945aaeedb126 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] discards 9e4e828fe1ae 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] discards f1f218c438c4 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] discards b28c9b5f713a 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] discards 0c4a6bd9680e 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/g [...] discards d15a3ce87fa5 42: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 3726a1afc7dc 42: onsuccess: #478: 1: Success after binutils/gcc/linux/g [...] new 3154a272c5a4 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/g [...] new 9cbe115d4009 44: onsuccess: #480: 1: Success after binutils/gcc/linux/g [...] new 0a76104176c4 45: onsuccess: #481: 1: Success after binutils/gcc/linux/g [...] new 2f33187ce148 46: onsuccess: #483: 1: Success after binutils/gcc/linux/g [...] new 79b52bb7b20b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/g [...] new 17f67230368f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/g [...] new 77fb47ed1c77 49: onsuccess: #487: 1: Success after binutils: 11 commits new 439812e3af87 50: onsuccess: #490: 1: Success after binutils: 6 commits new 47f2d8c61953 51: onsuccess: #493: 1: Success after binutils: 13 commits new e47cc4196d21 52: onsuccess: #495: 1: Success after binutils/gcc/linux/g [...] new d20384fb0b72 53: onsuccess: #496: 1: Success after binutils/gcc/linux/g [...] new e846d5e2650e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/g [...] new b93ee148f07d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/g [...] new 66102c106926 56: onsuccess: #499: 1: Success after binutils/gcc/linux/g [...] new 9761613fdc0c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/g [...] new 77035447a057 58: onsuccess: #501: 1: Success after binutils/gcc/linux/g [...] new 675d5645e73d 59: onsuccess: #502: 1: Success after binutils/gcc/linux/g [...] new 01f921ea44bf 60: onsuccess: #503: 1: Success after binutils/gcc/linux/g [...] new 1fcc28e4cdfe 61: onsuccess: #504: 1: Success after binutils/gcc/linux/g [...] new 39e3a120dfb4 62: onsuccess: #505: 1: Success after binutils/gcc/linux/g [...] new 2fb008b785a5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/g [...] new d0b5e4a983bc 64: onsuccess: #507: 1: Success after binutils/gcc/linux/g [...] new 6b46d9efbcf8 65: onsuccess: #508: 1: Success after binutils/gcc/linux/g [...] new fcdf0a4932d5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/g [...] new 345d2f0363c4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/g [...] new 46df7090e459 68: onsuccess: #511: 1: Success after binutils/gcc/linux/g [...] new 18012905fd7f 69: onsuccess: #512: 1: Success after binutils/gcc/linux/g [...] new dd1388b4cad4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/g [...] new 424b4c3656e3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/g [...] new 1bead442ea9c 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 [...] new 90da4f2f0b7e 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/g [...] new 5c736f703463 74: onsuccess: #517: 1: Success after binutils/gcc/linux/g [...] new 1733d1f7e255 75: onsuccess: #518: 1: Success after binutils/gcc/linux/g [...] new c05e19d85c2f 76: onsuccess: #519: 1: Success after binutils/gcc/linux/g [...] new 94f1ec628d5c 77: onsuccess: #520: 1: Success after binutils/gcc/linux/g [...] new 87224e063e26 78: onsuccess: #522: 1: Success after binutils: 10 commits new 98ff80c41956 79: onsuccess: #523: 1: Success after gcc: 25 commits new e9d7c5f8cbf5 80: onsuccess: #524: 1: Success after linux: 9 commits new 2ba5c173b45e 81: onsuccess: #525: 1: Success after binutils/gcc/linux/g [...] new 32844776f3b1 82: onsuccess: #526: 1: Success after binutils/gcc/linux/g [...] new 239fcdc6498b 83: onsuccess: #527: 1: Success after binutils/gcc/linux/g [...] new 4b25d1970f19 84: onsuccess: #528: 1: Success after binutils/gcc/linux/g [...] new d6f45b89435c 85: onsuccess: #529: 1: Success after binutils/gcc/linux/g [...] new 9d9dc12a7dd4 86: onsuccess: #532: 1: Success after gcc: 16 commits new 10eed17c8190 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267- [...] new 43d898e17928 88: onsuccess: #534: 1: Success after linux: 12 commits new 4d4c6b91a1e6 89: onsuccess: #536: 1: Success after binutils: 27 commits new 5af6d1f8db8e 90: onsuccess: #538: 1: Success after glibc: 10 commits new b0c0ad981d5a 91: onsuccess: #539: 1: Success after linux: 27 commits new 3dc204e1d43b 92: onsuccess: #543: 1: Success after glibc: 4 commits new e1d491fc0455 93: onsuccess: #544: 1: Success after linux: 34 commits new 2c1d6a6339a4 94: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new b780628c235a 95: onsuccess: #546: 1: Success after binutils/gcc/linux/g [...] new 2438e29c65ab 96: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 930d5e5f56e3 97: onsuccess: #548: 1: Success after binutils/gcc/linux/g [...] new 6d24870c87a3 98: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 3da90d7d3d24 99: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 57836245467e 100: onsuccess: #551: 1: Success after binutils/gcc/linux/ [...] new d6ace63e8312 101: onsuccess: #552: 1: Success after binutils/gcc/linux/ [...] new 8e51f116940d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/ [...] new a7a292aef63b 103: onsuccess: #555: 1: Success after binutils: 4 commits new 1f612240ffe4 104: onsuccess: #558: 1: Success after binutils: 3 commits new eb8a09c1f417 105: onsuccess: #560: 1: Success after binutils/gcc/linux/ [...] new d768fe4e70b0 106: onsuccess: #561: 1: Success after binutils/gcc/linux/ [...] new 6f88586ae252 107: onsuccess: #562: 1: Success after binutils/gcc/linux/ [...] new 3413e6243a78 108: onsuccess: #563: 1: Success after binutils/gcc/linux/ [...] new 8b363528787b 109: onsuccess: #564: 1: Success after binutils/gcc/linux/ [...] new 73859115e48e 110: onsuccess: #565: 1: Success after binutils/gcc/linux/ [...] new e1cd0a3ec5c9 111: onsuccess: #566: 1: Success after binutils/gcc/linux/ [...] new 925429b38605 112: onsuccess: #567: 1: Success after binutils/gcc/linux/ [...] new 6a9e72a10d1b 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 4 [...] new 9ba80f9ffac1 114: onsuccess: #569: 1: Success after binutils/gcc/linux/ [...] new 6f74eea8c59d 115: onsuccess: #570: 1: Success after binutils/gcc/linux/ [...] new 1ffc7d96a87f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/ [...] new 17134a806a19 117: onsuccess: #572: 1: Success after binutils/gcc/linux/ [...] new 1e610a8df420 118: onsuccess: #573: 1: Success after binutils/gcc/linux/ [...] new 5987eda95523 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/ [...] new 4071955d5f00 120: onsuccess: #575: 1: Success after binutils/gcc/linux/ [...] new d0571fe37ef9 121: onsuccess: #576: 1: Success after binutils/gcc/linux/ [...] new 0c0c8a2f2a2a 122: onsuccess: #577: 1: Success after binutils/gcc/linux/ [...] new 8f4c7bf62d3e 123: onsuccess: #578: 1: Success after binutils/gcc/linux/ [...] new e0d9412567a2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/ [...] new db93e7835b79 125: onsuccess: #581: 1: Success after binutils: 4 commits new 65c1813ace2d 126: onsuccess: #582: 1: Success after gcc: 9 commits new c15b34d87ea3 127: onsuccess: #584: 1: Success after linux: 21 commits new 82c7862dc2d7 128: onsuccess: #586: 1: Success after binutils: 22 commits new 3e0a32d7fd32 129: onsuccess: #588: 1: Success after linux: 4 commits new 139a35e20ac5 130: onsuccess: #589: 1: Success after binutils/gcc/linux/ [...] new 262f808c5ae9 131: onsuccess: #590: 1: Success after binutils/gcc/linux/ [...] new c422e26da98a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/ [...] new 4c763cab0bed 133: onsuccess: #592: 1: Success after binutils/gcc/linux/ [...] new f9b3954acc16 134: onsuccess: #593: 1: Success after binutils/gcc/linux/ [...] new 944d7bd57069 135: onsuccess: #594: 1: Success after binutils/gcc/linux/ [...] new 73c73fae6784 136: onsuccess: #595: 1: Success after binutils/gcc/linux/ [...] new 13c3ae285f96 137: onsuccess: #596: 1: Success after binutils/gcc/linux/ [...] new 21932e931b8f 138: onsuccess: #597: 1: Success after binutils/gcc/linux/ [...] new 6f08d08a210e 139: onsuccess: #599: 1: Success after binutils: 10 commits new 4a9167daca8b 140: onsuccess: #600: 1: Success after gcc: 23 commits new 65c9f8f13e24 141: onsuccess: #601: 1: Success after linux: 794 commits new c632cdba2547 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 2b1909e3cf2b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...]

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 (08c46c068327) \ 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 1740 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 52988 -> 53116 bytes 04-build_abe-gcc/console.log.xz | Bin 233460 -> 235308 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8656 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 234812 -> 236956 bytes 08-build_abe-gdb/console.log.xz | Bin 51024 -> 52792 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3868 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2668 -> 2656 bytes 11-check_regression/console.log.xz | Bin 7968 -> 6324 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 217 +- 11-check_regression/results.regressions | 46 - 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 46 - sumfiles/g++.log.xz | Bin 2924716 -> 2905260 bytes sumfiles/g++.sum | 127 +- sumfiles/gcc.log.xz | Bin 2568608 -> 2571516 bytes sumfiles/gcc.sum | 4744 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 951820 -> 953576 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230612 -> 230804 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 475896 -> 469524 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2632 insertions(+), 2906 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