From: Ian Jackson <Ian.Jackson@eu.citrix.com> To: osstest service owner <email@example.com>, Wei Liu <firstname.lastname@example.org>, email@example.com, Jim Fehlig <firstname.lastname@example.org>, Andrew Cooper <email@example.com> Subject: Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages] Date: Mon, 4 Apr 2016 17:55:20 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com>, <firstname.lastname@example.org> Ian Jackson writes ("Policy for force pushing smoke branch Was: Re: [Xen-devel] [xen-unstable-smoke test] 88656: regressions - FAIL"): > Wei Liu writes ("Policy for force pushing smoke branch Was: Re: [Xen-devel] [xen-unstable-smoke test] 88656: regressions - FAIL"): > > It would take some time for libvirt fix to land and propagate to our own > > mirror. > > There is also a risk that the libvirt fix wouldn't pass osstest's push > gate for the libvirt branch. > > > I would like to avoid holding backing xen.git push for too long > > if possible. So I'm for force-pushing the smoke branch and subsequently > > master branch if necessary. > > I concur. I will wait a bit for contrary opinions, though. I have now pushed a0f793d82d5ec2d0b67c57d7130bf01c91396c60 to smoke, apropos of: osstest service owner writes ("[xen-unstable-smoke test] 88672: regressions - FAIL"): > flight 88672 xen-unstable-smoke real [real] > http://logs.test-lab.xenproject.org/osstest/logs/88672/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144 > > version targeted for testing: > xen a0f793d82d5ec2d0b67c57d7130bf01c91396c60 I'll do a force push to xen.git#master if this is the only blocker, too. Also, any necessary force push of the osstest tested libvirt branch. Thanks, Ian. _______________________________________________ Xen-devel mailing list Xenemail@example.com http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-04 16:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-04-04 18:53 [xen-unstable test] 88588: regressions - FAIL osstest service owner 2016-04-04 15:58 ` [xen-unstable-smoke test] 88672: " osstest service owner 2016-04-04 13:15 ` [xen-unstable-smoke test] 88656: " osstest service owner 2016-04-04 13:28 ` Policy for force pushing smoke branch Was: " Wei Liu 2016-04-04 13:32 ` Ian Jackson 2016-04-04 16:55 ` Ian Jackson [this message] 2016-04-05 10:31 ` Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages] [and 1 more messages] Ian Jackson 2016-04-05 10:36 ` Wei Liu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Policy for force pushing smoke branch Was: Re: [xen-unstable-smoke test] 88656: regressions - FAIL [and 1 more messages]' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).