| Re: [cross-project-issues-dev] Validating Aggregator fails because of legacy update site -> MAT |
Hi Michael, is it possible to identify such an inconsistent state and provide a better error message? The current error message is very misleading. I got this error when running the b3 aggregation tests from the b3 editor before pushing to gerrit. And I spend half an hour to find out what is wrong with my repository. Regards, Dennis. > Am 24.05.2017 um 09:46 schrieb Mickael Istria <mistria@xxxxxxxxxx>: > > Hi Krum, > > As far as I understand, the "legacy update site" issue may just be the way aggragation failed because of the update, but not the cause of the failure. We can imagine the during the aggregation process, your repo was updated (update of repo during aggregation isn't supported by the aggregation process), so it put aggregation in an inconsistent state and the aggregator wrongly reported that the cause is usage of legacy update site. > With last message from Alexander saying everything is working now, I think we can assume everything is back to work and stop worrying about it. > > HTH > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Viele Grüße, Dennis Hübner
Attachment:
signature.asc
Description: Message signed with OpenPGP