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 6460665a237 127: onsuccess: #584: 1: Success after linux: 21 commits discards c433c2730b9 126: onsuccess: #582: 1: Success after gcc: 9 commits discards eca708eb3a0 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 37625a684d2 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards fbd174be60a 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 1f8d05465ca 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards a94310ea2e5 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 3526927d6fc 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 2dd44f9b4d0 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 14be10b4e5f 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards ac8b9280375 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards f0465432cd1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 73ca17c40e9 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 7abf1e9909d 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards bafe432a4c3 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 4fc14da0ff9 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 32279e03f39 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 6283dffd325 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 8cb94cf6422 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards f1c8643ffe3 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 64b5ec05631 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 87023f66521 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 154afda462f 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 919c4ea660e 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 8c804637974 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 408476f7a3d 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 20378aad4dc 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 788cfd8c26f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards aeb1c517f16 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards e1836f12257 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 774e24e085d 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 055c3507f8e 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards d4e80750958 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards c02603d37fc 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 4c5174cfdb9 93: onsuccess: #544: 1: Success after linux: 34 commits discards c2b5b033ef8 92: onsuccess: #543: 1: Success after glibc: 4 commits discards c8c656b607b 91: onsuccess: #539: 1: Success after linux: 27 commits discards 265f5846f9b 90: onsuccess: #538: 1: Success after glibc: 10 commits discards c31dae5dab6 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 9aad77d8130 88: onsuccess: #534: 1: Success after linux: 12 commits discards 10436904f4c 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 22fcadc13ef 86: onsuccess: #532: 1: Success after gcc: 16 commits discards f09b9766a97 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 5a7b5fc58c1 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 3323db2dfa6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 517ad805ceb 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards 64ef2e4f4ef 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 02059c70f6f 80: onsuccess: #524: 1: Success after linux: 9 commits discards cac6f6e5ad9 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 789b1c8ec89 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 1135aa35726 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards 85586d95e18 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards 55b782443a3 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards 4d523fb51a9 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards 3c00333a0ce 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 9844d5864ac 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards dc712bf3e96 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 42cf71ce3ab 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 5d888e19084 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards fae72b0438d 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 45cab906309 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards ddb1d81cbcc 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards fdf33b3d4f9 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 1016a607aa5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards b78660eea6e 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards e901ef8ef42 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards 134b8dc18da 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards f1ccd29e35b 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards ec3966367c8 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 8d290f0c893 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 976d0d7d08f 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 245c3a7ef04 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 456d8b955b6 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 559dc9d537e 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 9f2dabbdb40 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards d3e24207c02 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 17456cd6281 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 4dc21ab1a75 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 261d8bdc67e 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 147f104cb6d 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards d624f14d6e4 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards b76631ee0a9 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards f9c0d21379a 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards d31b52db255 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 8e2584f8e77 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards 7b5719e0531 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 2b443500414 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards f19224d355c 40: onsuccess: #476: 1: Success after linux: 69 commits discards 1a28f16f7d1 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 1dda24c300c 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards b7b46d27183 37: onsuccess: #470: 1: Success after binutils: 3 commits discards a38ed0c4be8 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 5141d4803fe 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 8aed59b2c7c 34: onsuccess: #465: 1: Success after binutils: 11 commits discards d8b36c4e158 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] discards 6d2b49da2b3 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] discards 359301b9c5a 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] discards 18b7a923c3b 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] discards edf524aa490 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] discards 901bfd310f0 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] discards 490ebf1eb7d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new 8e6ad87d9f9 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gl [...] new c4271ea56da 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gl [...] new 9ed5010d280 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gl [...] new b1fed83a990 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gd [...] new ec62814f6a1 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gl [...] new 7501ad85408 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gd [...] new 14346ae1e5f 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gl [...] new 927c7adbd5c 34: onsuccess: #465: 1: Success after binutils: 11 commits new d4a87237aac 35: onsuccess: #467: 1: Success after glibc: 2 commits new 14ae2f2295b 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 8fa7ef70157 37: onsuccess: #470: 1: Success after binutils: 3 commits new a4a396cb2fe 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new 85f9d31523c 39: onsuccess: #474: 1: Success after binutils: 8 commits new 4ff0f9b987a 40: onsuccess: #476: 1: Success after linux: 69 commits new 7ecbf9b5ef9 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 1774fe8235b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 0d80c7f9f09 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 10c6077033a 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 6eb1fd3b7d5 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 75a42779360 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 4e7f994934b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 0661261f7ea 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new da4424396bb 49: onsuccess: #487: 1: Success after binutils: 11 commits new 1a41273fd3c 50: onsuccess: #490: 1: Success after binutils: 6 commits new 16f9c9cc035 51: onsuccess: #493: 1: Success after binutils: 13 commits new b815e41e996 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 0653648c007 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new 45dea898fd3 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new be1ce7d972b 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new d7edb956d6f 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 05cacb1da91 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new ad5b82d7d2b 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new f8f12215523 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new c625a1d72a2 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new d90c541f8f6 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new 41c6ba7d142 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 378114ca327 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 33389942709 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new d36bdbe4c7c 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 8573e745171 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new f52ff009015 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new 976505c7655 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 38599f638b7 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new b7879f6f34e 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new 4a7318c8d56 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 3755354f986 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new b67b429f6e7 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new f33fd210d52 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new f7aa29cb910 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new 61411721e33 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new 32c21fea1d9 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 458170632ec 78: onsuccess: #522: 1: Success after binutils: 10 commits new 8dde3a28963 79: onsuccess: #523: 1: Success after gcc: 25 commits new 3145e13dd8a 80: onsuccess: #524: 1: Success after linux: 9 commits new 3cff1a9cb24 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new ef8cf458a6d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new 99a139d8f21 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new 76e3211bb72 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 940648812fb 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new f4f9c6c4418 86: onsuccess: #532: 1: Success after gcc: 16 commits new 40280bec33b 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new 01ffff890d1 88: onsuccess: #534: 1: Success after linux: 12 commits new d1a4561de77 89: onsuccess: #536: 1: Success after binutils: 27 commits new 68aba640be1 90: onsuccess: #538: 1: Success after glibc: 10 commits new 1d0b7dc3882 91: onsuccess: #539: 1: Success after linux: 27 commits new 607fcaa53d9 92: onsuccess: #543: 1: Success after glibc: 4 commits new e8f4d8f02ae 93: onsuccess: #544: 1: Success after linux: 34 commits new 2bbad3a67b8 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 563398eb5c5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new 6f7ca86e9f2 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new dda97e90130 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 52ae81f820c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 75a5f368407 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new d209ed7cf49 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new a7d020417bd 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new bf3e565f165 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 0850b5a61e3 103: onsuccess: #555: 1: Success after binutils: 4 commits new 6a162dbef7e 104: onsuccess: #558: 1: Success after binutils: 3 commits new 823395dc8cd 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new d43be6e6716 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new c5fe52003f4 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new 85d75796ae1 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new beb8c6dac02 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 7d6c296f656 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 2bfe4da7aa8 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 611332d14f8 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new c4a2669d58b 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new d577b1cda45 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 816b0e430c0 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 4ba05e669a7 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 0af7d5d6949 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 6f133b47af6 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new d90bbe2b7cf 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 91dae12f67b 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new fe478473c45 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 92ef588de26 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 68e6fb9f3bf 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 53ccbb5e27f 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 9c0c3ba8918 125: onsuccess: #581: 1: Success after binutils: 4 commits new 9560471c2fb 126: onsuccess: #582: 1: Success after gcc: 9 commits new e044e4492e7 127: onsuccess: #584: 1: Success after linux: 21 commits new 3556bd7ce1b 128: onsuccess: #586: 1: Success after binutils: 22 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 (6460665a237) \ 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 1652 -> 1924 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52488 -> 52132 bytes 04-build_abe-gcc/console.log.xz | Bin 233752 -> 235044 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 8972 bytes 07-build_abe-glibc/console.log.xz | Bin 235740 -> 236196 bytes 08-build_abe-gdb/console.log.xz | Bin 50544 -> 50552 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2656 -> 2584 bytes 11-check_regression/console.log.xz | Bin 5584 -> 4764 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 36 +- 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2920980 -> 2914808 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2551176 -> 2559268 bytes sumfiles/gcc.sum | 4114 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 954088 -> 951812 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229568 -> 229584 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470168 -> 473404 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2210 insertions(+), 2301 deletions(-)