Closed CampGareth closed 6 years ago
This has some knock-on UX implications, for instance where does reco's output end and logging from the build process begin?
$ reco test run test-histogram
preparing simulation
done
archiving
done
uploading
done
running simulation
status: QUEUED
Waiting for Batch job to start
status: STARTED
mkdir -p ""/mnt/.reco-work/sdaccel/dist""
cd "/mnt/.reco-work/sdaccel/dist" && XCL_EMULATION_MODE=hw_emu emconfigutil --xdevice xilinx:aws-vu9p-f1:4ddr-xpr-2pr:4.0 --nd 1
****** configutil v2017.1_sdx (64-bit)
**** SW Build 1933108 on Fri Jul 14 11:54:19 MDT 2017
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.
creating deployment
done. Deployment ID: f4ba587d-7d7d-4993-b588-e57fcac0ff9b
you can run "reco deployment log f4ba587d-7d7d-4993-b588-e57fcac0ff9b" to manually stream logs
status: SUBMITTED
Waiting for Spot Instance Request to be created
status: QUEUED
Waiting for EC2 instance to be allocated
status: STARTED
Beginning log stream for deployment f4ba587d-7d7d-4993-b588-e57fcac0ff9b
Device/Slot[0] (/dev/xdma0, 0:0:1d.0)
xclProbe found 1 FPGA slots with XDMA driver running
f4ba587d-7d7d-4993-b588-e57fcac0ff9b
New output, now with line break and 'beginning logs' message.
Loose timestamping for console output