search for: harbormaster

...of pre merge testing) and discuss it and explore all the possible solutions? >> I think the discussion would be much more productive if we take it from first principles here. > >That's really what I've tried doing below. Quoting myself: > > > And if the solution is that Harbormaster suddenly becomes usable without an unreasonable time investment from me, then I'm fine with that too. I'm not looking to switch to GitHub PRs for the sake of it, I'm looking to solve problems that are harming libc++ in the current system. > >Maybe I should have stated that earlier...

...o now? I got a bunch of libcxx failing on my revision a few weeks ago. The LLVM-premerge-test project recently added presubmit on Linux. Windows will hopefully follow soon (in beta right now I believe), and Mac afterward! (Even though mac is lacking on the cloud provider availability) . From the Harbormaster documentation [1]: > > You'll need to write a nontrivial amount of code to get this working > today. In the future, Harbormaster will become more powerful and have more > builtin support for interacting with build systems. > > So while I appreciate all the efforts being ma...

Sorry, I didn't notice this change of default last night. Thanks for fixing this! -- Mehdi On Tue, Jul 28, 2020 at 5:50 AM MyDeveloper Day via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I've made the change > > https://reviews.llvm.org/harbormaster/plan/5/ > > MyDeveloperDay <https://reviews.llvm.org/p/MyDeveloperDay/> changed the Hold > Drafts behavior for this plan from Always to Never. > > I apologize in advance if that was the wrong thing to do. > > MyDeveloperDay. > > On Tue, Jul 28, 2020 at 1:44 PM MyDev...

lld/test/ELF/invalid/symtab-sh-info.s (check-lld-elf) is recently flaky on Windows, e.g. https://reviews.llvm.org/harbormaster/unit/view/192869/ http://45.33.8.238/win/27684/step_10.txt It fails like every 3 or 4 builds. Could someone with a Windows machine check what is going on? Is that due to output non-determinism (just my guess) in yaml2obj.exe? -------------- next part -------------- An HTML attachment was scrubbed....

...testing) and discuss it and explore all > the possible solutions? > I think the discussion would be much more productive if we take it from > first principles here. > > > That's really what I've tried doing below. Quoting myself: > > > And if the solution is that Harbormaster suddenly becomes usable without > an unreasonable time investment from me, then I'm fine with that too. I'm > not looking to switch to GitHub PRs for the sake of it, I'm looking to > solve problems that are harming libc++ in the current system. > > Maybe I should have sta...

...." (https://reviews.llvm.org/D84742) >> >> >> >> As many have seen, pre-merge checks are flaky and just generally >> unusable, >> >> and this case was no exception, the build failed and the phabricator >> >> hsa rejected the revision: "Harbormaster returned this revision to the >> author >> >> for changes because remote builds failed." >> >> There is still no mention of that review in llvm-commits. >> >> >> >> Please unbreak phabricator at once :) >> >> I don't recall...

...on will be sent for review once this build passes: Build 82647: pre-merge checks." (https://reviews.llvm.org/D84742) As many have seen, pre-merge checks are flaky and just generally unusable, and this case was no exception, the build failed and the phabricator hsa rejected the revision: "Harbormaster returned this revision to the author for changes because remote builds failed." There is still no mention of that review in llvm-commits. Please unbreak phabricator at once :) I don't recall seeing any discussion/proposal for any such behaviour. Roman

On Tue, Feb 25, 2020 at 4:19 AM Christian Kühnel via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Louis, > > I think this is a good idea. We should start with some local experiments > where people are willing to try it and figure out how well that works and > what does not. Why not allow this for "not significant" changes? They are > merged without review

...asses: >> Build 82647: pre-merge checks." (https://reviews.llvm.org/D84742) >> >> As many have seen, pre-merge checks are flaky and just generally unusable, >> and this case was no exception, the build failed and the phabricator >> hsa rejected the revision: "Harbormaster returned this revision to the author >> for changes because remote builds failed." >> There is still no mention of that review in llvm-commits. >> >> Please unbreak phabricator at once :) >> I don't recall seeing any discussion/proposal for any such behaviour....

...VM Developers Mailing List <llvm-dev at lists.llvm.org> Cc: Nico Weber <thakis at chromium.org> Subject: [llvm-dev] lld :: ELF/invalid/symtab-sh-info.s is flaky on Windows lld/test/ELF/invalid/symtab-sh-info.s (check-lld-elf) is recently flaky on Windows, e.g. https://reviews.llvm.org/harbormaster/unit/view/192869/<https://reviews.llvm.org/harbormaster/unit/view/192869/> http://45.33.8.238/win/27684/step_10.txt<http://45.33.8.238/win/27684/step_10.txt> It fails like every 3 or 4 builds. Could someone with a Windows machine check what is going on? Is that due to output non-determ...

Hi All, I just posted a review with arcanist (which I'm fairly new to) and it included a build status. How it got there is totally opaque to me, but my workflow was: Using git+svn (following the setup in https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-git-svn) make a change, commit with 'git commit', create review with 'air diff'. It would be cool if

Hi folks, Bad news: the permerge testing service is down after a Jenkins update. We're working on it but it's more difficult to resolve this than expected. I disabled the builds right now. I'll keep you posted once it's back online. Sorry for the downtime... Best, Christian -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Jan 14, 2020 at 09:56:53PM +0000, Renato Golin via cfe-dev wrote: > GitHub PR is the "de facto standard", everyone knows, the entry cost > is practically zero. The UI is lean and missing features, but the > large availability of tooling (either targeting GitHub directly or > plain git) makes up for a lot of it. Just like with the "Everyone knows git", I