Added explicit pathwaysutils.initialize() call to JetStream

[wstcliyu]

Description

pathwaysutils will soon require a call to initialize().

Tests

Depending on GitHub actions for tests

Checklist

Before submitting this PR, please make sure (put X in square brackets):

• I have performed a self-review of my code.
• I have necessary comments in my code, particularly in hard-to-understand areas.
• I have run end-to-end tests tests and provided workload links above if applicable.
• I have made or will make corresponding changes to the doc if needed.

[vivianrwu]

I think this is less of an "error" and more of "we are running jetstream without pathways. Could we clarify too that this could be intended behavior, or else users may think that there is some failure happening.

[wstcliyu]

I think this is less of an "error" and more of "we are running jetstream without pathways. Could we clarify too that this could be intended behavior, or else users may think that there is some failure happening.

Thanks. Updated the log to "Running JetStream without Pathways. Module pathwaysutils is not imported." Please review again.

[vipannalla]

looks good, can you fix the lint issue?

[vivianrwu]

Thanks for the fixes, lgtm!

[wstcliyu]

It's weird that it could not pass the checks (pyink format check & test coverage report). I don't see a quick fix due to lack of change suggestions. Shall we bypass the checks?

[vivianrwu]

It's weird that it could not pass the checks (pyink format check & test coverage report). I don't see a quick fix due to lack of change suggestions. Shall we bypass the checks?

pyink you can fix by running pyink --pyink-indentation 2 --line-length 80 <file_name>

[wstcliyu]

Thank you. Could you also guide me how to add test coverage for pathwaysutils.initialize(). pathwaysutils is not in the requirements file so this line is never called really.

[vivianrwu]

Thank you. Could you also guide me how to add test coverage for pathwaysutils.initialize(). pathwaysutils is not in the requirements file so this line is never called really.

You could probably write a test expecting the error.

[wstcliyu]

@vipannalla I added the unit test for module engine init. This unit test can pass by running separately coverage run -m unittest -v jetstream.tests.engine.test_init but cannot pass by coverage run -m unittest -v

[vipannalla]

Its complaining about unit test coverage for a test file, which should really be excluded from the check.