-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: jtreg8.0
-
Component/s: tools
-
None
When running a jtreg test that uses "@compile foo.jasm" test action, the messages generated (if any) by asmtools during the jasm file compilation are being written out to the stdout of the jtreg process instead of being reported in the test's jtr file.
jtreg upgraded to 8.1 version of asmtools recently and this appears to be a new behaviour in this version of asmtools (as compared to 7.0-b09).
Looking at the code in org.openjdk.asmtools.jasm.Main (the tool that jtreg launches to compile the jasm files), the constructors that jtreg uses to construct that instance have been deprecated in favour of newer ones. It looks like moving to the new constructors will allow jtreg to configure the destination of these log messages.
jtreg upgraded to 8.1 version of asmtools recently and this appears to be a new behaviour in this version of asmtools (as compared to 7.0-b09).
Looking at the code in org.openjdk.asmtools.jasm.Main (the tool that jtreg launches to compile the jasm files), the constructors that jtreg uses to construct that instance have been deprecated in favour of newer ones. It looks like moving to the new constructors will allow jtreg to configure the destination of these log messages.
- caused by
-
CODETOOLS-7903081 Update asmtools and remove jcov traces
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jtreg/2cffb4d7
-
Review(master)
openjdk/jtreg/301