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 c673a329b1 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2a40a51c56 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 1f094b71f2 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 341c0b60a4 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 8b88fbd35c 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 8999a7f037 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards ab0eba9d58 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 7121e9e57c 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards f53936389f 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 13a9987cb8 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 337c8170c5 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards de7213ee5e 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5f801657e8 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 25448cab2e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 01599ad8fc 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 69cf360812 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 0d9eabbab5 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 40e52250c0 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards ead6a8739f 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards faa7165001 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 95c3fd3a3c 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 035050165b 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 23de02a981 127: force: #27: : Failure after baseline build: no new commits discards a43f2ef0b3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 5f34b13671 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards f6db34f651 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 2761fdac6c 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 8fd0d460ee 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 1c3ce10067 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 050009b68a 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards a5a31312b9 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 68d6190e9f 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d9550bc973 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 9b162f1da2 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a7ef6fecfb 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 38c8ce5af4 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards cbbc848257 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards f374256f36 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 755df245b9 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 5acb17f617 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 21f6536236 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 865546612a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 59b1c42f74 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 05f9463e5c 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards af07d733e0 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards a332f851df 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 58311c0025 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 8ec28a55b3 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 9b556e270f 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 37533dabf7 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 12e7570d3c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 9a362d393c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 8a94f2a780 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards e7bb520fa9 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 189676d07f 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 584c3d312c 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards b9643b6d85 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 43bdfccf57 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards a06f6acac4 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards dbd36384ad 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 3ea6902d59 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 3ffab06897 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8652c0625f 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards e0862694a0 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards deb38cc7cf 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 59179fc56c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 8d71ee784a 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards a2b51b1482 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 2c9043211c 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards ba418c3d33 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 7d1696c7fe 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 7f4b8c0a4e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 5405e68abc 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 1a54ff19c2 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards d0ce12c1f4 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards d9ffab5fd4 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 35e8e67406 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards dc28f0e6de 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards c34c5b425c 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 00bd7307a8 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 75f0ea4556 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards c2e046efd8 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards daf932c68e 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 9ede370f31 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 1f98f6f72e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards fe1c14433b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 50ad047235 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 26c6d31afb 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 2f37cde456 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b8eeb20db 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards f47cce961c 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards a6b6b390d5 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 4aec9fac47 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards f5d9df12db 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 618b1608ea 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 47463f632b 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 6c0dcee023 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 496bde7fd2 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 3720f79bfa 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 34c6a9f71b 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 0ada2ba0ab 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 8174ef6c0b 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 0b2b21ba38 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new eb61e73e05 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new ce507e613d 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new fbdc2a1b49 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new c42e4ec370 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 140ba22a3d 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 492838d3cd 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 940ae024be 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new ebedc1ae5e 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 1d4feea583 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 4078800239 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 722704b64d 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 40a29a5ba2 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 5c84686183 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 5860b7047e 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new a2c21024aa 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new ec2cad33bb 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new bbbe7bbbe8 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new f3d3cffcbe 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 3aa30449f1 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new ee8376c082 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new dc263d3d09 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 1cd0277590 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new fe209f877c 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 7372e3aa6e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 7ef5133c03 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new fa36dca4df 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 5b666652bc 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 2a42246c40 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 97f8150e5b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 4b645aa12d 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 59f643b9f9 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 35fa7468df 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 17a475a03f 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 973c93eec5 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 8b64e0bfe3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 23abe7f0d6 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 2c215fc70c 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new bbda09a2e2 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new f2431ddb47 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new b316ce1d92 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 3d2c71054a 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 10908dead5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new cfd6e4153d 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new c989d11f5b 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 464a74113f 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new a3bd1c61cb 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new ff33e326e1 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 6e2ff081b3 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 4dfce6f04e 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 485a8f735a 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 273ba893b5 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new fec7f8857a 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 421d40cb97 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 87b6d15ab0 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new e16ad4efe1 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 5bb1611ea5 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new d88763eefd 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 1f7585cc9a 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 95f0b0794b 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 9f4dd23a42 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 2c76b1b666 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a1c5ff73eb 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 24919e4aa0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 2003124433 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new eb957c1d41 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new cf0bd37f13 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 7a3bbea651 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 864e06b867 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ec84ae68b5 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new fcd74dba53 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7d088dfdb7 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 7f24dbd008 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 7337942580 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 1e52d2cd0e 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new f23369dace 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 1637db03b3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 7c3c50c5d3 127: force: #27: : Failure after baseline build: no new commits new 72e2edd10c 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new ef981d7dd2 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 3a1a2db147 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 520f5c494b 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 6a93a1281c 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 0dc25d4736 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 84cdf22e76 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new b55ce3827d 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 23a2a02c84 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new ca7bf581d6 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 42172a411f 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f7750d661b 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 3ab1d7848f 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 761003e8c1 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new a9d9665d4d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new af123f23d9 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 9b96ce63b7 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 095adbcb19 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4f4996c29d 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new ff504041f6 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a77d332338 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new f79bf836ec 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4de8f2cb15 150: onsuccess: #55: 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 (c673a329b1) \ 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 2216 -> 2244 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 35148 -> 35380 bytes 04-build_abe-gcc/console.log.xz | Bin 203184 -> 203164 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 240968 -> 241168 bytes 08-build_abe-gdb/console.log.xz | Bin 34832 -> 34948 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3012 -> 3160 bytes 11-check_regression/console.log.xz | Bin 1964 -> 1952 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 36 ++++++++++++++++---------------- 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 | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14420 -> 14408 bytes sumfiles/gdb.sum | 4 ++-- 24 files changed, 51 insertions(+), 51 deletions(-)