1 | | Replying to [comment:27 mk@…]: |
2 | | > * [http://www.chopapp.com/#lfgg4v91] @ lines 7295 & 7300 |
3 | | |
4 | | Ian pointed out on KDE-MAC that one should watch out for more occurrences of {{{meinproc4}}} in the log. |
5 | | |
6 | | And, yes, there are also (successfully started) calls in lines 7277 and 7294: |
7 | | {{{ |
8 | | :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kmymoney4-devel/kmymoney4-devel/work/kmymoney/doc && /opt/local/bin/meinproc4 --check --cache /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/doc/index.cache.bz2 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kmymoney4-devel/kmymoney4-devel/work/kmymoney/doc/index.docbook |
9 | | . |
10 | | . |
11 | | . |
12 | | :info:build cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kmymoney4-devel/kmymoney4-devel/work/build/doc && /opt/local/bin/meinproc4 --stylesheet /opt/local/share/apps/ksgmltools2/customization/kde-include-man.xsl --check /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_kde_kmymoney4-devel/kmymoney4-devel/work/kmymoney/doc/man-kmymoney.1.docbook |
13 | | }}} |
14 | | Well, and the 1st one creates the cache file {{{index.cache.bz2}}} indicating that in line 7276 |
15 | | {{{ |
16 | | :info:build [ 8%] Generating index.cache.bz2 |
17 | | }}} |
18 | | while in line 7300 it already gets accessed in parallel for building the docu as notified in line 7293 |
19 | | {{{ |
20 | | :info:build [ 9%] Generating kmymoney.1 |
21 | | }}} |
22 | | Here we are!!! |
23 | | |
24 | | This is clearly a concurrency problem. Ian, thanks very much!!! |
25 | | |
26 | | '''It is strange, that this has never surfaced on Linux up to now... Does KDE's CI system build only non-concurrently? I guess I have to figure that out next.''' |
| 1 | Disregard the former versions of comment:29, as I misinterpreted the log. |