[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #31372 [Core Tor/Tor]: Appveyor and Travis should use "make -k"
#31372: Appveyor and Travis should use "make -k"
-------------------------------------------------+-------------------------
Reporter: nickm | Owner: nickm
Type: enhancement | Status:
| needs_review
Priority: Medium | Milestone: Tor:
| 0.4.2.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-ci, 029-backport, 035-backport, | Actual Points: .1
040-backport, 041-backport, 042-should |
Parent ID: | Points:
Reviewer: teor | Sponsor:
-------------------------------------------------+-------------------------
Comment (by nickm):
I think that the search approach might be better: we have to do that
anyway for jenkins builders, and it's a good idea to get in practice. Do
you think that's plausible? If so, let's merge_ready this.
> It's probably also worth mentioning that this change will slow down
failures. I think that's ok, but I sent an email to the network team list
with other ways to speed up CI.
Thanks! I also think it's okay.
The tradeoff is that we find out later when there is compilation failure,
but we learn ''everything'' about the compilation failure and we don't
have to do multiple back-and-forth steps. Learning about a success is
just as slow as it was before.
I know that Appveyor will report failure as soon as one builder has
failed. Does travis do the same?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/31372#comment:17>
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