Skip to content

[foxy backport] Benchmark lifecycle features (#1462)#1471

Merged
brawner merged 1 commit intofoxyfrom
brawner/backport-1462
Nov 23, 2020
Merged

[foxy backport] Benchmark lifecycle features (#1462)#1471
brawner merged 1 commit intofoxyfrom
brawner/backport-1462

Conversation

@brawner
Copy link
Copy Markdown
Contributor

@brawner brawner commented Nov 19, 2020

This backports the lifecycle benchmarks from #1462. This should probably wait for merging until performance_test_fixture is released into foxy as merging this PR will break rpr jobs.

  • Benchmark lifecycle features

Signed-off-by: Stephen Brawner brawner@gmail.com

* Benchmark lifecycle features

Signed-off-by: Stephen Brawner <brawner@gmail.com>

* Cleanup

Signed-off-by: Stephen Brawner <brawner@gmail.com>
@brawner brawner requested a review from cottsay November 19, 2020 23:27
@brawner brawner changed the title Benchmark lifecycle features (#1462) [foxy backport] Benchmark lifecycle features (#1462) Nov 19, 2020
@brawner
Copy link
Copy Markdown
Contributor Author

brawner commented Nov 19, 2020

Foxy job, with benchmarks on and testing --packages-select rclcpp_lifecycle

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@cottsay
Copy link
Copy Markdown
Member

cottsay commented Nov 20, 2020

@ros-pull-request-builder retest this please

@brawner
Copy link
Copy Markdown
Contributor Author

brawner commented Nov 20, 2020

Windows shows some ms build warnings which are not expected with performance jobs, but they were addressed in rolling and are awaiting a backport PR of ros2/rcutils#311

@cottsay
Copy link
Copy Markdown
Member

cottsay commented Nov 23, 2020

@ros-pull-request-builder retest this please

@brawner brawner merged commit bea9c5a into foxy Nov 23, 2020
@delete-merged-branch delete-merged-branch bot deleted the brawner/backport-1462 branch November 23, 2020 03:30
@brawner
Copy link
Copy Markdown
Contributor Author

brawner commented Nov 23, 2020

Thanks Scott for reminding me about this. Looks like the Fpr job went through cleanly.

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.

3 participants