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 ad9f012f0d 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards 3bd8a48938 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 95cdbf2861 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 8c3319530c 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 4273118399 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards b4b3c5200d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 5df1719d96 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 296537c1c1 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 484dbd3145 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 4097f6df8c 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 344e61f32a 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 4520638013 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 9f3bcd6ee6 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 70ac232c63 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 193487de6e 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 9256529e11 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 1838aeeb38 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 0654d27f91 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards cb471a2ea8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 245f04b90a 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 62ece4718a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 84da073c59 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 8cdf239a13 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 42a77fdf60 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards b4651beec6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 25fe91a626 93: onsuccess: #544: 1: Success after linux: 34 commits discards 0fcac0c9b5 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 10c0662cbd 91: onsuccess: #539: 1: Success after linux: 27 commits discards 4c4a3ad213 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 62b6646f9c 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 2b24e91981 88: onsuccess: #534: 1: Success after linux: 12 commits discards 7de0fa8034 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 6145571234 86: onsuccess: #532: 1: Success after gcc: 16 commits discards fcbf26ed2a 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 8224dde6a7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 08a1a33dc2 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards b0d4828d80 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 5bfb8602fc 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 933a249f96 80: onsuccess: #524: 1: Success after linux: 9 commits discards af648c0b23 79: onsuccess: #523: 1: Success after gcc: 25 commits discards faf8dbfa38 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 2b98f6476c 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 9307964bfa 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 799a5158ab 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 25333333b3 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards a302c11666 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 409dfaa869 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 8a63b3e55e 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 1ceec8c589 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 557a8cda85 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 8b4e0a38a4 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards d236f0ce83 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 973e86eae3 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 20bf03af69 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards e64058cfca 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards a7fa1866f5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 5e05f2dba0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 36f530d987 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards eda8868b67 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 43f0e01f07 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 3a3c47412c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards bcf3747409 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 293083b56e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 4007ae3bc7 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards e5f90b25dd 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 06649526b4 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 4cc08950b3 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 59989c4785 51: onsuccess: #493: 1: Success after binutils: 13 commits discards ded0a807c6 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 050346f4b1 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 6c20d4b74e 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards b052bf6a3e 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 7f5700e41c 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 5e23ce7f62 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards e5747a09e8 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 6c491a3c33 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 135cc23f1b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 8863a2712d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards bd9015ab55 40: onsuccess: #476: 1: Success after linux: 69 commits discards acc0073b11 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 346ac59e1e 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 2cb07adb3c 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 76c5f5dfbf 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 5c12c02a97 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 2dbe3a0e57 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 650c0a60bf 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards b223d1ce26 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards ecb939aed6 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 999bdc6d0d 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 99c8444b57 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 150631f7b7 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 91df006a4c 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards f2c694be6d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 405456ac88 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards d7486b1beb 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards b8320ede00 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards bf6ea693d6 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7ed5d69170 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e5c3355bbc 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d18eb26f58 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2bba199435 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b31f90936f 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1c0b5d7717 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b9ae471842 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ce78442249 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f948f5589f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new f5cde6457f 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new baf5ea14ca 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new ed47d1d34a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 960989fc5b 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 9b314895a5 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 354be05582 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 7df74db0b0 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new e43a45592d 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 9ae6a14237 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new c99f6fe7ec 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 0de80ae17e 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 9882c89aef 34: onsuccess: #465: 1: Success after binutils: 11 commits new 9afe78d161 35: onsuccess: #467: 1: Success after glibc: 2 commits new 3e9fdae9c1 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 596bf503be 37: onsuccess: #470: 1: Success after binutils: 3 commits new 80fd032bc8 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new c38f3b8526 39: onsuccess: #474: 1: Success after binutils: 8 commits new f7c353f6df 40: onsuccess: #476: 1: Success after linux: 69 commits new 67d4e40fe3 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new b885d1b9df 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 7c09ccb8dc 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 139ff848d6 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 32be72c32e 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 0ff9071143 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new ae91d60a5b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 8b7738d039 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 67278499c6 49: onsuccess: #487: 1: Success after binutils: 11 commits new a67548517d 50: onsuccess: #490: 1: Success after binutils: 6 commits new 154e8c05a5 51: onsuccess: #493: 1: Success after binutils: 13 commits new 3cd9f3c1df 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 617aff013a 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 2ae961b702 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 09b39156ab 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new b670117b5a 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 551f78393e 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new e8803211db 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 951b20cc9c 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new f0eabb3d75 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 26a45144e4 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 84acc815c8 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 1e7299e781 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new d3efa85fe5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new b6e4c7250c 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 8c67f68c38 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new fcb90468e4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new d0c3578d93 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 713aed94f1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new cb11af18b4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 186a020771 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new a7d42d1b2e 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 380c18bf08 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 8f454b5974 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new a53b33f421 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new ba3596105d 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 4789349ec9 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new c79cdb178c 78: onsuccess: #522: 1: Success after binutils: 10 commits new 3928d953d6 79: onsuccess: #523: 1: Success after gcc: 25 commits new 7e6141fbdb 80: onsuccess: #524: 1: Success after linux: 9 commits new ca87b22dde 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new ddf62d9190 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 23a99ec3b6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 859c4366b2 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new c3a6e171d9 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 86fec912c6 86: onsuccess: #532: 1: Success after gcc: 16 commits new f7c26e680f 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 2d16580b55 88: onsuccess: #534: 1: Success after linux: 12 commits new c4ac4733e2 89: onsuccess: #536: 1: Success after binutils: 27 commits new 5a3f4a2c13 90: onsuccess: #538: 1: Success after glibc: 10 commits new 8afdb70f84 91: onsuccess: #539: 1: Success after linux: 27 commits new 07fe7ff5f5 92: onsuccess: #543: 1: Success after glibc: 4 commits new 97723deae2 93: onsuccess: #544: 1: Success after linux: 34 commits new 7b06bd2bfe 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 51b1cf48aa 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7eed076e8d 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new cc59c4d638 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 265dc78937 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 769a421011 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 675d6dfdb8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 77bee2d886 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 761d409fce 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new f33cf83aa8 103: onsuccess: #555: 1: Success after binutils: 4 commits new 1c3cdf168b 104: onsuccess: #558: 1: Success after binutils: 3 commits new 13e1227e45 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 4e08982eee 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new ac6c6b4eb8 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 1d3cd476ec 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 7394ed2e84 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 084fd0be14 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 363d1ba43c 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new bc44d52a3b 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new cdf18ab266 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 4c7a5b8eed 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new aae826bedb 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 0a0ece943a 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 51bd0715b9 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new e012ece76b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 06ecbb2a2b 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...]
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 (ad9f012f0d) \ 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 1684 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2716 bytes 03-build_abe-binutils/console.log.xz | Bin 53868 -> 52316 bytes 04-build_abe-gcc/console.log.xz | Bin 232708 -> 234424 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 235132 -> 235776 bytes 08-build_abe-gdb/console.log.xz | Bin 51996 -> 51608 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2392 -> 2596 bytes 11-check_regression/console.log.xz | Bin 5584 -> 46864 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 4525 +++++++++++ 11-check_regression/mail-body.txt | 101 + 11-check_regression/results.compare | 4579 ++++++++++- 11-check_regression/results.compare2 | 9836 ++++++++++++++++++++++- 11-check_regression/results.regressions | 101 + 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 101 + sumfiles/g++.log.xz | Bin 2907768 -> 2924280 bytes sumfiles/g++.sum | 5298 +++++++------ sumfiles/gcc.log.xz | Bin 2529016 -> 2556128 bytes sumfiles/gcc.sum | 12728 ++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 950384 -> 952288 bytes sumfiles/gfortran.sum | 296 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229616 -> 229540 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 474560 -> 474904 bytes sumfiles/libstdc++.sum | 14 +- 42 files changed, 29152 insertions(+), 8639 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