[SR-2961] utils/run-test should accept the same "optimization mode" flags build-script does
#45.551 aberto em 15 de out. de 2016
Métricas do repositório
- Stars
- (69.989 stars)
- Métricas de merge de PR
- (Mesclagem média 8d 17h) (510 fundiu PRs em 30d)
Description
| Previous ID | SR-2961 |
| Radar | None |
| Original Reporter | Beingessner (JIRA User) |
| Type | Task |
| Votes | 0 |
| Component/s | |
| Labels | Task, StarterBug |
| Assignee | None |
| Priority | Medium |
md5: 8f750d918784d982d243854e145f4366
Issue Description:
Currently run-test requires you to pass the build-directory for the compiler/stdlib to use for the tests, but this is tedious and requires the user to actually know what the name of the target they're building was.
A more ergonomic workflow would be to allow the same flags that build-script accepts to be passed to run-test, and have it derive the compiler from that. I'm not sure what the complete set of flags relevant flags is, but -d, -r, and -R are probably the most important. More complex scenarios can always fall-back to the current workflow.