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 06ecbb2a2b 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] discards e012ece76b 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] discards 51bd0715b9 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] discards 0a0ece943a 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] discards aae826bedb 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 4c7a5b8eed 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] discards cdf18ab266 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards bc44d52a3b 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 363d1ba43c 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards 084fd0be14 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 7394ed2e84 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards 1d3cd476ec 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards ac6c6b4eb8 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 4e08982eee 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 13e1227e45 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 1c3cdf168b 104: onsuccess: #558: 1: Success after binutils: 3 commits discards f33cf83aa8 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 761d409fce 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 77bee2d886 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 675d6dfdb8 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 769a421011 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 265dc78937 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards cc59c4d638 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 7eed076e8d 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 51b1cf48aa 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 7b06bd2bfe 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 97723deae2 93: onsuccess: #544: 1: Success after linux: 34 commits discards 07fe7ff5f5 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 8afdb70f84 91: onsuccess: #539: 1: Success after linux: 27 commits discards 5a3f4a2c13 90: onsuccess: #538: 1: Success after glibc: 10 commits discards c4ac4733e2 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 2d16580b55 88: onsuccess: #534: 1: Success after linux: 12 commits discards f7c26e680f 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 86fec912c6 86: onsuccess: #532: 1: Success after gcc: 16 commits discards c3a6e171d9 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 859c4366b2 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 23a99ec3b6 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards ddf62d9190 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards ca87b22dde 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 7e6141fbdb 80: onsuccess: #524: 1: Success after linux: 9 commits discards 3928d953d6 79: onsuccess: #523: 1: Success after gcc: 25 commits discards c79cdb178c 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 4789349ec9 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards ba3596105d 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards a53b33f421 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 8f454b5974 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 380c18bf08 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards a7d42d1b2e 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 186a020771 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards cb11af18b4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 713aed94f1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards d0c3578d93 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards fcb90468e4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 8c67f68c38 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards b6e4c7250c 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards d3efa85fe5 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 1e7299e781 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 84acc815c8 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 26a45144e4 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards f0eabb3d75 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 951b20cc9c 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards e8803211db 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 551f78393e 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards b670117b5a 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 09b39156ab 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 2ae961b702 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 617aff013a 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 3cd9f3c1df 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 154e8c05a5 51: onsuccess: #493: 1: Success after binutils: 13 commits discards a67548517d 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 67278499c6 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 8b7738d039 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards ae91d60a5b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 0ff9071143 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 32be72c32e 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 139ff848d6 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 7c09ccb8dc 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards b885d1b9df 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 67d4e40fe3 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards f7c353f6df 40: onsuccess: #476: 1: Success after linux: 69 commits discards c38f3b8526 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 80fd032bc8 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 596bf503be 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 3e9fdae9c1 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 9afe78d161 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 9882c89aef 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 0de80ae17e 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards c99f6fe7ec 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 9ae6a14237 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards e43a45592d 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 7df74db0b0 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 354be05582 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 9b314895a5 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 960989fc5b 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards ed47d1d34a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards baf5ea14ca 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards f5cde6457f 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards f948f5589f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards ce78442249 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards b9ae471842 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c0b5d7717 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05c0340dbc 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e3da056e44 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 972f52b309 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 1ad2aaa6e3 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 44af406ff5 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new bec80abf97 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 954c6107cd 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 67524b692c 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 55bf1c9f6b 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 5abf6754db 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new b0cbdda7bb 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new de10678f57 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new bfe111b939 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new a57dfa5c2c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new f3539e76e8 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new c5342c89ea 34: onsuccess: #465: 1: Success after binutils: 11 commits new a256e1aefe 35: onsuccess: #467: 1: Success after glibc: 2 commits new a096fdc558 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 803a8d5a56 37: onsuccess: #470: 1: Success after binutils: 3 commits new 80646887f9 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new b75952a730 39: onsuccess: #474: 1: Success after binutils: 8 commits new a9439d3f72 40: onsuccess: #476: 1: Success after linux: 69 commits new 6ce6d2faab 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new cccd4a1ec1 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 6b33b71aa0 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 09b36e22f9 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new a0ad209162 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new d7c554d031 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new d38d945084 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 91f932a572 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 4352abbf17 49: onsuccess: #487: 1: Success after binutils: 11 commits new a59e63676d 50: onsuccess: #490: 1: Success after binutils: 6 commits new 07362ce035 51: onsuccess: #493: 1: Success after binutils: 13 commits new d0625436d9 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 6cccab8da6 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 1b7e73350c 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new e3423cc6a9 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 17992a416e 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 936baa538d 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 8b3df08e01 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 1ac129ffcb 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 81300e8519 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 771e78b469 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 9887abdc26 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new c5ef5260c4 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 4e4a9ac65b 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 728d09f16e 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new c19a18f016 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new a63fa0ada8 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new e4fd4800db 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 7f014c47c9 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 19c2f9ac8d 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 75f93d90be 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 14d136f8a0 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new a2f2ce23ae 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 73593da467 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new bb9e63d925 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 5b78998f1b 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new e3b819747a 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new c5ecd982b3 78: onsuccess: #522: 1: Success after binutils: 10 commits new 0ebb4d33fe 79: onsuccess: #523: 1: Success after gcc: 25 commits new b3a42f8b12 80: onsuccess: #524: 1: Success after linux: 9 commits new c38d471593 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new a9e6f9f886 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 3e5d2d1c4d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 66b0af7b7a 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 752f1fde28 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 66a768804a 86: onsuccess: #532: 1: Success after gcc: 16 commits new 541d6d9e4a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 40a31631fc 88: onsuccess: #534: 1: Success after linux: 12 commits new cf6de951bb 89: onsuccess: #536: 1: Success after binutils: 27 commits new c1d6a43abc 90: onsuccess: #538: 1: Success after glibc: 10 commits new b1c1e5a68b 91: onsuccess: #539: 1: Success after linux: 27 commits new ee3bc57503 92: onsuccess: #543: 1: Success after glibc: 4 commits new 3cb917b5b9 93: onsuccess: #544: 1: Success after linux: 34 commits new de3e50fbb8 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 050b6c61e5 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 13e19747d1 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 6fa77e5600 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 6162d7adca 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 87a2a24e32 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 770bbef16f 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new cfd3656850 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 3ed174bedf 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new bfaec1ecf6 103: onsuccess: #555: 1: Success after binutils: 4 commits new fea61bbdc7 104: onsuccess: #558: 1: Success after binutils: 3 commits new 2aae278718 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 13ab4806dc 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 9f08d9a97c 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new bcc98c537b 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 65d7fb4cf1 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 4f8a2521f9 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 2d55d3f651 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new a392e62ee0 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 29c08fb266 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 61626ce8bb 114: onsuccess: #569: 1: Success after binutils/gcc/linux/gd [...] new 32e0254aaf 115: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new f885d0cb10 116: onsuccess: #571: 1: Success after binutils/gcc/linux/gd [...] new 4769b1c4cd 117: onsuccess: #572: 1: Success after binutils/gcc/linux/gd [...] new 8714aabd89 118: onsuccess: #573: 1: Success after binutils/gcc/linux/gd [...] new 3b66d536e9 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/gd [...] new f446170bb5 120: onsuccess: #575: 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 (06ecbb2a2b) \ 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 1696 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52316 -> 53300 bytes 04-build_abe-gcc/console.log.xz | Bin 234424 -> 233552 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 9536 bytes 07-build_abe-glibc/console.log.xz | Bin 235776 -> 235808 bytes 08-build_abe-gdb/console.log.xz | Bin 51608 -> 51332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2596 -> 2776 bytes 11-check_regression/console.log.xz | Bin 46864 -> 7144 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 4532 +------------- 11-check_regression/mail-body.txt | 65 +- 11-check_regression/results.compare | 4561 +------------- 11-check_regression/results.compare2 | 9847 +------------------------------ 11-check_regression/results.regressions | 90 +- 12-update_baseline/console.log | 42 +- 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 | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 90 +- sumfiles/g++.log.xz | Bin 2924280 -> 2905416 bytes sumfiles/g++.sum | 30 +- sumfiles/gcc.log.xz | Bin 2556128 -> 2554508 bytes sumfiles/gcc.sum | 4440 +++++++------- sumfiles/gfortran.log.xz | Bin 952288 -> 950168 bytes sumfiles/gfortran.sum | 22 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 229540 -> 229544 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 474904 -> 470020 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 2485 insertions(+), 21365 deletions(-)