Regres: Reverse full test run order

Doing a test run with LLVM after the one with Subzero results in various tests timing out (including some 'UNSUPPORTED' ones). The Subzero test run doesn't exhibit this issue. It's unclear at this point why this happens, but reversing the order appears to stabilize it. Bug: b/156728197 Change-Id: I6450d2d95d6043ef206d09f0020313fbf4b3f2e2 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/45149Tested-by: Nicolas Capens <nicolascapens@google.com> Reviewed-by: Antonio Maiorano <amaiorano@google.com> Kokoro-Result: kokoro <noreply+kokoro@google.com>

Regres: Reverse full test run order
660c3bc9 · Nicolas Capens · Nicolas Capens · c9625f16 · 660c3bc9
Commit 660c3bc9 authored May 13, 2020 by Nicolas Capens Committed by Nicolas Capens May 15, 2020
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

main.go tests/regres/cmd/regres/main.go +2 -2

No files found.
--- a/tests/regres/cmd/regres/main.go
+++ b/tests/regres/cmd/regres/main.go
@@ -295,10 +295,10 @@ func (r *regres) run() error {
 	for {
 		if now := time.Now(); toDate(now) != lastUpdatedTestLists {
 			lastUpdatedTestLists = toDate(now)
-			if err := r.runDaily(client, backendSubzero, true); err != nil {
+			if err := r.runDaily(client, backendLLVM, false); err != nil {
 				log.Println(err.Error())
 			}
-			if err := r.runDaily(client, backendLLVM, false); err != nil {
+			if err := r.runDaily(client, backendSubzero, true); err != nil {
 				log.Println(err.Error())
 			}
 		}