You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the #4 has been merged I sometimes receive the following error during build:
[gstreamer/stderr] /home/stivius/linuxdeploy-plugin-gstreamer.sh: line 110: : command not found
It completes successfully on my local machine despite these errors but fails in GitHub actions for some reason.
I'm not an expert in bash, but I did some research on this topic. set -e means exit immediately if a command exits with a non-zero status grep -v means select non-matching lines grep --help tells us exit status is 0 if any line is selected, 1 otherwise
And we have the following line 110 in the script: "$(file "$i" | grep -v ELF --silent)" which means that if ELF is found grep will return 0 I suppose.
Could it be the root problem which causes the script to fail?
The text was updated successfully, but these errors were encountered:
Since the #4 has been merged I sometimes receive the following error during build:
It completes successfully on my local machine despite these errors but fails in GitHub actions for some reason.
I'm not an expert in bash, but I did some research on this topic.
set -e
means exit immediately if a command exits with a non-zero statusgrep -v
means select non-matching linesgrep --help
tells us exit status is 0 if any line is selected, 1 otherwiseAnd we have the following line 110 in the script:
"$(file "$i" | grep -v ELF --silent)"
which means that if ELF is foundgrep
will return0
I suppose.Could it be the root problem which causes the script to fail?
The text was updated successfully, but these errors were encountered: