Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build 2195 for main with status FAILURE - npcap_test.go - Operation did not complete successfully because the file contains a virus or potentially unwanted software. #37574

Closed
elasticmachine opened this issue Jan 7, 2024 · 5 comments
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team Team:Security-Linux Platform Linux Platform Team in Security Solution

Comments

@elasticmachine
Copy link
Collaborator

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2024-01-07T19:51:52.928+0000

  • Duration: 136 min 9 sec

Test stats 🧪

Test Results
Failed 2
Passed 28178
Skipped 1972
Total 30152

Test errors 2

Expand to view the tests failures

Build&Test / packetbeat-windows-2016-windows-2016 / TestNpcap/Install – github.com/elastic/beats/v7/packetbeat/npcap
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestNpcap/Install
        npcap_test.go:61: unexpected error running installer to default location with compat=false: npcap: failed to start Npcap installer: fork/exec C:\Users\jenkins\AppData\Local\Temp\TestNpcap1332116326\001\installer.exe: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
        npcap_test.go:63: installing Npcap DLL
        npcap_test.go:63: replace existing version: WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
        npcap_test.go:61: unexpected error running installer to C:\some\other\location with compat=false: npcap: failed to start Npcap installer: fork/exec C:\Users\jenkins\AppData\Local\Temp\TestNpcap1332116326\001\installer.exe: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
        npcap_test.go:63: installing Npcap DLL
        npcap_test.go:63: replace existing version: WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
        npcap_test.go:61: unexpected error running installer to default location with compat=true: npcap: failed to start Npcap installer: fork/exec C:\Users\jenkins\AppData\Local\Temp\TestNpcap1332116326\001\installer.exe: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
        npcap_test.go:63: installing Npcap DLL
        npcap_test.go:63: replace existing version: WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
        npcap_test.go:61: unexpected error running installer to C:\some\other\location with compat=true: npcap: failed to start Npcap installer: fork/exec C:\Users\jenkins\AppData\Local\Temp\TestNpcap1332116326\001\installer.exe: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
        npcap_test.go:63: installing Npcap DLL
        npcap_test.go:63: replace existing version: WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
    --- FAIL: TestNpcap/Install (1.60s)
     
    

Build&Test / packetbeat-windows-2016-windows-2016 / TestNpcap – github.com/elastic/beats/v7/packetbeat/npcap
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestNpcap
    --- FAIL: TestNpcap (3.81s)
     
    

Steps errors 4

Expand to view the steps failures

packetbeat-windows-2016-windows-2016 - mage build unitTest
  • Took 3 min 14 sec . View more details here
  • Description: mage build unitTest
packetbeat-windows-2016-windows-2016 - mage build unitTest
  • Took 1 min 46 sec . View more details here
  • Description: mage build unitTest
packetbeat-windows-2016-windows-2016 - mage build unitTest
  • Took 1 min 30 sec . View more details here
  • Description: mage build unitTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error "hudson.AbortException: script returned exit code 1"

@elasticmachine elasticmachine added automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jan 7, 2024
@pierrehilbert pierrehilbert changed the title Build 2195 for main with status FAILURE Build 2195 for main with status FAILURE - npcap_test.go - Operation did not complete successfully because the file contains a virus or potentially unwanted software. Jan 8, 2024
@elasticmachine
Copy link
Collaborator Author

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@pierrehilbert
Copy link
Collaborator

@narph / @ebeahan could we have someone to have a look here please?

@efd6
Copy link
Contributor

efd6 commented Jan 15, 2024

@pierrehilbert This is https://go.dev/doc/faq#virus. We do need to have these tests and they necessarily involve shelling out to another executable in order to mimic the process involved in installing the Npcap DLL during Packetbeat execution startup. This issue should be reported to MS to get them to improve their handling of Go executables (see FAQ entry above). We could rewrite the mocks in something else, since any executable that performs the checks that the mocks do will suffice (src ref: https://github.com/elastic/beats/tree/main/packetbeat/npcap/testdata). If someone can provide either PS or bat equivalents, I can help integrate them into the tests.

@ebeahan ebeahan added Team:Security-Linux Platform Linux Platform Team in Security Solution and removed Team:Security-External Integrations labels Jan 31, 2024
@elasticmachine
Copy link
Collaborator Author

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

@jlind23
Copy link
Collaborator

jlind23 commented Oct 11, 2024

Closing as outdated.

@jlind23 jlind23 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team Team:Security-Linux Platform Linux Platform Team in Security Solution
Projects
None yet
Development

No branches or pull requests

5 participants