Page MenuHomePhabricator

[services] Clean up `run_performance_tests.sh` using ShellCheck
ClosedPublic

Authored by abosh on Aug 2 2022, 2:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 14, 11:40 AM
Unknown Object (File)
Tue, Jun 11, 4:26 PM
Unknown Object (File)
May 19 2024, 1:14 AM
Unknown Object (File)
May 10 2024, 8:45 AM
Unknown Object (File)
May 10 2024, 8:45 AM
Unknown Object (File)
May 1 2024, 5:53 PM
Unknown Object (File)
Apr 29 2024, 5:17 PM
Unknown Object (File)
Apr 29 2024, 5:17 PM

Details

Summary

Related Linear issue here. This is part of a set of diffs that will allow ShellCheck to be added to the CI. See inline comments for specific details of the ShellCheck error/warning output.

Test Plan

Similarly as in D4724, I went to @karol's diff D4580 where this code was introduced. Looks like @karol noted:

the desired behavior for them is to fail with a message "unimplemented".

So I'm assuming this was supposed to break, and that is why it is still failing? I don't have much context on this. Either way, this diff is scoped to the ShellCheck side of the script, so if it's supposed to fail/be broken then I think that's outside the scope of this diff.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Aug 2 2022, 2:15 PM
Harbormaster failed remote builds in B11074: Diff 15241!
This revision is now accepted and ready to land.Aug 2 2022, 11:18 PM

bash-wise, this looks correct. But I would wait for @karol 's response before moving forward.

Adding @karol as blocking to get more context on the test plan.

This revision now requires review to proceed.Aug 3 2022, 6:52 AM

It would be more readable if you wrapped the diffs into a stack.

Diff looks ok.

Performance tests are unimplemented for tunnelbroker, they work well for blob and they're blocked for backup (don't work).

This revision is now accepted and ready to land.Aug 3 2022, 7:14 AM

It would be more readable if you wrapped the diffs into a stack.

I agree! Although since the code for a lot of these diffs technically doesn't really depend on each other, I wasn't sure if to make a depends on. But I guess next time I will, since some of these diffs are closely related.

Performance tests are unimplemented for tunnelbroker, they work well for blob and they're blocked for backup (don't work).

Got it.

I agree! Although since the code for a lot of these diffs technically doesn't really depend on each other, I wasn't sure if to make a depends on.

Personally, I treat dependenices on Phabricator as a storytelling tool more than a way to actually indicate formal dependency relationships. Another way to think about it... a diff is a commit, and a stack is a branch.

I agree! Although since the code for a lot of these diffs technically doesn't really depend on each other, I wasn't sure if to make a depends on.

Personally, I treat dependenices on Phabricator as a storytelling tool more than a way to actually indicate formal dependency relationships. Another way to think about it... a diff is a commit, and a stack is a branch.

Makes sense, I'll keep that in mind for the future.