Closed steve-taylor closed 2 years ago
I am also experiencing this issue since yesterday and would appreciate a fix.
:tada: This issue has been resolved in version 1.2.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
@trittgers-principal @steve-taylor please see if v1
tag works now for your actions. Close the issue if so or let me know what we need to do next.
v1
now points to the latest release that includes #13
Thanks for your contribution.
This works for me. Thanks!
Consider the following xunit output:
This is being reported as an error, which I've traced to
detection.sh
line 19.I noticed there's inconsistent usage of the
-L
option ofgrep
. This is important because the-L
option not only suppresses output (replacing it with the name of the file), but also inverts the match.Interestingly, when I ran this locally on macOS to reproduce the issue, I couldn't reproduce it. However, I was able to reproduce it in Linux. It seems that
grep -L
always returns0
on macOS, whereas it returns1
on Linux when a match is found (i.e. opposite of whatgrep -l
would do).The pseudocode of this snippet:
appears to be the following:
failures="0"
, thenerrors="1+"
, then one or more tests failed.errors="0"
, thenfailures="1+"
, then one or more tests failed.More concisely, failure occurs if one of the following is true:
failures="0"
and doesn't containerrors="1+"
;errors="0"
norfailures="1+"
; orfailures="0"
and does containerrors="0"
.This is what I think is needed:
failures="1+"
;errors="1+"
; orfailures
attribute (could be a malformed test report).In which case,
find_fail
should become:As a bonus, it also works on macOS.