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

[BUG] Qualification ui output goes to wrong folder #5838

Closed
tgravescs opened this issue Jun 15, 2022 · 1 comment · Fixed by #5875
Closed

[BUG] Qualification ui output goes to wrong folder #5838

tgravescs opened this issue Jun 15, 2022 · 1 comment · Fixed by #5875
Assignees
Labels
bug Something isn't working P0 Must have for release tools

Comments

@tgravescs
Copy link
Collaborator

Describe the bug
Running the qualification tool without any options now generates the UI, but it doesn't go into the correct output folder, it just goes into ./ :

22/06/15 10:02:09 INFO ToolTextFileWriter: Stage Exec Info output location: rapids_4_spark_qualification_output/rapids_4_spark_qualification_output_stages.csv
22/06/15 10:02:09 INFO QualificationReportGenerator: Generating UI data in ui/html/index.html
@tgravescs tgravescs added bug Something isn't working P0 Must have for release tools labels Jun 15, 2022
@amahussein amahussein self-assigned this Jun 15, 2022
@amahussein
Copy link
Collaborator

This behavior seems consistent with passing --output-directory
When the tool is executed with the following argument--output-directory output_dir, the user gets:

  • output_dir/ui
  • output_dir/rapids_4_spark_qualification_output

Running the qualification tool without any options, the output_folder will be by default ./. This will gives two directories:

  • ./ui
  • ./rapids_4_spark_qualification_output

Is the ui directory supposed to be a subdirectory of rapids_4_spark_qualification_output ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P0 Must have for release tools
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants