[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[STINNER Victor]

STINNER Victor  added the comment:

AMD64 FreeBSD CURRENT Shared 3.x is back to green. I close the issue.

https://buildbot.python.org/all/#/builders/168/builds/1356 likely failed 
because kkobs upgrade the FreeBSD CURRENT VM while the buildbot job was running 
(inconsistency between *running* libc and kernel, I guess).

--
resolution:  -> fixed
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

Possibly, but unlikely as the system had been freshly installed and rebooted 
before the worker was restarted.

The worker processes, however, had not been stopped prior to, or during the 
upgrade, so it's possible that the worker had an inconsistent build state that 
had resumed, or used before-upgrade information, code or objects during tests

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Could this be that the libc was outdated?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

Ran rebuild (in the BB UI) on that failed build (#1356), and test_os now passes:

0:22:52 load avg: 8.38 [339/419] test_os passed

Victor independently logged into the host and ran a from scratch build/test and 
test_os passes for him too (verifying my from scratch test results)

Only thing I can think of is a cached/inconsistent BB build environment after 
the host FreeBSD update, that cleared itself after the first build

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[STINNER Victor]

STINNER Victor  added the comment:

> https://buildbot.python.org/all/#/builders/168/builds/1356

Just to confirm: test_os was run twice and was killed twice by signal 12.

0:00:04 load avg: 3.45 [  8/419/1] test_os crashed (Exit code -12)
...
Re-running failed tests in verbose mode
Re-running test_os in verbose mode
...
test_copy_file_range (test.test_os.FileTests) ... *** Signal 12

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

Hmm... a test checkout of master/default on the host in question has 
test_copy_file_range{_*} passing:

[user@CURRENT-amd64:/usr/home/user/repos/cpython] ./python -m test -vvv test_os 
|grep range
...
test_copy_file_range (test.test_os.FileTests) ... ok
test_copy_file_range_invalid_values (test.test_os.FileTests) ... ok
test_copy_file_range_offset (test.test_os.FileTests) ... ok
...
Ran 280 tests in 2.503s

OK (skipped=45)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[STINNER Victor]

STINNER Victor  added the comment:

It would be better if the FreeBSD kernel would return ENOSYS error code rather 
than killing the process with SIGSYS :-)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

See Also: #26826

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

Possibly related:

https://reviews.freebsd.org/D20584 - Add a linux compatible copy_file_range(2) 
syscall

https://lists.freebsd.org/pipermail/freebsd-current/2019-July/073747.html

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Kubilay Kocak]

Kubilay Kocak  added the comment:

@Pablo Upgrade to latest CURRENT revision a few hours ago. Some system software 
is still updating. I'll push a rebuild on BB once complete. Stand by :)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
nosy: +koobs

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

@koobs, did you changed recently the buildbot?

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[Pablo Galindo Salgado]

Pablo Galindo Salgado  added the comment:

Oh, FreeBSD, what have you done now.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37959] test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT buildbot

[STINNER Victor]

New submission from STINNER Victor :

https://buildbot.python.org/all/#/builders/168/builds/1356

test_nop (test.test_os.FSEncodingTests) ... ok
test_access (test.test_os.FileTests) ... ok
test_closerange (test.test_os.FileTests) ... ok
test_copy_file_range (test.test_os.FileTests) ... *** Signal 12
Stop.
make: stopped in /usr/home/buildbot/python/3.x.koobs-freebsd-current/build
program finished with exit code 1
elapsedTime=1562.592656

man signal says:

"12SIGSYS   create core imagenon-existent system call invoked"

I bet that the "non-existent system call" is: copy_file_range. The configure 
script says:

"checking for copy_file_range... yes"


Se also bpo-37711: "regrtest: re-run failed tests in subprocesses".

--
components: Tests
messages: 350609
nosy: pablogsal, vstinner
priority: normal
severity: normal
status: open
title: test_os.test_copy_file_range() killed by SIGSYS (12) on FreeBSD CURRENT 
buildbot
versions: Python 3.8, Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com