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 1216324432c 126: onsuccess: #582: 1: Success after gcc: 9 commits discards b2830c8a3ec 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 6e89d087185 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 431c76b50c1 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards d4e3fa8e3d1 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 3f893470096 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards d8edacca20c 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 1a95da1ec34 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 5a6cd4fc54b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 760eaf6c63a 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 633ecbeaf02 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards b1c12459ec3 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards fc3e9ab8d60 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 3553efd60eb 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 88c234a4ac9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 7cfe45d1cd5 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 02b6db8a825 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards ad0713176de 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 3d3e6a133dc 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 02cb273c188 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 1cd22c40c05 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 85274af4d4a 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 27eae385592 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 79a71b59a32 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 0dd94e42d16 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 9358d5d1076 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 7e658035700 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 3844a6be9a1 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards d992eec155a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 49c1d6238be 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards bc96e2830f1 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 62b5e063a4c 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards db47fadb759 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards ee70322f651 93: onsuccess: #544: 1: Success after linux: 34 commits discards 05af2425202 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 9d82ab43ae9 91: onsuccess: #539: 1: Success after linux: 27 commits discards ebef90f2149 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 267463b3d0a 89: onsuccess: #536: 1: Success after binutils: 27 commits discards e92e3c9d493 88: onsuccess: #534: 1: Success after linux: 12 commits discards 78b9e464b03 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 8139f1f2ee3 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 17471530f5e 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 578405028dc 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards de99a8725aa 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards d1f92436494 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards 4f594255d68 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards e23301e37e0 80: onsuccess: #524: 1: Success after linux: 9 commits discards 3bcf8fd276b 79: onsuccess: #523: 1: Success after gcc: 25 commits discards fbf925ee25a 78: onsuccess: #522: 1: Success after binutils: 10 commits discards dfdd37f09b3 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards e3baebc294a 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards ccf930690b3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards d4f8102cb07 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards 14ad6eaec5d 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards ff68fa5a473 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 1c81fda7f6e 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 61eda552305 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards bb12f2e7e7b 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards ea890be08cd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 03805bdde3c 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards 0cc6f47a756 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards 7e4991d5202 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 068122a72e9 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 5ed1ecee2ce 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards 1698cc1d62c 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards eafd3e0e81f 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards 9714d9b3897 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards beee14d1195 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards d676ac99e7c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards dd82802954d 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 0defa6a2c84 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards dd0d92d9d49 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards a410ffe721e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards de8c09306ba 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 965f2e07f7f 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards c80b37e4c8a 51: onsuccess: #493: 1: Success after binutils: 13 commits discards b9dca491c1e 50: onsuccess: #490: 1: Success after binutils: 6 commits discards edceef8a4e1 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 3057943ff94 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 05a8bf6439e 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 7dbe4b96c76 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards cd6340928bf 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards 8d6c913ff70 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 2e4bd9cfdf5 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 536fdc72388 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 8bcdee0345c 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards 8ea8c7b052d 40: onsuccess: #476: 1: Success after linux: 69 commits discards 9123091b1d1 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 40a64349f93 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards 16abde1afa4 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 1e355dae0fb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 45f8c0b68e8 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 136ccb4fa95 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 175fb7f98fa 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] discards 2140b2aa63c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] discards 29545e1bcb0 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] discards ca46dfe0223 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] discards ed3e5d51f4b 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] discards a3017e469f6 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] discards 19c139a5239 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] discards 334b461e083 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] new dacc21aa59c 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gl [...] new 490ebf1eb7d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 901bfd310f0 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] new edf524aa490 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] new 18b7a923c3b 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] new 359301b9c5a 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] new 6d2b49da2b3 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] new d8b36c4e158 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] new 8aed59b2c7c 34: onsuccess: #465: 1: Success after binutils: 11 commits new 5141d4803fe 35: onsuccess: #467: 1: Success after glibc: 2 commits new a38ed0c4be8 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new b7b46d27183 37: onsuccess: #470: 1: Success after binutils: 3 commits new 1dda24c300c 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new 1a28f16f7d1 39: onsuccess: #474: 1: Success after binutils: 8 commits new f19224d355c 40: onsuccess: #476: 1: Success after linux: 69 commits new 2b443500414 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 7b5719e0531 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 8e2584f8e77 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new d31b52db255 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new f9c0d21379a 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new b76631ee0a9 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new d624f14d6e4 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 147f104cb6d 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 261d8bdc67e 49: onsuccess: #487: 1: Success after binutils: 11 commits new 4dc21ab1a75 50: onsuccess: #490: 1: Success after binutils: 6 commits new 17456cd6281 51: onsuccess: #493: 1: Success after binutils: 13 commits new d3e24207c02 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 9f2dabbdb40 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 559dc9d537e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 456d8b955b6 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 245c3a7ef04 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 976d0d7d08f 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 8d290f0c893 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new ec3966367c8 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new f1ccd29e35b 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new 134b8dc18da 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new e901ef8ef42 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new b78660eea6e 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 1016a607aa5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new fdf33b3d4f9 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new ddb1d81cbcc 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 45cab906309 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new fae72b0438d 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 5d888e19084 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new 42cf71ce3ab 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new dc712bf3e96 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 9844d5864ac 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 3c00333a0ce 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new 4d523fb51a9 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new 55b782443a3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new 85586d95e18 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new 1135aa35726 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 789b1c8ec89 78: onsuccess: #522: 1: Success after binutils: 10 commits new cac6f6e5ad9 79: onsuccess: #523: 1: Success after gcc: 25 commits new 02059c70f6f 80: onsuccess: #524: 1: Success after linux: 9 commits new 64ef2e4f4ef 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 517ad805ceb 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 3323db2dfa6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 5a7b5fc58c1 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new f09b9766a97 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 22fcadc13ef 86: onsuccess: #532: 1: Success after gcc: 16 commits new 10436904f4c 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new 9aad77d8130 88: onsuccess: #534: 1: Success after linux: 12 commits new c31dae5dab6 89: onsuccess: #536: 1: Success after binutils: 27 commits new 265f5846f9b 90: onsuccess: #538: 1: Success after glibc: 10 commits new c8c656b607b 91: onsuccess: #539: 1: Success after linux: 27 commits new c2b5b033ef8 92: onsuccess: #543: 1: Success after glibc: 4 commits new 4c5174cfdb9 93: onsuccess: #544: 1: Success after linux: 34 commits new c02603d37fc 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d4e80750958 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 055c3507f8e 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 774e24e085d 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new e1836f12257 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new aeb1c517f16 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 788cfd8c26f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 20378aad4dc 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 408476f7a3d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 8c804637974 103: onsuccess: #555: 1: Success after binutils: 4 commits new 919c4ea660e 104: onsuccess: #558: 1: Success after binutils: 3 commits new 154afda462f 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 87023f66521 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 64b5ec05631 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new f1c8643ffe3 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 8cb94cf6422 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 6283dffd325 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 32279e03f39 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 4fc14da0ff9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new bafe432a4c3 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 7abf1e9909d 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 73ca17c40e9 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new f0465432cd1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new ac8b9280375 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 14be10b4e5f 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 2dd44f9b4d0 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 3526927d6fc 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new a94310ea2e5 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 1f8d05465ca 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new fbd174be60a 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 37625a684d2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new eca708eb3a0 125: onsuccess: #581: 1: Success after binutils: 4 commits new c433c2730b9 126: onsuccess: #582: 1: Success after gcc: 9 commits new 6460665a237 127: onsuccess: #584: 1: Success after linux: 21 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 (1216324432c) \ 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 1660 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52228 -> 52488 bytes 04-build_abe-gcc/console.log.xz | Bin 233872 -> 233752 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8800 bytes 07-build_abe-glibc/console.log.xz | Bin 236252 -> 235740 bytes 08-build_abe-gdb/console.log.xz | Bin 51280 -> 50544 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2656 bytes 11-check_regression/console.log.xz | Bin 6076 -> 5584 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 9 +- 11-check_regression/results.compare2 | 97 +- 11-check_regression/results.regressions | 27 - 12-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 27 - sumfiles/g++.log.xz | Bin 2924860 -> 2920980 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2547136 -> 2551176 bytes sumfiles/gcc.sum | 4142 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 955288 -> 954088 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2248 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 229436 -> 229568 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 472996 -> 470168 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2211 insertions(+), 2321 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