File tree Expand file tree Collapse file tree 5 files changed +33
-24
lines changed Expand file tree Collapse file tree 5 files changed +33
-24
lines changed Original file line number Diff line number Diff line change @@ -21,7 +21,9 @@ side-bar.
21
21
tutorials/05_deploy_example
22
22
tutorials/06_ioc_changes
23
23
tutorials/07_generic_ioc
24
- tutorials/08_support_module
24
+ tutorials/08_debug_generic_ioc
25
+ tutorials/09_test_generic_ioc
26
+ tutorials/10_support_module
25
27
26
28
+++
27
29
Original file line number Diff line number Diff line change @@ -290,34 +290,12 @@ directory:
290
290
.. warning ::
291
291
292
292
This will FAIL. There is a deliberate error which we will fix in the next
293
- step .
293
+ Tutorial .
294
294
295
295
You should see this error::
296
296
297
297
../URLDriver.cpp:22:10: fatal error: Magick++.h: No such file or directory
298
298
299
- Investigate the Build Failure
300
- -----------------------------
301
-
302
- When a container build fails the container image is created up to the point
303
- where the last successful Dockerfile command was run. This means that we can
304
- investigate the build failure by running a shell in the container. ``ec ``
305
- provides us with the following convenience command to do this:
306
-
307
- .. code-block :: bash
308
-
309
- ec dev debug-last
310
-
311
- Now we have a prompt inside the part build container and can retry the failed
312
- command.
313
-
314
- .. code-block :: bash
315
-
316
- cd /repos/epics/support/adurl
317
- make
318
-
319
- You should see the same error again.
320
-
321
299
322
300
323
301
Original file line number Diff line number Diff line change
1
+ Debugging Generic IOC Builds
2
+ ============================
3
+
4
+ This tutorial is a continuation of `07_generic_ioc `. Here we will look into
5
+ debugging failed builds and fix the build failure from the previous tutorial.
6
+
7
+ Investigate the Build Failure
8
+ -----------------------------
9
+
10
+ When a container build fails the container image is created up to the point
11
+ where the last successful Dockerfile command was run. This means that we can
12
+ investigate the build failure by running a shell in the container. ``ec ``
13
+ provides us with the following convenience command to do this:
14
+
15
+ .. code-block :: bash
16
+
17
+ ec dev debug-last
18
+
19
+ Now we have a prompt inside the part-built container and can retry the failed
20
+ command.
21
+
22
+ .. code-block :: bash
23
+
24
+ cd /repos/epics/support/adurl
25
+ make
26
+
27
+ You should see the same error again.
Original file line number Diff line number Diff line change
1
+ Testing and Deploying a Generic IOC
2
+ ===================================
File renamed without changes.
You can’t perform that action at this time.
0 commit comments