-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 11, 12
-
Component/s: infrastructure
-
None
-
b23
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8207293 | 12 | Erik Joelsson | P3 | Resolved | Fixed | b03 |
| JDK-8207500 | 11.0.2 | Erik Joelsson | P3 | Resolved | Fixed | b01 |
| JDK-8207611 | 11.0.1 | Erik Joelsson | P3 | Resolved | Fixed | b02 |
Ralf Schmelter reported this issue on build-dev: http://mail.openjdk.java.net/pipermail/build-dev/2018-July/022658.html
This bug addresses his first problem, that the *.obj.log files we generate when running native compilation sometimes get truncated, which in turn causes unreliable incremental builds on Windows.
The suggested fix is to add an explicit $(RM) of the .obj.log file before running the command, and run tee with -a flag so that neither tee truncates the file.
This bug addresses his first problem, that the *.obj.log files we generate when running native compilation sometimes get truncated, which in turn causes unreliable incremental builds on Windows.
The suggested fix is to add an explicit $(RM) of the .obj.log file before running the command, and run tee with -a flag so that neither tee truncates the file.
- backported by
-
JDK-8207293 *.obj.log files get truncated causing unreliable incremental builds on Windows
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-