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

fix all shellcheck warnings #729

Open
marc-hb opened this issue Jul 3, 2021 · 11 comments
Open

fix all shellcheck warnings #729

marc-hb opened this issue Jul 3, 2021 · 11 comments
Assignees
Labels
good first issue Good for newcomers P3 Low-impact bugs or features type:enhancement New framework feature or request

Comments

@marc-hb
Copy link
Collaborator

marc-hb commented Jul 3, 2021

shellcheck finds bugs, notably issues with set -e: do this before #312

Related: #740

@marc-hb marc-hb added good first issue Good for newcomers type:enhancement New framework feature or request labels Jul 3, 2021
greg-intel added a commit that referenced this issue May 25, 2023
Per issue #729, "Fix all shellcheck warnings".

Prior to this commit there were 13 in this file, now zero.
greg-intel added a commit that referenced this issue May 25, 2023
Per issue #729, "Fix all shellcheck warnings".

Prior to this commit there were 13 in this file, now zero.
greg-intel added a commit that referenced this issue Jun 1, 2023
Per issue #729, "Fix all shellcheck warnings".

Prior to this commit there were 13 in this file, now zero.
@greg-intel greg-intel self-assigned this Jun 5, 2023
@greg-intel

This comment was marked as outdated.

@greg-intel

This comment was marked as outdated.

@greg-intel
Copy link
Contributor

image

There are currently seven open PRs, once they're all merged I believe this ticket can be closed, @marc-hb ?

@marc-hb marc-hb added the P2 Critical bugs or normal features label Jun 22, 2023
@greg-intel
Copy link
Contributor

Think I'm caught up on all the PRs.

@marc-hb
Copy link
Collaborator Author

marc-hb commented Jul 6, 2023

Could you please update and re-share the spreadsheet to reflect the new status?

@greg-intel
Copy link
Contributor

image

@marc-hb see any remaining candidates in the ones I left behind?

@greg-intel
Copy link
Contributor

greg-intel commented Jul 12, 2023

Also of note, Fred proposed a rewrite to run-all-tests: #1019

@marc-hb
Copy link
Collaborator Author

marc-hb commented Jul 12, 2023

Could you please update and re-share the spreadsheet to reflect the new status?

I meant can you make the fixed tests green and with a "0" to see what's left at a glance? Scanning "19 FIXED" lines one by one does not give any overview (and I'm not even sure what it means)

PS: did you just copy the same image again??

@greg-intel
Copy link
Contributor

I guess the previous image was already up-to-date. Here, I've color coded the status to make it easier to see which files were left out, all files that were fixed or were "0" are green for column C.
image

@marc-hb
Copy link
Collaborator Author

marc-hb commented Jul 12, 2023

Thanks, now this gives an overview. "the new status" meant not interested in the number of issues when you started to work on this.

I'm happy to close this and leave the rest for whenever someone wants to resurrect a test.

@marc-hb marc-hb added P3 Low-impact bugs or features and removed P2 Critical bugs or normal features labels May 1, 2024
@marc-hb
Copy link
Collaborator Author

marc-hb commented May 1, 2024

test-case/*.sh not clean yet as of 47af510

test-case/check-audio-equalizer.sh
test-case/check-pause-release-suspend-resume.sh 1 failure
test-case/check-reboot.sh - many failures
test-case/check-runtime-pm-double-active.sh - very many
test-case/check-runtime-pm-status.sh - many
test-case/check-userspace-paplay.sh 1 failure
test-case/check-userspace-parecord.sh 1 failure
test-case/verify-ucm-config.sh many

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers P3 Low-impact bugs or features type:enhancement New framework feature or request
Projects
None yet
Development

No branches or pull requests

2 participants