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
Running s4 with multiple errant files will print errors like ERROR: something something for file ./logs/... (which is expected). These lines printed to stderr occur in a varying order for subsequent runs of s4. This degrades the quality of comparison done in ./tools/compare-current-and-expected/compare.sh.
To Reproduce
in ./tools/compare-current-and-expected/common.sh
comment out the line filters ERROR: strings
run ./tools/compare-current-and-expected/update.sh
run ./tools/compare-current-and-expected/compare.sh until failure
The lines starting with ERROR: are in varying order.
This may be similar cause as #213 where multi-threaded design is causing this behavior. However, it needs investigation to see if it's possible to accumulate errors for "the first round of processing" and then print errors along with normal prints in order of file path. Thinking about it, why isn't this already happening?
jtmoon79
added
the
difficult
A difficult problem; a major coding effort or difficult algorithm to perfect
label
Mar 22, 2024
Problem
Running
s4
with multiple errant files will print errors likeERROR: something something for file ./logs/...
(which is expected). These lines printed to stderr occur in a varying order for subsequent runs ofs4
. This degrades the quality of comparison done in./tools/compare-current-and-expected/compare.sh
.To Reproduce
./tools/compare-current-and-expected/common.sh
comment out the line filters
ERROR:
strings./tools/compare-current-and-expected/update.sh
./tools/compare-current-and-expected/compare.sh
until failureThe lines starting with
ERROR:
are in varying order.Another simpler approach:
s4
manually with known errant filesEnvironment:
The text was updated successfully, but these errors were encountered: