It still seems like, for a smoke test, we're doing way too much work. This appears to be much more than what I get from build-script -t when I run tests locally. Maybe I'm misunderstanding the intended role of our smoke tests, but since nobody is correcting me, I'm betting not.
Anyway, regardless of the explanation, what can be done about this? Between a spurious failure in LLDB and the length of the smoke test it took several hours to be able to merge something that could not possibly break the build, which seems absurd.
ยทยทยท
Sent from my iPad
On Oct 18, 2016, at 11:44 PM, mishal_shah <mishal_shah@apple.com> wrote:
On Oct 18, 2016, at 8:29 PM, Michael Gottesman <mgottesman@apple.com> wrote:
On Oct 18, 2016, at 6:40 PM, Dave Abrahams via swift-dev <swift-dev@swift.org> wrote:
I thought the smoke test was supposed to be a fairly quick test
that just covered the basics, but it seems to be doing plenty of *really
long* tests, for example:
https://ci.swift.org/job/swift-PR-Linux-smoke-test/1916/console
which has already been running for over 30 minutes. Am I missing
something?I think people have over time been adding more to the Linux tests. But I am not in the know. Mishal, do you know whats happening here?
This is most likely due to number cores we have for Linux bots, the new Linux bots are 12 cores vs 48 cores and we are running multiple executors on it.
Old - 48 cores / 4 executors = 12 cores
New - 12 cores / 2 executors = 6 coresThanks,
Mishal ShahMichael
--
-Dave
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev