about summary refs log tree commit diff stats
path: root/082scenario_screen.cc
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2016-07-22 23:36:19 -0700
committerKartik K. Agaram <vc@akkartik.com>2016-07-22 23:36:19 -0700
commit60e11efcb042cb9cfb3fc50d8d7e36d74020b6ae (patch)
tree939aba1c2493874df2af1fbf09a663803b048e32 /082scenario_screen.cc
parentd8f7ec8ec9251e4f4aef179e83d291c7518e984e (diff)
downloadmu-60e11efcb042cb9cfb3fc50d8d7e36d74020b6ae.tar.gz
3137
Complicated logic to not run core tests. I only want to disable core
tests if:

  a) I'm changing CFLAGS on the commandline (usually to disable
  optimizations, causing tests to run slower in a debug cycle)
  b) I'm not printing a help message (either with just 'mu' or
  'mu --help')
  c) I'm loading other files besides just the core.

Under these circumstances I only want to run tests in the files
explicitly loaded at the commandline.

This is all pretty hairy, in spite of my attempts to document it in
four different places. I might end up taking it all out the first time I
need to run core tests under all these conditions.
Diffstat (limited to '082scenario_screen.cc')
0 files changed, 0 insertions, 0 deletions
kartik.com> 2020-07-10 23:53:28 -0700 6631' href='/akkartik/mu/commit/html/run_one_test.subx.html?h=hlt&id=ec73ed1230d75deb0f913a32617c9f1e0a5ca640'>ec73ed12 ^
b7ec0398 ^







1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91