This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 122832e3f2 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards a5e97f271c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards cbfd4c6d05 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 9afab76d3c 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 0b646bd12f 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards e39ba4ce30 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 82d2ef82e8 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 24298a3762 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 48748abb02 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 5cd98cc0b8 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 617db9c346 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 33dc2d6cf6 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 399869a449 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards dc5659d281 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 64684810e5 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 889714bb4b 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards e788f13756 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards cdb7e9e902 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards cb1ae06d7f 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 8d94a0ef7d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards e7e81f1cd9 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards a331fc7b0d 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 61778d9793 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 87ea01862f 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 802c15c5ee 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards d5aab85bc2 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 14708159b9 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 68cc29feeb 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 427ff79aa2 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 5fc0dd9330 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 84dcd4e760 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards a3fc06f1e8 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards e375ff3401 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 0238d45970 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards 255e8d2052 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards fa2421a487 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards a77896f540 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards dc95154cea 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards a51a7735a5 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards 3231e47f42 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 265b38748c 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 81891dd92d 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards dac26ece7a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 7e65fd3723 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards df66f58348 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards b0bec8a61d 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards d68941201a 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards d488a1804a 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 4c91724802 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards fe364ae435 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 02361aa2d1 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 114004c511 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d899ac606b 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 8d3cc2982f 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 455acbdd38 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards f5e1fe9e41 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards 8bc3c7887b 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards f7f4be1bc6 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 904a4b2a43 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 43d0c6d6ce 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 582d74d31c 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards b081b0a4ed 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 5a9b656c8a 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 549f6ebbee 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards c53c0f4765 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 7c911f7104 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards b2bd13ed8a 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 94bc3a91ad 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards c96514e106 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 7bc6da3197 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards e4a8d7d0e7 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards fa99e0e15f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 9c9b185915 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards c77ec9b56b 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 83b3d61309 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards eabf6123ba 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 5fcfb81f9a 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 58f7d7aed9 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 70569885a6 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards b12ceba017 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 2d14af48b5 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 9d0090b795 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards b8e84ce866 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards f811395522 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards ffe3606d60 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards aab6cd024a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 524a14fa35 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards 353ebba8e9 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards ab137db75b 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 8b07fa81fb 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards eebef4a2b8 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards d7ad15d932 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 67933c2028 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards e983178afa 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards 2ff20b5f49 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards dbc020011b 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards c55f3fb17b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards c16ea4128e 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 4ba8adb31d 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 31082fb899 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 73efd75629 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new cc023a8709 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new ad882a7288 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new 577c7a1d3a 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new 3e2f993b13 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new fe0edc8d57 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new cd3b913149 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new fb0045793d 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 7489f8c940 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 16b2db05f9 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new df87fd8aed 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 3ad66e9dc4 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 6008c34a39 287: onsuccess: #2103: 1: Success after gcc: 9 commits new 86aff461d5 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new 3df57840dd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 1b51018008 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 7b526a597a 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new cab0192ab7 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new ef23e7a638 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new 3ee3542d02 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 3dbdfbfc84 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new c5a9916b3a 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f1293e1326 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 64fb764095 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new feefe0c5d2 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 57c6dfcc10 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 2a10daf59b 301: onsuccess: #2118: 1: Success after linux: 16 commits new 63ff90cecf 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 9daf822009 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 0bbd8ae00a 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 94cd22429f 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 072f292963 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 9baa537f07 307: onsuccess: #2124: 1: Success after gcc: 2 commits new e1f38025b0 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 77a0b02ea6 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new e95969cc65 310: onsuccess: #2129: 1: Success after binutils: 4 commits new d1d919b683 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 91af0dc10b 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 2f21bb2960 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new ce69c45304 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 5738ca7a65 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new fed893d09e 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new fddd578b81 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new a16ece18bb 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new 9c0bf617ce 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new 919ef023bf 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e41a828cda 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 537131e932 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 163716f1c7 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new ee931eaa34 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new ea23b99598 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d9ca5b1549 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 1f2c6712d6 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 62e65779ce 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new 391ff87ca8 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new bab047de63 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 45e0bb8537 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new fbaca7098b 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 14f0c62547 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new c9adac6c8e 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new f5e03569e3 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new b22c0934c8 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cc9244b668 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new f4d16ac7f1 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new dbf0b00930 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 43a94fd0be 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 23513fe457 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 8b6a027c87 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 3ff1f9612a 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new dc0a2af762 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 1bb151a3b8 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 2081dd6f3f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new c38061eb83 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new bd675a7617 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 668a7f572f 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 663d36c02f 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 17accf1c67 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 70ed1dc412 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 28ad8dc67a 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 08824f263a 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 0a52c1fe29 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new eaea25eb08 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 16873edb3d 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new 0e2eb65e15 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 864a30f996 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 610198ffd6 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 07b142f727 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new d3e32e9e9d 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new ceb710b284 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new bc34a3d587 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 1fe5c14875 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new d7757529b3 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 1fb49a3338 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 9bddddfed4 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 38192afb8c 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new aee68c2909 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new f0d5abd93d 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 45af7d9c93 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new a3268e3022 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new bf11229c83 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 6465eeb40f 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 341c752346 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new fdddd83b18 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 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 (122832e3f2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1768 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 31444 -> 31228 bytes 04-build_abe-stage1/console.log.xz | Bin 92112 -> 91988 bytes 06-build_abe-linux/console.log.xz | Bin 8916 -> 8908 bytes 07-build_abe-glibc/console.log.xz | Bin 236868 -> 236880 bytes 08-build_abe-stage2/console.log.xz | Bin 228280 -> 229236 bytes 09-build_abe-gdb/console.log.xz | Bin 38592 -> 38608 bytes 10-build_abe-qemu/console.log.xz | Bin 32364 -> 32128 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3028 -> 2672 bytes 13-check_regression/console.log.xz | Bin 7700 -> 5804 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 7 + 13-check_regression/mail-body.txt | 27 + 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 106 +- 13-check_regression/results.regressions | 27 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 27 + sumfiles/g++.log.xz | Bin 2637088 -> 2672236 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2185368 -> 2202476 bytes sumfiles/gcc.sum | 2244 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886900 -> 898476 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214324 -> 214544 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2676 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438936 -> 438060 bytes sumfiles/libstdc++.sum | 33 +- 42 files changed, 1354 insertions(+), 1333 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions