Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log output dir at end of run #912

Merged
merged 18 commits into from
Nov 12, 2020
Merged

Conversation

lcadalzo
Copy link
Contributor

@lcadalzo lcadalzo commented Nov 9, 2020

Fixes #908

@ng390
Copy link
Contributor

ng390 commented Nov 12, 2020

This logs the DockerPaths version of the output directory. Would it be clearer to log the HostPaths version, unless in interactive mode? Or we could just emphasize that it is a path in the docker container.

Copy link
Contributor

@ng390 ng390 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor changes w.r.t. using DockerPaths/HostPaths

@lcadalzo
Copy link
Contributor Author

Currently we log DockerPaths regardless, see this example log that occurs at start of run:
2020-11-12 17:20:51 6a9c55b655dd __main__[4290] WARNING Outputs will be written to /armory/outputs/2020-11-12T150059.839212

This class doesn't know whether --interactive was set or not. Perhaps we could modify to:

"Saving evaluation results to {scenario_output_dir}/{filename} path inside container"

@ng390 ng390 merged commit a3b1fc1 into twosixlabs:master Nov 12, 2020
@lcadalzo lcadalzo deleted the 908-output-dir-log branch December 22, 2021 22:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Log the full output path upon closing scenario
2 participants