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 f446170bb5 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 3b66d536e9 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards 8714aabd89 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards 4769b1c4cd 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards f885d0cb10 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards 32e0254aaf 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 61626ce8bb 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards 29c08fb266 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards a392e62ee0 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 2d55d3f651 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 4f8a2521f9 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 65d7fb4cf1 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards bcc98c537b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 9f08d9a97c 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 13ab4806dc 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 2aae278718 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards fea61bbdc7 104: onsuccess: #558: 1: Success after binutils: 3 commits discards bfaec1ecf6 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 3ed174bedf 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards cfd3656850 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 770bbef16f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 87a2a24e32 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 6162d7adca 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 6fa77e5600 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 13e19747d1 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 050b6c61e5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards de3e50fbb8 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 3cb917b5b9 93: onsuccess: #544: 1: Success after linux: 34 commits discards ee3bc57503 92: onsuccess: #543: 1: Success after glibc: 4 commits discards b1c1e5a68b 91: onsuccess: #539: 1: Success after linux: 27 commits discards c1d6a43abc 90: onsuccess: #538: 1: Success after glibc: 10 commits discards cf6de951bb 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 40a31631fc 88: onsuccess: #534: 1: Success after linux: 12 commits discards 541d6d9e4a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 66a768804a 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 752f1fde28 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 66b0af7b7a 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 3e5d2d1c4d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards a9e6f9f886 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards c38d471593 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards b3a42f8b12 80: onsuccess: #524: 1: Success after linux: 9 commits discards 0ebb4d33fe 79: onsuccess: #523: 1: Success after gcc: 25 commits discards c5ecd982b3 78: onsuccess: #522: 1: Success after binutils: 10 commits discards e3b819747a 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 5b78998f1b 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards bb9e63d925 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 73593da467 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards a2f2ce23ae 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 14d136f8a0 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 75f93d90be 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 19c2f9ac8d 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 7f014c47c9 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards e4fd4800db 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards a63fa0ada8 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards c19a18f016 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 728d09f16e 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 4e4a9ac65b 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards c5ef5260c4 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 9887abdc26 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 771e78b469 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 81300e8519 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 1ac129ffcb 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 8b3df08e01 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 936baa538d 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 17992a416e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards e3423cc6a9 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 1b7e73350c 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 6cccab8da6 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards d0625436d9 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 07362ce035 51: onsuccess: #493: 1: Success after binutils: 13 commits discards a59e63676d 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 4352abbf17 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 91f932a572 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards d38d945084 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards d7c554d031 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards a0ad209162 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 09b36e22f9 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 6b33b71aa0 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards cccd4a1ec1 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 6ce6d2faab 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards a9439d3f72 40: onsuccess: #476: 1: Success after linux: 69 commits discards b75952a730 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 80646887f9 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 803a8d5a56 37: onsuccess: #470: 1: Success after binutils: 3 commits discards a096fdc558 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards a256e1aefe 35: onsuccess: #467: 1: Success after glibc: 2 commits discards c5342c89ea 34: onsuccess: #465: 1: Success after binutils: 11 commits discards f3539e76e8 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards a57dfa5c2c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards bfe111b939 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards de10678f57 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards b0cbdda7bb 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 5abf6754db 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 55bf1c9f6b 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 67524b692c 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 954c6107cd 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards bec80abf97 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 44af406ff5 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 1ad2aaa6e3 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 972f52b309 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards e3da056e44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5954117739 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 972d47b23b 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 390d0fe380 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 35e239168e 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 88fadb8775 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 9629d422ed 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 4481ef8bf6 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 508218938d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 44f497f536 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new bd5c863a2f 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 10074151c1 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 6e6c1532b0 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 53bceb4394 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 8037df3e2c 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 0756712fed 34: onsuccess: #465: 1: Success after binutils: 11 commits new ae36ce1730 35: onsuccess: #467: 1: Success after glibc: 2 commits new 3e25d16fa8 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 3ee7ed95bc 37: onsuccess: #470: 1: Success after binutils: 3 commits new cfaa4688a8 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new fcf5854bce 39: onsuccess: #474: 1: Success after binutils: 8 commits new 7b9f90de7c 40: onsuccess: #476: 1: Success after linux: 69 commits new c6e001ef8c 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 020400c154 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 29c40eed65 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 3589417d5d 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new e2cf5f86ce 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new e0911ca3aa 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 2b605f6b5c 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new eac7d4882a 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new c0038fb99c 49: onsuccess: #487: 1: Success after binutils: 11 commits new f5c67354e9 50: onsuccess: #490: 1: Success after binutils: 6 commits new eb92a9c9ad 51: onsuccess: #493: 1: Success after binutils: 13 commits new 0fbd34d343 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new f84b7ce094 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new ede17a9ab9 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 9b4fff114e 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new a920d362f2 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new a6825a1cbc 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 80ff674431 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 24168dacf0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 2462b97521 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 3bdda31b0d 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 645c116bc2 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 6e9ed1a9fe 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 25e9f3e7be 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 0fd262fee3 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 6ea65c125f 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new c4ceb6eee9 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new d9bff3b629 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 096f1e270d 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 929689cd17 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 0538db6666 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 3f1ecfe315 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 56f8bad2ce 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 422862e9a1 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new f64f56281d 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 779e0663fd 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new f1e8296d1e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 397e3c019e 78: onsuccess: #522: 1: Success after binutils: 10 commits new 66d2d1fa60 79: onsuccess: #523: 1: Success after gcc: 25 commits new ec4c6d22c9 80: onsuccess: #524: 1: Success after linux: 9 commits new 078853907e 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new c0a7b02c47 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new d5fc598178 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new ce1c327613 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 17d79e85a3 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 63a8c84af3 86: onsuccess: #532: 1: Success after gcc: 16 commits new e358bd4d64 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new a99d746313 88: onsuccess: #534: 1: Success after linux: 12 commits new f0ad4675ea 89: onsuccess: #536: 1: Success after binutils: 27 commits new 622090dc63 90: onsuccess: #538: 1: Success after glibc: 10 commits new e5c29c556f 91: onsuccess: #539: 1: Success after linux: 27 commits new a1936b76be 92: onsuccess: #543: 1: Success after glibc: 4 commits new a24a2a6c62 93: onsuccess: #544: 1: Success after linux: 34 commits new b64fd18ee0 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new d324cfa70f 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 446521ecdb 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 68ab069c76 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 3667b18dd9 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 341307d287 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new e4b9e77550 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 2397075d1c 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 7ff329bbe6 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 486a904376 103: onsuccess: #555: 1: Success after binutils: 4 commits new cbaa01b9b0 104: onsuccess: #558: 1: Success after binutils: 3 commits new 79a2415165 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new e916305002 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 897a5572a2 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 671f341803 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new f091b13682 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 2e5710786b 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 39eba30485 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new 138d3427ea 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new e830ca5ca7 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 789d6fc57c 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 625cd29cd7 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 0fe466dda1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new c116e64444 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new bb7fd7167d 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new e2d880e4e4 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new 0184546736 120: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new 4bc712fa26 121: onsuccess: #576: 1: Success after binutils/gcc/linux/gl [...]

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 (f446170bb5) \ 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 1700 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 53300 -> 53664 bytes 04-build_abe-gcc/console.log.xz | Bin 233552 -> 233124 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9536 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 235808 -> 236432 bytes 08-build_abe-gdb/console.log.xz | Bin 51332 -> 51848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2776 -> 2512 bytes 11-check_regression/console.log.xz | Bin 7144 -> 6832 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 11 - 11-check_regression/mail-body.txt | 121 +- 11-check_regression/results.compare | 30 +- 11-check_regression/results.compare2 | 163 +- 11-check_regression/results.regressions | 31 - 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 123 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 31 - sumfiles/g++.log.xz | Bin 2905416 -> 2913988 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 2554508 -> 2556376 bytes sumfiles/gcc.sum | 4329 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 950168 -> 948984 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229544 -> 229652 bytes sumfiles/libgomp.sum | 24 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470020 -> 470736 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2524 insertions(+), 2686 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