-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Merge pull request #40595 from hamishknight/straw-bales" #40623
Revert "Merge pull request #40595 from hamishknight/straw-bales" #40623
Conversation
…les" This reverts commit a67a043, reversing changes made to 9965df7. This commit or the earlier commit this commit is based on (swiftlang#40531) broke the incremental bot.
@swift-ci Please test |
preset=buildbot_incremental,tools=RA,stdlib=RA |
incremental builder: https://ci.swift.org/job/oss-swift-incremental-RA-macos/14501/ |
|
Reverting this is likely to cause significantly more breakage overall, so let’s see if we can’t fix the CI. Is it just not getting the sources, or is there a compilation error? |
The incremental builder needs to run update checkout, that is, it needs a fullish build once to get the new sources |
I don't know why the failure is. But nearly all bots are red right now. |
There seem to be different issues. I have seen the issue mentioned above and here is a different one: https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/18158/console
|
Here is a -- probably incomplete -- list of bots currently failing with either of these two errors:
|
This one has found the sources and has SWIFT_ENABLE_EXPERIMENTAL_STRING_PROCESSING=TRUE, but did not try to build either _MatchingEngine or _StringProcessing. 10:47:37 -- Using Experimental String Processing library for _MatchingEngine (/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_04/swift-experimental-string-processing).
10:47:37 -- Using Experimental String Processing library for _StringProcessing (/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_04/swift-experimental-string-processing). I wonder if it just needs a clean build. |
The build bot should have been cleaned in between 2 days. That at least would be my understanding of doing things sensibly (i.e the bots clean the workspace overnight). The issue did not seem to resolve itself since yesterday, though. I can't tell why. That said I tried a clean build locally with It could be that the bots don't use I will wait until tomorrow to see what happens tonight. |
According to the following run the bot That also seems to be the bot that the incremental macOS bot runs on: https://ci.swift.org/job/oss-swift-incremental-RA-macos/14503/. I am going to try to trigger a build now by committing an NFC change. This build should be on a clean workspace if it runs on |
Okay, this run https://ci.swift.org/job/oss-swift-incremental-RA-macos/14504 is indeed running on |
Mishal informed us that new repos need to be manually added to the CI and that @drewmaxwell-apple should be able to help add it. Drew, could you help us add it when you get a chance? |
Okay. Sounds like we have found a way to not break the bots: first we configure the various CI configurations to check out the necessary repo. Once this is complete we can re-commit this change. |
This reverts commit a67a043, reversing
changes made to 9965df7.
This commit or the earlier commit this commit is based on (#40531) broke the
incremental bot.