Searched refs:POSIX (Results 1 – 25 of 529) sorted by relevance
12345678910>>...22
1 # This set of tests is run only with the 8-bit library. It tests the POSIX3 # not be run with JIT (which is not available for the POSIX interface).11 ** Ignored with POSIX interface: auto_callout15 ** Ignored with POSIX interface: find_limits20 ** Ignored with POSIX interface: partial_hard50 No match: POSIX code 17: match failed61 No match: POSIX code 17: match failed70 Failed: POSIX code 15: bad back reference at offset 6 75 No match: POSIX code 17: match failed98 No match: POSIX code 17: match failed[all …]
1 # This set of tests is run only with the 8-bit library. It tests the POSIX4 # POSIX interface).15 No match: POSIX code 17: match failed
1 # This set of tests is run only with the 8-bit library. It tests the POSIX4 # POSIX interface).
5 This document lists the items that will be tested for POSIX signals.16 the POSIX Test Suite creators are listed below.20 Tag - tag that applies to the function in the POSIX spec21 Complexity - POSIX test suite owners' intuitions at complexity of the function23 Recommended? - set to "NO" if the POSIX spec recomments using *other*25 Priority - POSIX test suite owners' intuitions at priorities of these67 - Any additional information listed in the POSIX System Interfaces document69 - Any functional requirements listed in the POSIX Base Definitions document.70 (ex. Testing that each signal listed in the POSIX Base Definitions
30 ref - For reference document (generally a POSIX specification)38 XBD# - POSIX Base Definitions document39 XSH# - POSIX System Interfaces document40 XCU# - POSIX Shell and Utilities document41 XRAT# - POSIX Rationale document58 the official POSIX Specs, then simply put in62 pt:<POSIXtag> - If the assertion is taken from a POSIX specification and there63 is a POSIX tag (pt) associated with it, the additional string65 POSIX tag.
10 Functional tests test the behavior of functional areas of the POSIX*11 specification. They do not relate directly to lines in the POSIX19 taxed by excessively using the functional areas in the POSIX specification20 or monitoring how the functional areas in the POSIX specification behave30 Each of these are further subdivided into POSIX area (Timers, Semaphores,33 Within the functional/<POSIX area> directory, you should create the71 - create directories corresponding to POSIX chapters (see .1-1990 or75 * POSIX (R) is a registered trademark of the IEEE
2 POSIX Test Test Suites.5 POSIX Test Test Suites.15 - Code under test that is targeted* for the POSIX Test Suite reporting.29 4. If the code under test is compatible with another POSIX version (e.g.,45 *targeted implementation = an implementation which POSIX Test Suite will47 **Process for tracing a test case to previous POSIX specifications not
10 Conformance tests test conformance to the POSIX* specification. They test23 definitions/ - This directory contains tests for each *.h file in the POSIX27 POSIX spec. Tests are taken from the System Interfaces document.62 Tests which the POSIX spec uses the words "may" or "implementation-defined"90 * POSIX (R) is a registered trademark of the IEEE
4 Every area of the POSIX spec that has tests written for it should be tracked by16 Completion of POSIX Function Conformance Tests18 There should be one line for each POSIX function included in this area of the19 POSIX spec. The tests for these functions are currently found in the47 the POSIX spec such as "Clocks & Timers (TMR)".
4 Releases of the POSIX Test Suite will happen at defined (TBD) intervals.29 M = Major release. The initial scope of the POSIX Test Suite corresponds30 to M=1. That includes tests for all initially scoped POSIX areas (signals,
32 dnl Check if getpwnam_r and getpwuid_r are POSIX.1 compatible33 dnl POSIX draft version returns 'struct passwd *' (used on Solaris)34 dnl NOTE: getpwent_r is not POSIX so we always use getpwent39 # The prototype for the POSIX version is:47 …TPW_R_POSIX], 1, [Define to 1 if you have getpwnam_r and getpwuid_r that are POSIX.1 compatible.]) 55 # The prototype for the POSIX draft version is:63 …R_DRAFT], 1, [Define to 1 if you have getpwnam_r and getpwuid_r that are draft POSIX.1 versions.])
1 Build Notes for POSIX Test Suite5 The POSIX Test Suite should be able to be run independently of any given6 OS, so the OS-specific steps for configuring the POSIX Test Suite to run36 POSIX message queues have been available in FreeBSD since 6.x. Please add:56 POSIX semaphores have been available in FreeBSD since 5.x. Please add:64 Notes for running POSIX Test Suite against Linux implementations of65 POSIX functionality. (Note: If these implementations are accepted into81 If LinuxThreads is the default POSIX thread implementation,86 If NPTL is the default POSIX thread implementation, add '-lpthread' to LDLIBS.108 POSIX Message Queue (Wronski/Benedyczak's implementation) has been[all …]
3 1. Open POSIX* Test Suite Overview13 1. Open POSIX* Test Suite Overview16 The POSIX Test Suite is an open source test suite with the goal of23 POSIX operating system.35 - Enable assertion based traceability for conformance testing of POSIX37 statements about our coverage of the POSIX specification.74 HOWTO_DefinitionsTest - ideas behind testing POSIX header files120 The Open POSIX Test Suite is not affiliated with the IEEE or The Open Group.122 * POSIX (R) is a registered trademark of the IEEE
13 …S is helping kernel, library and application developers and OSDs on their POSIX related work. Plea…19 …4-29 cvs pull (NPTL enabled) and linux-2.6.5-mm6 kernel.It is noted that "POSIX Message Queues" ha…22 POSIX Test Suite 1.4.0 includes more pthread conformance test cases. Now we have test cases coverin…25 POSIX Test Suite test pass results available for [CVS pull 3-04-04, Kernel 2.6.1, libc-2004-02-15 a…28 POSIX Test Suite test pass results available for [CVS pull 2-20-04, Kernel 2.6.1, libc-2004-02-01 a…
7 No worries! Here's a quick doc to help you around POSIX** Test Suite.45 POSIX* Test Suite project page: http://posixtest.sf.net57 HOWTO_DefinitionsTest - ideas behind testing POSIX header files62 ** POSIX (R) is a registered trademark of the IEEE
45 # undef POSIX47 # define POSIX macro49 # undef POSIX64 #if defined(POSIX)212 #if defined(POSIX)
5 area defined by POSIX.8 funtional area (somewhat like POSIX options), or by APIs.18 the work of adding Robust Mutex to POSIX is still on going.
64 # Test whether 'malloc' is POSIX compliant (sets errno to ENOMEM when it72 [Define if the 'malloc' function is POSIX compliant.])78 # Test whether malloc, realloc, calloc are POSIX compliant,82 AC_CACHE_CHECK([whether malloc, realloc, calloc are POSIX compliant],87 dnl all Unix implementations of the function are POSIX compliant.
19 AC_MSG_CHECKING([for POSIX sh \$() command substitution])29 * POSIX sh \$() command substition does not work with this shell.38 * Run this configure script using a better (i.e. POSIX compliant) shell.
2 :mod:`termios` --- POSIX style tty control7 :synopsis: POSIX style tty control.11 pair: POSIX; I/O control14 This module provides an interface to the POSIX calls for tty I/O control. For a16 page. It is only available for those Unix versions that support POSIX
35 in POSIX mode by default, but uses non-POSIX mode if the *posix* argument is65 compatibility mode. When operating in POSIX mode, :class:`~shlex.shlex`66 will try to be as close as possible to the POSIX shell parsing rules.88 string (``''``) in non-POSIX mode, and ``None`` in POSIX mode).185 Characters that will be considered as escape. This will be only used in POSIX201 :attr:`escape`. This is only used in POSIX mode, and includes just ``'"'`` by261 (``''``), in non-POSIX mode, and to ``None`` in POSIX mode.271 When operating in non-POSIX mode, :class:`~shlex.shlex` will try to obey to the294 When operating in POSIX mode, :class:`~shlex.shlex` will try to obey to the
2 Attempt to use a user-defined rwlock as a POSIX rwlock: rwlock 0x.........8 Attempt to use a POSIX rwlock as a user-defined rwlock: rwlock 0x.........
42 POSIX, enumerator52 Type type = Type::POSIX;
463 POSIX, enumerator471 HandleType::POSIX,472 HandleType::POSIX,485 if (type == HandleType::POSIX) { in TEST_F()491 EXPECT_EQ(PlatformHandle::Type::POSIX, scoped_handle.get().type); in TEST_F()535 if (type == HandleType::POSIX) { in DEFINE_TEST_CLIENT_TEST_WITH_PIPE()537 EXPECT_EQ(PlatformHandle::Type::POSIX, scoped_handle.get().type); in DEFINE_TEST_CLIENT_TEST_WITH_PIPE()
17 Build and run the tests for POSIX area specified by the 3 letter tag18 in the POSIX spec