Fedora-Cloud-30-20200214.0 compose check report

2020-02-13 Thread Fedora compose checker
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproj

Re: How do we keep an eye on the CompNeuro Lab image's status?

2020-02-13 Thread Matthew Miller
On Thu, Feb 13, 2020 at 12:27:30PM -0800, Adam Williamson wrote: > > Sorry, very noob question: how would the NeuroFedora SIG keep up with > > the status of the CompNeuro Lab image? Could someone point me to the > > docs please, I wasn't able to find them on the wiki. > > > > I found it on Koji an

Re: How do we keep an eye on the CompNeuro Lab image's status?

2020-02-13 Thread Ankur Sinha
On Thu, Feb 13, 2020 12:27:30 -0800, Adam Williamson wrote: > On Thu, 2020-02-13 at 20:04 +, Ankur Sinha wrote: > > Hello, > > > > Sorry, very noob question: how would the NeuroFedora SIG keep up with > > the status of the CompNeuro Lab image? Could someone point me to the > > docs please, I w

Re: How do we keep an eye on the CompNeuro Lab image's status?

2020-02-13 Thread Adam Williamson
On Thu, 2020-02-13 at 20:04 +, Ankur Sinha wrote: > Hello, > > Sorry, very noob question: how would the NeuroFedora SIG keep up with > the status of the CompNeuro Lab image? Could someone point me to the > docs please, I wasn't able to find them on the wiki. > > I found it on Koji and realise

How do we keep an eye on the CompNeuro Lab image's status?

2020-02-13 Thread Ankur Sinha
Hello, Sorry, very noob question: how would the NeuroFedora SIG keep up with the status of the CompNeuro Lab image? Could someone point me to the docs please, I wasn't able to find them on the wiki. I found it on Koji and realised that the image wasn't created because of some dependency errors, b

Fedora-32-20200213.n.0 compose check report

2020-02-13 Thread Fedora compose checker
No missing expected images. Failed openQA tests: 97/158 (x86_64), 1/2 (arm) Old failures (same test failed in Fedora-32-20200212.n.1): ID: 520572 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/520572 ID: 520573 Test: x86_64 Server-boot-iso inst

Fedora 32 compose report: 20200213.n.0 changes

2020-02-13 Thread Fedora Branched Report
OLD: Fedora-32-20200212.n.1 NEW: Fedora-32-20200213.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 2 Dropped packages:0 Upgraded packages: 86 Downgraded packages: 0 Size of added packages: 61.52 MiB Size of dropped packages:0 B Size of

Re: Git forge requirements discussion

2020-02-13 Thread Kamil Paral
On Wed, Feb 12, 2020 at 10:35 AM Kamil Paral wrote: > On Tue, Feb 11, 2020 at 10:42 PM Ben Cotton wrote: > >> On Tue, Feb 11, 2020 at 4:37 PM Matthew Miller >> wrote: >> > >> > Can you put the voting/polls idea in the form of a user story? >> > >> I think #44 on the list I sent covers that: >>

Fedora-Cloud-31-20200213.0 compose check report

2020-02-13 Thread Fedora compose checker
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproj

Fedora-Cloud-30-20200213.0 compose check report

2020-02-13 Thread Fedora compose checker
No missing expected images. Passed openQA tests: 1/1 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproj