- Issue created by @catch
- Status changed to Needs review
5 months ago 6:54am 1 August 2024 - Status changed to RTBC
5 months ago 7:18am 1 August 2024 - ๐ณ๐ฑNetherlands spokje
Nice!
Code changes make sense, idea makes (very much) sense, green tests => RTBC for me.
Wish I'd thought of this at the beginning of trying to optimize pipeline runs instead of when a lot of the work is done, since it probably would have saved hours trying to identify the slowest tests, however better late than never.
Nobody thought of this until now, although whilst reading the IS it all seems so obvious.
Blinded by the obvious perhaps... - ๐ฎ๐นItaly mondrake ๐ฎ๐น
fwiwโฆ well, ๐ Allow run-tests.sh to report skipped/risky/incomplete PHPUnit-based tests Needs work attempted this, but then it was stopped in the basis that the script would go in GitLab CI.
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
If run-tests.sh remains, then IMHO reporting skipped/risky/incomplete would still be useful in PHPUnit times. Now itโs only pass/fail/exception which is very simpletest-ish.
- ๐ฌ๐งUnited Kingdom catch
Re-opened ๐ Allow run-tests.sh to report skipped/risky/incomplete PHPUnit-based tests Needs work since we'll be using run-tests.sh for a while yet.
- ๐ฎ๐นItaly mondrake ๐ฎ๐น
Hairsplitting... it would be more sccurate to report the timing of execution that is included in the JUnit log.
- Status changed to Needs work
4 months ago 4:53am 11 August 2024 - Status changed to Needs review
4 months ago 1:33pm 11 August 2024 - Status changed to RTBC
4 months ago 2:23pm 11 August 2024 - Status changed to Fixed
4 months ago 9:54am 14 August 2024 - ๐ซ๐ทFrance nod_ Lille
Automatically closed - issue fixed for 2 weeks with no activity.