All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Lucas Bates <lucasb@mojatatu.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, mleitner@redhat.com, vladbu@mellanox.com,
	dcaratti@redhat.com, kernel@mojatatu.com
Subject: Re: [RFC net-next 1/1] tdc.py: Introduce required plugins
Date: Wed, 10 Apr 2019 16:33:52 +0200	[thread overview]
Message-ID: <a0c266ba-8749-c8a6-738a-7fe905682398@6wind.com> (raw)
In-Reply-To: <1554846285-20657-1-git-send-email-lucasb@mojatatu.com>

Le 09/04/2019 à 23:44, Lucas Bates a écrit :
> Some of the testcases (for example, all of the fw tests) in tdc
> require activating the nsplugin. This RFC introduces a feature which
> tags one such test with the keyword "requires". Anyone running a test
> that requires nsplugin will now get a warning if they are missing
> the plugin.
> 
> After compiling the list of test cases to execute, tdc will
> gather all of the required plugins for that run, and validate
> that they have been enabled with a symlink in the plugins/
> directory. If required plugins are missing, tdc will create the
> symlink for the user and then terminate. (This is because plugin-
> specific options may exist and need to be parsed at startup)
I still don't understand the goal of this plugin. Why not simply include it in
the core code (like it was some times ago)?

> 
> Please provide feedback.  If this is amenable to all, I will proceed
> to submit for the rest.
After your patch, I got the following error:
$ ./tdc.py
Traceback (most recent call last):
  File "./tdc.py", line 740, in <module>
    main()
  File "./tdc.py", line 734, in main
    set_operation_mode(pm, args)
  File "./tdc.py", line 692, in set_operation_mode
    check_required_plugins(pm, alltests)
  File "./tdc.py", line 583, in check_required_plugins
    os.chown('plugins/{}'.format(fname), uid=int(os.getenv('SUDO_UID')),
TypeError: int() argument must be a string or a number, not 'NoneType'


Regards,
Nicolas

  reply	other threads:[~2019-04-10 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 21:44 [RFC net-next 1/1] tdc.py: Introduce required plugins Lucas Bates
2019-04-10 14:33 ` Nicolas Dichtel [this message]
2019-04-11 20:54   ` Lucas Bates
2019-04-12  8:31     ` Nicolas Dichtel
2019-04-12 15:21       ` Lucas Bates
2019-04-12 15:42         ` Nicolas Dichtel
2019-04-12 16:07           ` Lucas Bates
2019-04-12 23:37             ` Nicolas Dichtel
2019-04-16 15:19               ` Lucas Bates

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=a0c266ba-8749-c8a6-738a-7fe905682398@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel@mojatatu.com \
    --cc=lucasb@mojatatu.com \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@mellanox.com \
    --cc=xiyou.wangcong@gmail.com \
    /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.