Skip to content

Add timestamp in the log file name for parallel add/remove-topo#24099

Open
weiguo-nvidia wants to merge 1 commit intosonic-net:masterfrom
weiguo-nvidia:add_log_timestamp_for_parallel_add_remove_topo
Open

Add timestamp in the log file name for parallel add/remove-topo#24099
weiguo-nvidia wants to merge 1 commit intosonic-net:masterfrom
weiguo-nvidia:add_log_timestamp_for_parallel_add_remove_topo

Conversation

@weiguo-nvidia
Copy link
Copy Markdown
Contributor

Summary: Add timestamp in the log file name for parallel add/remove-topo
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511

Approach

What is the motivation for this PR?

Deploy multi-server testbed, add/remove-topo save log in /tmp/add_topo_$i.log and /tmp/remove_topo_$i.log.
If deploy failure, it will retry. But the new log will overwrite the old log, causing hard to debug the failure in first run.

How did you do it?

Add timestamp in the log file.

Before fix

- add_topo_0.log
- add_topo_1.log

After fix

- add_topo_0_20260420_200812.log
- add_topo_1_20260420_200812.log

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

…llel add/remove-topo

- Issue
Deploy multi-server testbed, add/remove-topo save log in /tmp/add_topo_$i.log and /tmp/remove_topo_$i.log.
If deploy failure, it will retry. But the new log will overwrite the old log, causing hard to debug the
failure in first run.

- Fix
Add timestamp in the log file.

Before fix
- add_topo_0.log
- add_topo_1.log

After fix
- add_topo_0_20260420_200812.log
- add_topo_1_20260420_200812.log

Change-Id: I13be628cb5250e0fa2b64a8890c92d8ebf0619dc
Signed-off-by: weiguo-nvidia <[email protected]>
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@github-actions github-actions bot requested review from r12f, sdszhang and wangxin April 21, 2026 10:27
@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

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.

2 participants