From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-test.pl failures
Date: Fri, 17 Oct 2008 08:49:20 +0000 [thread overview]
Message-ID: <48F85190.5040106@tuffmail.co.uk> (raw)
In-Reply-To: <40880A7E.4050400@bulldog.unca.edu>
Kay Sievers wrote:
> On Tue, Sep 16, 2008 at 7:16 PM, Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>> On Tue, Sep 16, 2008 at 03:09, Alan Jenkins <alan-jenkins@tuffmail.co.uk> wrote:
>>
>>> commit 8753fadf2a6ecead372e71b8bf9336cf29f9c958
>>>
>>> Lots of the udev tests fail here. udev_sysfs.c broke when
>>> util_resolve_sys_link() switched API.
>>>
>> Ah, sorry, should be fixed now.
>>
>>
>>> I'll leave this up to you - maybe
>>> your next commit is going to do away with udev_sysfs.c altogether :-).
>>>
>> It will go away soon, yeah. We should get rid of udev_sysfs.c and
>> "struct udevice".
>>
>
> Along with a lot of other stuff, udev_sysfs.c is gone. Also the global
> event environment is replaced by a per-device property list. The
> daemon, and everything else uses the libudev code now.
>
> It seems to work fine here, but the code may be a bit rough at the
> moment, until it has seen more testing. But, it should be pretty easy
> now to play around with a threaded version of the daemon.
>
> Thanks,
> Kay
>
Great. I don't have so much time now though; I need to concentrate on
project work.
Going back to the original subject line... :-). I see the tests still
pass, but some of them make suspicious noises now.
TEST 7: label test of max sysfs files
device
'/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1'
expecting node 'boot_disk1'
libudev: add_rule_key_pair: skip, too many keys of the same type in a
single rule
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
add: ok
libudev: add_rule_key_pair: skip, too many keys of the same type in a
single rule
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
remove: ok
TEST 19: Handle stupid backslashed multi lines in config file (and
replace kernel name)
device '/devices/pci0000:00/0000:00:1d.7/usb5/5-2/5-2:1.0/tty/ttyACM0'
expecting node 'modem'
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:4'
add: ok
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:4'
remove: ok
TEST 118: ENV{} test (assign2)
device
'/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1'
expecting node 'part'
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
add:
ok
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
remove: ok
TEST 129: final assignment
device
'/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda'
expecting node 'ok'
libudev: lookup_group: specified group 'nobody'
unknown
Argument "nobody" isn't numeric in numeric ne (!=) at ./udev-test.pl
line 1671.
permissions:
ok
add:
ok
remove: ok
TEST 144: overlong comment line
device
'/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda1'
expecting node 'yes'
libudev: add_to_rules: invalid KERNEL
operation
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
add:
ok
libudev: add_to_rules: invalid KERNEL
operation
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
remove: ok
TEST 146: TEST absolute path
device
'/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda'
expecting node 'there'
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
add: ok
libudev: add_to_rules: invalid rule
'/home/alan/Documents/bootup/src/udev/test/udev-test.rules:1'
remove: ok
next prev parent reply other threads:[~2008-10-17 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 18:10 udev-test.pl failures Erik Harrison
2004-04-22 21:28 ` Kay Sievers
2004-04-22 22:15 ` Greg KH
2008-09-16 10:09 ` Alan Jenkins
2008-09-16 17:16 ` Kay Sievers
2008-10-16 23:43 ` Kay Sievers
2008-10-17 8:49 ` Alan Jenkins [this message]
2008-10-17 12:05 ` Kay Sievers
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 \
--in-reply-to=48F85190.5040106@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=linux-hotplug@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.