| Scenario | Bug Id | Description | Failures |
|---|
| math_cexp_scenario | bug516_2(cpow) | The cpow(x, y) family of functions shall compute the complex power function x^y, with a branch cut for the first parameter along the negative real axis. If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpow(x, y) return (-1) + (near)(1e-16) * i. This result is too far from (-1). If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpow(x, y) return (-1) - (near)(1e-16) * i. This result is too far from (-1). If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1). If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1). |
failure 1
| 3 more...
failure 2
failure 3
failure 4
|
| math_exp_scenario | bug512_1(log1p) | The log1p(x) family of functions shall compute log(1.0 + x). According to LSB, the functions shall fail if argument is less than -1 and set error code to EDOM. But on the target machine the functions set error code EOK instead of EDOM if the argument is less than -1. |
failure 5
| 8 more...
failure 7
failure 8
failure 9
failure 11
failure 12
failure 13
failure 15
failure 16
|
| math_exp_scenario | bug512_2(log1p) | The log1p(x) family of functions shall compute log(1.0 + x). According to LSB, the functions shall fail if argument equals to -1 and set error code to ERANGE. But on the target machine the functions set error code EOK instead of ERANGE in this case. |
failure 6
| 2 more...
failure 10
failure 14
|
| math_gamma_scenario | bug516(gamma) | According to LSB, gamma(x) family of functions shall return either HUGE_VAL or NaN if x is a non-positive integer. But on the target machine the functions don't return HUGE_VAL or NaN if the argument is not positive. |
failure 26
| 2 more...
failure 27
failure 28
|
| math_gamma_scenario | bug516(lgamma) | According to LSB, lgamma(x) family of functions shall return +HUGE_VAL if x is a non-positive integer. But on the target machine the functions don't return +HUGE_VAL if the argument is not positive. |
failure 17
| 2 more...
failure 19
failure 21
|
| math_gamma_scenario | bug516(lgamma_r) | According to LSB, lgamma_r(x) family of functions shall return +HUGE_VAL if x is a non-positive integer. But on the target machine the functions don't return +HUGE_VAL if the argument is not positive. |
failure 18
| 2 more...
failure 20
failure 22
|
| math_gamma_scenario | bug516(tgamma) | The tgamma(x) family of functions shall compute the mathematical gamma() function of x. According to LSB, if x is a negative integer NaN shall be returned. But on the target machine, the functions don't return NaN if the argument is negative. |
failure 23
| 2 more...
failure 24
failure 25
|
| math_rand_scenario | bug511_2(initstate) | The initstate() function handles restarting of random-number generator. According to LSB, upon successful completion, initstate() shall return a pointer to the previous state array; otherwise, a null pointer shall be returned. But on the target machine the function returns neither a pointer to the previous state, nor NULL pointer. |
failure 29
| 5 more...
failure 30
failure 31
failure 32
failure 33
failure 34
|
| math_real_fdim_overflow_scenario | bug512(fdim) | The fdim(x, y) family of functions shall determine the positive difference between their arguments. According to LSB, if the result overflows then fdim() shall fail and shall set ERANGE error code. But on the target machine, the functions set error code EOK instead of ERANGE when overflow occurs. |
failure 35
| 2 more...
failure 36
failure 37
|
| math_real_scenario | bug512(llrint) | The llrint() family of functions shall round their argument to the nearest integer value, rounding according to the current rounding direction. According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an integer then the functions shall set EDOM error code. But on the target machine, the functions set error code EOK instead of EDOM in these cases. |
failure 38
| 17 more...
failure 42
failure 46
failure 50
failure 54
failure 58
failure 62
failure 66
failure 70
failure 74
failure 78
failure 82
failure 86
failure 90
failure 94
failure 98
failure 102
failure 106
|
| math_real_scenario | bug512(llround) | The llround() family of functions shall round their argument to the nearest integer value, rounding halfway cases away from zero, regardless of the current rounding direction. According to LSB, if argument is NaN, +Inf -Inf, or the correct value is not representable as an integer then the functions shall set EDOM error code. But on the target machine, the functions set error code EOK instead of EDOM in these cases. |
failure 39
| 17 more...
failure 43
failure 47
failure 51
failure 55
failure 59
failure 63
failure 67
failure 71
failure 75
failure 79
failure 83
failure 87
failure 91
failure 95
failure 99
failure 103
failure 107
|
| math_real_scenario | bug512(lrint) | The lrint() family of functions shall round their argument to the nearest integer value, rounding according to the current rounding direction. According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an integer then the functions shall set EDOM error code. But on the target machine, the functions set error code EOK instead of EDOM in these cases. |
failure 40
| 17 more...
failure 44
failure 48
failure 52
failure 56
failure 60
failure 64
failure 68
failure 72
failure 76
failure 80
failure 84
failure 88
failure 92
failure 96
failure 100
failure 104
failure 108
|
| math_real_scenario | bug512(lround) | The lround() family of functions shall round their argument to the nearest integer value, rounding halfway cases away from zero, regardless of the current rounding direction. According to LSB, if argument is NaN, +Inf, -Inf, or the correct value is not representable as an integer then the functions shall set EDOM error code. But on the target machine, the functions set error code EOK instead of EDOM in these cases. |
failure 41
| 17 more...
failure 45
failure 49
failure 53
failure 57
failure 61
failure 65
failure 69
failure 73
failure 77
failure 81
failure 85
failure 89
failure 93
failure 97
failure 101
failure 105
failure 109
|
| math_real_scenario | bug512(remquo) | The remquo(x, y, quo) family of functions shall return the floating-point remainder r = x-ny when y is non-zero und update quo variable. According to LSB, if the x argument is +Inf, -Inf, or the y argument is +0 or -0 and the other argument is non-NaN. then error code shall be set to EDOM. But on the target machine, the functions set error code EOK instead of EDOM in these cases. |
failure 110
| 5 more...
failure 111
failure 112
failure 113
failure 114
failure 115
|
| process_meta_user_scenario | bug102(setuid) | The setuid() function sets the real user ID, effective user ID, and the saved set-user-ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real user ID or the saved set-user-ID, setuid() shall set the effective user ID to this value. But on the target machine setuid() fails when trying to set the effective user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 138
| 1 more...
failure 139
|
| process_meta_user_scenario | bug103(setreuid) | The setreuid() function shall set the real and effective user IDs of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the saved set-user-ID, setreuid() shall always be successful to set the real user ID to this value. But on the target machine setreuid() fails when trying to set the real user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 136
| 1 more...
failure 137
|
| process_meta_user_scenario | bug104(setgid) | The setgid() function sets the real group ID, effective group ID, and the saved set-group-ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real group ID or the saved set-group-ID, setgid() shall set the effective group ID to this value. But on the target machine setgid() fails when trying to set the effective group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 120
| 1 more...
failure 121
|
| process_meta_user_scenario | bug106(setregid) | The setregid() function shall set the real and effective group IDs of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the saved set-group-ID, setregid() shall always be successful to set the real group ID to this value. But on the target machine setregid() fails when trying to set the real group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 122
| 13 more...
failure 123
failure 124
failure 125
failure 126
failure 127
failure 128
failure 129
failure 130
failure 131
failure 132
failure 133
failure 134
failure 135
|
| process_meta_user_scenario | bug82(seteuid) | The seteuid() function sets the effective user ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real user ID or the saved set-user-ID, or if the process has appropriate privileges, seteuid() shall set the effective user ID to this value. But on the target machine seteuid() fails when trying to set effective user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 118
| 1 more...
failure 119
|
| process_meta_user_scenario | bug83(setegid) | The setegid() function sets the effective group ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real group ID or the saved set-group-ID, or if the process has appropriate privileges, setegid() shall set the effective group ID to this value. But on the target machine setegid() fails when trying to set effective group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 116
| 1 more...
failure 117
|
| process_resources_ulimit_priviledged_scenario | bug794(ulimit) | It is a test suite deficiency that will be fixed soon. |
failure 140
|
| process_resources_ulimit_unpriviledged_scenario | bug794(ulimit) | It is a test suite deficiency that will be fixed soon. |
failure 141
|
| signal_sigstr_basic_scenario | bug685(strsignal) | If sig is not a valid signal number, strsignal shall return either a pointer either a pointer to the string "unknown signal", or a null pointer. SYNOPSIS ... char * strsignal(int sig); ... RETURN VALUE If sig is a valid signal number, strsignal() shall return a pointer to the appropriate description string. Otherwise, strsignal() shall return either a pointer to the string "unknown signal", or a null pointer. ... But in real, strsignal return "Unknown signal", a space, and a number sig. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0685. |
failure 143
|
| time_conversion_scenario | bug379(asctime_r) | The asctime_r() function converts date and time to a string and returns it. According to LSB, if the function is unsuccessful, it should return NULL, But on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. |
failure 145
| 1 more...
failure 146
|
| time_conversion_scenario | bug380(asctime) | The asctime() function converts date and time to a string and returns it. According to LSB, if the function is unsuccessful, it should return NULL, But on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. |
failure 144
|
| time_time_scenario | bug377(stime) | The stime() function shall set the system's idea of the time and date to the time referenced by function argument. According to LSB, if this argument is NULL then stime() shall set error code to EINVAL. But it sets error code to EFAULT instead of EINVAL. The bug was fixed in libc 2.4. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0377. |
failure 147
| 8 more...
failure 148
failure 149
failure 150
failure 151
failure 152
failure 153
failure 154
failure 155
|
| util_assert_errx_scenario | bug488(errx) | The errx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 156
| 8 more...
failure 157
failure 158
failure 159
failure 160
failure 161
failure 162
failure 163
failure 164
|
| util_assert_verrx_scenario | bug489(verrx) | The verrx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 165
| 8 more...
failure 166
failure 167
failure 168
failure 169
failure 170
failure 171
failure 172
failure 173
|
| util_assert_warnx_scenario | bug486(warnx) | The warnx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 174
| 199 more...
failure 175
failure 176
failure 177
failure 178
failure 179
failure 180
failure 181
failure 182
failure 183
failure 184
failure 185
failure 186
failure 187
failure 188
failure 189
failure 190
failure 191
failure 192
failure 193
failure 194
failure 195
failure 196
failure 197
failure 198
failure 199
failure 200
failure 201
failure 202
failure 203
failure 204
failure 205
failure 206
failure 207
failure 208
failure 209
failure 210
failure 211
failure 212
failure 213
failure 214
failure 215
failure 216
failure 217
failure 218
failure 219
failure 220
failure 221
failure 222
failure 223
failure 224
failure 225
failure 226
failure 227
failure 228
failure 229
failure 230
failure 231
failure 232
failure 233
failure 234
failure 235
failure 236
failure 237
failure 238
failure 239
failure 240
failure 241
failure 242
failure 243
failure 244
failure 245
failure 246
failure 247
failure 248
failure 249
failure 250
failure 251
failure 252
failure 253
failure 254
failure 255
failure 256
failure 257
failure 258
failure 259
failure 260
failure 261
failure 262
failure 263
failure 264
failure 265
failure 266
failure 267
failure 268
failure 269
failure 270
failure 271
failure 272
failure 273
failure 274
failure 275
failure 276
failure 277
failure 278
failure 279
failure 280
failure 281
failure 282
failure 283
failure 284
failure 285
failure 286
failure 287
failure 288
failure 289
failure 290
failure 291
failure 292
failure 293
failure 294
failure 295
failure 296
failure 297
failure 298
failure 299
failure 300
failure 301
failure 302
failure 303
failure 304
failure 305
failure 306
failure 307
failure 308
failure 309
failure 310
failure 311
failure 312
failure 313
failure 314
failure 315
failure 316
failure 317
failure 318
failure 319
failure 320
failure 321
failure 322
failure 323
failure 324
failure 325
failure 326
failure 327
failure 328
failure 329
failure 330
failure 331
failure 332
failure 333
failure 334
failure 335
failure 336
failure 337
failure 338
failure 339
failure 340
failure 341
failure 342
failure 343
failure 344
failure 345
failure 346
failure 347
failure 348
failure 349
failure 350
failure 351
failure 352
failure 353
failure 354
failure 355
failure 356
failure 357
failure 358
failure 359
failure 360
failure 361
failure 362
failure 363
failure 364
failure 365
failure 366
failure 367
failure 368
failure 369
failure 370
failure 371
failure 372
failure 373
|
| util_float_scenario | bug518_2(logb) | The logb() function shall compute the exponent of the integral part of logarithm of its argument as a signed floating-point value. According to LSB, if this argument is 0, ERANGE error shall be set in errno. But on the target machine this function sets error code EOK instead of ERANGE. |
failure 375
| 5 more...
failure 376
failure 377
failure 378
failure 379
failure 380
|
| util_float_scenario | bug518_3(nextafter) | The nextafter(x, y) family of functions functions shall compute the next representable floating-point value following x in the direction of y. According to LSB, if the correct value is subnormal or underflows then ERANGE error code shall be set. But on the target machine the function sets error code EOK instead of ERANGE. |
failure 381
| 29 more...
failure 382
failure 383
failure 384
failure 385
failure 386
failure 387
failure 388
failure 389
failure 390
failure 391
failure 392
failure 393
failure 394
failure 395
failure 396
failure 397
failure 398
failure 399
failure 400
failure 401
failure 402
failure 403
failure 404
failure 405
failure 406
failure 407
failure 408
failure 409
failure 410
|
| util_float_scenario | bug518_4(nexttoward) | The nexttoward(x, y) family of functions functions shall compute the next representable floating-point value following x in the direction of y. According to LSB, if the correct value is subnormal or underflows then ERANGE error code shall be set. But on the target machine the function sets error code EOK instead of ERANGE. |
failure 411
| 29 more...
failure 412
failure 413
failure 414
failure 415
failure 416
failure 417
failure 418
failure 419
failure 420
failure 421
failure 422
failure 423
failure 424
failure 425
failure 426
failure 427
failure 428
failure 429
failure 430
failure 431
failure 432
failure 433
failure 434
failure 435
failure 436
failure 437
failure 438
failure 439
failure 440
|
| util_float_scenario | bug518_5(scalb) | The scalb() family of functions shall compute x*r^n, where r is the radix of the machine's floating-point arithmetic. According to LSB, the functions shall set EDOM error code when x is zero and n is +Inf, or x is Inf and n is -Inf and ERANGE when overflow occurs. But the functions sets error code EOK in these cases. |
failure 441
| 11 more...
failure 442
failure 443
failure 444
failure 445
failure 446
failure 447
failure 448
failure 449
failure 450
failure 451
failure 452
|
| util_float_scenario | bug518_6(scalbln) | The scalbln() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing FLT_RADIX^n explicitly. According to LSB, the functions shall set ERANGE error code when overflow occurs. But on the target machine the function sets error code EOK instead of ERANGE in this case. |
failure 453
| 8 more...
failure 454
failure 455
failure 456
failure 457
failure 458
failure 459
failure 460
failure 461
|
| util_float_scenario | bug518_7(scalbn) | The scalbn() family of functions shall compute x * FLT_RADIX^n efficiently, not normally by computing FLT_RADIX^n explicitly. According to LSB, the functions shall set ERANGE error code when overflow occurs. But on the target machine the function sets error code EOK instead of ERANGE in this case. |
failure 462
| 8 more...
failure 463
failure 464
failure 465
failure 466
failure 467
failure 468
failure 469
failure 470
|
| util_format_wprintf_swprintf_scenario | bug505(swprintf) | According to LSB, on error swprintf() function shall return -1 and set errno global variable. On the target machine, swprintf() function returns -1, but doesn't set error code in errno global variable. This contradicts LSB standard for this function. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. |
failure 471
|
| util_format_wprintf_vswprintf_scenario | bug506(vswprintf) | According to LSB, on error vswprintf() function shall return -1 and set errno global variable. On the target machine, vswprintf() function returns -1, but doesn't set error code in errno global variable. This contradicts LSB standard for this function. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. |
failure 472
|