Closed povolev15 closed 4 months ago
1 545 files 1 545 suites 2h 58m 3s :stopwatch: 108 587 tests 108 525 :white_check_mark: 59 :zzz: 3 :x: 116 881 runs 116 819 :white_check_mark: 59 :zzz: 3 :x:
For more details on these failures, see this check.
Results for commit 8bd05ac6.
3 tests 3 :white_check_mark: 6m 15s :stopwatch: 3 suites 0 :zzz: 3 files 0 :x:
Results for commit 8bd05ac6.
3 tests 3 :white_check_mark: 6m 5s :stopwatch: 3 suites 0 :zzz: 3 files 0 :x:
Results for commit 8bd05ac6.
20 files 20 suites 6m 8s :stopwatch: 265 tests 265 :white_check_mark: 0 :zzz: 0 :x: 340 runs 340 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 8bd05ac6.
24 files 24 suites 13m 16s :stopwatch: 362 tests 362 :white_check_mark: 0 :zzz: 0 :x: 369 runs 369 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 8bd05ac6.
51 files 51 suites 21m 43s :stopwatch: 357 tests 357 :white_check_mark: 0 :zzz: 0 :x: 375 runs 375 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 8bd05ac6.
19 tests 19 :white_check_mark: 23m 7s :stopwatch: 4 suites 0 :zzz: 4 files 0 :x:
Results for commit 8bd05ac6.
72 files 72 suites 22m 51s :stopwatch: 617 tests 617 :white_check_mark: 0 :zzz: 0 :x: 671 runs 671 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 8bd05ac6.
Can we please (temporarily) add tests that ensure the new transactions cannot be called?
How do we ensure that we do not accidentally override any of the critical files (e.g. config.txt
)?
closing this draft pr will open a new one
*Related issue(s)**:
Fixes #14066