[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] 2wk atomic release candidate: 20170228
- From: Dusty Mabe <dusty dustymabe com>
- To: atomic-devel projectatomic io, Fedora Cloud SIG <cloud lists fedoraproject org>
- Subject: Re: [atomic-devel] 2wk atomic release candidate: 20170228
- Date: Tue, 28 Feb 2017 09:13:59 -0500
On 02/28/2017 08:56 AM, Colin Walters wrote:
> On Tue, Feb 28, 2017, at 01:37 AM, Dusty Mabe wrote:
>
>> The atomic images are here:
> ^ Host =)
>
>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/CloudImages/x86_64/images/
>
> Autocloud:
> https://apps.fedoraproject.org/autocloud/jobs/857
> Looks like it flaked.
Yeah, kushal and roshi are trying to track down this issue and/or see
if it goes away by moving the testing into taskotron. Here is the
tracker for that:
https://pagure.io/atomic-wg/issue/232
>
>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170228.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170228.0.iso
>
> Right now for the ISO, openQA isn't really integrated into our processes, but one can find results here:
> https://openqa.fedoraproject.org/group_overview/1
> Which has:
> https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=25&build=Fedora-Atomic-25-20170228.0&groupid=1
> So that seems OK.
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]