[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #29036 [Core Tor/Tor]: Coverage merge failures cause test_process_slow stderr check to fail
#29036: Coverage merge failures cause test_process_slow stderr check to fail
-------------------------------------------------+-------------------------
Reporter: teor | Owner: ahf
Type: defect | Status:
| assigned
Priority: High | Milestone: Tor:
| 0.4.1.x-final
Component: Core Tor/Tor | Version: Tor:
| unspecified
Severity: Major | Resolution:
Keywords: 041-accepted-20190115, regression, | Actual Points:
tor-ci |
Parent ID: | Points: 0.5
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by teor):
Replying to [comment:5 ahf]:
> I'm not sure if I read the output correctly, but does this error
condition mean that the test binaries (and the child-process binary)
output "Merge mismatch for function X" on standard error?
>
> We can detect that line in stderr's first line if we want to in the
process tests, but I don't think that would be the right solution. Can we
either fail in an earlier way when this condition appears OR figure out a
way to reset the state so these "Merge mismatch" disappear?
Let's try deleting the cached coverage files before building?
Or let's delete the coverage files after a coverage run, so they don't
take up space in the cache?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29036#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs