Fedora-Cloud-33-20210307.0 compose check report

2021-03-06 Thread Fedora compose checker
No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210306.0):

ID: 802328  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/802328
ID: 802335  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/802335

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Development repos accumulating prior daily builds [FIXED]

2021-03-06 Thread Robert G. (Doc) Savage via test
On Fri, 2021-03-05 at 12:16 -0800, Kevin Fenzi wrote:
> On Fri, Mar 05, 2021 at 01:53:34PM -0600, Robert G. (Doc) Savage via
> test wrote:
> > 
> > Kevin,
> > 
> > Thanks for submitting those PRs. Do you have a sense of when the
> > scripts will actually be updated and the older files flushed?
> 
> The scripts are updated now, but rawhide compose failed today
> (due to xorg-x11-server-utils being retired and lorax still trying to
> install it). 
> 
> https://github.com/weldr/lorax/issues/1117
> 
> as soon as that gets fixed and we get a compose the old duplicates
> should go away. 

Kevin,

My local rsync just finished up. It's a couple hundred gigs lighter. :-
)  Thanks.


--Doc Savage
    Fairview Heights, IL
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
Chris,

The only other difference I can think of is that sdb the "first" time was 
acquired by the kernel after booting. Again, the SIIG docking station. The 
system "noticed" the device and udev "fixed" things up so the drive is usable. 
The "second" time, sdb was already powered up.

I could power down sdb and reboot then power it up if you think it might 
provide information.

Regards,

George...






On Saturday, March 6, 2021, 1:36:13 PM PST, Chris Murphy 
 wrote: 





fdisk says:
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda8      436217856 3907029167 3470811312  1.6T 83 Linux

sda8 is 1777055391744 bytes

Btrfs says:
  dev_item.total_bytes    1777055391744

Those agree. The scrub message comes from
block/blk-core.c:655:  pr_info_ratelimited("attempt to access beyond
end of device\n"

I don't know why it would be triggered.



fdisk says:
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
/dev/sdb1        2048 976773167 976771120 465.8G 83 Linux

sdb1 is 500106813440 bytes.

kernel says:
[152968.929912] sdb: p1 size 1465144002 extends beyond EOD, enabling
native capacity

this is coming from
block/partitions/core.c:573:                  "%s: p%d size %llu
extends beyond EOD, ",
and
block/partitions/core.c:519:            printk(KERN_CONT "enabling
native capacity\n");

I've got no idea what it's complaining about though. Seems like the
kernel and fdisk have very different ideas about how to read this
partition map.

btrfs says:
dev_item.total_bytes    500106813440

The partition map and btrfs have the exact same bytes again, that's
good. The only discrepancy here is the kernel's block core is confused
about it. I don't know why that would be. Does that EOD message happen
on every boot for sdb1?


--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
Chris,

No message appeared but the message came out at the beginning of btrfs-convert. 
I could convert again if that would help.

dmesg for "this" boot enclosed:

Regards,

George...





On Saturday, March 6, 2021, 1:36:13 PM PST, Chris Murphy 
 wrote: 





fdisk says:
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda8      436217856 3907029167 3470811312  1.6T 83 Linux

sda8 is 1777055391744 bytes

Btrfs says:
  dev_item.total_bytes    1777055391744

Those agree. The scrub message comes from
block/blk-core.c:655:  pr_info_ratelimited("attempt to access beyond
end of device\n"

I don't know why it would be triggered.



fdisk says:
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
/dev/sdb1        2048 976773167 976771120 465.8G 83 Linux

sdb1 is 500106813440 bytes.

kernel says:
[152968.929912] sdb: p1 size 1465144002 extends beyond EOD, enabling
native capacity

this is coming from
block/partitions/core.c:573:                  "%s: p%d size %llu
extends beyond EOD, ",
and
block/partitions/core.c:519:            printk(KERN_CONT "enabling
native capacity\n");

I've got no idea what it's complaining about though. Seems like the
kernel and fdisk have very different ideas about how to read this
partition map.

btrfs says:
dev_item.total_bytes    500106813440

The partition map and btrfs have the exact same bytes again, that's
good. The only discrepancy here is the kernel's block core is confused
about it. I don't know why that would be. Does that EOD message happen
on every boot for sdb1?


--
Chris Murphy
[0.00] microcode: microcode updated early to revision 0x2f, date = 
2019-02-17
[0.00] Linux version 5.12.0-0.rc1.162.fc35.x86_64 
(mockbu...@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.0.0 20210210 (Red 
Hat 11.0.0-0), GNU ld version 2.35.1-34.fc34) #1 SMP Mon Mar 1 17:12:47 UTC 2021
[0.00] Command line: 
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.12.0-0.rc1.162.fc35.x86_64 
root=UUID=45b37c32-c85f-4d01-b0d5-008faf6ee085 ro 
resume=UUID=11bd3385-b265-4149-9da1-352284344307 nomodeset
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable
[0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
[0.00] BIOS-e820: [mem 0x2000-0x201f] reserved
[0.00] BIOS-e820: [mem 0x2020-0x3fff] usable
[0.00] BIOS-e820: [mem 0x4000-0x401f] reserved
[0.00] BIOS-e820: [mem 0x4020-0xaac0cfff] usable
[0.00] BIOS-e820: [mem 0xaac0d000-0xaad8dfff] reserved
[0.00] BIOS-e820: [mem 0xaad8e000-0xaad94fff] usable
[0.00] BIOS-e820: [mem 0xaad95000-0xaad95fff] reserved
[0.00] BIOS-e820: [mem 0xaad96000-0xaad96fff] usable
[0.00] BIOS-e820: [mem 0xaad97000-0xaadb7fff] reserved
[0.00] BIOS-e820: [mem 0xaadb8000-0xaadc5fff] usable
[0.00] BIOS-e820: [mem 0xaadc6000-0xaade7fff] reserved
[0.00] BIOS-e820: [mem 0xaade8000-0xaaf22fff] usable
[0.00] BIOS-e820: [mem 0xaaf23000-0xaafe7fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xaafe8000-0xaaffcfff] usable
[0.00] BIOS-e820: [mem 0xaaffd000-0xaaff] ACPI data
[0.00] BIOS-e820: [mem 0xab00-0xafff] reserved
[0.00] BIOS-e820: [mem 0xe000-0xe3ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed1-0xfed13fff] reserved
[0.00] BIOS-e820: [mem 0xfed18000-0xfed19fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff98-0xffbf] reserved
[0.00] BIOS-e820: [mem 0xffd8-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00024f7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.6 present.
[0.00] DMI: ASUSTeK Computer Inc. N53SN/N53SN, BIOS N53SN.209 01/10/2012
[0.00] tsc: F

Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
Chris,

Scrub is still running. When it's done, I'll reboot a couple of times. 

sdb is in a SIIG 3.0 USB 2x docking station. Could it be NOT passing some 
device commands? I have sent a query to the developer(s) of smartmontools just 
in case.

 Regards,

George..

On Saturday, March 6, 2021, 1:36:13 PM PST, Chris Murphy 
 wrote: 





fdisk says:
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
/dev/sda8      436217856 3907029167 3470811312  1.6T 83 Linux

sda8 is 1777055391744 bytes

Btrfs says:
  dev_item.total_bytes    1777055391744

Those agree. The scrub message comes from
block/blk-core.c:655:  pr_info_ratelimited("attempt to access beyond
end of device\n"

I don't know why it would be triggered.



fdisk says:
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
/dev/sdb1        2048 976773167 976771120 465.8G 83 Linux

sdb1 is 500106813440 bytes.

kernel says:
[152968.929912] sdb: p1 size 1465144002 extends beyond EOD, enabling
native capacity

this is coming from
block/partitions/core.c:573:                  "%s: p%d size %llu
extends beyond EOD, ",
and
block/partitions/core.c:519:            printk(KERN_CONT "enabling
native capacity\n");

I've got no idea what it's complaining about though. Seems like the
kernel and fdisk have very different ideas about how to read this
partition map.

btrfs says:
dev_item.total_bytes    500106813440

The partition map and btrfs have the exact same bytes again, that's
good. The only discrepancy here is the kernel's block core is confused
about it. I don't know why that would be. Does that EOD message happen
on every boot for sdb1?


--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread Chris Murphy
fdisk says:
 Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
 /dev/sda8   436217856 3907029167 3470811312  1.6T 83 Linux

sda8 is 1777055391744 bytes

Btrfs says:
  dev_item.total_bytes1777055391744

Those agree. The scrub message comes from
block/blk-core.c:655:   pr_info_ratelimited("attempt to access beyond
end of device\n"

I don't know why it would be triggered.



fdisk says:
 Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
 /dev/sdb12048 976773167 976771120 465.8G 83 Linux

sdb1 is 500106813440 bytes.

kernel says:
 [152968.929912] sdb: p1 size 1465144002 extends beyond EOD, enabling
native capacity

this is coming from
block/partitions/core.c:573:   "%s: p%d size %llu
extends beyond EOD, ",
and
block/partitions/core.c:519:printk(KERN_CONT "enabling
native capacity\n");

I've got no idea what it's complaining about though. Seems like the
kernel and fdisk have very different ideas about how to read this
partition map.

btrfs says:
 dev_item.total_bytes500106813440

The partition map and btrfs have the exact same bytes again, that's
good. The only discrepancy here is the kernel's block core is confused
about it. I don't know why that would be. Does that EOD message happen
on every boot for sdb1?

--
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread Chris Murphy
On Sat, Mar 6, 2021 at 1:53 PM George R Goffe  wrote:
>
> [17325.282263] BTRFS warning (device sdb1): checksum error at logical 
> 498744950784 on dev /dev/sdb1, physical 1415872512, root 256, inode 257, 
> offset 262144, length 4096, links 1 (path: image)
> [17325.282299] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 1, gen 0
> [17325.282310] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744950784 on dev /dev/sdb1
> [17325.282307] BTRFS warning (device sdb1): checksum error at logical 
> 498744688640 on dev /dev/sdb1, physical 1415610368, root 256, inode 257, 
> offset 0, length 4096, links 1 (path: image)
> [17325.282384] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 2, gen 0
> [17325.282387] BTRFS warning (device sdb1): checksum error at logical 
> 498744819712 on dev /dev/sdb1, physical 1415741440, root 256, inode 257, 
> offset 131072, length 4096, links 1 (path: image)
> [17325.282397] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744688640 on dev /dev/sdb1
> [17325.282441] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 3, gen 0
> [17325.282454] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744819712 on dev /dev/sdb1
> [17325.282671] BTRFS warning (device sdb1): checksum error at logical 
> 498745081856 on dev /dev/sdb1, physical 1416003584, root 256, inode 257, 
> offset 393216, length 4096, links 1 (path: image)
> [17325.282697] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 4, gen 0
> [17325.282706] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498745081856 on dev /dev/sdb1
> [17325.303497] BTRFS warning (device sdb1): checksum error at logical 
> 498745212928 on dev /dev/sdb1, physical 1416134656, root 256, inode 257, 
> offset 524288, length 4096, links 1 (path: image)
> [17325.303536] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 5, gen 0
> [17325.303548] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498745212928 on dev /dev/sdb1
> [17325.347416] BTRFS warning (device sdb1): checksum error at logical 
> 498744954880 on dev /dev/sdb1, physical 1415876608, root 256, inode 257, 
> offset 266240, length 4096, links 1 (path: image)
> [17325.347453] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 6, gen 0
> [17325.347465] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744954880 on dev /dev/sdb1
> [17325.351201] BTRFS warning (device sdb1): checksum error at logical 
> 498745344000 on dev /dev/sdb1, physical 1416265728, root 256, inode 257, 
> offset 655360, length 4096, links 1 (path: image)
> [17325.351235] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 7, gen 0
> [17325.351246] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498745344000 on dev /dev/sdb1
> [17325.356651] BTRFS warning (device sdb1): checksum error at logical 
> 498744823808 on dev /dev/sdb1, physical 1415745536, root 256, inode 257, 
> offset 135168, length 4096, links 1 (path: image)
> [17325.356672] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 8, gen 0
> [17325.356680] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744823808 on dev /dev/sdb1
> [17325.358061] BTRFS warning (device sdb1): checksum error at logical 
> 498744958976 on dev /dev/sdb1, physical 1415880704, root 256, inode 257, 
> offset 270336, length 4096, links 1 (path: image)
> [17325.358081] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 9, gen 0
> [17325.358089] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498744958976 on dev /dev/sdb1
> [17325.359272] BTRFS warning (device sdb1): checksum error at logical 
> 498745085952 on dev /dev/sdb1, physical 1416007680, root 256, inode 257, 
> offset 397312, length 4096, links 1 (path: image)
> [17325.359288] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
> flush 0, corrupt 10, gen 0
> [17325.359295] BTRFS error (device sdb1): unable to fixup (regular) error at 
> logical 498745085952 on dev /dev/sdb1

You're hitting the same bug as before. The errors only affect root 256
inode 257 path image, i.e. ext2_saved/image which is the rollback
image. No other files are affected. This bug isn't related to the
device size messages.

-- 
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to sp

Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
fc35-bash 5.1 ~# btrfs inspect-internal dump-super  /dev/sda8 | grep bytes
total_bytes 1777055391744
bytes_used  1771772448768
dev_item.total_bytes    1777055391744
dev_item.bytes_used 1777053872128
fc35-bash 5.1 ~# btrfs inspect-internal dump-super  /dev/sdb1 | grep bytes
total_bytes 500106813440
bytes_used  364380844032
dev_item.total_bytes    500106813440
dev_item.bytes_used 366454042624








On Saturday, March 6, 2021, 12:56:58 PM PST, Chris Murphy 
 wrote: 





Also need:

sudo btrfs insp dump-s /dev/sda8 | grep 'total_bytes\|dev_item.total_bytes'
sudo btrfs insp dump-s /dev/sdb1 | grep 'total_bytes\|dev_item.total_bytes'


--
Chris
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread Chris Murphy
Also need:

sudo btrfs insp dump-s /dev/sda8 | grep 'total_bytes\|dev_item.total_bytes'
sudo btrfs insp dump-s /dev/sdb1 | grep 'total_bytes\|dev_item.total_bytes'

--
Chris
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
Chris,

Started scrub on sdb1 now... lots of errors. see below.

On Saturday, March 6, 2021, 12:31:02 PM PST, Chris Murphy 
 wrote: 





On Sat, Mar 6, 2021 at 10:07 AM George R Goffe  wrote:
>
> Chris,
>
> I'm trying to re-create the "beyond end of disk" problem. I have nowhere near 
> enough extra space to hold the image and tar file you've asked for AND, 
> there's too much personal information for me for me to feel comfortable 
> posting it publicly.

Understood. e2image doesn't have a filename scrubber like the
btrfs-image equivalent (-s and -ss). I don't have a good work around
for this, and suggest asking on the ext4 development list.

> I'm converting a smaller drive now and see an error message "1234 [ 
> 3341.845090] sdb: p1 size 1465144002 extends beyond EOD, enabling native 
> capacity". Do you think this will cause the error condition from scrub that 
> "we" are looking for?

What do you get for

fdisk -l /dev/sda
fdisk -l /dev/sdb

[17691.435473] perf: interrupt took too long (5043 > 5032), lowering 
kernel.perf_event_max_sample_rate to 39000
fc35-bash 5.1 ~# fdisk -l /dev/sda
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000LX001-1RG1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xbe1e64f5

Device Boot Start    End    Sectors  Size Id Type
/dev/sda1  * 2048    4196351    4194304    2G 83 Linux
/dev/sda2 4196352    8390655    4194304    2G 83 Linux
/dev/sda3 8390656   33556479   25165824   12G 82 Linux swap / Solaris
/dev/sda4    33556480 3907029167 3873472688  1.8T  5 Extended
/dev/sda5    33558528  167776255  134217728   64G 83 Linux
/dev/sda6   167778304  301996031  134217728   64G 83 Linux
/dev/sda7   301998080  436215807  134217728   64G 83 Linux
/dev/sda8   436217856 3907029167 3470811312  1.6T 83 Linux
fc35-bash 5.1 ~# fdisk -l /dev/sdb
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: 5AS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00056b05

Device Boot Start   End   Sectors   Size Id Type
/dev/sdb1    2048 976773167 976771120 465.8G 83 Linux




[12632.689114] BTRFS: device fsid 61eb6107-6b66-4aab-a3ce-5c22838a4ffa devid 1 
transid 30 /dev/sdb1 scanned by systemd-udevd (301062)
[17284.215093] BTRFS info (device sdb1): disk space caching is enabled
[17284.215103] BTRFS info (device sdb1): has skinny extents
[17284.215105] BTRFS info (device sdb1): flagging fs with big metadata feature
[17284.724090] BTRFS info (device sdb1): creating UUID tree
[17284.798392] BTRFS info (device sdb1): checking UUID tree
[17294.986389] BTRFS info (device sdb1): scrub: started on devid 1
[17325.282263] BTRFS warning (device sdb1): checksum error at logical 
498744950784 on dev /dev/sdb1, physical 1415872512, root 256, inode 257, offset 
262144, length 4096, links 1 (path: image)
[17325.282299] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
flush 0, corrupt 1, gen 0
[17325.282310] BTRFS error (device sdb1): unable to fixup (regular) error at 
logical 498744950784 on dev /dev/sdb1   
     
[17325.282307] BTRFS warning (device sdb1): checksum error at logical 
498744688640 on dev /dev/sdb1, physical 1415610368, root 256, inode 257, offset 
0, length 4096, links 1 (path: image)
[17325.282384] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
flush 0, corrupt 2, gen 0
[17325.282387] BTRFS warning (device sdb1): checksum error at logical 
498744819712 on dev /dev/sdb1, physical 1415741440, root 256, inode 257, offset 
131072, length 4096, links 1 (path: image)
[17325.282397] BTRFS error (device sdb1): unable to fixup (regular) error at 
logical 498744688640 on dev /dev/sdb1   
     
[17325.282441] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
flush 0, corrupt 3, gen 0
[17325.282454] BTRFS error (device sdb1): unable to fixup (regular) error at 
logical 498744819712 on dev /dev/sdb1   
     
[17325.282671] BTRFS warning (device sdb1): checksum error at logical 
498745081856 on dev /dev/sdb1, physical 1416003584, root 256, inode 257, offset 
393216, length 4096, links 1 (path: image)
[17325.282697] BTRFS error (device sdb1): bdev /dev/sdb1 errs: wr 0, rd 0, 
flush 0, corrupt 4, gen 0
[17325.282706] BTRFS error (device sdb1): unable to fixup (regular) error at 
logical 498745081856 on dev /dev/sdb1   
  

Re: Need help with btrfs.

2021-03-06 Thread Chris Murphy
On Sat, Mar 6, 2021 at 10:07 AM George R Goffe  wrote:
>
> Chris,
>
> I'm trying to re-create the "beyond end of disk" problem. I have nowhere near 
> enough extra space to hold the image and tar file you've asked for AND, 
> there's too much personal information for me for me to feel comfortable 
> posting it publicly.

Understood. e2image doesn't have a filename scrubber like the
btrfs-image equivalent (-s and -ss). I don't have a good work around
for this, and suggest asking on the ext4 development list.

> I'm converting a smaller drive now and see an error message "1234 [ 
> 3341.845090] sdb: p1 size 1465144002 extends beyond EOD, enabling native 
> capacity". Do you think this will cause the error condition from scrub that 
> "we" are looking for?

What do you get for

fdisk -l /dev/sda
fdisk -l /dev/sdb


-- 
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 34 git clone error

2021-03-06 Thread Qiyu Yan
Okay... I don't think this is related to fedora. Are you in mainland China? If 
so you may want a proxy to play with GitHub. 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora 34 git clone error

2021-03-06 Thread wang_chen
git clone -b v1.11.3 https://github.com/PX4/PX4-Autopilot.git

正克隆到 'PX4-Autopilot'...
fatal: 无法访问 'https://github.com/PX4/PX4-Autopilot.git/':OpenSSL SSL_read: 
连接被对方重设, errno 104

-->
fatal: Cannot access'https://github.com/PX4/PX4-Autopilot.git/': OpenSSL 
SSL_read: The connection was reset by the other party, errno 104 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Need help with btrfs.

2021-03-06 Thread George R Goffe via test
Chris,

I'm trying to re-create the "beyond end of disk" problem. I have nowhere near 
enough extra space to hold the image and tar file you've asked for AND, there's 
too much personal information for me for me to feel comfortable posting it 
publicly.

I'm converting a smaller drive now and see an error message "1234 [ 
3341.845090] sdb: p1 size 1465144002 extends beyond EOD, enabling native 
capacity". Do you think this will cause the error condition from scrub that 
"we" are looking for? The sdb1 partition is smaller than "native capacity" by 
the way. Is this a problem?

Regards,

George...





On Friday, March 5, 2021, 3:51:14 PM PST, Chris Murphy 
 wrote: 





On Fri, Mar 5, 2021 at 10:39 AM Chris Murphy  wrote:
>
> Quick follow up on one thing I can't reproduce from George's scrub:
>
> [36365.549230] BTRFS error (device sda8): scrub: tree block
> 1777055424512 spanning stripes, ignored. logical=1777055367168
> [36365.549262] attempt to access beyond end of device
>                sda8: rw=0, want=3470811376, limit=3470811312
>
> I think this is just a benign artifact of the convert, and once the
> ext2_saved/image file is deleted, it will go away. I've asked upstream
> about it but I'm not sure when I'll hear back.

Ok Qu wants to see it. No need to file any bugs though. I'll just
track it upstream.

> mount -o ro,rescue=all /dev/sda8 /mnt/btrfs
> losetup -r /dev/loop1 /mnt/btrfs/ext2_saved/image
> e2image -Q /dev/loop1 /path/to/sda8ext4-e2image.bin
>
> I estimate the file could be around 700MB (maybe up to 2G). It can be
> compressed:
>
> tar -S -acf sda8ext4-e2image.bin.tar.gz sda8ext4-e2image.bin

And then upload the 'sda8ext4-e2image.bin.tar.gz' file some place
convenient like nextcloud, google drive, drop box, or equivalent.  A
user on #fedora recommended https://siasky.net/ but I don't know if
that can accept files as big as this will be.

Post the download URL here or email it offlist and I'll add it to the
upstream thread.


-- 
Chris Murphy
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora-IoT-34-20210306.0 compose check report

2021-03-06 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 1/16 (x86_64), 4/15 (aarch64)

Old failures (same test failed in Fedora-IoT-34-20210305.0):

ID: 802207  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/802207
ID: 802216  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/802216
ID: 802223  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/802223
ID: 802226  Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/802226
ID: 802227  Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi
URL: https://openqa.fedoraproject.org/tests/802227

Soft failed openQA tests: 3/16 (x86_64), 1/15 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-34-20210305.0):

ID: 802199  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/802199
ID: 802200  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/802200
ID: 802201  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/802201
ID: 802215  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/802215

Passed openQA tests: 12/16 (x86_64), 10/15 (aarch64)
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora-34-20210306.n.0 compose check report

2021-03-06 Thread Fedora compose checker
No missing expected images.

Failed openQA tests: 10/126 (aarch64), 6/187 (x86_64)

New failures (same test not failed in Fedora-34-20210305.n.0):

ID: 802006  Test: aarch64 Server-dvd-iso install_updates_nfs@uefi
URL: https://openqa.fedoraproject.org/tests/802006
ID: 802009  Test: aarch64 Server-dvd-iso base_update_cli@uefi
URL: https://openqa.fedoraproject.org/tests/802009
ID: 802051  Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi
URL: https://openqa.fedoraproject.org/tests/802051
ID: 802094  Test: x86_64 universal install_lvmthin
URL: https://openqa.fedoraproject.org/tests/802094
ID: 802122  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/802122
ID: 802161  Test: aarch64 universal install_with_swap@uefi
URL: https://openqa.fedoraproject.org/tests/802161
ID: 802167  Test: aarch64 universal install_scsi_updates_img@uefi
URL: https://openqa.fedoraproject.org/tests/802167
ID: 802183  Test: x86_64 KDE-live-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/802183

Old failures (same test failed in Fedora-34-20210305.n.0):

ID: 801938  Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/801938
ID: 801942  Test: x86_64 Workstation-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/801942
ID: 801998  Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/801998
ID: 802049  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/802049
ID: 802065  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/802065
ID: 802142  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/802142
ID: 802176  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/802176
ID: 802181  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/802181

Soft failed openQA tests: 56/126 (aarch64), 89/187 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-34-20210305.n.0):

ID: 802003  Test: aarch64 Server-dvd-iso 
install_repository_hd_variation@uefi
URL: https://openqa.fedoraproject.org/tests/802003
ID: 802004  Test: aarch64 Server-dvd-iso 
install_repository_nfs_variation@uefi
URL: https://openqa.fedoraproject.org/tests/802004

Old soft failures (same test soft failed in Fedora-34-20210305.n.0):

ID: 801870  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/801870
ID: 801871  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/801871
ID: 801873  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/801873
ID: 801876  Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/801876
ID: 801877  Test: x86_64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/801877
ID: 801878  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/801878
ID: 801879  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/801879
ID: 801880  Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/801880
ID: 801881  Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/801881
ID: 801882  Test: x86_64 Server-dvd-iso install_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/801882
ID: 801883  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/801883
ID: 801884  Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/801884
ID: 801885  Test: x86_64 Server-dvd-iso install_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/801885
ID: 801886  Test: x86_64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/801886
ID: 801887  Test: x86_64 Server-dvd-iso install_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/801887
ID: 801889  Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/801889
ID: 801890  Test: x86_64 Server-dvd-iso install_vnc_server
URL: https://openqa.fedoraproject.org/tests/801890
ID: 801891  Test: x86_64 Server-dvd-iso install_vncconnect_client
URL: https://openqa.fedoraproject.org/tests/801891
ID: 801892  Test: x86_64 Server-dvd-iso install_vncconnect_server
URL: https://openqa.fedoraproject.org/tests/801892
ID: 8018

Fedora 34 compose report: 20210306.n.0 changes

2021-03-06 Thread Fedora Rawhide Report
OLD: Fedora-34-20210305.n.0
NEW: Fedora-34-20210306.n.0

= SUMMARY =
Added images:2
Dropped images:  4
Added packages:  0
Dropped packages:0
Upgraded packages:   5
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   860.46 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -5.84 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-34-20210306.n.0.armhfp.raw.xz
Image: KDE raw-xz aarch64
Path: Spins/aarch64/images/Fedora-KDE-34-20210306.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-34-20210305.n.0.s390x.tar.xz
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-34-20210305.n.0.s390x.raw.xz
Image: Container_Base docker s390x
Path: Container/s390x/images/Fedora-Container-Base-34-20210305.n.0.s390x.tar.xz
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-34-20210305.n.0.s390x.qcow2

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  anaconda-34.24.5-3.fc34
Old package:  anaconda-34.24.5-2.fc34
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 22.33 MiB
Size change:  3.84 KiB
Changelog:
  * Tue Mar 02 2021 Martin Kolman  - 34.24.5-3
  - Choose the best locale more carefully (#1933384) (vponcova)


Package:  firefox-86.0-7.fc34
Old package:  firefox-85.0-11.fc34
Summary:  Mozilla Firefox Web browser
RPMs: firefox firefox-testresults firefox-wayland firefox-x11
Size: 308.59 MiB
Size change:  -3.46 MiB
Changelog:
  * Mon Feb 08 2021 Martin Stransky  - 85.0.1-1
  - Updated to 85.0.1

  * Tue Feb 23 2021 Martin Stransky  - 85.0.1-2
  - Fixed some reftest run in Mock

  * Tue Feb 23 2021 Martin Stransky  - 86.0-1
  - Update to 86.0
  - Disabled Wayland backend on KDE/Plasma

  * Fri Feb 26 2021 Martin Stransky  - 86.0-2
  - Built with system nss

  * Mon Mar 01 2021 Martin Stransky  - 86.0-3
  - Added icecat-78.7.1-fix_error_template_with_C_linkage.patch to
build on F34+

  * Mon Mar 01 2021 Martin Stransky  - 86.0-4
  - Enable Wayland backend only when Wayland display is set.

  * Mon Mar 01 2021 Martin Stransky  - 86.0-6
  - Run xpcshell tests sequential
  - Test fixes

  * Wed Mar 03 2021 Martin Stransky  - 86.0-7
  - Added fix for mozbz#1694670


Package:  kernel-5.11.3-300.fc34
Old package:  kernel-5.11.0-156.fc34
Summary:  The Linux kernel
RPMs: kernel kernel-core kernel-debug kernel-debug-core 
kernel-debug-devel kernel-debug-modules kernel-debug-modules-extra 
kernel-debug-modules-internal kernel-devel kernel-lpae kernel-lpae-core 
kernel-lpae-devel kernel-lpae-modules kernel-lpae-modules-extra 
kernel-lpae-modules-internal kernel-modules kernel-modules-extra 
kernel-modules-internal
Size: 494.18 MiB
Size change:  -2.14 MiB
Changelog:
  * Fri Feb 26 2021 Justin M. Forbes  [5.11.1-2]
  - MARKER needs SUBLEVEL for stable, I need to think of a better longterm 
solution (Justin M. Forbes)
  - Config updates for 5.11.1 (Justin M. Forbes)
  - Set CONFIG_DEBUG_HIGHMEM as off for non debug kernels (Justin M. Forbes)
  - CONFIG_DEBUG_HIGHMEM should be debug only (Justin M. Forbes)
  - Added redhat/fedora-dist-git-test.sh for a quick and easy script to test 
changes (Justin M. Forbes)
  - Changes for building stable Fedora (Justin M. Forbes)
  - Clean up redhat/configs/pending-common/generic/CONFIG_USB_RTL8153_ECM as it 
messes with scripts (Justin M. Forbes)
  - Bluetooth: btusb: Some Qualcomm Bluetooth adapters stop working (Hui Wang)
  - process_configs.sh: fix find/xargs data flow (Ondrej Mosnacek)
  - Fedora config update (Justin M. Forbes)
  - fedora: minor arm sound config updates (Peter Robinson)
  - Fix trailing white space in 
redhat/configs/fedora/generic/CONFIG_SND_INTEL_BYT_PREFER_SOF (Justin M. Forbes)
  - Add a redhat/rebase-notes.txt file (Hans de Goede)
  - Turn on SND_INTEL_BYT_PREFER_SOF for Fedora (Hans de Goede)
  - ALSA: hda: intel-dsp-config: Add SND_INTEL_BYT_PREFER_SOF Kconfig option 
(Hans de Goede) [1924101]
  - CI: Drop MR ID from the name variable (Veronika Kabatova)
  - redhat: add DUP and kpatch certificates to system trusted keys for RHEL 
build (Herton R. Krzesinski)
  - The comments in CONFIG_USB_RTL8153_ECM actually turn off CONFIG_USB_RTL8152 
(Justin M. Forbes)
  - Update CKI pipeline project (Veronika Kabatova)
  - Turn off additional KASAN options for Fedora (Justin M. Forbes)
  - Rename the master branch to rawhide for Fedora (Justin M. Forbes)
  - Makefile targets for packit integration (Ben Crocker)
  - Turn off KASAN for rawhide debug builds

Fedora-IoT-35-20210306.0 compose check report

2021-03-06 Thread Fedora compose checker
Missing expected images:

Iot dvd x86_64
Iot dvd aarch64

Failed openQA tests: 5/15 (aarch64), 1/16 (x86_64)

New failures (same test not failed in Fedora-IoT-35-20210305.0):

ID: 801858  Test: aarch64 IoT-dvd_ostree-iso iot_rpmostree_overlay@uefi
URL: https://openqa.fedoraproject.org/tests/801858
ID: 801866  Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/801866
ID: 801867  Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi
URL: https://openqa.fedoraproject.org/tests/801867

Old failures (same test failed in Fedora-IoT-35-20210305.0):

ID: 801847  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/801847
ID: 801856  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/801856
ID: 801863  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/801863

Soft failed openQA tests: 3/16 (x86_64), 1/15 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-35-20210305.0):

ID: 801839  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/801839
ID: 801840  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/801840
ID: 801841  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/801841
ID: 801855  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/801855

Passed openQA tests: 12/16 (x86_64), 9/15 (aarch64)

New passes (same test not passed in Fedora-IoT-35-20210305.0):

ID: 801853  Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/801853
ID: 801868  Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/801868

Installed system changes in test x86_64 IoT-dvd_ostree-iso 
install_default@uefi: 
Used mem changed from 175 MiB to 193 MiB
Previous test data: https://openqa.fedoraproject.org/tests/800804#downloads
Current test data: https://openqa.fedoraproject.org/tests/801839#downloads

Installed system changes in test x86_64 IoT-dvd_ostree-iso 
install_default_upload: 
Used mem changed from 174 MiB to 193 MiB
Previous test data: https://openqa.fedoraproject.org/tests/800805#downloads
Current test data: https://openqa.fedoraproject.org/tests/801840#downloads

Installed system changes in test aarch64 IoT-dvd_ostree-iso 
install_default_upload@uefi: 
Used mem changed from 184 MiB to 207 MiB
System load changed from 0.04 to 0.21
Previous test data: https://openqa.fedoraproject.org/tests/800820#downloads
Current test data: https://openqa.fedoraproject.org/tests/801855#downloads
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora-Cloud-32-20210306.0 compose check report

2021-03-06 Thread Fedora compose checker
No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210305.0):

ID: 801830  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/801830
ID: 801837  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/801837

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
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.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora-Rawhide-20210305.n.1 compose check report

2021-03-06 Thread Fedora compose checker
No missing expected images.

Compose FAILS proposed Rawhide gating check!
2 of 43 required tests failed, 4 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 11/187 (x86_64), 16/126 (aarch64)

New failures (same test not failed in Fedora-Rawhide-20210304.n.0):

ID: 801455  Test: x86_64 Server-dvd-iso server_cockpit_updates
URL: https://openqa.fedoraproject.org/tests/801455
ID: 801478  Test: x86_64 Workstation-live-iso install_default_upload 
**GATING**
URL: https://openqa.fedoraproject.org/tests/801478
ID: 801537  Test: aarch64 Minimal-raw_xz-raw.xz base_selinux@uefi
URL: https://openqa.fedoraproject.org/tests/801537
ID: 801538  Test: aarch64 Minimal-raw_xz-raw.xz 
base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/801538
ID: 801539  Test: aarch64 Minimal-raw_xz-raw.xz release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/801539
ID: 801555  Test: aarch64 Server-dvd-iso 
install_repository_hd_variation@uefi
URL: https://openqa.fedoraproject.org/tests/801555
ID: 801603  Test: aarch64 Workstation-raw_xz-raw.xz desktop_terminal@uefi
URL: https://openqa.fedoraproject.org/tests/801603
ID: 801608  Test: aarch64 Cloud_Base-qcow2-qcow2 base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/801608
ID: 801616  Test: x86_64 universal install_arabic_language
URL: https://openqa.fedoraproject.org/tests/801616
ID: 801630  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/801630
ID: 801639  Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/801639
ID: 801656  Test: x86_64 universal install_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/801656
ID: 801693  Test: aarch64 universal install_arabic_language@uefi
URL: https://openqa.fedoraproject.org/tests/801693
ID: 801701  Test: aarch64 universal install_cyrillic_language@uefi
URL: https://openqa.fedoraproject.org/tests/801701
ID: 801705  Test: aarch64 universal install_european_language@uefi
URL: https://openqa.fedoraproject.org/tests/801705
ID: 801713  Test: aarch64 universal install_with_swap@uefi
URL: https://openqa.fedoraproject.org/tests/801713

Old failures (same test failed in Fedora-Rawhide-20210304.n.0):

ID: 801464  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/801464
ID: 801536  Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/801536
ID: 801550  Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/801550
ID: 801574  Test: aarch64 Server-dvd-iso modularity_tests@uefi
URL: https://openqa.fedoraproject.org/tests/801574
ID: 801601  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/801601
ID: 801617  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/801617
ID: 801694  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/801694
ID: 801729  Test: aarch64 universal upgrade_minimal_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/801729
ID: 801736  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/801736
ID: 801746  Test: x86_64 KDE-live-iso desktop_browser **GATING**
URL: https://openqa.fedoraproject.org/tests/801746
ID: 801747  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/801747

Soft failed openQA tests: 52/126 (aarch64), 76/187 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-Rawhide-20210304.n.0):

ID: 801602  Test: aarch64 Workstation-raw_xz-raw.xz desktop_printing@uefi
URL: https://openqa.fedoraproject.org/tests/801602
ID: 801604  Test: aarch64 Workstation-raw_xz-raw.xz 
desktop_update_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/801604
ID: 801640  Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/801640
ID: 801718  Test: aarch64 universal install_repository_http_graphical@uefi
URL: https://openqa.fedoraproject.org/tests/801718

Old soft failures (same test soft failed in Fedora-Rawhide-20210304.n.0):

ID: 801422  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/801422
ID: 801423  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/801423
ID: 801425  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/801425
ID: 801430  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/801430
ID: 801431  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL