text:
Can't run now-cli on PC

I installed now on my windows 10 pc and after an update, it always say

OS: Windows 10
Node Version: v6.9.5

now is bundled from now-desktop for windows

Is your Windows version 32 bit or 64?

https://www.microsoft.com/en-us/download/details.aspx?id=11533
Also please run fciv.exe -both now.exe against now executable that causes that error message.

No answer for 15 days

I'm also getting the message This app can't run on your PC
Versions:
OS: Windows 10 pro 64 bit
Now: 1.2.3
Node: v6.9.5

Ran this: certutil -hashfile now.exe
SHA1 hash of file now.exe:
fb ff 64 3c 3e 46 70 a8 c7 d2 3d e5 c3 85 d9 5c df dd 29 6e
CertUtil: -hashfile command completed successfully.

@leo Please open this issue ....I too have got the same error...I downloaded Now Desktop 2.3.5 and I'm getting the following error on my Win 10 Pro 64 bit
Node version : 7.4.0
λ certutil -hashfile now.exe
SHA1 hash of file now.exe:
d17c6509c92822121abcd37b799e675e0b32d330
Is there any way we can gets logs of now?

Have you installed the binary through Now Desktop or did you just download Now Desktop expecting it to replace the binary automatically? 😊

Here's the thing @leo . As @hutch120 mentioned when we click on the Now Desktop , we get that error...no interface is even presented to us to download ....we just get  that Win10 error message.

Oh. So Now Desktop doesn't work? Not Now CLI.

Actually both....even typing cli in the terminal gives the same issue

Also running into this issue.

@Esslamb I had to redo npm global install of now for the problem to go away. YMMV.

@indcoder I just tried to remove it, it gave me some trouble so I removed it manually and re installed but still the same. The prompt just launches and then it prints access is denied.  Any ideas ?

@Esslamb  which version are you running? I have got 7.3.1 but this issue cannot be resolved till we know what the logs are saying @leo Where does now-cli log to default when initializing?

I tried installing the CLI alone without the desktop app but I still run into the same smart screen issue.

Same issue, can't run now from CLI

I'm running Win7 32-bit

Can someone confirm if this is still broken or fixed?

I will DL the latest version and try tonight @leo I uninstalled the CLI my windows machine due to the problems and just used my mac so hopefully, it's fixed.

@leo This seems fixed for me mate no more smart screen warnings. Thanks!

Going to optimistically close then, then :) Thanks for the confirmation @Esslamb!

https://user-images.githubusercontent.com/15871340/31042210-2de75320-a5c0-11e7-83bb-048524348e5b.png
Same issue, can't run now from CLI.
I'm running Win7 32-bit.

source: gharchive/issue

authors: Esslamb Qix- fallen90 hutch120 igorklopov indcoder itaditya leo sonyapax

repo: zeit/now-cli

license_type: permissive

license_source: github-api


text:
Rewrite styled-jsx/css

Since when we introduced it in v1 tagging a string with css would generate both scoped and global styles because there was no way for us to guess what were the user intentions.  This sucks because you'd get twice as much code in your bundles (ok gzip probably made this suck less but still it is not optimal).
I rewrote the entire external and outside of component styles  plugin to finally generate only scoped or global styles based on how the css string is tagged. Basically now css by default generates scoped styles and global styles can be created using css.global:
import css from 'styled-jsx/css'

// Scoped styles
export const button = css`button { color: hotpink; }`

// Global styles
export const body = css.global`body { margin: 0; }`

// Works also with default exports
export default css`div { color: green; }`

In addition to reduce the bundle size this change allows for one awesome thing that is... we could write a Webpack loader or use an existing one (I can talk to this guy) to let people write CSS in external .css files. This means that they'd get all the tools they are used to and they could do all the kind of transformations they want before running the styled-jsx transformation.
This branch introduces another neat feature that is a style resolver: css.resolve yields an object that contains the scoped className and the scoped styles (a react element):
import css from 'styled-jsx/css'

// Resolved styles
export const link = css.resolve`a { color: green; }`
// link.className -> scoped className to apply to `a` elements e.g. jsx-123
// link.styles -> styles element to render inside of your component

This solution was basically already possible in user land but now we have a proper API for it, and it can also work with dynamic styles:
function getStyles(color) {
  return css.resolve`
    a { color: ${color} }
  `
}

Final bonus. I created a Babel macro for resolve which should allow people to use this last feature in Create React App.
Since these are breaking changes, I'd say we release v3.
For more details take a look at the README.md, I am not expecting you to review this all :)

@giuseppeg Question about this PR. Does css.resolve still have the same behavior where nested selectors are prefixed?
Use case question I have is when passing a className to a third-party component, and I want only the top-level selector prefixed and everything within it not prefixed.

@jadengore yes every selector in the css string is scoped.

Use case question I have is when passing a className to a third-party component, and I want only the top-level selector prefixed and everything within it not prefixed.

For this you don't need styled-jsx I guess. You can just generate a unique classname that you would use like in ID to style the third party component with global styles

we could write a Webpack loader or use an existing one (I can talk to this guy) to let people write CSS in external .css files.

cc @hanford is currently using https://github.com/traveloka/styled-modules

Awesome!

When will this be released?

we are kinda blocked by https://github.com/thysultan/stylis.js/issues/101

