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 edadf22eea9 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 5f2909e76b8 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 14e3dc71518 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 1ff3b6c486a 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 64e195e1837 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 63924749da7 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards c2ed5215d80 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 442d059f089 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 6b1b9fc6462 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards ac6090b5610 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards d5b7e1125fe 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 69c546e5c5f 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 6629ba1dab4 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 3de00224dc9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards af5a2fa8fac 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 8fc37e648fe 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards db7e8bafd5f 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6be68bd03a2 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 195e69933fc 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 332f6c9020f 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 2017d75fed5 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 721616d2d90 104: onsuccess: #558: 1: Success after binutils: 3 commits discards e32cd2317af 103: onsuccess: #555: 1: Success after binutils: 4 commits discards aa558fbad3d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 43fdde783e9 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards f7dd2c1130f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards ac323cc116d 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards c301bb1e996 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 0da0a25597e 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 6e82c3a9265 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 6ba8c38b4a7 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 473c0eefe0b 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 79490f27327 93: onsuccess: #544: 1: Success after linux: 34 commits discards 8ff11bc12cc 92: onsuccess: #543: 1: Success after glibc: 4 commits discards e8da6b2d8e8 91: onsuccess: #539: 1: Success after linux: 27 commits discards 7f86dcd93c7 90: onsuccess: #538: 1: Success after glibc: 10 commits discards eaa079e8c64 89: onsuccess: #536: 1: Success after binutils: 27 commits discards f5ba735056e 88: onsuccess: #534: 1: Success after linux: 12 commits discards 36d5d4fb3f6 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards e6775ebd349 86: onsuccess: #532: 1: Success after gcc: 16 commits discards d7c438775a1 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards b894f12b367 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards d341ee583e2 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 96ddefca607 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards f6745ccea78 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 133a6b9f5c6 80: onsuccess: #524: 1: Success after linux: 9 commits discards 24322c17e49 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 3290d90a897 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 3c567741f2a 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards 374cd26bf66 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards f6dd60e9b56 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards e852162c410 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards f44d5fc3c7e 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 7c829929c00 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards e888fdf34c3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 1db5089967c 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards d1a90a55758 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards 0357cc8ee4f 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 25d9bb2aeca 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards bb73bdd122e 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards e69314dc830 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 841aa0e919e 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 5e82829b2fb 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards 589d888da76 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 1a23da704da 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards fcba0f27f28 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 6baedf9ee2a 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 6dded004ce8 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards b4feddaadab 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards d42e97b763c 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 14a598d0b97 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 4444038015a 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 70d91eaf9f2 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards ff04a957269 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards f1faab691c7 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 7c98a4d76de 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 1e464757434 49: onsuccess: #487: 1: Success after binutils: 11 commits discards b18b62d91ff 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards f4f968993fc 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 46310a200f7 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 03426ec9b9d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards c4c20f17e4b 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards b6e975ce4a6 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 3fe0c3a8087 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 6d2d50499a1 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards a8fad16bf2a 40: onsuccess: #476: 1: Success after linux: 69 commits discards 005aaf7029e 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 6706902faff 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards 9ed18c3c73c 37: onsuccess: #470: 1: Success after binutils: 3 commits discards f6e6fb03052 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards ff99e1b82fb 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 7cbc17ce934 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 03a87ec9b2b 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] discards ab3dee095f5 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] discards 184306ebd9f 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] discards 571a07b7cc0 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] discards 1be08bc2371 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] discards da4270c6052 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] discards 880fceebdc0 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 456a46f4f95 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] discards 571616076dd 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 2403ee680e9 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gl [...] new 334b461e083 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] new 19c139a5239 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new a3017e469f6 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] new ed3e5d51f4b 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] new ca46dfe0223 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] new 29545e1bcb0 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] new 2140b2aa63c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] new 175fb7f98fa 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] new 136ccb4fa95 34: onsuccess: #465: 1: Success after binutils: 11 commits new 45f8c0b68e8 35: onsuccess: #467: 1: Success after glibc: 2 commits new 1e355dae0fb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 16abde1afa4 37: onsuccess: #470: 1: Success after binutils: 3 commits new 40a64349f93 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new 9123091b1d1 39: onsuccess: #474: 1: Success after binutils: 8 commits new 8ea8c7b052d 40: onsuccess: #476: 1: Success after linux: 69 commits new 8bcdee0345c 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 536fdc72388 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 2e4bd9cfdf5 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 8d6c913ff70 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new cd6340928bf 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 7dbe4b96c76 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 05a8bf6439e 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 3057943ff94 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new edceef8a4e1 49: onsuccess: #487: 1: Success after binutils: 11 commits new b9dca491c1e 50: onsuccess: #490: 1: Success after binutils: 6 commits new c80b37e4c8a 51: onsuccess: #493: 1: Success after binutils: 13 commits new 965f2e07f7f 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new de8c09306ba 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new a410ffe721e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new dd0d92d9d49 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 0defa6a2c84 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new dd82802954d 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new d676ac99e7c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new beee14d1195 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new 9714d9b3897 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new eafd3e0e81f 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new 1698cc1d62c 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 5ed1ecee2ce 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 068122a72e9 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new 7e4991d5202 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 0cc6f47a756 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 03805bdde3c 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new ea890be08cd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new bb12f2e7e7b 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new 61eda552305 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 1c81fda7f6e 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new ff68fa5a473 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 14ad6eaec5d 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new d4f8102cb07 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new ccf930690b3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new e3baebc294a 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new dfdd37f09b3 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new fbf925ee25a 78: onsuccess: #522: 1: Success after binutils: 10 commits new 3bcf8fd276b 79: onsuccess: #523: 1: Success after gcc: 25 commits new e23301e37e0 80: onsuccess: #524: 1: Success after linux: 9 commits new 4f594255d68 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new d1f92436494 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new de99a8725aa 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 578405028dc 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 17471530f5e 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 8139f1f2ee3 86: onsuccess: #532: 1: Success after gcc: 16 commits new 78b9e464b03 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new e92e3c9d493 88: onsuccess: #534: 1: Success after linux: 12 commits new 267463b3d0a 89: onsuccess: #536: 1: Success after binutils: 27 commits new ebef90f2149 90: onsuccess: #538: 1: Success after glibc: 10 commits new 9d82ab43ae9 91: onsuccess: #539: 1: Success after linux: 27 commits new 05af2425202 92: onsuccess: #543: 1: Success after glibc: 4 commits new ee70322f651 93: onsuccess: #544: 1: Success after linux: 34 commits new db47fadb759 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 62b5e063a4c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new bc96e2830f1 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 49c1d6238be 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new d992eec155a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 3844a6be9a1 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 7e658035700 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 9358d5d1076 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 0dd94e42d16 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 79a71b59a32 103: onsuccess: #555: 1: Success after binutils: 4 commits new 27eae385592 104: onsuccess: #558: 1: Success after binutils: 3 commits new 85274af4d4a 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 1cd22c40c05 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 02cb273c188 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 3d3e6a133dc 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new ad0713176de 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 02b6db8a825 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 7cfe45d1cd5 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 88c234a4ac9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 3553efd60eb 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new fc3e9ab8d60 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new b1c12459ec3 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 633ecbeaf02 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 760eaf6c63a 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 5a6cd4fc54b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 1a95da1ec34 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new d8edacca20c 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 3f893470096 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new d4e3fa8e3d1 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 431c76b50c1 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 6e89d087185 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new b2830c8a3ec 125: onsuccess: #581: 1: Success after binutils: 4 commits new 1216324432c 126: onsuccess: #582: 1: Success after gcc: 9 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 (edadf22eea9) \ 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 1796 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52196 -> 52228 bytes 04-build_abe-gcc/console.log.xz | Bin 235004 -> 233872 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 235844 -> 236252 bytes 08-build_abe-gdb/console.log.xz | Bin 51000 -> 51280 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3872 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2948 -> 2580 bytes 11-check_regression/console.log.xz | Bin 4664 -> 6076 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 10 +- 11-check_regression/results.compare2 | 95 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 27 + sumfiles/g++.log.xz | Bin 2905400 -> 2924860 bytes sumfiles/g++.sum | 51 +- sumfiles/gcc.log.xz | Bin 2564648 -> 2547136 bytes sumfiles/gcc.sum | 4140 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 954508 -> 955288 bytes sumfiles/gfortran.sum | 72 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2248 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 229516 -> 229436 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 472160 -> 472996 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2389 insertions(+), 2165 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