DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 502] False negative for Windows compilation
Date: Mon, 06 Jul 2020 16:49:10 +0000	[thread overview]
Message-ID: <bug-502-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=502

            Bug ID: 502
           Summary: False negative for Windows compilation
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: UNH infra
          Assignee: ci@dpdk.org
          Reporter: david.marchand@redhat.com
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

link is failing for a series of patches of mine but this is not properly
reported.

I caught it by compiling for mingw myself, then I went in the dashboard and
checked the log file.

The series:
https://patchwork.dpdk.org/project/dpdk/list/?series=10816

The report:
https://lab.dpdk.org/results/dashboard/patchsets/11867/
https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/425c608ab9554151b7a1e47fa70fe698/log_upload_file/2020/7/dpdk_0fc601af3a72_11867_2020-07-06_14-51-02_NA.zip


Looking into log.txt:

[29/76] Compiling C object
lib/76b5a35@@rte_eal@sta/librte_eal_windows_eal.c.obj.
../lib/librte_eal/windows/eal.c:219:1: warning: no previous prototype for
'trace_mem_per_thread_free' [-Wmissing-prototypes]
 trace_mem_per_thread_free(void)
 ^~~~~~~~~~~~~~~~~~~~~~~~~
[30/76] Compiling C object
lib/76b5a35@@rte_eal@sta/librte_eal_common_malloc_heap.c.obj.


[59/76] Linking target lib/librte_eal-0.200.3.dll.
FAILED: lib/librte_eal-0.200.3.dll 
gcc @lib/librte_eal-0.200.3.dll.rsp
lib/76b5a35@@rte_eal@sta/librte_eal_common_eal_common_thread.c.obj:eal_common_thread.c:(.text.experimental+0x1b):
undefined reference to `rte_mp_disable'
collect2.exe: error: ld returned 1 exit status
[60/76] Linking static target lib/librte_pci.a.
[61/76] Generating rte_bus_pci_mingw with a custom command.
[62/76] Compiling C object
drivers/a715181@@rte_bus_pci@sta/bus_pci_pci_params.c.obj.
[63/76] Compiling C object
drivers/a715181@@rte_bus_pci@sta/bus_pci_pci_common.c.obj.
[64/76] Compiling C object
drivers/a715181@@rte_bus_pci@sha/bus_pci_pci_common.c.obj.
ninja: build stopped: subcommand failed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-07-06 16:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-502-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).