source: gharchive/pull-request

authors: giuseppeg jadengore timneutkens

repo: zeit/styled-jsx

license: mit

license_source: bigquery


text:
Add styled-jsx/babel-test plugin

Adds styled-jsx/babel-test plugin as per discussion with @giuseppeg.
The readme entry feels a bit long, but I think it's necessary to give some background to explain why you might (or might not) want to use it.
Closes #459.

@callumlocke is it ok if we release next week? or do you need this asap?

next week is good 👍

authors: callumlocke giuseppeg


text:
How can I test the preferences.json file I'm working on?

I'm trying to add a preferences.json file to my theme (better active tab) to allow the user to select whether the active tab indicator is on the right or on the left. I'm testing it with a preferences.json file that I add to my folder in .config/zen/chrome/zen-themes/... but I don't see the option when I open the browser, not even the gear icon.
The preferences file looks like this:
{
    "property": "theme.better-active-tab.on-right",
    "label": "Move tha active tab indicator to the right",
    "type": "checkbox"
}

Should I just create a pull request to the theme-store with the changes? I'd like to test that it works before that.

Make sure you encase it again with another curlies {}, I've made a mistake of not doing that
{
  {
      "property": "theme.better-active-tab.on-right",
      "label": "Move tha active tab indicator to the right",
      "type": "checkbox"
  }
}

Thanks, that was one piece of the puzzle. To get the options on the browser though, I had to edit the zen-themes.json file in ~/.config/zen and manually add the preferences file to the respective entry in the json.

authors: Dinno-DEV HliasOuzounis

repo: zen-browser/theme-store

license: MIT


text:
storage.get returns "null" on IOS Chrome

When I am on desktop browser I can retrieve the key from the hub correctly but when I open the web page on IOS Chrome it returns "null".
It also works on IOS Safari.

The compatibility section says that iOS is not supported.

@fernando-gl Check Notes on Safari 7+ (OSX, iOS) under Compatibility in the readme. Since all browsers on IOS use the Apple provided browser engine, its likely the local storage restrictions apply in this case.

Can you guys recommend any workarounds for iOS Chrome?

@ViieeS yeah I had the same problem and ended up using cookies

authors: NukaPunk ViieeS christian-schulze ferezoz

repo: zendesk/cross-storage


text:
Update the CSS and JS assets

The assets for CSS and JS are a little outdated. Should be updated to newer versions, shouldn't they?

Also "jQuery", "Respond.js" and "HTML5 Shiv" should be removed.

@RalfEggert Any chance you'd be willing to provide the updated versions? :grin:

Looks like #309 will do this for us!

authors: RalfEggert froschdesign weierophinney

repo: zendframework/ZendSkeletonApplication


text:
Zend Data Cache: Add capability for the "lock-on-expire" feature

https://support.zend.com/hc/en-us/articles/203995253-Expired-data-cache-can-be-read-by-subsequent-scripts-for-a-time
Found in #61

Closed by a0f45af into develop (#80)

repo: zendframework/zend-cache


text:
MVC InputFilterPluginManager missing InputFilterAbstractFactory config

InputFilterPluginManager in MVC environment does not create input filter defined in config.
Code to reproduce the issue
$config = [
    'input_filter_specs' => [
        MyInput::class => [
            //...
        ],
    ],
];

$inputFilter = $container->get(InputFilter\InputFilterPluginManager::class)->get(MyInput::class);

Expected results
InputFilterPluginManager creates defined InputFilter
Actual results
Exception thrown

Plugin of type MyInput is invalid; must implement Zend\InputFilter\InputFilterInterface or Zend\InputFilter\InputInterface

Imho this happens because Module.php provide incomplete config.
    public function getConfig()
    {
        $provider = new ConfigProvider();

        return [
            'service_manager' => $provider->getDependencyConfig(),
            'input_filters' => $provider->getInputFilterConfig(), // this line is missing
        ];
    }

@weierophinney do you think it is a bug? Should I create PR?

@vaclavvanik
Please look at:
https://github.com/zendframework/zend-inputfilter/blob/a23e67d41de09bbc325543acb756ba448f182c20/src/Module.php#L30-L42
...and you will find input_filters.

Or do you try to add the entire specification as array in the configuration and not the factories?

Doesn't it say the problem right here:

Plugin of type MyInput is invalid; must implement Zend\InputFilter\InputFilterInterface or Zend\InputFilter\InputInterface

https://github.com/zendframework/zend-inputfilter/blob/a23e67d41de09bbc325543acb756ba448f182c20/src/InputFilterPluginManager.php#L125-L143
your MyInput class does not implement those interfaces or extend other class that does

@Xerkus
I think @vaclavvanik wants to insert the input-filter specification as an array into the configuration and for this the InputFilterAbstractFactory must be added manually as described in the documentation:

Setup
When using zend-mvc version 2 releases, this functionality is disabled by default. To enable it, you must add the Zend\InputFilter\InputFilterAbstractServiceFactory abstract factory to the Zend\InputFilter\InputFilterPluginManager configuration, which is under the input_filters configuration key.

https://docs.zendframework.com/zend-inputfilter/specs/#setup

@froschdesign I see, $autoAddInvokableClass = true masked the problem.

@froschdesign as I wrote above I think, that it is a bug, that in Module.php is missing config line with input_filters. Which causes that InputFilterAbstractFactory is not registered in InputFilterPluginManager.
In ConfigProvider is InputFilterAbstractFactory registered.

@vaclavvanik
Did you see the hint in the documentation?

By the way, this is the same behaviour as in zend-form. The abstract factory FormAbstractServiceFactory is  not registered by default. You must add the factory to your configuration and then you can use the configuration key forms..

In the docs is:
For Expressive when using the configuration manager, and for zend-mvc v3 releases, the functionality is enabled by default, assuming you are using the component installer.
I am using mvc v3 and InputFilterAbstractFactory is not registered... :-/

Just checked, docs are indeed wrong. It is not registered for any mvc version by default.

@vaclavvanik
I'm confused, unfortunately. If you use version v3 then you should have also the last version of zend-inputfilter! And the latest of version of zend-inputfilter contains the InputFilterAbstractFactory!

See: https://github.com/zendframework/zend-inputfilter/releases/tag/release-2.8.2

@vaclavvanik
I will create a pull request when I'm back on my computer and will ping you for testing.

@froschdesign #162 fixed InputFilterAbstractFactory registration in ConfigProvider (Expressive). MVC v3 uses Module and in this class has not 'input_filters' config key in getConfig() which causes that InputFilterAbstractFactory is not registered... (really confusing)

@vaclavvanik

really confusing

Right, because in zend-form is the behaviour different. :confused:

authors: Xerkus froschdesign vaclavvanik

repo: zendframework/zend-inputfilter


text:
mail is going into spam and taking too long to deliver.

Hi,
I have written mail fuctionality like below and the mail is going to spam always and it is taking too long to deliver the mail.
$message = new Message();
        $message->setTo(
            'abc@xyz.com',
            'user name'
        );

        $message->setFrom("admin@xyz.com", "xyz");
        $message->setSubject("subject");
        $message->setReplyTo('admin@xyz.com', 'xyz');

        $message->setBody("sample email");
        $mail = new Mail();
        $mail->send($message);

i tried adding the headers like below but no luck.
$message = new Message();
        $message->setTo(
            'abc@xyz.com',
            'user name'
        );

        $message->getHeaders()->addHeaderLine('MIME-Version', '1.0');
        $message->getHeaders()->addHeaderLine('Content-Type', 'text/html');
        $message->getHeaders()->addHeaderLine('Content-Transfer-Encoding', '8bit');
        $message->getHeaders()->addHeaderLine('X-Mailer:', 'PHP/'.phpversion());

         $message->setFrom("admin@xyz.com", "xyz");
        $message->setSubject("subject");
        $message->setReplyTo('admin@xyz.com', 'xyz');

        $message->setBody("sample email");
        $mail = new Mail();
        $mail->send($message);

Please suggest me what i am doing wrong here and how to fix it to send the email to inbox instead of spam.

The reason messages are marked as spam generally have to do with configuration of the mail transport server via which the email is sent. Based on your above example, you're likely using the default transport, which send via the system "sendmail" binary; this could be sendmail, postfix, ssmtp, or one of a dozen other MTAs depending on what OS you use.
You will need to research what MTA your system uses to send emails, and how to configure it correctly so as to avoid other servers from flagging mail from it as spam. This is a complex subject, and difficult to get right. As such, the better solution is to use known good providers such as Gmail, or commercial transactional email providers that use SMTP.

repo: zendframework/zend-mail


text:
AbstractControllerTestCase's count not compatible with PHP 7.2

This line and similar:
https://github.com/zendframework/zend-test/blob/master/src/PHPUnit/Controller/AbstractControllerTestCase.php#L252
Rely on count, whose behavior has changed in PHP 7.2:
http://php.net/manual/en/migration72.incompatible.php#migration72.incompatible.warn-on-non-countable-types
I think the fix is a simple boolean, taking advantage of short-circuit and behavior:
        $params_exist = ( (null !==$params) && (count($params) > 0));
Will make that a PR if I'm not off the mark.

@bitwombat In case $params can be only array|null and we check count($params) != 0 we can replace if with simply if ($params) and it will give us exactly the same result.
PR is very welcome ! 👍

Fixed in #63

Beat me to it!  Good work.

authors: bitwombat webimpress

repo: zendframework/zend-test


text:
Update Fieldset.php

See: https://github.com/zendframework/zf2/issues/6143#issuecomment-56533308

@jiromm I'd like to include this in 2.4, but:

I need unit tests demonstrating usage of the feature, and these (and existing tests) need to pass
your branch needs to be rebased against current master

If you can do these in the next two weeks, I'll add it to the 2.4 milestone.

@weierophinney That was already fixed in 2.3.4
Thanks.

Closed, per request from author.

authors: jiromm weierophinney


text:
Add some extensions

Merge đi anh :D

Sorry em mấy cái này ít dùng quá, em nên tách riêng ra, đẩy lên pod vd như BadgeButton

Còn mấy acis alert thì răng anh :(

authors: Stjng zendobk

repo: zendobk/SwiftUtils


text:
Consider unifying the terminology collection_id / CONCEPT_RECORD_ID

Currently (0.11.0), the documentation of the CLI uses the term "collection"  as well as the termn "concept" to describe the same thing. It may be better to pick one and stick with it (probably "concept", as that is what zenodo themselves use).
Note

there is also $DRAFT_ID and $LATEST_ID, maybe these should both be renamed to $RECORD_ID for consistency.
this also affects the terms used in zenodraft-autocomplete, maybe id should be record_id and collection_id should be concept_id

Fixed in 298cf28314d9158e4d0cc569801a59c09216be5a, closing this issue

repo: zenodraft/zenodraft


text:
Input focus/click does not copy to clipboard in Firefox.

Minimal example
https://jsfiddle.net/1u3xwnLh/
Expected behaviour
In most browsers, clicking (focusing into) the input field will successfully copy the input value to the clipboard.
Actual behaviour
Instead of copying input value to clipboard, despite hitting the success callback, the clipboard does not actually contain the input value.
Browsers affected
Firefox (45) does not work, but does in most other modern browsers like Chrome.

Hey @zackgilbert, the JSFiddle you shared is incomplete. Can you provide one that reproduces the error you're describing?

I made a small update to your example and everything seems to be working fine: https://jsfiddle.net/1u3xwnLh/1/

I also noticed you also loaded the file from GitHub Raw which doesn't contain the proper MIME types. Try using one of our CDN providers: https://github.com/zenorocha/clipboard.js/wiki/CDN-Providers

Your update (adding the button to click), while totally fixing the issue
(and what I've had to do to fix the issue in my project), defeats the
issue. I'll try to get the jsfiddle working (had it working from a standard
html file).
On Mon, Jun 20, 2016 at 12:17 PM, Zeno Rocha notifications@github.com
wrote:

I made a small update to your example and everything seems to be working
fine: https://jsfiddle.net/1u3xwnLh/1/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zenorocha/clipboard.js/issues/265#issuecomment-227208205,
or mute the thread
https://github.com/notifications/unsubscribe/AAaZjqFf2iOTWmpnWr5eYU-PQsH-mQOOks5qNstDgaJpZM4I56l1
.

Ok, I'll wait for the updated jsfiddle but I don't think it's possible to copy the input value to the clipboard when focusing on the input field.

Man. Well, got the fiddles to work as intended (https://jsfiddle.net/1u3xwnLh/4/), but of course now I can't reproduce the error in Firefox. Not sure why its not working in my app but not in the example. Computers are fun.
I'll just close this for now until I can more accurately reproduce the issue.

Cool! Are you using the script from GitHub Raw locally? Maybe that was the problem.

Nope. I have a locally saved filed for that. Probably just conflicts with other js code.

authors: zackgilbert zenorocha


text:
OpenAPI security

Is your feature request related to a problem? Please describe.
As I'm transitioning from FastAPI to Zenstack, I'm used to have the generated Swagger UI with authentication built-in. For endpoints requiring auth, there is a padlock to identify them. I would love to have the same within Zenstack.
Describe the solution you'd like
Ideally, I would like an automatic addition of an empty security field in the generated schema when the model/operation (endpoint) doesn't require any authentication (e.g. for a model with the @@allow('create', true) attribute).
Describe alternatives you've considered
Add manually a security field in @@openapi.meta attribute.
E.g:
    @@openapi.meta({
        description: 'A user of the pet store',
        create: {
            description: 'I would like to disable Swagger UI authentication for this operation',
            security: []   <--- here
        },
    })

Additional context

When I add this in the generated specification :

It removes the authentication check :

Working example : https://github.com/Azzerty23/petstore-openapi-zenstack

Thanks for the proposal @Azzerty23 !
Yes, security settings are missing right now. Following the specification, I believe we need to add three things:

A way to express security scheme
Maybe just extend the plugin options:
plugin openapi {
    ...
    securityScheme = [
        { myBearer: { type: 'http', scheme: 'bearer' } },
        { myApiKey: { type: 'apiKey', in: 'header', name: 'X-API-KEY' } }
    ]
}

These can just be dumped into the 'components' section in the spec as is.

Generate spec using the scheme
By default, if "securityScheme" is configured, a root-level "security" setting will be added to the spec, including all schemes,
security:
    - myBearer: []
    - myApiKey: []

On the route level, as you suggested, we can statically analyze if an operation is fully open, and if so, generate an override with security: [].

Explicitly customize route-level security
As you suggested, we can allow further customization of security for a route using @@openapi.meta, either setting it to empty or some specific scheme.

Does this generally look good to you?

Yes, that's the perfect solution !

I updated the exemple for reference if that helps: https://github.com/Azzerty23/petstore-openapi-zenstack
And while I'm at it, it would have been nice to be able to customize the tags description: [ModelName] operations by default. Maybe like this:
@@openapi.meta({
        description: 'A user of the pet store',  // to replace User operations
        create: {
            ...
        },
    })

Got it. We'll try to incorporate these in the next release.

Again, sorry for that, it would be nice to be able to deprecate an endpoint.

Yes, we can use this issue to keep collecting missing features around openapi.

Fixed by #340 and #342

repo: zenstackhq/zenstack


text:
Ability to add breadcrumbs via module

Ability to add breadcrumbs via module

@TheMaaarc use $links->teardown();

repo: zephir/luya


text:
Implement Microchip SAM family CAN controller driver

Summary
A number of Microchip (formerly, Atmel) SAM family SoCs include a CAN 2.0A/B and CAN-FD capable host controller peripheral.
In order to take advantage of this, it is necessary to implement a driver for it, that can interface to the existing Zephyr CAN protocol stack.
Target Devices
The following Microchip SAM family devices implement the "Microchip CAN Controller" peripheral:

SAM C21
SAM E51/E54
SAM E70
SAM V70/V71

Note that the following (old generation) Atmel SAM family devices also include a CAN controller peripheral, but this is completely different from the "Microchip CAN Controller" and therefore incompatible; this issue does not propose to support them:

SAM 3X
SAM 4E

Is anyone already working on this by any chance?
cc @benpicco @nandojve @mnkp @aurel32 @karstenkoenig @alexanderwachter

Not that I know off.
Do you plan to work on that driver by any chance?

Not that I know off.
Do you plan to work on that driver by any chance?

Not anytime soon, but it is in my long-term backlog for now.

I'm not working...happy to read that!

FYI: those Microchip (formerly Atmel) products implement Bosch M_CAN IP. The same IP is used by ST (FDCAN) and TI (TCAN4550) so there may be value in having a generic driver.

I just implemented the driver for STM32G4 (FDCAN) #22832

FYI: those Microchip (formerly Atmel) products implement Bosch M_CAN IP. The same IP is used by ST (FDCAN) and TI (TCAN4550) so there may be value in having a generic driver.

@DarrylGamroth Comparing the CAN FD register maps of the SAM and STM32 SoCs, I can see that is indeed the case. Thanks for the very useful info!

I just implemented the driver for STM32G4 (FDCAN) #22832

@alexanderwachter It looks like it would be possible to support the Atmel SAM series just by refactoring your "STM32" CAN FD driver in that PR :)

Not working on any CAN drivers lately :-(
@DarrylGamroth Oh wow thanks for pointing that out! I knew the TCAN4550 standalone controller had a bosch m_can ip but not that it's also what's in the STs FDCAN. The TCAN4550 looked really sweet, but the price of that evaluation board is just a bit much...

@DarrylGamroth thanks for pointing this out!
I‘ll rename the driver then!

I separated the generic part of the can_m module. Some functions need to be implemented for every platform, like all clock related stuff. Unfortunately, the STM FDCAN is not 100% compatible with can_m. It misses some registers, and the size of the message RAM differs. There will be some #ifdefs in the code.

Nice!
Could the message RAM definition be defined in Devicetree similar to the Linux dts then use DT_REG_ADDR_BY_NAME(DT_INST(0, bosch_m_can), message_ram) to get the base and DT_REG_SIZE_BY_NAME(DT_INST(0, bosch_m_can), message_ram) for the size?
I might be wrong with the correct DT macro usage but you get the general idea.

Sure, it is not finished yet. There are some other things, especially in the init, that need to be changed.

I am currently working on a M_CAN driver specialization for the SAMV71 series. My current progress can be found here: https://github.com/Urist-McGit/zephyr/commits/can_mcan_samv71_driver
The work is done for the most part. I am unfortunately stuck on a problem very likely related to the message ram. To summarize the current progress: the driver sends and receives messages on the right pins, with the correct bitrate etc. But unfortunately I receive and send somewhat random messages, sometimes all zero, sometimes random garbage, sometimes the right message. All testing is currently done in normal, not CANFD mode, since I only have a USB2CAN dongle.
I would be very glad to accept some guidance with my problem. I think it would be useful to have the collaboration in a WIP PR or something like that, where I could also lay out the exact way I test the driver, what hardware I test on etc. I am open to any other suggestions though. Thanks in advance!

@Urist-McGit can you write a message in the canbus slack channel? Michael Albrechr, @legoabram and me already solved this problem. It is the cache! You need to invalidate the caches after a write and before a read of the msg_sram

@Urist-McGit The cache invalidation fix for the common M_CAN driver code is in the main tree now. Do you plan on picking up your work on the Atmel SAMV71 M_CAN driver front-end?

After a discussion on the zephyr slack channel, I found out that @legoabram and Michael Albrecht had already implementented a prototype of the specialization before me. They did not mention it anywhere here so I unfortunately redid their work for the most part. Have you tried pinging them? They should be able to help you :)
It has been quite some time since I touched the code, but if I remember correctly, my code works for the samv71 revision B board and support for revision A was in the works. My company has since moved on from the project and I dont have the hardware at hand anymore. I won't be able to finish it, but maybe someone can pick up the work.

incoming...
#41674

authors: DarrylGamroth Urist-McGit alexanderwachter henrikbrixandersen karstenkoenig nandojve stephanosio

repo: zephyrproject-rtos/zephyr


text:
Cannot build samples/net/sockets/echo for cc3220sf_launchxl

Describe the bug
Cannot build samples/net/sockets/echo for cc3220sf_launchxl
To Reproduce
Steps to reproduce the behavior:

build samples/net/sockets/echo for cc3220sf_launchxl

Expected behavior
build should succeed
Impact
Annoyance.
Logs and console output
In file included from /workdir/zephyr/subsys/net/ip/net_context.c:40:
/workdir/zephyr/subsys/net/ip/tcp2.h:120:1: error: useless type name in empty declaration [-Werror]
 void net_tcp_init(void);

Environment (please complete the following information):

OS: Linux
Toolchain: (Zephyr SDK
Latest master

Additional context
It showed up in CI through PR #24873

I have put up a fix in #27476. It is concerning however that CI didn't try to build for platforms using non-native stack when the tcp2 PR was submitted. Is this a gap that can be addressed for the future?

Is this a gap that can be addressed for the future?

This should be addressed for sure. We seem to be missing tests that would validate that non-native stacks can be compiled properly. Would you be able to propose something for this?

Is this a gap that can be addressed for the future?

This should be addressed for sure. We seem to be missing tests that would validate that non-native stacks can be compiled properly. Would you be able to propose something for this?

@jukkar I am not familiar with how CI determines which test to build given a PR, hence my question. Is this documented somewhere?

authors: jukkar tbursztyka vanti


text:
kconfig warning are being ignored by sanitycheck

Sanitycheck should report failure when kconfig has warnings, for example on the regular sanitycheck run we get the following:
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
^C
sky:zephyr(fix_shippable): grep -r  "warning" sanity-out/ | grep select
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
^C
sky:zephyr(fix_shippable): grep -r  "warning" sanity-out/ | grep select
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test_socwatch/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/bbc_microbit/tests/power/power_states/test/config-sanitycheck.log:warning: (UART_NRF5) selects GPIO_NRF5 which has unmet direct dependencies (GPIO && SOC_FAMILY_NRF5 || SOC_FAMILY_NRF5 && GPIO || BOARD_96B_CARBON_NRF51 && UART_NRF5 || BOARD_ARDUINO_101_BLE && UART_NRF5 || BOARD_CURIE_BLE && UART_NRF5 || BOARD_QUARK_SE_C1000_BLE && UART_NRF5)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_nios2/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_riscv32/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/quark_se_c1000_devboard/samples/net/wpan_serial/test_x86/build.log:warning: (NET_L2_BT && NET_L2_IEEE802154) selects NET_6LO which has unmet direct dependencies (NETWORKING && !NET_L2_RAW_CHANNEL && NET_IPV6)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/drivers/build_all/test_build_ethernet/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_subscriber/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_subscriber/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_subscriber/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_publisher/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_publisher/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/lib/mqtt_publisher/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/socket/udp/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/socket/udp/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/tests/net/socket/udp/test/build.log:warning: (SLIP && BT_H4 && BT_H5 && CONSOLE_HANDLER && UART_PIPE && NET_SLIP_TAP) selects UART_INTERRUPT_DRIVEN which has unmet direct dependencies (SERIAL && SERIAL_SUPPORT_INTERRUPT || BOARD_MPS2_AN385 && SERIAL || BOARD_V2M_BEETLE && SERIAL || BOARD_TINYTILE && USB && USB_UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/shell/shell/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getchar/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/echo/test/config-sanitycheck.log:warning: (CONSOLE_GETCHAR) selects UART_CONSOLE_DEBUG_SERVER_HOOKS which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)
sanity-out/qemu_xtensa/samples/subsys/console/getline/test/config-sanitycheck.log:warning: (CONSOLE_SHELL && CONSOLE_GETCHAR && CONSOLE_GETLINE) selects CONSOLE_HANDLER which has unmet direct dependencies (CONSOLE && UART_CONSOLE)

@ulfalizer this is a rather old bug, I get some of it was already addressed, anything remaining we should take care of?

addressed in many Kconfig enhancements recently.


text:
zperf: Add support to stop/start download

If by mistake we issue zperf download with wrong port, then we cannot re-issue the command as server is already started. We need a command to stop the server and start with proper port. @rlubos

https://github.com/zephyrproject-rtos/zephyr/pull/52684/ solves this.


text:
Intel CAVS 15/18/25: tests/subsys/input/api/ crashing board

Describe the bug
After calling tests/subsys/input/api/ all other tests failing. For run other tests need to restart board.
67ccf6d this commit add tests that failing on cavs
To Reproduce
twister -W --hardware-map /home/ztest/cavs/cavs.map
--device-testing
-T tests/subsys/input/api/
-x=CONFIG_BOOT_DELAY=500
-v --no-skipped-report

Expected behavior
Tests pass.
Logs and console output
INFO    - 1/2 intel_adsp_cavs25         tests/subsys/input/api/subsys.input.api.synchronous  ERROR Device issue (Flash error?) (device 0.587s)
INFO    - 2/2 intel_adsp_cavs25         tests/subsys/input/api/subsys.input.api.thread      ERROR Device issue (Flash error?) (device 0.589s)

Environment (please complete the following information):
OS: Linux
Toolchain: Zephyr SDK
Latest main (419dda3)

Hey tried to run this on a board:
$ west build -p -b nrf52dk_nrf52832 tests/subsys/input/api
$ west flash

seems to run fine. The test should only require the iterable sections stuff to work, is that platform doing something odd with the linker?

Could you try to see if this fixes the problem by any chance? https://github.com/zephyrproject-rtos/zephyr/pull/55967

@majunkier  is this still an issue?

tests/subsys/input/api/subsys.input.api.synchronous - it's working.
tests/subsys/input/api/input.api.thread - building is fine, when we execute :
START - test_sequence_thread report: 0 report: 1 input_cb_unfiltered: 0 report: 2 input_cb_filtered: 0 report: 3 ... report: 15 Assertion failed at WEST_TOPDIR/zephyr/tests/subsys/input/api/src/main.c:75: input_api_test_sequence_thread: (ret not equal to -ENOMSG) ret: 0 FAIL - test_sequence_thread in 0.002 seconds )
Toolchain: Zephyr 0.16.0
OS: Ubuntu 20.04.6 LTS

Hi @majunkier any update on this?

more readable output of the failure:
*** Booting Zephyr OS build zephyr-v3.3.0-4093-g5781478fd5c4 ***
Running TESTSUITE input_api
===================================================================
START - test_sequence_thread
report: 0
report: 1
input_cb_unfiltered: 0
report: 2
input_cb_filtered: 0
report: 3
report: 4
report: 5
report: 6
report: 7
report: 8
report: 9
report: 10
report: 11
report: 12
report: 13
report: 14
report: 15
Assertion failed at WEST_TOPDIR/zephyr/tests/subsys/input/api/src/main.c:75: input_api_test_sequence_thread: (ret not equal to -ENOMSG)
ret: 0
FAIL - test_sequence_thread in 0.002 seconds
===================================================================
TESTSUITE input_api failed.
------ TESTSUITE SUMMARY START ------
SUITE FAIL -   0.00% [input_api]: pass = 0, fail = 1, skip = 0, total = 1 duration = 0.002 seconds
- FAIL - [input_api.test_sequence_thread] duration = 0.002 seconds
------ TESTSUITE SUMMARY END ------
===================================================================
RunID: 4453d3d0b465075ce77101694eb64bf0
PROJECT EXECUTION FAILED

so, it it is not crashing, is it? This is just a test failing.

test passes if we just use one core (i.e. CONFIG_SMP=n)

authors: AmberHibberd fabiobaltieri majunkier nashif


text:
sockets: offloaded: modem not connecting

ESP-AT modem fails to send data
After downloading the latest updates the ESP-AT modem no longer send data over IP4 network.
The device connects to the network and appears to have address assigned but is unable to connect to other services; eg SNTP or MQTT.

ESP32-AT Modem
Have attempted to find change that is effecting connection, have been rolling but not found  specific commit?
...

To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=board_xyz
make
See error

Expected behavior
A clear and concise description of what you expected to happen.
Impact
Showstopper
Logs and console output
The target stopped in MemManage exception state.
Reason: Unknown at 0x00000000.
For more information about analyzing faults on Cortex-M, refer to:
https://wiki.segger.com/Cortex-M_Fault.
Environment (please complete the following information):

OS:  Windows
CMake version: 3.25.0-rc2
west version "1.0.0"
Zephyr version: 3.4.0-rc1 (build: v3.4.0-rc1-50-g147d4067e6de)

Question: why is this listed under 'Platform ESP32' if most likely it will be used with other chips than ESP32?
ESP-AT is actually an ESP-IDF application.

Question: why is this listed under 'Platform ESP32' if most likely it will be used with other chips than ESP32?
ESP-AT is actually an ESP-IDF application.

You're right nothing to do with ESP32 specifically it's a general networking issue. I'm frustrated with the lack of hardware testing.

It should in fact be before the recv not after:
SET_ERRNO(net_context_connect(ctx, addr, addrlen, cb, timeout,
ctx->user_data));
SET_ERRNO(net_context_recv(ctx, zsock_received_cb, K_NO_WAIT,
ctx->user_data));

No, it should not. This was a conscious change, to prevent race condition between connect/recv - see https://github.com/zephyrproject-rtos/zephyr/issues/58084 for the details about the problem.
Native IP stack allows to register recv callback before connection - offloaded implementations should comply with this behavior.

Seems to be solved in #59857

Fixed.

authors: RomainPelletant WilliamGFish carlescufi rftafas rlubos


text:
twister code coverage report base directory not setting

Describe the bug
passing in --coverage-basedir ../XXX/src/
leads to

Traceback (most recent call last):
  File "/opt/nordic/ncs/v2.4.0/zephyr/./scripts/twister", line 201, in <module>
    ret = main(options)
  File "/opt/nordic/ncs/v2.4.0/zephyr/scripts/pylib/twister/twisterlib/twister_main.py", line 212, in main
    run_coverage(tplan, options)
  File "/opt/nordic/ncs/v2.4.0/zephyr/scripts/pylib/twister/twisterlib/coverage.py", line 278, in run_coverage
    coverage_tool.generate(options.outdir)
  File "/opt/nordic/ncs/v2.4.0/zephyr/scripts/pylib/twister/twisterlib/coverage.py", line 101, in generate
    ret = self._generate(outdir, coveragelog)
  File "/opt/nordic/ncs/v2.4.0/zephyr/scripts/pylib/twister/twisterlib/coverage.py", line 208, in _generate
    subprocess.call(["gcovr", "-r", self.base_dir, "--gcov-executable",
  File "/usr/local/Cellar/python@3.10/3.10.13/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py", line 345, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/local/Cellar/python@3.10/3.10.13/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/local/Cellar/python@3.10/3.10.13/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py", line 1796, in _execute_child
    self.pid = _posixsubprocess.fork_exec(
TypeError: expected str, bytes or os.PathLike object, not NoneType

Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? qemu_cortex_m3
What have you tried to diagnose or workaround this issue? I edited coverage.py to check if self.base_dir == None and it is none though even i set it in the python script or pass it through calling twister
To Reproduce
Steps to reproduce the behavior:
./scripts/twister --coverage --coverage-basedir ../XXX/src/ -p qemu_cortex_m3  -c --coverage-tool gcovr  -T ../XXX/tests

Expected behavior
code coverage report should generate
Environment (please complete the following information):

OS: Mac
Toolchain zephyr sdk 0.16.3
Commit SHA or Version used

Additional context
Add any other context that could be relevant to your issue, such as pin setting,
target configuration, ...

not able to reproduce

does  --coverage-basedir need to be in quotes?

seems like passing --gcov-tool gcov does the trick, but coverage report is blank

base directory still not setting. showing as '.'

Sorry, I still can't reproduce this, please provide exact steps which lead to this error
i9:zephyr(topic/twister/predicate): ./scripts/twister --coverage --coverage-basedir tests/kernel/threads/thread_init/src/ -p qemu_cortex_m3  -c --coverage-tool gcovr  -T tests/kernel/threads/thread_init/
Deleting output directory /home/nashif/zephyrproject/zephyr/twister-out
INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.5.0-4936-gc84df7ded81a
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report /home/nashif/zephyrproject/zephyr/twister-out/testplan.json
INFO    - JOBS: 20
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - Total complete:    1/   1  100%  skipped:    0, failed:    0, error:    0
INFO    - 1 test scenarios (1 test instances) selected, 0 configurations skipped (0 by static filter, 0 at runtime).
INFO    - 1 of 1 test configurations passed (100.00%), 0 failed, 0 errored, 0 skipped with 0 warnings in 10.17 seconds
INFO    - In total 3 test cases were executed, 1 skipped on 1 out of total 675 platforms (0.15%)
INFO    - 1 test configurations executed on platforms, 0 test configurations were only built.
INFO    - Generating coverage files...
INFO    - Using gcov tool: /home/nashif/bin/zephyr-sdk-0.16.4/x86_64-zephyr-elf/bin/x86_64-zephyr-elf-gcov
INFO    - HTML report generated: /home/nashif/zephyrproject/zephyr/twister-out/coverage/index.html
INFO    - Saving reports...
INFO    - Writing JSON report /home/nashif/zephyrproject/zephyr/twister-out/twister.json
INFO    - Writing xunit report /home/nashif/zephyrproject/zephyr/twister-out/twister.xml...
INFO    - Writing xunit report /home/nashif/zephyrproject/zephyr/twister-out/twister_report.xml...
INFO    - Run completed

reopen with how you get the issue with the upstream tree please.

authors: carriegong nashif


text:
tests: posix: common: separate into smaller testsuites

Is your enhancement proposal related to a problem? Please describe.
The posix.common testsuite contains a lot of mostly unrelated testsuites. As a result, the code size is large, but mostly the data size is extremely large.
It would require less variation from default settings, and would reduce ram requirements to split that testsuite into smaller groups of more closely related testsuites.
Describe the solution you'd like
The obvious way to group related testsuites is by Option Group.
E.g.

POSIX_RW_LOCKS
POSIX_SEMAPHORES
POSIX_SIGNALS
POSIX_SINGLE_PROCESS
POSIX_SPIN_LOCKS
POSIX_THREADS_BASE
POSIX_THREADS_EXT
POSIX_TIMERS
XSI_SYSTEM_LOGGING

and potentially others.
testcase.yaml permutations can be designed to enable or disable features specific to one Option Group, like TSS, TSA, TSH (see Codes).
Additionally, such a grouping would theoretically improve bug attribution capabilities; if an error was traced (either via stacktrace or bug description) to a certain posix function, there would be a 1:1 correspondance to an Option Group, so typically, only that testsuite would need to be executed.
Describe alternatives you've considered
The way the testsuite has been designed historically.
Additional context
This came up in the context of #79443 but it was already thought of as a nice-to-have.

Can I take a stab at this one please, if it's ok could it be assigned to me?

@zacck - please do!

@cfriedt  I'm new to Zephyr and while I have looked at the links and docs supplied above I believe I need an example to start breaking this down would you be able to assist with some information that would help here?

@zacck If you have just started with Zephyr, I think you will need to be familiarized with Twister and the different KV pairs in the testcase.yaml, see Test Runner (Twister)
@cfriedt do you expect the zephyr/tests/posix/common test to be broken down into multiple tests? Because while we can break the test into multiple sub-tests within the tests/posix/common/testcase.yaml, the existing testcase.yaml would be pretty big when we want to make sure that each sub-test are tested with different configurations (different C libs, spin validation, tls, ...) that we have: (<number of option group sub-test> x <number of configurations>)

@cfriedt do you expect the zephyr/tests/posix/common test to be broken down into multiple tests?

They should be broken down into  separate app directories.
That's mainly because the single application is getting quite large, and the configuration requirements are not always clear.
It would be better if the prj.conf and memory requirements were minimal.

It could be good to split this into smaller commits / a task list.

@cfriedt  yeah breaking this down would be awesome, I am going to do that once I have a solid plan ahead which should be around tomorrow 16th OCT 24.

@cfriedt  yeah breaking this down would be awesome, I am going to do that once I have a solid plan ahead which should be around tomorrow 16th OCT 24.

Cool - it can be separate PRs, which should simplify things. I'll do pthteads, because it is likely the most confusing.

authors: cfriedt ycsin zacck