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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards f189dd2ab5 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards c56085dadc 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 73b5387cfc 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards f1a7602c88 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 0674a2b68c 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 707b2d259d 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards d77a57722c 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards cf52a1cb00 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c97f902627 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f1300fe4e 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 947300ed46 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards c246c5bece 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards d1dbd89ec2 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ac0869dde5 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 53f649db5e 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards e4ca585277 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 445194cc60 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 94661b0fbd 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards e388dac84f 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 63297f72b5 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 693ab75ea2 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards f5aabeec1f 127: force: #27: : Failure after baseline build: no new commits discards e9749c1b06 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards deba6ab55a 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 00e63683f8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 4ba2278449 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 4c2896139e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards f669a469c2 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 0736d5ab80 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 4172b1045b 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 49198cabd8 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 0893067025 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards d2bf5e598b 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 74e55eb5aa 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 4abd2beff5 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 339fe69339 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 6ea94dd9cf 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 18584e0e27 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards c08ac0ac0e 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 033ac18e64 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards f3e5c56a19 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards b39cb2c1c8 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 8b225743dd 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 5d020813ca 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 406803939a 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 87f7e3688d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards b97f321b9e 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards d94ac9a9d1 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 6c0ed6dc02 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 6c3f2d2ef6 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 93058e4139 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards d0141e8d37 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 6998afa600 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards b8e6d38d8a 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 9310a28e39 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards f6ecc0ce3f 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 2ccd2f1eea 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards eabbadd8d4 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards c922211a5b 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 749b29a3e7 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards d23ee2c591 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c198e64ffd 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards e937fd1188 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 093217c428 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 7532d92742 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 8d8d95ca89 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 1c6d9d0128 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 3711b983e6 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 834c8a77a3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 5759868714 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 7179da6451 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards d35f6d5f88 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 16d8111eff 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards d8db24ed67 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards e931db4cf4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 0472fb08b0 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 95157481ce 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 519528bb62 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards bc2c610571 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 0ffa291223 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 26eefba65d 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d21e317c5 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 83ba7f8321 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 454b27442c 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards f79667cea7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards e970c7242c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards a92497c074 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 3e44c77af3 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards ce84f0944f 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 4cda5e7d35 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards f7eecce4bb 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 6bb362f735 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards 172fa346a5 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 07125efab7 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 4ec24b39c1 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards f07012b2fc 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 2b72ab2beb 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards a3fbebdfaa 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 333e9b6f17 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 9f6fda03f0 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards e22096ac6d 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new fda0da502e 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new 0ada2ba0ab 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 34c6a9f71b 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 3720f79bfa 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new 496bde7fd2 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 6c0dcee023 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 47463f632b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 618b1608ea 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new f5d9df12db 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 4aec9fac47 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new a6b6b390d5 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new f47cce961c 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 7b8eeb20db 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 2f37cde456 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 26c6d31afb 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 50ad047235 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new fe1c14433b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 1f98f6f72e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 9ede370f31 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new daf932c68e 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new c2e046efd8 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 75f0ea4556 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 00bd7307a8 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new c34c5b425c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new dc28f0e6de 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 35e8e67406 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new d9ffab5fd4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new d0ce12c1f4 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 1a54ff19c2 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 5405e68abc 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 7f4b8c0a4e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 7d1696c7fe 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new ba418c3d33 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 2c9043211c 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new a2b51b1482 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 8d71ee784a 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 59179fc56c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new deb38cc7cf 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new e0862694a0 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8652c0625f 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 3ffab06897 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 3ea6902d59 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new dbd36384ad 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a06f6acac4 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 43bdfccf57 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new b9643b6d85 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 584c3d312c 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 189676d07f 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new e7bb520fa9 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 8a94f2a780 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 9a362d393c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 12e7570d3c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 37533dabf7 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 9b556e270f 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 8ec28a55b3 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 58311c0025 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new a332f851df 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new af07d733e0 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 05f9463e5c 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 59b1c42f74 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 865546612a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 21f6536236 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 5acb17f617 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 755df245b9 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new f374256f36 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new cbbc848257 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 38c8ce5af4 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a7ef6fecfb 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 9b162f1da2 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new d9550bc973 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 68d6190e9f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new a5a31312b9 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 050009b68a 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1c3ce10067 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 8fd0d460ee 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 2761fdac6c 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new f6db34f651 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 5f34b13671 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a43f2ef0b3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 23de02a981 127: force: #27: : Failure after baseline build: no new commits new 035050165b 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 95c3fd3a3c 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new faa7165001 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new ead6a8739f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 40e52250c0 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 0d9eabbab5 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 69cf360812 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 01599ad8fc 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 25448cab2e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5f801657e8 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new de7213ee5e 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 337c8170c5 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 13a9987cb8 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f53936389f 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 7121e9e57c 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new ab0eba9d58 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 8999a7f037 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 8b88fbd35c 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 341c0b60a4 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 1f094b71f2 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 2a40a51c56 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new c673a329b1 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (f189dd2ab5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2084 -> 2216 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 35152 -> 35148 bytes 04-build_abe-gcc/console.log.xz | Bin 203376 -> 203184 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8808 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 241024 -> 240968 bytes 08-build_abe-gdb/console.log.xz | Bin 35024 -> 34832 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3136 -> 3012 bytes 11-check_regression/console.log.xz | Bin 4808 -> 1964 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 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 +- jenkins/notify.sh | 3 +++ mail/changes-list-long.txt | 24 ------------------- mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 34 --------------------------- mail/short-diag.txt | 1 - manifest.sh | 40 +++++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14440 -> 14420 bytes sumfiles/gdb.sum | 4 ++-- 29 files changed, 59 insertions(+), 113 deletions(-) create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt